"Carla Schroder wrote an editorial piece this week on Linux Today entitled Editor's Note: What is User-friendly, Really?. "In it, Carla claims to be "90% satisfied" with KDE3 and "60% satisfied" with KDE SC 4.3. Why? "KDE 4 sacrifices customizability and efficiency for glitz.
Now everyone is gone, I'm the lone wolf here in San Diego. Still working on a couple of loose ends, including the final article (which is next on my todo, after I've done this blog and done some stuff for Qualcomm as we promised during our meeting).
I knew the esp the first to articles were long and booooring - al talks, little fun. This time I'll do better, I promise.
You can expect an epic tale of hackers risking their lifes to get to the university while the streets were flooded, only to arrive in a place threatened by two dragons and a few too-cute babies. And more flooding. If it wasn't for the good care of Jeff we'd have been without beer, snacks and wifi...
So expect an article tomorrow around this time on the dot.
Of course, Solaris has been a primary target for OpenOffice for ages, so KOffice is a little late to the game on this particular platform. But I guess that’s my fault, since I’m one of the packagers for KDE4 on Solaris, and I hadn’t gotten around to it yet. So this weekend I spent a little under two hours hammering together a specfile (RPM-style) for koffice and getting the whole darn thing to build. Screenshot of KWord in action as proof. I tried KPresenter as well, but that crashed on changing the list style, so I didn’t think that was a ...read more...
I haven’t written a proper tech article since before I (re-)started this blog, so I thought it was high time. Besides, I’ve been wanting to write this post ever since I read some articles on Google’s Chrome OS, around the time right after my old blog vaporized. So there’s a couple of buzzwords to hopefully sucker you into clicking the ‘more’ button and actually reading the article – It’s about Google’s upcoming Chrome OS and it’s implications for the web, the desktop and the browser, as well as why desktop evolution can take an alternative path, exemplified by KDE’s budding Project Silk movement.
I’d really like to link to some of the posts I read on Chrome OS as they were really interesting, but I read them around half a year ago and I sadly couldn’t find them anymore. Anyway I’m going to start by doing a brief exploration of what Google likely wants to achieve with Chrome OS. Most of you probably already have an idea of what Chrome OS will be like:
So if you worked with some version control systems for a bit, you’ve probably heard of a concept called branches. It is quite a simple concept: you can perform several development processes in parallel without them interfering with each other. Most projects use branches for experimental features that could set hell loose and for backporting bugfixes to older releases. Subversion and CVS people usually dislike branches, because they involve lots of uninteresting and painful work that they don’t want to do. That is easily explained by the way branches are implemented there.
As you might know, branches in SVN are implemented in a very interesting fashion. They are not, in fact, implemented at all. SVN branch is just a folder, which is created when a branch is started. If you want to merge it back, you need to remember the revision number, when you created the branch, and use that magical number in a complex “svn merge” command. But still, SVN project history remains a straight line.
Well folks, Camp KDE is all wrapped up. Hopefully Jeff finds time to upload some videos real-soon-now (TM) for those of you that could not make it to the talks.
Anyway, just wanted to mention a few things that I thought were great and things that could have been better. It's sort of important for me to pay attention to this, since I kept telling people I'd try to host Camp KDE next year in Toronto.
So, the awesome things: Jeff did a great job, considering he almost singlehandedly put this thing together. Jeff is my hero. The training was the highlight of the week for me, and I'm so happy that he arranged that for us. The group that was there brought a positive attitude to the whole event (should I expect anything less from the KDE community, honestly?), even though the weather sucked. I got to pick a few people's brains and feel a little more comfortable with C++ as a result of the week. Whee!
it’s hard to believe it’s over already… Thursday evening, everyone who was left had a proper dinner together in an actual restaurant. :) It took them a while to make a table long enough for us. Oh, and wade was there – I forgot to mention he made a surprise appearance wednesday evening. :) Friday most people were gone – but me, jos and frank were still around. We discussed kde and the cloud and things over a delicious lunch (there’s a little place called.. Rick’s? Just one block from the hostel) and (eventually) made our way downtown for some shopping. :) i didn’t really mean to buy anything, but I found a few nice things that were on sale. That evening we ate at Rick’s again, and james joined us, and we ran into little william and his family :) jos and frank had fun learning to eat crab legs; I’m sure there are photos somewhere. Back at the hostel the power was back on downstairs, but off again upstairs. We talked to ...read more...
After Nokia purchsed Trolltech last year, doubts arose about how Nokia would handle the dual licensing model of Qt, the advanced cross-platform toolkit which lies at the base of the KDE Free software desktop.
In it, Carla claims to be "90% satisfied" with KDE3 and "60% satisfied" with KDE SC 4.3. Why? "KDE 4 sacrifices customizability and efficiency for glitz. [...] There is a trend to dumb Linux down in a fruitless attempt to appeal to Jane and Joe Sixpack. Which is wasted effort, because in doing so computer-savvy users are being ignored and frustrated, and Jane and Joe Sixpack don't care anyway."
What's interesting about this for me is that Gwenview's redesign wasn't to appeal to Jane and Joe Sixpack. It was to take a powerful app with a rather clumsy UI and turn it into a powerful app with a slick UI. Now, I don't know about you, but I like tools that fit my hand when I use them; using tools that fit the tentacles of an octopus might be interesting ...read more...
Today, a package was delivered to my house containing an item which I’ve been missing for a long time, years in fact. A second battery for my laptop. I’ve been working on various power management solutions in KDE in the past years, and they all had one problem: I couldn’t really test if everything worked with more than one battery plugged in. In that area, I always depended on others to help me debugging and fixing problems, not the ideal workflow, so some bugs have gone uncaught in the past.
Not anymore! Now I’ve got this second battery in the optical drive slot of my dear Thinkpad T60, I can immediately identify problems with displaying the charge rate of more than one battery, and I did. One bug displaying a wrongly formatted translation string in the battery’s popup has already bitten the dust, within one hour of delivery of the second battery, I committed a patch to the 4.4 branch and trunk of KDE SC. As far as I can see, ...read more...
I just commited an update to the Gdb Qt pretty printers, they work now for Qt 4.6. (I didn't test 4.5, but most won't work anymore I guess)
The printers need to poke around in private members, that's why they depend on a specific Qt version.
They are still located in the kdevelop svn, instructions on how to enable them see here. (the svn url changed as kdevelop is now in extragear)
Unfortunately my merge request for Qt that would add them directly to Qt got rejected, so it is a bit difficult to support multiple Qt versions - for now 4.6 only is supported. Perhaps in future more people will discover this feature in Gdb and they will get added... You know where to find them.
Last week I was in Berlin, and besides getting some work done, picking up some espresso beans and meeting old friends, I also received a wonderful German cold bug. From my boss Karsten, presumably. We all know that parents of small children are plague-bearers, but his kids are apparently in a different pathogen group than mine — as a result of which I’ve been pretty much laid-up all week with sniffles, headaches and the like. I can focus for about 2 hours at a time, after which it’s back to bed. I don’t recall colds hanging around this tenaciously or virulently before; the only good thing I can say about it is that 2 hours is enough time to write blog entries on random legal and licensing topics (and also technical KDE things, but that’s coming up).
The list of "Key Quests for 2010" was alphabetical. It was a sensible ordering and it prevented me from having to prioritize them in some linear fashion that could never be definitive anyways: all the points are important, though often in different ways, for different reasons and even with different key audiences. So, alphabetical ordering it was! This meant that WebKit was going to be the last topic, and now here we are. (Honestly, I'm glad I'll be able to get back to more "stream of consciousness, spur of the moment" blogging! :)
The topic of WebKit is not the easiest one. It's had its share of controversy and until recently QtWebKit wasn't really, at least in my opinion, quite up to scratch for production usage outside of fairly simple use cases. With Qt 4.6, which came with improvements across the board and new API for things like DOM access, it has turned a very important corner and makes the topic of "What does KDE want to do with QtWebKit?" ever more pressing.
User interfaces are the last great Linux problem. What really makes Linux user-friendly-- is it limited options and loads of eye candy? What about functionality, and depths of riches to explore? I've been using KDE 4.3 all day every day for a month now, and I have mixed feelings.
When I was contemplating the topics for my "Key Quests for 2010" list in December 2009, even before I had decided whether I'd share the list with others, the issue of KDE's web footprint came up pretty quickly in the process. It is very often our first impression for people who would like to get involved or who would like to find out more about us. It is where people go before they know how to (or if they want to) communicate with us directly. It also has been something we've really struggled with improving.
Nobody really "owns" the web sites, which makes it a bit trickier (as it can devolve into a free-for-all), and we haven't historically been very good at integrating web designers and developers into the workflow without a bunch of C++ geeks piling on. ;) So, it's been a struggle.
It would be great if we were able to give the web sites completely over to a web development team and rely on them to consult the people who have been around KDE the ...read more...
I have been really lazy to write anything here for quite some time now. I enjoyed the simple life away from the blogocube (it’s actually a dodecahedron, but blogododecahedron is a mouthful) but now I’m back.
I’ve realized that I’ve made more commits to Kickoff since Tokamak 3 (mostly related to krunner integration) than to Lancelot, which is just plain wrong. So, I decided to change that and do something I was planning for quite some time now – a huge refactoring.
The first thing I noticed is that the Puck (Plasma UI compiler used in Lancelot) modules are rather outdated and reflect Lancelot widgets from the old liblancelot and not the new liblancelot2 so it got updated. It was rather cool to see that despite that, Puck still worked and didn’t break the build.
Puck will eventually (read: when Qt Declarative UI becomes stable and Plasma-integrated) be abandoned and left to rust, but ATM it seems a not so near future.
Jonathan Corbet из Linux Weekly News опубликовал статистику патчей, принятых в ядро Linux между 24 декабря 2008 и 10 января 2010: от версии 2.6.28 до версии 2.6.32 — всего 2.8 миллиона строк кода за период (в среднем, 7000 строк в день), порядка 55 тысяч крупных изменений.
Во главе списка, конечно, RedHat — его доля 12%, далее следует Intel с 8%, IBM и Novell — по 6% и Oracle — 3%. Однако, 18% вклада в новый код ядра не имеет связи с какими-то корпорациями, и 7% нового кода не было классифицировано.
Также стоит отметить, что есть компании, которые не были включены в список, но при этом используют и изменяют технологии на базе Linux, не обогощая общественное достояние (к примеру, Google).
In my previous post I showed off a new approach to detecting troubled projects based upon both developers and the artifacts they are responsible for. As we saw in KMail, there was one contributor who was responsible for the majority of the commits, bu not the artifacts. Modularity in the community gave indication that the code is probably nicely modularised, too.
OK, so is KMail special or do we see this more often. Is trouble, normal? Since I was asked about KOffice, I have now repeated these visualisations for KWord.
So, KWord is strongly dependent upon one particular contributor for the commits. Don’t forget there could be many reasons for this (mostly process related), or it might be indicative of a project in trouble. If we look at the artifact modularisation…
… we see that while the community/artifacts appear to be nicely modularised, the principle contributor is not only making the most commits, ...read more...
We haven't posted a post with podcast notes in quite a while, but we're still going strong. If you aren't familiar with our curious tradition, every Wednesday at noon California time a gang of motley VMware admins, gurus, newbies, troublemakers, jokers, kibitzers, and seekers of knowledge gather around a virtual campfire and record a podcast. All are welcome, and a good time is had by all. You can listen to the podcast via the widget on the right, the mp3, or via iTunes. If you ask those in the know, however, they'll tell you that showing up live is much more fun, because the chat is usually going strong before, during, and after the show. We get about 30-50 people live every week, and if you dial in (via POTS or VOIP) you can ask a question or give a comment at any time, because ...read more...
Hi everyone. Just 4 quick things I wanted to point out to the community regarding various Promo activities. If you’re one of those people lurking about Planet KDE who’s been itching to start contributing, here are some ideas for you to get started.
First, not too long ago I made a YouTube video about a use case for Marble, one of our KDE Education applications. This has now been posted on the official KDE YouTube channel. Go check it out! And make sure you check out all the other cool videos there while you’re at it. James Cain (our recent Camp KDE “Be Free” award winner) has done a fabulous job reworking the look of the site and accumulating some new videos lately. You can even subscribe so that you get an alert when new videos are posted. Very cool stuff. However we can always use more videos. I created mine simply using Kdenlive in less than an evening. If you think you’d be interested in giving this ...read more...
so last night went well; after the qt training we stayed at the uni. it’s still stormy out there, and apparently we missed a flash flood. I got several bugs fixed and backported (screensaver stuff again), so I’m happy. :)
anyways, wednesday was the normal qt training; today is embedded training. not embedded like the n900, but embedded as in framebuffers and really tiny devices. we all got livecds with the embedded environment, and spent some time getting that set up (several people don’t have cd drives, others want to run it in a vm, etc…). Then we got to actually run an app in the virtual framebuffer and make a hello-world app (without instructions… but it was basically just a new qt app + the embedded project settings).
after lunch the training continued… and… holy crap it’s 7pm. where’d the time go? and it’s the last day, too…. :(
we’re off to a restaurant for dinner now (at least I think we are; it’s been fast food all week). most people are leaving tomorrow; I’m leaving ...read more...
Multiple vulnerabilities were found in kdelibs found which can be exploited by malicious people to 1) make XMLHttpRequests to remote sites 2) cause denial of service ------------------------------------------------------------------------ Pardus Linux Security Advisory 2010-11 email@example.com ...
В 2008-с году Китай ворвался в топ самых быстрых компьютеров в мире, заняв сразу 11-е место. Супер компьютер Dawning 5000a работает на процессорах AMD а операционная система Windows HPC Server. Сейчас планы китайских ученых еще более амбициозны. Новый супер компьютер Dawning 6000 будет построен на процессорах полностью разработанных в Китае Loongson 3 с архитектурой MIPS. Операционная система Linux. Предполагается производительность супер компьютера достигнет петафлопсного уровня.
So what is going on in the konv land? Version 1.2.2 will be released soon, which is great enough but I have something even better for you. Post 1.2.2 we will have DCC Whiteboard! (imagine the 20th century/fox music: “dadadadaaaa…dadadadaa”) A basic “multiplayer paint” which implements dcc whiteboard, specs can be found here. It won’t be in 1.2.2 as it is not ready but, as you can see, it basically works :)
Now to the show-stoppers, the whiteboard specs lack many things to keep the drawing 100% in sync. For example it is impossible to keep the size of the image in sync, it has no real size, but how can you save an image without a size? I ended up resizing the image as needed but with a limit to 2048×2048 pixel, for the sake of all broken gfx drivers. And now imagine one side uses floodfill with a different image size than the other, the result will be different. I *could* implement a extra resize ...read more...
Of course not. At the turn of the 20th century everybody was saying that photography killed painting. And later cinema killed theatre, and television killed cinema. The last technological revolution, the digital one, killed the business of the record companies. And this time, it may be finally true...
MIDI is about making music, and making music is about musical instruments. After all, a business that remains still alive is the musical instruments industry. Not all the musical instruments sold around the world are bought by professional musicians. Most of the market are aficionados and hobbyists. Everybody would like, in one or another point of the life, to become a musician, or learn to play a musical instrument. Well, this is the place of the MIDI software in the desktop ecosystem. It is not about passively listening music, but using tools to inspect, interact, learn, modify, understand music. That may explain how VMPK had more than 5000 downloads from SourceForge last month. Even when it is not able to play songs by itself!