Slashdot Mirror


KDE & Gnome Usability Engineers Interviewed

Gentu writes "After the recent flamewar between the KDE and Gnome user camps, OSNews brings together the most influencial KDE and Gnome usability engineers to talk about how they will be able to overcome a number of obstacles in order to 'unify' KDE and Gnome in ways that could bring to the Unix desktop an easy to use, integrated and fully interoperated DE to better compete with the commercial alternatives. Waldo from SuSE and Havoc from Red Hat are taking part to the interview, and also Aaron, the head of KDE's usability."

29 of 372 comments (clear)

  1. Sigh.. by Sh0t · · Score: 5, Insightful

    There is no flamewar. There is no "war".

    Users can use whatever they want, the two proejcts get along better than most to be honest.

    THis whole fued thing has been overhyped by "news" sites since gnome was created and it's quite silly.

    it's just a simple choice of DE, nothing more.

    1. Re:Sigh.. by myLobster · · Score: 3, Informative


      The article does not even suggest a flamewar - quite the opposite really.

      --

      Ceci n'est pas une .sig
    2. Re:Sigh.. by larien · · Score: 4, Informative

      I think the point is that it's a "user" flamewar rather than a "developer" flamewar. You're right in that Gnome/KDE get on fairly well (well, they do now; I think there was some antagonism early on), but users get very angry in the same way we have perl/python/ruby wars, emacs/vi, debian/redhat/suse/mandrake/slackware/whatever wars....

    3. Re:Sigh.. by addaon · · Score: 4, Funny

      Yeah, except that it makes sense that some people might want to use KDE, and some might want to use GNOME. What possible justifaction is there for emacs? [ducks]

      --

      I've had this sig for three days.
  2. As long as the result isn't Knome... by Kjella · · Score: 3, Funny

    ...I'm happy. Even Bluecurve sounded better ;)

    Kjella

    --
    Live today, because you never know what tomorrow brings
    1. Re:As long as the result isn't Knome... by CoolVibe · · Score: 5, Insightful
      I hope KDE drops that whole K-naming gimmick. Although I love KDE, and I use it every day, it's the one thing that I find downright irritating.

      So, I plea to everyone that develops new KDE apps, _DON'T_ use that silly K-ism shtick. It was fun the first two versions. It's getting old. Be original for a change, okay? Thanks.

    2. Re:As long as the result isn't Knome... by supergiovane · · Score: 5, Funny
      If you want, you can try my Kremoveinitial, a very useful utility which removes the K initial from every KDE app on your disk.

      Disclaimer: it's still beta and very buggy, but in case of necessity

      ill -9 kremoveinitial

      should solve any problem

      --
      Signatures are for stupids.
  3. Good news! by mschoolbus · · Score: 4, Insightful

    Oh now Linux developers are actually trying to make a unified GUI standard? Its sure nice to see everyone moving to the right idea here, but I am sure people will still complain because it is all about 'choice'...

  4. Interoperability is king by nitehorse · · Score: 5, Informative

    There's a relatively large thread going on in the kde-core-devel mailinglist about such interoperability efforts that you guys might be interested in, too... check out this thread for the whole story.

    The short version is - arts, the KDE sound daemon, uses glib code internally, but the maintainer wanted to move the glib code to rely on an externally-installed glib (instead of maintaining a copy of glib in the arts distribution). Lots of developer confusion over this has ensued, but a lot of interesting discussion has also resulted. Check it out.

    1. Re:Interoperability is king by IamTheRealMike · · Score: 4, Informative
      There's a similar thread on the GNOME desktop-devel-list, basically a debate about DBUS vs CORBA turned into some KDE users (developers? maybe) having a go at GObject yet again.

      The main sticking point seems to be GObject, but I've yet to find a KDEer elucidate what is so bad about it, especially considering it was designed with language bindings in mind.

    2. Re:Interoperability is king by nitehorse · · Score: 5, Informative
      I think that a lot of the problem with GObject is (in most KDE developers' minds) is that we feel it's a hack for C to help make OO programming available, where OO is much more readily available in other languages.

      The OO paradigm wasn't around when C was designed, and C certainly is an awkward language to use OO in.

      It's the difference between saying:
      QPushButton *button = new QPushButton("Hello, world!");
      and:
      GtkButton *button = gtk_button_new_with_label("Hello, World!");
      In one case, you have clearly defined language-level constructs and rules about what happens when you use said constructs; using the 'new' keyword on any object means that the language will automatically call the constructor for the object in question.

      So instead of having to write a x_button_new_with_specific_property function, you define a class with the properties, and the proper constructors (because C++ has rules about how constructors get called, instead of forcing the programmer to remember a name mapping for every _new function with every possible permutation of the _with_property names at the end).

      I support GObject personally insofar as it is used for the language bindings, because programming GTK in ruby or python should be easy and fun and take full advantage of the OO properties of those languages; but for use in C? Thanks, but no thanks.
    3. Re:Interoperability is king by nitehorse · · Score: 3, Interesting

      If that's true, then PLEASE, point me to a single Bonobo object implemented in Python.

      Or Ruby.

      Or Java.

      Or SmallTalk. Or OCaml, LISP, Scheme, or Perl. Any one of them.

      Where are they? Where is the "Implementing a Bonobo object in Python" tutorial? Where's the documentation? Where are the examples, the real-life apps using them?

      That's my point. They don't exist, so pointing at KDE/KParts and saying "You have to use C++ for KParts!" is silly, because you have to use C for Bonobo (to implement, anyway. Unless I'm wrong - which, if I am, please do tell me. :)

  5. Usability and Fonts by silvakow · · Score: 5, Insightful

    The one reason that people walk by a Linux system and immediately think it's arcane is typically the use of anti-aliased fonts. People feel much more comfortable learning systems that look pretty. After all, people never bought Windows because it was stable (not that I'm saying this is the only reason or anything, but it certainly helps ...).

    --
    In the long run, we're all dead.
    1. Re:Usability and Fonts by samhalliday · · Score: 3, Informative
      what are you talking about flame-bait?

      nobody thinks Xfree86 (its not just gnu/linux you know!) is archane becuase it uses anti-aliased fonts... if anything, people would think it arcane if it did NOT support anti-aliasing.

      granted this support has come a lot after windows has supported it, and some GUI libraries still need to catch up (nto an issue for gtk+2 or qt3) but for older machines, bitmapped fonts look much prettier than rendered ttf's.

      just what is your point?

      the main reason people walk by gnu/linux is that they dont know what it is, or if they do, they have so many windows apps they would rather not lose them ... or they see it as a geek's OS requiring geeks command line skills (true geeks use FreeBSD by the way). I have never in my life heard of anyone walk by a Linux system and immediately think it's arcane becuase it uses anti-aliased fonts.

  6. Unnecessary by tgv · · Score: 5, Insightful

    What I would like to see is not another technical feat, but an effort to bring the Linux desk top closer to the a-technical masses.

    I've recently had the "pleasure" of reinstalling Red Hat Linux and neither Gnome nor KDE are user-friendly at all. Yes, they do copy the Windows 95 desk top, but no, that's not going to help my father. And don't even start about the built-in file/web/help/and-what-not browsers.

    With all this high configurability that's available in both windowing systems, couldn't a group of more human-interface oriented people build a layman interface on top of either Gnome or KDE?

  7. Integration across the desktop by manyoso · · Score: 5, Interesting

    In general I found myself agreeing with Aaron
    's comments more than the others. The main problem I see with Havoc and Waldo and all the others pushing for more shared technologies across the desktop is the implementation technology. KDE is built from the ground up upon Qt/C++ and this is one of the major reasons for it's considerable success. I see no reason to change this winning strategy.

    Recently, we've been discussing the incorporation of Glib into KDE on the core development list. While I am not against this per se, I wonder whether the GNOME developers will ever allow the use of Qt/C++ in any shared technology. It seems to this day that Qt licensing is still a problem for GNOME. One of the greatest ironies in all of Free Software, IMHO.

    If Havoc and Waldo are serious about integration then this problem will have to be addressed in earnest. I do not want to see KDE come down a level in technology just so that GNOME apps can integrate into KDE. Better to improve the great applications we currently have in KDE then waste so much time focusing on some elusive merging of these two.

    Besides, choice is good and GNOME with KDE offer this. Where we can agree upon specs and closing superficial differences we should and that will help those who choose to use GNOME apps in KDE and vice versa. But please, let's not rearchitect KDE and strip it of Qt.

    1. Re:Integration across the desktop by manyoso · · Score: 3, Interesting

      They are far superior when it comes to an object oriented development environment. Code reuse is a good thing and C++ has support for object orientation in the language itself. Now, while it isn't necessary for everything, it certainly is the best solution for a desktop. KDE is more integrated and one of the major reasons is the use of Qt/C++.

      BTW, I don't take the 'KDE is perfect, GNOME sucks' attitude. I prefer KDE, but this choice does not in and of itself disparage GNOME. Plenty of opportunities for improvement on both sides.

    2. Re:Integration across the desktop by tjansen · · Score: 3, Insightful

      Most KDE developers have chosen KDE because they think it is superior. Otherwise they would have chosen Gnome. For example, I worked on Gnome stuff for a while but it was almost unusable for me. Then I decided to give KDE a try and never went back.

      So today the fundamental rift is that KDE developers think that C++/Qt is the most productive environment. Using GLib is just no fun, it is painful compared to C++/Qt, Java, C#, basically every modern programmign environment. And I also think that it is not possible to compete with MacOS X and Windows using C/Glib technology. They are already years ahead, and trying to catch up using a more primitive programming environment is crazy. I could understand to go 100% Mono, but C/glib?
      I would rather stop developing on GUI software and/or buy a Mac than write GUI apps using glib.

  8. Useability Engineer? by theGreater · · Score: 5, Funny

    Seriously, I love the titles we're given these days. Currently I'm a Senior in a Computer Science program... but really, I think I should get a raise and the new title "Education Subscriber" or maybe "Learning Engineer".

    Is this type of deal limited only to the Tech Sector, or is everybody throwing about hyphens and "Engineer" to make people sound more important?

    Other good tack-on words I can think of would be associate (no, that's not the Fry Cook, that's our Comestibles Associate), analyst (hey, I'm not a waitress, I'm an Order Analyst), and vice president (no, I'm not the bus boy, I'm the VP of Table Maintenence).

    -theGreater Cynic.

  9. one API. one look. by CreatorOfSmallTruths · · Score: 5, Interesting

    a unified look and feel to both Gnome and KDE will be great. I would even go further to suggest that someone should write a book in the lines of the M$ book of standards (its a book full of "thats how a window should look like" and "thats how a button should look like" etc.) for the linux environment.
    I know this is sort of a blasphemy, after all - linux is about tweaking, but nevertheless its quite irritating to use middle mouse to paste in one program, ctrl-v in the other and shift-insert in the third , without any way of deciding or even a way to know in advance.
    just my 2 cents...

  10. Keep Dangerous options away, please! by rithvik · · Score: 5, Insightful

    I just installed Gentoo, to try out kde 3.1. Well, it is just great. The one problem was this. The FIRST option in Konqueror setting menu is Show Menubar. Click on it by accident (which is easy since it is the first option), and you are in lost world. It was ok for me, since I know how to tinker and find out that control+M turns tyhe menu back (still it was difficult), imagine the newbie hitting this setting. WTF..

    1. Re:Keep Dangerous options away, please! by bahwi · · Score: 3, Insightful

      Those types of options need to be well-hidden. MS has had these options in various flavours and forms(and in the forms of service packs, etc, which broke more things than they fixed). One of the bad assumptions about Windows is that is is easy-to-use. If you start someone out on BSD or Linux and move them to Windows, and then even to another version of Windows, they wonder what the hell you are doing. Microsoft continues to move commonly-used options and functions around. I'm not saying that KDE and Gnome are the ultimate, but I see people saying we should take a lesson from Microsoft.

      If that's the case, I think we should take KDE's Control Center, name it to Control Panel, move it under Applications->Accessories->System Functions. The in the next minor release, let's move it under Applications->System->Options and call it System Control. Then in the next minor release, we need to call it "KDE System Control" and move it to Applications->Utilities->System->Options.

      The point is, taking a lesson from Network Neighborhood, moving things from one place to another is a PITA. That's one of the good things about KDE & Gnome. When they change something that big it's not hard to find it, the name rarely changes. So yes, MS should take a lesson from us.

      Options like the one you mentioned are there for those who prefer it, but need to be well hidden under an "Advanced Dialog". Why? Because there are people who expect things to work in certain ways that we consider "stupid" or "difficult" or "dangerous" when in fact it is quite the opposite for that person. Yes, I prefer more and more configuration options, and yes, I believe they need to be well, well, well hidden. Perhaps an overall option in the control center where you can set configurability from "Basic", "Advanced", "Expert", "Don't Blame Us"

      Just my 2c

  11. Finally at long last..... by NDPTAL85 · · Score: 4, Interesting

    ...REASON joins the open source movement!!!

    Choice is good, when limited. When allowed to run free, its actually a prison unto itself.

    Too many GUI's, desktop environments, xfree86 shells, WHATEVER you wanna call them (see there's even too much choice on naming the damn things) and userbases get splintered along with their apps making Linux HARDER not EASIER to use.

    A united GUI is the best chance Linux has for a respectable marketshare on the desktop.

    And for all you "But you will RUIN my LEENUCKS if you make it easy to use, I like being counter-culture and unique!!!!!" and "Dammit. Choice is sacrosanct! I don't care if NO ONE can figure out how to use Linux, if it doesn't have 500,000 different ways of doing the same thing then it isn't worth installing! Can't you see? Linux is ALL about WASTEFUL and POINTLESS duplication of effort! Why go foward when you can spend eternity going nowhere!!?!?!" people relax. I am sure someone will create a new Linux distro, the "Ub3r L33t Linux Extra-Special Hard To Use" distro with a built in AI that will monitor your usage over time and re-arrainge various commands randomly to keep you on your toes and make sure Linux never becomes "too easy" for you. Legions of filthy unwashed nerds and geeks, dissilusioned by the increasingly easier to use mainstream distros will flock to this new permanently hard to use distro. They will form communities to provide each other with moral support. Real Estate firms will notice a skyrocketing in their sales and rentals of basement unit apartments/condos as the geeks settle in for a lifelong pursuit of sunlight shunning and the disdainment of anything easy or social. Although these geeks and nerds will think their intelligence is par none, they will miss all other technological advances and fall further and further behind the rest of society. When their savings finally runs out and they apply for computer jobs interviewers will be amazed that you've all spent the past 5 years using what will appear to the rest of the world as "DOS Linux". Laughed out of the interview the poor geeks will have to settle for flipping burgers at the local fast food restaurant for a short time until they are replaced by burger flipping robots. Finally realizing their worthlessness to society in general they will join an EverQuest cult where they will all live in massive communes cut off from the rest of the world and live peacefully until someone forgets to pay the EverQuest bill and they all jump off a bridge from mass depression.

    --
    Mac OS X and Windows XP working side by side to fight back the night.
  12. Common object model by IamTheRealMike · · Score: 3, Insightful
    One of the biggest problems in making KDE and GNOME integrate well and feel consistant is the lack of a standard object model. As Havoc pointed out, some kind of "hub" would be great in future, allowing people to share Qt/C++ code with GLib/C with .NET with Python with Perl.

    Unfortunately, getting such a thing into KDE looks set to be next to impossible. A small but vocal minority appear to be dead-set against using even GObject, which only tackles a small subset of the problem of code sharing - the idea of using GObject seems to scare them witless.

    I wouldn't normally name names, but it's starting to get very irritating. Neil Stevens and Zack Rusin in particular, (there are others) consistantly object whenver the possibility of using something based on GObject (even when wrapped in the KDE style) is brought up. I've yet to see them state what is wrong with GObject, beyond "it's not appropriate" or "KDE developers should only have to use Qt C++".

    To be honest, this isn't the first time I wish KDE had gone with CORBA. Unfortunately, by dropping it before it matured, they blew a hole in the consistancy of the Linux desktop a mile wide, leaving their answer to "how do we get consistancy" to be "only use KDE apps".

    1. Re:Common object model by nitehorse · · Score: 5, Insightful
      Well, it's still not possible for me to access those distributed objects from the command line.

      I can tell my media player (Kiwi) to go to the next song with this command from a script, or the command line, or from another app:
      dcop kiwi KiwiIFace nextTrack
      Talking with a few GNOME developers, it seems that something this simple, this useful, is still not possible in GNOME (Please, correct me if it is! I hate being misinformed).

      As far as the 'distributed' nature of CORBA: Can you show me how to take advantage of this? I can't find any documentation on the Net about it, and the APIs in CORBA are hopelessly complicated (even for me to understand, and I'm a developer...). If my Gnumeric object is on another machine, how will Evolution embed that Gnumeric object locally to show a spreadsheet? Is that even possible? IIUC, it's supposed to be, but I've yet to see it done.

      The language-neutrality I'll give you, but in response to that: How many useful Bonobo parts are being implemented in Python? How about ruby? Or Perl? Or maybe Smalltalk, or Java? No? Why are they all in C, if the language doesn't matter? (Again, correct me if I'm wrong - but I've yet to see a Bonobo part implemented in C++, let alone any scripting language.)

      In short, I find that the KDE technology gives us flexibility that we don't see in GNOME, and it works plenty fast enough for our uses, while also being easily accessible to new developers.

      When I was adding new DCOP functions to Kiwi (having never used DCOP before) it took me all of twenty minutes to figure it out; once I had figured it out, adding the second DCOP function took five minutes. How long do you suppose it takes a new GNOME developer to get up-to-speed on using ORBit?
  13. the fundamentals are key by path_man · · Score: 3, Interesting

    When I look at areas where both Gnome and KDE can both improve, I see the basics. Things like printing. Things like sound setup. CDRW... DVD... improved .jpg and .tiff and other image management & manipulation.

    I know the immediate, knee-jerk response is going to be that there are great programs out there which handle all of the things I listed above. The problem is they aren't as integrated into either Gnome or KDE as they SHOULD be. Whether we like it or not, the Microsoft Windows 2k & XP interface is the gold standard for how applications are integrated into the desktop.

    What we should be thinking of is how we simplify the integration of applications into both KDE and Gnome desktops.

    --
    The surest sign of intelligent life in the universe is that none of it has tried to contact us. -- Calvin & Hobbes
  14. detail not opinion by mydigitalself · · Score: 3, Insightful

    "The new start menu is also an abomination. In fact, those two days with Windows XP reminded me why most people hate computers. I'd hate them too if that was all that was out there."

    as a linux/freebsd user you would think i wouldn't, but i actually quite like the new start menu. i really like the fact that it adds shortcuts on the fly to your most recently used programs. i think it looks very elegant and it also simplifies a lot of tasks for people such as my mother (the usual metaphor!) in terms of its "My Recent Documents", "Connect To" etc...

    my problem here with these guys statements is that they all, and in particular Aaron just makes these swooping opinionated statements without any meat to back them up.

    i was also concerned that none of them have much experience with Windows XP. i would assume that apple looks at it all the time to not only imitate things it has done well, but to avoid things it does badly. surely these guys should be analysing osx and XP and doing the same thing?

  15. Know thy enemy/ Too much is simply too much by FullCircle · · Score: 5, Insightful

    I find it highly disturbing that they don't use Windows every so often. I mean, come on, Microsoft spends TONS of cash on usability studies and 99% of the world knows Windows.

    I don't want an XP clone (although the thought is not that bad) but if you are creating a new UI, XP should be required study. Both for it's good AND bad points.

    They should also use OSX, MacOS9, Be, and any other OS worth mentioning on a regular basis. XP is not the be-all-end-all.

    Unix is the ONLY OS without a standard GUI.

    IMHO, the KDE vs. GNOME battle hurts Linux on the desktop more than it helps. Great, we have choices. But really, if there was a LINUX GUI, not two half-assed UI's, we could be much further along on our way to a really good UI. Red Hat 8.0 is the only distro to "get" this and they were crucified for trying it.

    1. The best code from each would have been used and the worst would have been dropped.
    2. There would be twice as many developers.
    3. Users would not have to choose their problems.
    4. Tech support would be possible.
    5. Graphical tools could be made for system configuration and packaging if they did not have to support a multitude of OS's.

    Too many options is good for a technical individual, too many options is NOT a good thing for a group. If they can't get together, I hope they both fail or lose mindshare. The Linux community would be better off with it's own standard GUI.

    It's not the packaging, the number of distro's or X Windows holding Linux back as I hear so often. It's the desktop. The other problems can be solved with a standard GUI.

    --
    If tyranny and oppression come to this land, it will be in the guise of fighting a foreign enemy. - James Madison
  16. Reinventing the wheel by ortholattice · · Score: 3, Insightful
    This is a good interview, but I find the following vaguely troubling:
    5. What are a few things you like and dislike about the Windows XP interface?...
    Aaron J. Seigo: I've used Windows XP for a scant total of 2 days...
    Havoc Pennington: ...The task-based interface looks interesting, but I've never tried it out...
    Waldo Bastian: I am not familar with Windows XP.
    For better or worse, MS has spent untold millions on usability studies of the user interface in Windows XP. Perhaps a lot of the UI decisions were misguided, but I doubt the decision to include this feature or that was made lightly. Although I personally dislike the XP interface (the first thing I did was switch to the "classic" theme - and of course immediately install Cygwin, Mozilla, etc.:), I think its features should be carefully studied and evaluated on their own merits. Also (IMO), a feature should perhaps be "biased" towards the MS behavior for the default settings, if there is no clear advantage otherwise, simply because that's what most people are familiar with. This will make the desktop attractive and comfortable for the greatest number of people. Those who dislike it can of course configure it however they want.

    MS did a lot of work on this. Maybe a lot of the results are distasteful - but that doesn't mean one should hide one's head in the sand. There may be some good things and some bad things, but choices can be made more intelligently when there is a broad base of knowledge to draw upon.

    (Same comments for Mac UI of course...)