KDE Developers and Usability Folks on Cooperation

sultanoslack writes "Over at NewsForge a story just popped up on the usability experts from OpenUsability and some of the issues on working with KDE development teams, specifically the KDE PIM team. There's some interesting content on the different working styles of the two groups as well as a little bit on some of the improvements that were part of the recent KDE 3.4 release."

Comments

Great!

[Anonymous Coward]

Just wanted to share my excitement about this.

I think it's great that the KDE Devs have no problem acknowledging that KDE could even be better if it focuses more on usability.

Don't get me wrong, KDE is far from the usability nightmare some folks want to make it, however it certainly has issues and it certainly can use some polish. (As can probably any other environment out there for that matter)

Now getting usability expert on board to solve these issues sure is the right way and if KDE 3.4 is anything to judge from, there are great things to come for KDE.

Rock on!

How about working together with GNOME?

[mpontes]

Am I the only one who hates the way the whole GNU/Linux community is split up? There are already few apps (with a GUI) compared to Windows applications, if the community keeps splitting up, Linux will never pose a real threat to Windows in the desktop world. Your average PC user doesn't want to have to deal with a different look-and-feel every time he boots an application, so he'll be stuck with the apps that were developed for his desktop environment. Heck, I stick with Kopete because Gaim looks so damned ugly under KDE.

Sure, I have a lot of choices under GNU/Linux. Too bad that for every choice I make I become more and more limited.

Re:How about working together with GNOME?

[molnarcs]

Am I the only one who hates the way the whole GNU/Linux community is split up?

Unfortunately, no, you are not alone with this opinion. What you fail to see is that there developers are not droids. In other words, you can't think of them as a pool that you can shape into whatever form you like. You can't tell a GNOME developer to work for KDE because the latter has a better chance of success (as it seems now). The GNOME developer works on GNOME because that is what he wants to work on. And this is not necessarily a bad thing: competition between the two major desktop environments might be considered as a driving force behind the rapid growth of linux DEs actually.

For instance GNOME and KDE have incompatible aims - they approach usability from different perspectives ("less is more" vs. "more and more, better organized" to put it very simply). On the other hand, standardization of low level services/components might be a good thing, and work is already in progress (albeit I have to admit it is slow) to achieve that via freedesktop.org. Also, you have to be aware of the contradiction of your post: your problem is that there is too much and too few choice at the same time. You'd prefer to use GAIM instead of kopete (you have a choice) but because you choose KDE, you have to use Kopete for a consistent look (no choice). The question you need to ask is this: what is the problem with Kopete? What I'm trying to say is that KDE's application stack becomes more and more complete. They have their own, well integrated office suite (koffice). They have kopete, music players, webbrowser, even a viable gimp replacement for average needs (have you seen krita in koffice 1.4beta? - it is absolutely fascinating!) - and so on.

What needs to be done is to improve that application stack. So if Kopete is not fully satisfactory (you would like to use GAIM, don't you?) - than you should specify the problems. If a number of users agree with your claim - and that's the point of this article - you would be able to communicate your needs/problems to the developers, helping them improve the app you are currently 'forced' to use.

Re:Ignore the expert behind the curtain.

[evanbd]

How do you know they're good developers? Who's going to do the vetting?

I think the answer is the same -- good work is evident to others in both cases, even if the observer isn't an expert.

Re:KDE Print

[vegaspctech]

Seriously, I totally agree with you. I think kprinter actually is a very good example of the problems kde faces. Kprinter is technically an awsome tool if you take the time to really get into it. However the problem is, for simply setting up a local printer it is way to confusing.

No, but your post is a very good example of the problems KDE, Gnome and the rest face, when it comes to adoption by Windows users. If something has a configuration option or two less than Windows does for the same thing, then it's not configurable enough. If it's got a configuration option or two more than Windows does, it's too confusing. I just pulled up the default Windows and vendor provided printer configuration panels on Windows 2k, XP and 98 SE and printer properties in Kprinter for KDE 3.4. Kprinter appears to have just a couple more options than the default Windows equivalent and a couple less than the configuration tools provided by Epson and Canon. The most significant difference I see is a matter of depth. In Kprinter and the Epson tool all the options appear to be presented at the same depth, a handful of tabbed pages in one window, while the Windows and Canon tools have buttons on some pages that open additional windows. The latter have most the same options as the former, they just hide more of them.