Posts 

I know it is not so nice to complain and bash a project when you don't contribute to it. And yes until now, I did not contributed to the KDE4 desktop as I wished. I compiled it regularly and used the libraries, but did not run the KDE4 desktop or KDE4 version of the applications except KDevelop and Quanta. But as 4.0 is approaching, I decided that it is time to test, use, report bugs and even make fixes to it. I use KDE since a long time (~7 years), I think I always compiled from source, and for several years I compiled from CVS/Subversion regularly. I wasn't afraid to use the alpha/beta/whatever version as my daily desktop. But with KDE4 somehow I feel lost. I tried a few days ago to start a KDE4 session. After getting through some issues that the libraries were not found unless LD_LIBRARY_PATH is modified (and knotify even with this setup has problem to find libkaudiodevicelist.so), I finally got it running. Well, it looks nice at first. So what to do there? I can start the KDE4 applications from the Run Command dialogbox. This dialog is a nice improvement over the old version, especially the autocompletion is handy. In my version the menu was still missing, which isn't nice, but I don't care that much. What I care more is the speed, or to be exact, the lack of it. I blamed first the debug version of the libraries and the desktop, so I did a complete fresh build without debug information (a sidenote: my KDE3 is compiled WITH debug info and works fast enough). Sadly, it isn't faster. An example: right click on the desktop, and until the menu is shown, 3-4 seconds can pass. During this time Plasma and XOrg are heavily using the CPU. Moving around a window makes again ~58% CPU load (by kwin). Moving the mouse over the taskbar gives me 60% CPU usage by plasma AND 50% CPU usage by XOrg. This slowness if everywhere on the desktop. I click somewhere and it takes some seconds until it reacts. The "natural" reaction is to click again, which makes things worse. What is the reason of this slowness, I don't know. But I am worried about it, because I have a fairy decent computer here, everything is fast except my video card: AMD Opteron 180 Dual Core (2.4Ghz), 2GB Dual Channel RAM, 7200RPM SATA HDD, Nvidia FX5500 card (with the binary drivers). The card isn't the state of the art one, but should be more than enough for desktop usage. I tried compiz with it, and it works OK. I can see the reaction lag with compiz as well (compared to the KDE3 version of kwin, which is lightning fast), but it is still quite usable. I tried to remove kwin and use another window manager. This made at least the window operations faster, but the desktop was still slow. That's about the speed. Now about the usability side: I have no idea if what I tried is implemented at all or not, if there are plans to do them for the final release or not, but certainly I can say that as it is now, it is close to be unusable. There is the panel on the bottom with the taskbar and the clock. The taskbar let's say works, but I couldn't figure out what really a left/right click on an empty area of the taskbar does. It minimizes/restores the running applications, but I don't see the logic. I also don't know how to move around the taskbar on the panel. I don't know how to move the panel. It is possible to add new applets to the desktop, but I don't know how to move those applets to a panel. Moving them around on the screen is terribly slow. There is also an Unknown Applet on my panel which "could not be created". I have no idea what it is or how it appeared there. I also saw some bugs, like black boxes on top of windows appearing when you move a window over an applet, but this kind of issues are just simple bugs, acceptable at this stage of the development. Unfortunately this experience can have only one outcome: I cannot use KDE4 as my daily desktop. Not even as a testing desktop. So the solution is to test only the libraries and the applications. Luckily it is pretty easy to have a setup where you can run KDE4 applications under KDE3. Well, the first and one of the most important applications is Konqueror. I'm writing this blog from Konqueror4. Altough I feel a slowness here as well (when navigating through the menus, for example), this isn't a big issue, it is usable. I saw some rendering bugs, an ugly infinite loop when loading a certain page, but I saw similar issues with the old Konqui as well. There is a problem with the editor area where I write the blog text (home bring to the beginning of the text, not the beginning of the line, mouse scrolling does not work) and the closing buttons on the tabs do not work, but again, in beta stage these are "normal" bugs. For the applications the solution is to report the bugs or try to fix them. :) I will happily report them. Read More

Kubuntu 7.10 was released today. Much jubilation and celebrations all around. I think we can safely say we're the first distro to include KDE 3.5.8 and KDE 4 Beta 3. Read More

What a coincidence today happened. In the morning I used KDEPrint's 'poster' frontend to create a "poor man's poster" in A1 size from 4 A3 printouts. In the afternoon, a lady mailed me, asking why her KDE print dialog on Solaris didn't show the poster dialog, while her husband's openSUSE KDE did show it. Read More

Hacking on KDE 4 is fun. There is so much goodness in the development platform. This begins with all the nice stuff Qt brings, little things like the addictive foreach, the beautiful API, or the amazing performance, and big things like the rich-text system Scribe or the model-view framework Interview. One of my favorites are the dockable toolbars. I could move them around all day and watch the smooth sliding in effects. Read More

Preparations for Gutsy's release continue apace. #ubuntu-release-party is going a bit nuts. Many thanks to those who have helped test CD candidates, davmor2 gets the prize for most testing this round I think. Read More

... is what Parley started doing lately. Pretending to have some very basic limited intelligence. Extending that to some more still very limited and basic intelligence will be easy now that the groundwork has been done. And I hope it's getting better at pretending then ;) Read More

As some of you may have known, KHTML in trunk has support for the <canvas> element. Unfortunately, it was based on some very old and borderline insane Apple code, which meant that except for the nice graphics bits written by Zack, it was all wrong, and when it worked, did so mostly by accident. Read More

This week is KDE 4 hack week for me and some other colleagues at SUSE. We have thrown in some of our ITO time (that's a certain fraction of our work time we can flexibly spend on innovative projects which aren't necessarily related to our day-to-day jobs) to help making KDE 4 ready for release before the total release freeze comes into effect on Friday. Some of the KDAB folks were attracted by this idea as well and will also chime in and do some serious KDE 4 hacking. So hopefully we will have a well-working KDE PIM in KDE 4. It certainly will be a fun week! Read More

As Cornelius blogged, this week the KDE people at SUSE are spending our hard-won innovation time on polishing KDE 4. The vast majority of our new development time is now allotted to KDE 4, so to make sure that our efforts go in the right direction and to coordinate them with the work the rest of the community, we'd like to announce an inaugural openSUSE KDE IRC meeting happening tomorrow, Wednesday 17 October, in #opensuse-kde on FreeNode, at 1800 CEST. That's 1700 BST, or 1200 EST or the same time of day as the openSUSE project meeting if you exist in the shadowy planes of hacker-time. The agenda so far is to discuss how to make KDE openSUSE 10.3++ the best ever, how you can contribute via the Build Service, and how to use KDE 4 already. Read More

Some of you may remember my blog post "How to simulate a slow network (after all, QT_FLUSH_PAINT=1 doesn't work with Qt3)" from nearly two years ago. After all, I'm still getting a private mail or two every half year inquiring about it. That blog post did describe in some detail how you can use a command like Read More