Slashdot Mirror


Gnome 2.6 Usability Review

TuringTest writes ""The user-centric UI webzine" UserInstinct has published a usability overview of the latest version of the GNOME desktop. While their conclusions and recommendations are not mind-blowing, it includes two interesting appendices with a survey of new users (and their reactions to the system) and a list of common tasks of modern computer users with a commentary on how Gnome performs in each one. Note that usually You Only Need to Test With 5 Users (this report tests 4), you need to test additional users when an interface has several highly distinct groups of users and thus the conclusions in this review should not be taken as definitive."

424 comments

  1. Only 4? by Anonymous Coward · · Score: 4, Funny

    Not 5? Well, this is worthless then. Listen to useability/web design guru Nielsen!

    1. Re:Only 4? by LostCluster · · Score: 0, Offtopic

      The fact that Nielsen's web usage numbers disagre with Alexa whose numbers disagre with other sources, etc. just shows how hard measuring an audience really is.

      Most TV networks don't particularly care how many people watch any given program. The program's just a honeypot to try to attract you into watching the ads. That's the key, that's what they get paid for, who is in the audience watching the ads. The key exception are the networks like HBO and Showtime, because they have no sponsors and they get paid by people who subscribe. Still, even they don't directly care how many people watch each show, they care how many people are willing to subscribe as a result of each show. How many people watched is a nice proxy for those numbers, but they're not the true money stats that the decision makers really want to know.

      Since web business models vary, so is the metric that needs to be driven up so that the site makes money. Sometimes it's page views, sometimes it's ad clicks, sometimes it's sales... etc.

      I don't think there's ever going to be a universially accepted metric for "most popular" website... nor will that ever be an important title to have money-wise. :)

    2. Re:Only 4? by Anonymous Coward · · Score: 3, Informative

      Wrong Nielsen. useit.com mentioned in the blurb is Jakob Nielsen.

    3. Re:Only 4? by Anonymous Coward · · Score: 0
      How do I modify Gnome to be Like Red Hat's version with the "start" button on the bottom?

      Can I install Red Hat's Gnome theme?

    4. Re:Only 4? by Red+Alastor · · Score: 1

      I don't know but personally, I installed Fedora and reverted back to the gnome default.

      --
      Slashdot anagrams to "Sad Sloth"
    5. Re:Only 4? by c0p0n · · Score: 1

      Yeah, when not working for Macromedia, he does usability analysis for on-line casinos and pr0n sites.

      --

      Your head a splode
    6. Re:Only 4? by Anonymous Coward · · Score: 0

      the word is usability.
      dumbass.

    7. Re:Only 4? by Anonymous Coward · · Score: 0

      You're supposed to capitalize the first letters of sentences, dumbass.

    8. Re:Only 4? by joeljkp · · Score: 1
      If you use Gentoo, just type
      #emerge redhat-artwork
      As for the menu at the bottom, right-click on the bottom panel and add it.
      --
      WeRelate.org - wiki-based genealogy
    9. Re:Only 4? by Dick+Faze · · Score: 1
      and pr0n sites

      Which do you think is more scary: the list of criteria used, or the definition of usability?

    10. Re:Only 4? by Anonymous Coward · · Score: 0

      Right click the panel itself... select properties and set the orientation, change it to bottom.

    11. Re:Only 4? by c0p0n · · Score: 1

      the guys that tested usability. I cannot imagine Nielsen doing it by himself... err in fact, I prefer not to imagine that at all, I still want to have sex without weird thoughts filling my mind.

      --

      Your head a splode
  2. Project GoneME by Anonymous Coward · · Score: 3, Interesting

    Hello,

    I have started a little project which is intended to get the GNOME Desktop into a different direction. It's not aimed for people who love GNOME as it is now - No, it's more aimed to those who are experts to Unix and who like and wish so many times that some of the changes that went into GNOME never happened. The project was started yesterday and the first patches to *fix* the buttonorder (as one of many ideas and points) were created already. I plan to create the outstanding *fixes* for correcting the buttonorder in the upcoming days (as I have time) and then like to head over to other things that I personally like to have fixed. The project is not aimed to be a cooperation with the core GNOME it's more private work that I started for my own needs.

    In case someone is interested then feel free to read more about it on the Project GoneME page. Please do not expect huge wonders, it's just a test to see if people might be interested or not. As said it mainly covers my own interests at the moment. Please also don't put to much value in my brought up project description, they need to be reworked and altered anyways. I wrote the stuff as they came into my mind.

    1. Re:Project GoneME by Anonymous Coward · · Score: 1, Interesting

      Simple and worthy ideas. Hail to you. I do wish the newer gnome offerings subscribed to the ideas of least suprise. "i'll just mouse over here and click ok.. eh, its cancel, wheres ok gone, oh - its over there. wtf?!"

      gconf is a terrible idea. Actually most of the lets reinvent everything glib stuff is a bad idea. As if the ridiculous type casting requirements in gtk+, and the over complicated signal mechanism. Hey you can connect anything to anything - fine, but make the simple callback case work, and don't just remarshall the bloody arguments behind my back! Gosh, that feels better... cheers.

    2. Re:Project GoneME by Cid+Highwind · · Score: 5, Insightful

      I plan to create the outstanding *fixes* for correcting the buttonorder in the upcoming days

      Since when does being an "expert to Unix" imply that you want your buttons in Microsoft order rather than Apple order?

      --
      0 1 - just my two bits
    3. Re:Project GoneME by Anonymous Coward · · Score: 0

      The text needs a bit of rework but it's not easy writing a technical perfect thought through proposal in an foreign language (english) for a project that exits for just 48 hours. It need some more time until things get settled, people found and the project description get reworked. Being an 'expert to Unix' was meant that there are people outside who dislike being put on the same level as joe clueless user. They might feel offended by such sentences. Simplyification in GNOME is for sure a good thing but GNOME should still follow the good old Unix fashion it should clearly FIT into the Unix world and not trying to grab everything they can touch and work on it and then leave the stuff half finished and later people come up complaining the hell out of the things because a lot of the stuff doesn't work. The KDE people are doing it nice they have their own cleanroom implementation without touching stuff from outside. They concentrate on improving their Desktop and have both parties (the average Joe User) as well as the Unix experts in mind. After all people who use Linux or any Unix like operating system do this because they want to learn something.

    4. Re:Project GoneME by thenextpresident · · Score: 0, Flamebait

      You have spammed this message on OSNews, and now you are spamming it here, and God knows where else. This is called spam.

      Project GoneME: Spamming my Gnome Project.

      --
      Jason Lotito
    5. Re:Project GoneME by tomhudson · · Score: 1, Interesting
      I agree! Putting the cancel on the left and the okay on the right is WEIRD! Most of us read left-to-right, and would expect the action we want to take (which should also be the default action) to be the first one.

      Every time I go into gnome I'm reminded why I prefer either the KDE or a black screen tty. It's just fucked up!

      Of course, this "study" is also 86ed. The "it's better because it looks and works more like windows" and "we can improve it by making it look even more like windows" crap fails to consider that most people who leave windows WANT something different.

      It's not like they can't learn to do stuff differently. They have to with every version of windows anyway. Sheesh. Slow news day, I guess.

    6. Re:Project GoneME by Anonymous Coward · · Score: 0

      It has been placed on exactly 4 places to say the truth. This can't be seen as spam as you like to make the people believe. It was placed on well chosen Threads with the hope that the one or other could be interested:

      - It was first introduced on Moo Bunny,
      - It then was post on GnomeSupport within the Development thread,
      - It was post on OSNews within the same Article,
      - It finally got post here on /. because the situation was just to perfect to be left out.

      No spamming nothing. It's also important for a community to make some noise to be heard without being offensive by plastering it in own Articles and then not being able to offer what they promise. Project GoneME doesn't promise anything. It's just an information for people who might be interested and like to participate. It's your choice to participate or not and that's almost all.

    7. Re:Project GoneME by JanneM · · Score: 4, Insightful

      Of course, Gnome does not have "Cancel" and "OK" - if you find a dialogue that does, it is a bug, and should be reported.

      --
      Trust the Computer. The Computer is your friend.
    8. Re:Project GoneME by superangrybrit · · Score: 1

      You're in the majority, GALAXY. Don't let these bozos scare you off.

      Spatial Browsing is counter-productive. Everybody knows and understands this (except the close minded fanatics.)

    9. Re:Project GoneME by Anonymous Coward · · Score: 0

      I suppose the argument is:
      + Motif was (is?) the official UNIX Toolkit
      + Motif's HIG was written by Microsoft to be similar to the Windows HIG
      + Gnome replaces Motif
      + Therefore, Gnome should follow Microsoft conventions.

      The other argument is that if everyone else does it one way, Gnome shouldn't do it the other way.

    10. Re:Project GoneME by Anonymous Coward · · Score: 0

      Generally agree but I think gconf is an excellent idea. It's a place to hold settings without all the problems of the windows registry corruption. How could it be done better?

    11. Re:Project GoneME by Skeezix · · Score: 1

      It has made me 10 times more productive. I'm not sure what you're talking about. I find I actually use the file manager now. A browser is fine if you want to browse around for files. I have no desire to do that. My files are more organized now and I can get to what I want much easier.

    12. Re:Project GoneME by merdark · · Score: 4, Informative

      Spatial browsing is one thing, but the rest of his ideas show an extreme lack of technical knowledge and rational thought.

      Not to mention his posts on osnews as ogalaxyo gave me the impression that he was a 12 year old kid who simply hasn't figured out how things work yet.

    13. Re:Project GoneME by thenextpresident · · Score: 1

      4 Places or 4,000, it doesn't matter. It's spam. Your promoting a project, and it's off-topic. It's merely a copy-paste of the original message.

      It's spam. You're a spammer. Spammers suck.

      --
      Jason Lotito
    14. Re:Project GoneME by Anonymous Coward · · Score: 0

      John Kerry? Is that you??? Dude, kick Bush's ASS!

    15. Re:Project GoneME by dhammabum · · Score: 1
      Couldn't this be done as a 'skin'? I just use Gnome, not a developer, but surely all this user junk should be abstracted just as backgrounds and button styles are?

      --
      I am not a robot. I am a unicorn.
    16. Re:Project GoneME by zsau · · Score: 2, Insightful

      The Gnome buttonorder isn't broken, so it can't be fixed. It's just different.

      BTW, can I chose my own buttonorder, or are you just imposing another decision on me? I might find some other aspects of GnoME interesting, but if the only option is Windows buttonorder or old-style Nautilus, you haven't 'fixed' anything. You've just imposed your own preferences.

      --
      Look out!
    17. Re:Project GoneME by CaptnMArk · · Score: 1

      I think of it as an IBM order and I strongly prefer it.

    18. Re:Project GoneME by Red+Alastor · · Score: 1

      I matters. Spam is *mass* mailing.

      --
      Slashdot anagrams to "Sad Sloth"
    19. Re:Project GoneME by Anonymous Coward · · Score: 0

      I think its just a rehash of the windows registry which I loathe. To my mind it encourages a black hole of config settings, and gconf-editor looks a bit too similar to regedit for comfort. For instance, for some wacked out reason my gnome panel starts on the top. I change it to bottom, save state, and I can't find the magic key to make it stay there. It also discourages self encapsulation of an application. Take mozilla - for the most part, I can just extract it under /opt and apart from ~/.mozilla I know theres no other place to worry about. I can even copy the user preferences around. No wizardry involved. Now for unix systems I agree theres not an ideal place for system wide settings. Its a problem I admit. With ms windows, the lines between OS and window system are intentionally blurred so its registry idea almost makes sense but the implementation isn't great. But at least thats a system thing. In a modern unix system, should such things be up to a desktop manager?
      To answer your question I prefer apps to be self contained if possible. User prefs have a home in an app specific dot file/dir with maybe a system wide /etc/app/settings or /opt/app/settings. Some of which would be overrideable, some of which wouldn't for locking down machines. Old school but I liked it. It solves most of what a registry system would do. A system for notifications of system wide changes would in my mind need adoption across KDE/GNOME/etc boundaries. Hard to find a natural place for that, because of the separation of OS, X Window System, Desktop Manager, Window Manager.

    20. Re:Project GoneME by Anonymous Coward · · Score: 0

      The KDE people are doing it nice they have their own cleanroom implementation without touching stuff from outside. They concentrate on improving their Desktop and have both parties (the average Joe User) as well as the Unix experts in mind.

      I see. Has it occured to you to use KDE then?

      After all people who use Linux or any Unix like operating system do this because they want to learn something.

      Ridiculous. If you don't know that UNIX is used far beyond simply as a learning tool then you're not the expert you claim to be. Lots of people use UNIX and UNIX like operating systems to get work done, not because they want to learn something.

    21. Re:Project GoneME by jhdsl · · Score: 1

      I agree! Putting the cancel on the left and the okay on the right is WEIRD! Most of us read left-to-right, and would expect the action we want to take (which should also be the default action) to be the first one.

      Most people are right handed. This means that the pointer will automatically be on the right side of the screen most of the time (I'm not kidding, observe yourself for a while and you'll see it).

      Thus, having okay on the right is better because it means less mouse movement.

    22. Re:Project GoneME by AbRASiON · · Score: 1

      His response was completely valid and assuming he's telling the truth relevant to this topic.

      I find your response moronic.

      It's moronic. You're a moron. Morons suck.

    23. Re:Project GoneME by BigSven · · Score: 1

      Changing the button order back by forking the GNOME project? That's about the stupiest thing I've ever heard about. Instead of writing patches for each and every app out there (patches which are certainly not going to be accepted), you should first of all submit a patch for

      http://bugzilla.gnome.org/show_bug.cgi?id=74669

      As soon as this is fixed and in a released GTK+ version, you can start to submit patches to application to make them respect this setting. Such patches would then have a good chance to be accepted.

      It would also help a lot if you stopped speaking about *fixing* the button order. I understand that you disagree with the decision (I do myself love it) but there is clearly no correct button order so there is nothing that could be fixed here.

    24. Re:Project GoneME by Anonymous Coward · · Score: 0

      This only applies to GTK+. But there are plenty of badly written GNOME and GTK+ applications outside which hardcode 'adds' buttons in the fashion how the GNOME HIG likes it.

      gtk_dialog_add_button (GTK_DIALOG (fontseldiag), GTK_STOCK_CANCEL, GTK_RESPONSE_CANCEL);
      gtk_dialog_add_button (GTK_DIALOG (fontseldiag), GTK_STOCK_OK, GTK_RESPONSE_OK);

      I don't see how this can be fixed with one setting inside GTK+ not to mention all the hard designed Buttons inside a *.glade file. Well though you might be able to check on GTK_STOCK_* or GTK_RESPONSE_* but why hasn't this been done already ?

    25. Re:Project GoneME by sploxx · · Score: 2, Insightful

      Hi!
      GOOD idea! Really. I'm using gnome right now, but the "remove-every-option-which-maybe-hard-to-understan d-for-some-people"
      attitude which some of the more influental gnome people start to have really pushes me back to KDE.
      Of course, this is only my opinion. But apparently I'm not the only one here...

      But I think you're doing one thing wrong. Instead
      of changing button orders permanently by a patch, better make such things configurable! That is the
      thing I'm missing most in the newer versions of gnome, removed flexibility because "it is better for you". Make an option for the button order. Give the user the power back to change window managers. Etc.pp.

      Maybe this is the least common denominator for all gnome forks? Other options/other configurations?
      That'd be nice because you could cooperate with
      the other forks around and, for features you agree with each other, have a productivity boost :)

      PS. And mods. The above poster does an advertisement. For a free software project. But that is clear and not hidden. He doesn't bash gnome, he doesn't bash KDE, nor does he belong to the GNAA.
      IMHO, the parent is in _no_ way "flamebait"!

    26. Re:Project GoneME by Xoro · · Score: 1

      Most people are right handed. This means that the pointer will automatically be on the right side of the screen most of the time

      You may not be kidding, but you are missing the point. The issue is not where the pointer is most of the time, the issue is where the pointer is when dialog boxes come up.

      Look at the top of the program you are using now -- see where all the menus and buttons are? Where is the "foot" menu? Where are the menus on the desktop menu bar? To which side of the screen do your desktop icons automatically align themselves?

      If we are designing things around the principle of where the right handed cursor usually lies, surely the whole enterprise is backwards. Is it? Suppose you say yes, arguing that the menus-buttons-icons should all be shifted over to the right side where they will be as easy to reach as the Yes button.

      In that case, the current design is still wrong. The is because the dialogs generally appear in response to interaction with just these items! As it stands, we must move the mouse all the way over to the left, choose an action, then drag the mouse diagonally across the dialog just to confirm it. Ridiculous.

      Left-to-right gives us compatibility with the dominant platform, conforms to the common yes-or-no speech pattern and provides the best ergonomic grouping.

      Bring it back.

      --
      Kill, Tux, kill!
    27. Re:Project GoneME by nutshell42 · · Score: 1
      Yes but the usability advantage due to the "improvement" of saving 2in of mouse movement is by far outweighed by the sheer stupidity of annoying 95% of the potential users (I seriously doubt I would switch to GNOME if I had OS X so I assume most people come from a Windows background) and all of the existing users that also use other Linux applications (I don't know anyone who doesn't mix [his DE of choice] with [the enemy] and [other X11 appliciations]).

      You can't tell me that it's better to have applications adhereing to different button orders than to have the possibly (I still think the advantage of being able to read left->right compensates for the fact that the button isn't in the lower right corner) inferior solution to offer a more consistent desktop

      --
      Don't think of it as a flame---it's more like an argument that does 3d6 fire damage
    28. Re:Project GoneME by BigSven · · Score: 1

      Perhaps you should read the bug report more carefully then. Of course adding the setting alone won't change any application but the setting is a pre-requisite for making the button order configurable. It's the first step that has to be taken and only if this setting is available in GTK+ will patches to application be accepted.

      I can only speak for The GIMP project but we would accept a patch that makes the button order dependant on a GTK+ setting. We would definitely not accept a patch simply changes the button order back.

    29. Re:Project GoneME by Vitus+Wagner · · Score: 2, Interesting
      Is this for unix geeks? Hamper networking by removing esound - only right architecture decision GNOME ever had?


      Typically UNIX geeks work in highly distributed environment and need networking sound server more than anyone else.


      If you were about replacing esound with NAS or rplay, there would be something to talk of.


      Really we need some project like this - for real unix geeks. There are lot of more or less useful things which are written for GNOME or KDE only. I need to keep GTK and GNOME libs with all associated stuff like gconf only for few useful apps like The Gimp and planner.


      I can outline some goals of the project which would make GNOME apps more integratable with traditional Unix desktop

      1. Write X Resources backend to gconf, so GNOME apps would automatically pick up your Xaw and Motif settings
      2. Make drop-in replacements for libesound which would allow to use any of audioservers out there.
      3. Fix ICCCM support to
      4. Make other IPC systems used in GNOME work over ICCCM to allow apps, started from different hosts interoperate via X server.
    30. Re:Project GoneME by Hognoxious · · Score: 1

      Surely the right way is to make it switchable (like if you reverse the mouse buttons because you're a southpaw, it applies to all apps. All well-behaved ones, anyway.

      --
      Confucius say, "Find worm in apple - bad. Find half a worm - worse."
    31. Re:Project GoneME by tomhudson · · Score: 1
      I'm a leftie, and I want the default action on the left.

      Also, as I pointed out, I read left-to-right, so in the interest of speed, the default action should also be on the left.

      Putting it opposite everything else is saying to the user "We think that whatever action you took may be a mistake, so we're going to let you cancel it easier than confirming it".

      Just get rid of the damn dialogs altogether. If I ask to do something, even "rm /*", just do it. If it bites me in the ass, well, I've learned something.

      What next - "I'm sorry Dave ... I can't do that"?

      And people wonder why I like command lines so much ...

    32. Re:Project GoneME by Hognoxious · · Score: 1
      The Gnome buttonorder isn't broken, so it can't be fixed. It's just different.
      The crashmatic coupe pedal order isn't broken, so it can't be fixed. It's just different. [beep! vrooOOOOMBANG!]
      --
      Confucius say, "Find worm in apple - bad. Find half a worm - worse."
    33. Re:Project GoneME by tomhudson · · Score: 1
      All right, "Cancel" and "Confirm" - in that order. It sucks. It should be left-to-right, with default action on the left, except in those locales where the BDI algorythm is right-to-left.

      What's so hard to understand about that?

      It has nothing to do with "imitating windows". I don't want anything that works like windows. I want something that exposes the underlying OS's capabilities.

      No wonder I use the black screen ttys so much. Alt-FunctionKey heaven. If Gnome was the only window manager, I wouldn't have startx in ANY of the runlevels.

    34. Re:Project GoneME by zsau · · Score: 1

      Analogies are great, aren't they? You can use them to argue your point, and mostly no-one else questions whether you're taking it to far. Are you?

      --
      Look out!
    35. Re:Project GoneME by freqres · · Score: 1

      What is this cancel and confirm crap? How about something much better, like "Chill out, dickwad" and "No problemo".

      --
      Rampant Ninja related crimes these days...Whitehouse is not the exception
    36. Re:Project GoneME by Slack3r78 · · Score: 1

      While I haven't read the usability studies to find the exact reasoning behind this order, I'd imagine that it is at least somewhat related to Fitts' Law. Basically, Fitts' Law states that the four corners of the screen are the easiest places for a user to reach, and therefore your most important functions should be placed in the corners to allow ease of access.

      I'd imagine this translates over to individual windows, albeit to a lesser extent. In most cases, a user is more likely to want to select a confirming action than a negative action, so it'd make sense placing to confirming option in the easiest to reach position in the window.

      I'll admit that, personally, I had the same negative initial reaction that you did, but after spending some time allowing myself to get used to it, I've actually come to prefer right-left ordering over Microsoft left-right ordering, for exactly the reason above. It's much faster to just throw the mouse in the general direction of the corner than it is to precisely position it in an arbitrary location.

    37. Re:Project GoneME by Anonymous Coward · · Score: 0

      "Cancel" and "Confirm" look the same, so that's a bug.

    38. Re:Project GoneME by tomhudson · · Score: 1
      The reason the 4 corners seem to be easier to reach is because people can't find their mouse pointer with all the screen clutter, so they wiggle it like crazy looking for it. Once you reach a corner, there's no place to go so the pointer stops there - unless you have your desktop set to switch to another desktop when you get to the side/bottom/top

      Putting xeyes in the taskbar eliminates this problem.

      But what does that have to do with putting the default action to the right of the cancel option? This only makes sense where reading is from right-to-left, not left-to-right.

      It was a mistake, trying to be different for the sake of being different.

      It's also an insult to the usr, presenting the cancel option first - in other words "We think you made a mistake, so we're showing you the cancel option first".

      I'd rather use a tty than use Gnome. And with the speed improvements in the latest version of KDE, Gnome is toast. (plus it just looks ugly)

    39. Re:Project GoneME by tomhudson · · Score: 2, Funny
      Or this:

      "Cancel" "Confirm" "Switch to KDE"

    40. Re:Project GoneME by Anonymous Coward · · Score: 0

      *lol*

    41. Re:Project GoneME by mwood · · Score: 1

      I'd settle for "it no longer takes a trillion cycles just to start a single stinkin' application".

    42. Re:Project GoneME by mwood · · Score: 1

      "Where is the pointer" is trivial compared to "where is the user's attention".

    43. Re:Project GoneME by mwood · · Score: 1

      Although I've argued a bit on this, I'm coming to the conclusion that the only agreement possible is agreement to disagree. Some people make visual concerns paramount, others ergonomic concerns, some lexical concerns, etc. Different styles of thinking is where a lot of software design decisions start, and no one is going to convince anyone else to switch his style of thinking merely by talking.

    44. Re:Project GoneME by mwood · · Score: 1

      Indeed, the reason Motif and MS Windows resemble one another is that they both learned a lot from TopView. :-} IBM's user interface guidelines (whatever the heck the name was) have influenced far more systems than many realize.

    45. Re:Project GoneME by tomhudson · · Score: 1
      --- which is why having a multitude of desktops is a "good thing" :-)

      Every time I hear people saying we should standardize on one desktop, I shudder. Monocultures are never as hardy, and tend not to evolve.

      Now if we could just get rid of the 2-minute delay (at least get rid of it for people who have excellent karma, so karma can actually mean something), Short posts and short answers wouldn't take up 2 more minutes than they need to :-)

    46. Re:Project GoneME by Slack3r78 · · Score: 1

      A quick scan of Apple's HIG netted the guidlines related to how to place options in a dialog box, but not the why.

      Perhaps more relevent, I found this post from the Gnome project's usability lead detailing why a right to left ordering should be easier to use. I'll note that I was wrong and it isn't exactly related to Fitts' Law, but it is a very similar concept.

      Either way, it's clear that there's been a lot of thought and planning put into this - it wasn't an arbitrary decision. It *seems* unnatural at first simply because most people are accustomed to the Windows style dialogs. The problem is, by growing accustomed to them, they generally seem to believe that it's the best way of doing things, without ever really considering what the actual meritts of either system are.

    47. Re:Project GoneME by mwood · · Score: 1

      My servers have no sound hardware and no reason to ever make a sound more complex than "beep", so I'd love to be able to configure all sound support out of the system.

    48. Re:Project GoneME by Anonymous Coward · · Score: 0

      Default in the lower right corner is the way Mac OS does it, right? Part of the reason for this is that, because the buttons are right justified, then the default option is in a predictable location, not moving around depending on window size and number of options. Besides, if you stop reading after the first option (which you seem to want to be able to do), how do you know whether that's really the best option to select?

      It could make sense to put the default option on the left, but only if you also left-justify the buttons. However, that warps the way most of us think about dialogs. Consider a "wizard" where the default action is "Next", but the button for "Next" is on the left. Most people consider the left to indicate past or previous things, and the right as next. Think of a book and how you turn the pages.

      There is no correct answer as you seem to believe-- or do you have empirical evidence that indicates that people can use your proposed arrangement more efficiently than the existing arrangement? Personally I want my default option in a corner-- not in the middle somewhere. I want my eye drawn to it. Whether it's on the left or right, I don't care... but since every OS seems to right justify buttons in dialogs, I want the default option in the lower-right corner.

    49. Re:Project GoneME by tomhudson · · Score: 2, Interesting
      thanks for the link. I'll comment on it below :-)

      I would disagree. I first started developing software way back when (before DOS), and the default action was always the first in line.

      when I moved to dos, any text dialog I made also had the default as the first, in a left-to-right sequence. It just seemed the normal thing to do.

      Windows didn't exist then, so it couldn't have been "contaminaton" from windows.

      Thanks for finding the reference. Now I can kill the BS (which is what it is) in the Gnome reference:

      The argument basically is that with left-right, top-bottom readers, your eye is left resting on the lower right corner of a window when you are done reading text. That makes the lower right corner the first thing you read when you are done with a block of text. Thus it is the most quickly acquired option, *AND* is conceptually first in your list of choices even if you scan the other buttons. This effect is particularly important when you start only glancing through the text to recognize the type of dialogue it is (rather than actually reading), which is where this shaves off irritation and inconvenience (that is, when you don't have to read all the choices because of familiarity, its nice to have the most common choice presented first).

      This is all very nice in theory, but overlooks several facts:

      1. the dialog is in another window, so people are not looking at the bottom right.
      2. this would only apply to screens of text, and only screens of continuous text. Most web pages, for example, don't fit this model
      3. when a dialog opens up, people who read left-to-right are going to visually acquire the new window, then start reading left-to-right. It's not a continuation of the previous window.

      That's why it's so irritating.

      People tend to organize spatial information using some sort of heirarchy. That is, you might spatially orient Las Vegas by knowing it is in Nevada, by knowing Nevada is in the U.S., by knowing the U.S. is in the American Continent. This has suprising effects on things like scanning speeds. Things that are 30 pixels apart but in the same "parent region" can seem closer than things that are 20 pixels apart but in a different parent region. But I digress.

      He (the author) is making a seriously wrong assumption, that all the users are the same sex. Men and women have different methods of orienting themselves (do a google of "sex difference brain orientation spatial maze" and read the results).

      A second wrong assumption is that people have to "navigate" their desktop. Most people do a lot of things on autopilot - like drive the same route to and from work. No conscious navigation required.

      We assume that the window is the parent region for the buttons. Thus your information about the button's position largely follows from the position of the dialogue window. It turns out that some areas of the parent region are "hotter" than others, that is it is easier to retain a strong sense of their relationship to the parent. Things in the corners have the strongest retainable relationship to the parent, followed by something in the exact center, followed by things on the edges. For a left-right, top-bottom reader, the hottest part of the window is the upper left corner (where we put the titlebar, which needs to be scanned very quickly when dealing with multiple windows), followed by the lower right corner. (note this is not Fitt's law, it is much weaker than Fitt's law which impacts actual "pointer" motion, not just scanning, but its still a significant effect)

      The title bar is the hottest area? Total bull. How many people even look at the title bar any more? It's not the hottest area visually, and it never was. I remember back in the '90s writing apps, I decided to try putting status messages, etc., in the title bar - they were completely unseen. Hell, you can put up a web page full of jokes and a title that says "If y

    50. Re:Project GoneME by tomhudson · · Score: 1
      Right-justifying dialogs isn't the function of the OS, but of the developer.

      The "wizards" function like vcr controls.

      << < > >>
      Look familiar?

      Dialogs don't need right-justified buttons - that's something Apple got wrong. Perpetuating it is just dumb.

      I read left-to-right. In a dialog that's asking me if I really want to do something, I don't want to have to read even 2 options. Just an OK or hit the escape key would be enough. 1 button. Or better yet, don't ask me.

      Honestly, haven't there been times you've klicked on Okay or Confirm or whatever, and only then realized that you didn't want to do it? Confirmation dialogs are useless and an insult to the user.

    51. Re:Project GoneME by mwood · · Score: 1

      Sure, choice is good. *My* "desktop environment" is "xsetroot -solid steelblue" plus a few lines in .fvwm2rc. But I do like having the app.s similar enough that I don't have to waste brainpower thinking about issues that have nothing to do with what I'm trying to accomplish. If I notice the user interface at all, that's bad.

    52. Re:Project GoneME by Slack3r78 · · Score: 1
      First, let me thank you for sticking to explaining the reasoning behind your ideas and not resorting to "OMG GNOME R TEH SUX0R" style flames. Interface usability is a topic that fascinates me, and I'm always glad to have a rational discussion on it, especially with those who have differing viewpoints from my own. :-)

      Windows didn't exist then, so it couldn't have been "contaminaton" from windows.

      Mea culpa, no offense intended. As I said, it's merely been my experience that people learn to like what they're most familiar with, for better or worse.

      This is all very nice in theory, but overlooks several facts:

      1. the dialog is in another window, so people are not looking at the bottom right.
      2. this would only apply to screens of text, and only screens of continuous text. Most web pages, for example, don't fit this model
      3. when a dialog opens up, people who read left-to-right are going to visually acquire the new window, then start reading left-to-right. It's not a continuation of the previous window.

      I believe you misread this section. What he's basically saying is that when a user is presented with a dialog, the way they're going to visually acquire it is as such:

      1. Start at the top-left most corner of the window.
      2. Begin scanning-left to right, reading the main body of the dialog box.
      3. When reaching the bottom of the dialog, continue to read the options in a left to right manner. When their eyes have reached the end of the last option, their eyes will be focused on the bottom-right corner.

      This means that if your confirming option is in the bottom-right corner, the user can immediately move to it, without having to refocus their vision on a different part of the screen.

      He (the author) is making a seriously wrong assumption, that all the users are the same sex. Men and women have different methods of orienting themselves (do a google of "sex difference brain orientation spatial maze" and read the results).

      No real argument on this one, I did think it was a rather poor argument for the concept he was talking about myself.

      A second wrong assumption is that people have to "navigate" their desktop. Most people do a lot of things on autopilot - like drive the same route to and from work. No conscious navigation required.

      You've just hit on *exactly* the reason why the right-left ordering is a good idea. By putting your confirming option in the bottom right, you ensure that it will always appear in the exact same location in *every* dialog box the user sees. With a left-right style, there's the opportunity for your confirming option to appear at different orientations inside your dialog, making for an inconsistent interface, which forces the user to consciously look for the default option. The confirming option always being in the same place facilitates the autopilot mode you're talking about.

      The title bar is the hottest area? Total bull. How many people even look at the title bar any more? It's not the hottest area visually, and it never was. I remember back in the '90s writing apps, I decided to try putting status messages, etc., in the title bar - they were completely unseen.

      As you've already noted, a dialog box is separate from the parent window, and by nature forces the user to give it their attention. I don't disagree that most of the time, people do filter out the title bar for normal applications, but in this case, it's all about context.

      I've already selected what I want to do, and the stupid box is asking me if I'm sure. I want to pick the first choice I see, which, being someone who reads left-to-right, should be on the left. Making me read the "Cancel" button first is dumb.

      Personally, I feel that the argument here i

    53. Re:Project GoneME by tomhudson · · Score: 1
      One of the things that came to my mind repeatedly is how technology has obsoleted certain things with regard to interfaces.

      For example, when people were using 12" monitors, a menu bar on top was a good idea, since it would still b below eye level. Nowadays, with everyone using 19" or better monitors, putting the menu bar on top is a serious mistake in terms of eye strain and ergonomics.

      So what was good for the old, early black-and-white macs is not good today.

      We're going to see another change sometime in the next few years, when 16:9 and 2:1 aspect ratio displays become the norm. Then, a menu/panel bar stretching across the bottom of the whole display will be a terrible waste, so we're going to end up with some sort of anchored control pad.

      We already see this with multiple-monitor setups.

      What would be nice would be a throwback to the old days, 2 monitors and two mice, and 2 pointers. (It actually works. I found this out accidently while connecting both a serial and a bus mouse to a dual-display setup I had way back when ... DOS could do it, and both mice worked. Since I'm ambidextrous, it was actually quite handy, and other people sitting at my box wouldn't get all funky trying to work a mouse on the wrong side of the display).

      All that being said, the desktop metaphor really sucks. It's been around since before DOS even, and it is time to change it.

      The original reason to use viewports or windows in graphic displays was because it took a lot less computing power to draw and clip rectangles than other shapes.

      There were demo programs back in the early 90s that allowed you to have a real 3d desktop (not the looking-glass thing, but a "real" one) by using either lcd glasses that blocked one eye at a time, and drew the left and right views in sync, or coloured glasses like the old 3d movies.

      I remember one book even had instructions for wiring up the original nintendo power glove to act as a controller.

      Now that we have displays that use tunnelled pixels elements to create left/right views, perhaps its time to resurrect that old concept.

      I remember when PCTools had 3 levels of user. In the Expert level, there were no confirmation boxes, etc. An interface that was smart enough to recognize that you've never, in the last 100 requests, ever clicked cancel should then offer to turn off that "feature". That would be user-friendly. This way, users could get up to speed - literally.

      This is the thinking, for example, behind showing the keyboard shortcuts in menus - after people see them so much, they learn them, and stop using the menus.

      When I first started, a graphical display of 320x200 was considered awesome ("you have graphics? And a touchpad? What's a touchpad?"). Nowadays, we have 20x the area as the norm. Lets get rid of the "folders" and "documents" metaphor. It is dated as all heck :-)

      People can learn what a directory, a file, and a symlink are :-)

    54. Re:Project GoneME by Tombstone-f · · Score: 1

      It would only make sense to put them left to right it they were left justified. Seeing as they're right justified, the most logical place for default choice is on the far right.
      At least that's I see it.

    55. Re:Project GoneME by tomhudson · · Score: 1
      So why the right-justification? Ever tried to read text that was right-justified? It's painful.

      Right-justification only makes sense when you're reading right-to-left.

      Besides, how hard would it be to make the mouse go to the "Confirm" button auto-magically by default? That would draw the user's eyes to it ... then they could have the "Cancel" button to the right. Again, left-to-right, since we're reading left-to-right anyway. Having the "Confirm" on the right is almost like the backtracking in perl when you save a split into variables... :-(

      Another advantage is if you decide to use the keyboard - enter does the trick, and tab goes to the cancel, as opposed to having to shift-tab to go backwards to cancel. It's a terrible, indefensible, setup.

    56. Re:Project GoneME by anonymous+cowherd+(m · · Score: 1
      When I first started, a graphical display of 320x200 was considered awesome ("you have graphics? And a touchpad? What's a touchpad?"). Nowadays, we have 20x the area as the norm.

      Actually, the difference in area between a 12" monitor and a 21" monitor is more like 4x the area, not 20x. The difference in resolution might be 20-30x, but the screen area is still only 4x.

      What happens when you try to draw on a 21" monitor using low-res icons and such is really small and hard to read text and icons. I run large size icons on my 19" monitor at home just because I typically am sitting about 4 feet away from it and I like to be able to see what I'm clicking.

      --
      http://neokosmos.blogsome.com
    57. Re:Project GoneME by tomhudson · · Score: 1
      The difference in pixels
      320x200 = 64,000
      1280x1024 = 1,310,720

      1,310,720/64,000 = 20.48 x
      The 12 inch monitors in those days were incapable of drawing at high resolutions; the video cards also didn't support virtual desktops with pan and zoom.

      A 1280x1024 display on a 19" monitor is much more readable than the 320x200 display on a 12" monitor from those days.

      Also, in those days, 12" really meant 10" diagonal (thick bezels, etc) - this was before the consumer laws said uh-uh you can't do that. Remember how all of a sudden boxes started being labelled 17" monitor 16" viewable? Or 17" monitor 15.5" viewable?

      I'm sitting in front of a SyncMaster 900NF at 1280x1024 with normal-sized (but high-colour count) icons under KDE with no problems. (Guess linux has fixed the early font display problems :-)

      If I ever need to zoom in on something (because, for example, someone specified 6pt fonts), its just a Ctrl+Shift+Plus keystroke away.

    58. Re:Project GoneME by rking · · Score: 1

      The "wizards" function like vcr controls.

      >>

      Look familiar?


      You're repeating his point. Rightmost or rightwards pointing commonly represents movement forewards, and leftmost movement back. Probably because pages and books are read, in western cultures at least, left to right. You can disagree with the importance of this if you like but repeating the point (and giving an example, look at vcrs!) while seeming to imply that you're disagreeing just seems odd.

      Dialogs don't need right-justified buttons

      Agreed.

      Honestly, haven't there been times you've klicked on Okay or Confirm or whatever, and only then realized that you didn't want to do it? Confirmation dialogs are useless and an insult to the user.

      I think there's a certain amount to that. They can be useful to someone fumbling around learning a new system, but once you know what you're doing they're merely irritating. When the menu comes up saying "Do you really want to intitiate thermo-nuclear warfare" you don't stop to think because repetitious use of dialogs has already trained you to click OK as the way to get rid of the thing.

    59. Re:Project GoneME by tomhudson · · Score: 1
      RE: the VCR thingee:

      I had pointed out that this was an exception in a previous post, because it relied on a familiar day-to-day object - the vcr, as it's metaphore.

      Hope that clears this up :-)

    60. Re:Project GoneME by Hognoxious · · Score: 1
      Analogies are great, aren't they? You can use them to argue your point
      I would say that Illustrate a point is more accurate.
      mostly no-one else questions whether you're taking it to far. Are you?
      No, IMHO.
      --
      Confucius say, "Find worm in apple - bad. Find half a worm - worse."
    61. Re:Project GoneME by ross+axe · · Score: 1
      Besides, how hard would it be to make the mouse go to the "Confirm" button auto-magically by default?

      I have used such tools. They are f**king annoying.

      That would draw the user's eyes to it ...

      No, that would draw the user's mouse cursor to it. Cursor follows eyes, not the other way round. When your cursor jumps around, you'll lose it and have to move the mouse in order to find it again.

      Another advantage is if you decide to use the keyboard - enter does the trick, and tab goes to the cancel, as opposed to having to shift-tab to go backwards to cancel. It's a terrible, indefensible, setup.

      Remember that escape will also choose the cancel button. Also remember that on anything more than a simple yes/no message box, the focus won't be on the OK/Confirm/whatever button anyway.

    62. Re:Project GoneME by tomhudson · · Score: 1
      Why not make it user-configurable?

      They could set it the way they want, or turn off each type of dialog. I don't want/need any "confirm"-"cancel" dialogs.

    63. Re:Project GoneME by Vitus+Wagner · · Score: 1

      It is your workstation which ought to have sound hardware. And sole need of sound daemon is to provide programs which run on other machines ability to produce sound at the same place where they show their UI.

    64. Re:Project GoneME by mwood · · Score: 1

      A server has no need to produce sound anywhere. Just try taking sound support off your server and see the parade of software the package manager will want to remove.

    65. Re:Project GoneME by Vitus+Wagner · · Score: 1
      Oh, no! How can I live without my beloved xpat2?!!


      Taking this seriously, it is you who mentioned word
      "server", not I. Personally I think that "server" and "client" applied to computer it is something from evil marketing model of Microsoft and Novell.
      If we are talking about Linux there is no servers and clients, there are just hosts.

    66. Re:Project GoneME by mwood · · Score: 1

      Okay, I have a host room with racks of hosts in it whose purpose is to serve up files, grub through databases, monitor host and network operation, watch for attempts to penetrate security, and carry out scheduled background grunt work. None of those hosts have any reason to make sounds. Nobody is sitting there, physically or virtually, driving these machines; they drive themselves. People have hosts on their desktops for browsing, etc. The hosts I have in mind are not for personal use.

      I want to remove unneeded complexity, to reduce attack surface and failure points, but when I take out sound it also takes out nearly the entire administrative interface. That reeks of an attitude that says that the computer is a toy for playing Doom, and any actual work is just a sideline.

      Basically, if I don't need it for system administration, diagnosis, or the service the machine was installed to provide, the host is better off without it and I want to be able to remove it. Ideally I'd like never to have installed that rubbish in the first place.

    67. Re:Project GoneME by Vitus+Wagner · · Score: 1
      People should have terminals on their desktops. And these terminals shouldn't produce no unexpected noice (such as fans, disks etc) but sounds which are willingly produced by programs user willingly run. It is what sound servers are for - serve sounds for users from applications which run on some rack-mounted thing mile away.


      Host rooms typically quite a noisy place due to high performance cooling systems and 10000rpm disks.


      But what host room has to do with user desktop projects like Gnome and GoneME? Nothing except that some of these hosts may run same OS which can also be used for running end-user apps.


      I can imagine some of those hosts running end-user apps to serve bunch of X-terminals around. But person who manages such hosts would comprehand neccessity of sound server, so it is scarcely your case.


      BTW, I'm not aware of any hardware X-terminal which is able to run esound. But there is a bunch of them which understands NAS protocol.

    68. Re:Project GoneME by mwood · · Score: 1

      Exactly. There might be files on an NFS server which represent sounds, but the server itself has no use for them; those belong to the clients. A tripwire server doesn't have any business with sound. A PGSQL server doesn't use sound. Yet the server's OS has sound plumbed into a thousand different bits that I have to use for administrative control of the server itself. This makes the admin. interface even heavier and slower, it unnecessarily exposes the machine to attack, it's more things that can crash unexpectedly, and it eats up storage to no purpose. But if I yank the sound support, the package manager calmly begins deleting most of the administrative interface.

      I'd love to ditch the packaged OS and hand-build just what we need, and I think I'd actually save time in the long run by doing so instead of endlessly jousting with the package, but so far this has not been approved.

    69. Re:Project GoneME by Anonymous Coward · · Score: 0
      Ah, what you are whinning about! Administrative interface! Now it is quite understandable why I simply cannot find common language with you.


      vi is the Administrative interface. And it doesn't need any sound.


      Various silly GUI administrative applets just make admin's job harder, because admin have to understand basic principles of software he administers anyway, and it is enough to cope with plain text configuration files. But when using GUI based admininstration tools admin have to know both basic principles and GUI glitches.


      So, happily say good by to these silly applets and manage you servers using vi.


      And I was talking about productivity tools such as instant messengers, which need to produce sounds. And sound server is as important thing as X server to use them.

  3. Oh my god by Anonymous Coward · · Score: 1, Insightful

    Why do Linux desktops try to mimic Windows so much?
    Programers have no sense of aesthetics.

    1. Re:Oh my god by kfg · · Score: 1

      Why do Linux desktops try to mimic Windows so much?

      They don't. Only the few that do do.

      KFG

    2. Re:Oh my god by frankthechicken · · Score: 2, Insightful

      I feel it is mainly because in an open source world there is less of an ability to strictly test usability and functionality, as this requires a different set of abilities than purely that of programming expertise.

      Indeed, when there are already a couple of tried and tested UI's on the market (i.e. Windows and OS-X). And with the money having already been spent on user testing the interfaces, the question is why re-invent the wheel?

      Build on what has already been developed.

      Once the underlying core has been built then experimentation can begin, with the many eyes approach hopefully leading to an even more intuitive OS and GUI.

    3. Re:Oh my god by Anonymous Coward · · Score: 0

      Why do Linux desktops try to mimic Windows so much? Because that's what the lusers are used to. It would confused poor Windows users if their Linux desktop looked different...

    4. Re:Oh my god by Anonymous Coward · · Score: 0

      Yeah, great plan. Working out great...

    5. Re:Oh my god by black+mariah · · Score: 1

      The problem is that most major desktops try to imitate both Windows and OSX and end up with a severely fucked version of neither. Then again, what do I know? I use Fluxbox.

      --
      'Standards' in computing only impress those who are impressed by things like 'standards'.
    6. Re:Oh my god by Anonymous Coward · · Score: 0

      Is this sarcasm?

    7. Re:Oh my god by Frogbert · · Score: 1
      The problem is that most major desktops try to imitate both Windows and OSX and end up with a severely fucked version of neither. Then again, what do I know? I use Fluxbox.

      I think that Fluxbox is pretty much the definition of a severely fucked version of neither.
    8. Re:Oh my god by black+mariah · · Score: 1

      Yeah, it's quite fucked at first. But when your computer is as puny as mine is, you learn to love it. It's one of those things where I use it, I like it, but there's no damn way I'd ever recommend it to anyone.

      --
      'Standards' in computing only impress those who are impressed by things like 'standards'.
    9. Re:Oh my god by Anonymous Coward · · Score: 0

      uh, I use kde and I have it setup just like aqua, it allows the application menu bar to be embedded in the panel just like in aqua, and most of kde can be set to behave almost exactly like aqua except for the dock.

    10. Re:Oh my god by ViolentGreen · · Score: 1

      And the few that do are the ones that are the most successful unfortunately.

      --
      Not everything is analogous to cars. Car analogies rarely work.
  4. Gnome Usability? by Anonymous Coward · · Score: 0, Funny



    What usability?

    The tunnel of mirrors file browsing is from Satan.

    Satan.

  5. Gramer? by Anonymous Coward · · Score: 0, Offtopic

    How do you feel about spelling Nazis?

    1. Re:Gramer? by starnix · · Score: 1

      Humorous that in a post where you are correcting someones grammer that you spell grammer incorrectly.

    2. Re:Gramer? by starnix · · Score: 1

      ...as did I. Damn. My bad.... {embarassed}

    3. Re:Gramer? by maskedbishounen · · Score: 1

      Don't worry, this is only /., and we are all very understanding geeks! No one will ridicule you here. ;)

      --
      "An infinite number of monkeys typing into GNU emacs would never make a good program."
    4. Re:Gramer? by starnix · · Score: 1

      LOL

    5. Re:Gramer? by QCompson · · Score: 1

      you spelled embareassed wrong. oh wait...

    6. Re:Gramer? by Anonymous Coward · · Score: 0
      Humorous that in a post where you are correcting someones grammer that you spell grammer incorrectly.

      Humorous, that in a post where you are correcting someone's grammar, that you spelled grammar incorrectly.

      ...as did I. Damn. My bad.... {embarassed}

      Oh FFS...

      ...as did I. Damn. My bad.... {embarrassed}

  6. Re:gramer correction by Anonymous Coward · · Score: 0

    Live from the spelling nazi: it's grammar. Two 'A's. Weird, but that's life in the English-speaking world for you...

  7. I found the "Hesitant User" study most interesting by James+A.+V.+Joyce · · Score: 2, Funny

    Task #1 - Email

    * Clicked Applications right away
    * Discovered "Internet"
    * Discovered "Web Browser"

    (The above happened in less than 10 seconds)

    * Ignored "Start Here"
    * User admitted to not being used to clicking on Start Here and decided to go looking after the desktop did not have an internet icon
    * Clicked URL bar
    * Typed in URL
    * Logged in
    * "Fuck no I don't want to do that" referring to saving passwords, never saves passwords at home
    * Read mail

    Guess GNOME really IS a terrible user interface, haha. (Before you mod me as a troll, RTFA, they actually say this.)

  8. Re:KDE Rocks ... Gnome Sucks by bach37 · · Score: 1

    And with that above post, I hereby say: let the KDE vs. Gnome flame wars begin!!!!!

  9. Finally, a scientific review by Iesus_Christus · · Score: 5, Insightful

    It's good to see a fairly unbaised, objective look at an open source product on Slashdot. Many times, we see either a "OMG Open Source = good" or a "I couldn't even get it installed, this sucks!" in place of an actual review. In this instance, it seems as though the reviewers actually tried to make this a fair review. They used users with different experience levels to get an overall picture of the usability of Gnome 2.6. While they could have used more than one user for each stereotype for statistical reasons, it seems at though they have done a decent job in their review. It is reviews like this that show us what to work on.

    1. Re:Finally, a scientific review by HFShadow · · Score: 3, Insightful

      It seems to me they were reviewing the tools more then gnome itself. If trillian, winamp or windows media player have confusing controls, I don't blame that on Windows, I blame it on the respective products. So why do so many linux review sites do the opposite? Totem being unstable has nothing to do with gnome 2.6. Rythmbox not having easy to find radio stations has nothing to do with gnome 2.6. The crappy file browsing window DOES have to do with gnome 2.6 and they apparently didn't even review deeply enough into it to see it.

    2. Re:Finally, a scientific review by pdxaaron · · Score: 1
      I attempted to check out some of their other reviews to see exactly how unbiased their reviews are. Suprise, Suprise... There aren't any. If fact it appears that the content list on the main page is all that exists on the site.

      It looks like they just started adding content July 6th!?! You can take their review as gospel all you want, I'll continue to read reviews from people that have withstood the test of time and had a bit more scrutiny.

    3. Re:Finally, a scientific review by Anonymous Coward · · Score: 0

      Considering totem may land in GNOME sooner rather than later I'd say it's fairly relevant.

      And rhythmbox and muine are two of the main music players that have some semblance of integration into the GNOME desktop.

      Both of these apps are frequently mentioned in desktop-devel-list.

  10. Mod me down - but you gotta see this: by Anonymous Coward · · Score: 5, Funny
    1. Re:Mod me down - but you gotta see this: by LostCluster · · Score: 1

      Hey, it's on topic enough... Add more marketing glitz and your get a smoother user presentation, but you've gotta pay more for it. Glitz is the enemy of the geek, but it does attract the mass public dependably...

    2. Re:Mod me down - but you gotta see this: by Anonymous Coward · · Score: 1, Funny

      That ad is WAY too long.

      It was like getting a blow job from my father.

    3. Re:Mod me down - but you gotta see this: by MikeXpop · · Score: 1

      Anyone have a link for the now old Lindows Rock? I thought that was funnier*

      *not funnier, but stupider. In a funny way.

      --
      Etiquette is etiquette. He kills his mother but he can't wear grey trousers.
    4. Re:Mod me down - but you gotta see this: by Bullet-Dodger · · Score: 1

      The goggles, they do nothing! (Umm, ear goggles that is... oh never mind)

    5. Re:Mod me down - but you gotta see this: by Vanieter · · Score: 1

      Jim Morrison is truly dead.

    6. Re:Mod me down - but you gotta see this: by Anonymous Coward · · Score: 0

      Holy shit, I took 15mg of valium today and just had 4 glasses of wine, I'm practically tripping balls here and that freaked me outttttt man. Somebody went freaking AWOL with the marketing budget there.

    7. Re:Mod me down - but you gotta see this: by Anonymous Coward · · Score: 0

      That was truly well done. I like this company. The owner might be a little egomaniacal, but I think they have the best chance at pushing Linux to the unwashed masses. Make it appeal to the lowest common denominator, and you'll always have a winner. And that geek showing off his little Linux PDA at the bus station thought I was a fool for saying that...

    8. Re:Mod me down - but you gotta see this: by TrancePhreak · · Score: 1

      I don't think I'd ever buy something from a company that cannot have someone code HTML properly, let alone their Flash is badly optimized.

      After loading the page, it asked me to install Flash 7, even tho I already have the newest one from Macromedia's site installed.

      Then, during the movie, randomly there would be slowdown.

      --

      -]Phreak Out[-
    9. Re:Mod me down - but you gotta see this: by Anonymous Coward · · Score: 0

      Good thing, or he'd expect royalties.

    10. Re:Mod me down - but you gotta see this: by Anonymous Coward · · Score: 0

      Mixing a long half-life benzo with alcohol, are you stupid or what?

  11. yea, computers for ignoramises by Anonymous Coward · · Score: 0

    Hurray! Let's hear it for people who don't
    have the competence to use vim!

    1. Re:yea, computers for ignoramises by Anonymous Coward · · Score: 0

      I use Emacs, you insensitive clod! ;-)

  12. I use ion2 with gnome _and _ kde applications by ClarkEvans · · Score: 2, Interesting

    ion2

    For those with FreeBSD who hate the mouse...
    # cd /usr/ports/x11-wm/ion-2
    # make install

    1. Re:I use ion2 with gnome _and _ kde applications by Anonymous Coward · · Score: 0

      Screw the KDS vs. Gnome flamewar!

      Let the ion2 vs ion3 flamewar begin!

    2. Re:I use ion2 with gnome _and _ kde applications by Anonymous Coward · · Score: 0

      you mean the ratpoison vs ion flame war!

  13. The mass public is the ultimate test... by LostCluster · · Score: 1

    6, 7 or 8 users might not get you that much more information than you'll get from a 5 user test... but it's when the public at large gets ahold of your program that it's really put to the test.

    Like the article says, you need to hold a second testing group when there's a second classification of user who uses your program. And when you release you program to the public, if it's a truely good program than somebody will think of a situation in which to use the tool you made that you didn't antisipate.

    1. Re:The mass public is the ultimate test... by Anonymous Coward · · Score: 0

      shut up nerd

    2. Re:The mass public is the ultimate test... by Anonymous Coward · · Score: 0

      yea, yer fuck'n wanker

  14. Re:I found the "Hesitant User" study most interest by netsharc · · Score: 0, Troll

    * Didn't know how to use Ximian Open Office, so the user closed it immediately and sat frustrated

    Oh man, poor girl (my instincts say it's a girl, because guys just don't sit there being frustated), I somehow feel bad for her, perhaps ready to cry because the computer isn't working "right".

    Anyway, being accostumed to Windows, I find the quirks of Linux frustating as well, for example sounds never work 100% for me, without tweaking. Sure, I can read the HOWTOs and tweak it till it's perfect, but sometimes I don't feel like it, especially when there's so many other quirks that need tweaking..

    --
    What time is it/will be over there? Check with my iPhone app!
  15. Re:Mod parent up! Lol! by bach37 · · Score: 1

    Ha! Oh my that's crazy!

  16. Needs one more user... by riptide_dot · · Score: 1

    Good review - it's especially funny because its raw (unedited) format. I especially liked the part in the Mac/Systems Architect User's notes that said:

    "Task #4 - ICQ/Chat

    * Loaded Gaim

    * "Holy crap" at the number of protocols

    *...

    I didn't know I was being recorded when I said that! :)
    I thought the review could have used just one more user though - the Beginner who is NOT "hesitant" (as the article puts it).

    --
    I was in the park the other day wondering why frisbees get bigger and bigger the closer they get - and then it hit me.
    1. Re:Needs one more user... by MBCook · · Score: 2, Interesting
      I'm not sure that I've ever seen a beginner who isn't "hesitant".

      When users become more accustom to computers and they are intermediate, some users will charge head on into things and get them selves into trouble. Some don't. It just depends.

      But I've observed MANY people in my short career of helping neighbors and friends and such with their computers. When they are beginners, they fall into one of three categories. The first is those who hate the comptuer and fight it all the way. They learn how to do a thing or two and use that, and that's it. They won't do anything more because they could break something, etc. It's more than being hesitant.

      The second group would include my little sister. They learn what they're doing and will explore a tiny bit, but by and large stick to what they know how to do and programs they know. In those programs, they may explore and they'll become very familiar and comfortable with them. But when it comes to doing something new, they are hesitant.

      The third group is hesitant about everything. They are like the first group in that they never branch out into new things (group two will over time, very slowly). They just stick to what they know. That said, they don't feel like they are fighting the computer and are comfortable using the program. But they do no exploring like group two. They only learn things when they need them, and ignore them the rest of the time.

      Thinking about it the only group I can think of who ISN'T hesitant is the very little kid. I'm talking 2 or 3 years old. They don't know to be scared of the computer (or even consider being scared of it). They'll plow into the computer head on and they may break it. But I wouldn't consider these kids "users"; at least in the normal sense. They may use a program or two (Putt Putt Goes to the Moon, The Busy World of Richard Scarey, whatever) but they don't use the computer, you know what I mean?

      So in conclusion, there really aren't many "non-hesitant" users out there. They would be a rare bird (in my expiriance).

      An interesting article though.

      --
      Comment forecast: Bits of genius surrounded by a sea of mediocrity.
    2. Re:Needs one more user... by Ford+Prefect · · Score: 1

      I'm not sure that I've ever seen a beginner who isn't "hesitant".

      I have. And believe me, they're the worst kind possible. :-)

      You're giving them a guided tour of some web application, carefully describing what all the different sections do and so on. They're sat there with the mouse, not listening at all - but instead clicking on anything and everything that looks like it might be vaguely link-like.

      "This button is for deleting messages. You select - "

      (Click click click!)

      "You've just deleted the instruction manual. I'll show you how to retrieve it from the trash."

      (Clickety-click!)

      "Noooo!"

      You see them trying to start Lotus Notes.

      Double-click on icon.

      Nothing appears to happen in the first two seconds or so. Double-click on icon again, just in case.

      Still nothing, so double-click on icon again, and swear at computer.

      Ten minutes later, roughly fifteen copies of Lotus Notes finally untangle themselves enough for one of them to display a password prompt.

      The fact that I brought up Lotus Notes as an example probably indicates that this wasn't the very small child - at least with a child you can confiscate the mouse and/or keyboard. Instead, he's in his mid-sixties, and the kind of boss that you really wonder what their purpose of existence is. Fortunately, he's not my boss. Hah!

      --
      Tedious Bloggy Stuff - hooray?
  17. Mod Parent Up by Anonymous Coward · · Score: 0

    Best off topic post EVER.

  18. Window focus by pjpII · · Score: 1

    My biggest problem with the version of Gnome that I use(2.4.?) is that window focus is handled extremely poorly - if I click on any part of the window EXCEPT the task bar, the window doesn't gain focus, whereas in Windows and KDE, the default is to give a window focus no matter where you click, which is much more reasonable. I'm open to suggestions to fix this problem- I'm forced to use Gnome if I want to play music, since Xmms inexplicably doesn't work in KDE. If its not a user configurable option, I think it would be nice if this was fixed in the newer versions of Gnome.

    Also, regarding the debates about the spacial mode file browsing, I wonder why nobody has entered the idea of tree based browsers into the debate. I don't use the "My Computer" style of file browsing- the "Explorer" program, with a panel for a tree based view, works much better for me, and seems like a more reasonable standard than either the classic or the spacial style browsers.

    1. Re:Window focus by ErichTheWebGuy · · Score: 1

      KDE application for listening to music: Noatun. Lighter and better (imho) than xmms.

      --
      bash: rtfm: command not found
    2. Re:Window focus by JanneM · · Score: 1

      if I click on any part of the window EXCEPT the task bar, the window doesn't gain focus, whereas in Windows and KDE, the default is to give a window focus no matter where you click, which is much more reasonable.

      Um, something is broken for you - giving focus no matter where you click is the default behaviour for Gnome. Without more info, I have no idea what could be wrong, though.

      --
      Trust the Computer. The Computer is your friend.
    3. Re:Window focus by donscarletti · · Score: 1

      Hmm, that happened to me once, I think it's a bug, I find it hard to believe that they meant it to happen. It hasn't happened to me in 2.6 though which is very good.

      --
      When Argumentum ad Hominem falls short, try Argumentum ad Matrem
    4. Re:Window focus by harikiri · · Score: 2
      I really dislike the UI of both XMMS and it's Window's predecessor Winamp. They fall into the category of "lets make EVERYTHING skinnable", which makes your application look SWEET!! but near incomprehensible for users to figure out quickly.

      For that reason I'm a big advocate of making the desktop skinnable/themeable - as opposed to modifying individual applications. They result in user's having to pause and wonder why "X" particular application looks and behaves differently to the rest of the desktop.

      --
      Man watching 6 MSCE's around a sun box, looks alot like the opening scene's of 2001:space odyssey...
    5. Re:Window focus by Rethcir · · Score: 1

      I'm not really sure why you would say Winamp is incomprehensible.. the default buttons are standard cd-player type symbols! maybe we are getting to the point where people are using Winamp before they ever have a CD player! (I would however agree that Winamp 5's menus/options/configuration stuff is a little wacky, for example the notifications stuff seems to be split between the option tray that pulls out of the main interface, and on the right-click menu from the system tray. This is also a complaint of mine with most MS products, the options are not centralized in one place as they should be. (I would also make this complaint about linux, when I was using Red Hat in the labs at school I seem to remember separate "settings" and "preferences" folders for no good reason)

    6. Re:Window focus by swv3752 · · Score: 1

      It is a window manager setting, and I suspect that he is using sawfish.

      --
      Just a Tuna in the Sea of Life
  19. Re:gramer correction by io333 · · Score: 1

    Well, it happened. My life's dream is now fulfilled; as special bonus, I was stabbed by a spelling nazi too!

    I'm Slashdotted out, so I'm going out.

    COMPUTER OFF!

    Oh, that's not going to work until voice recognition in Longhorn. Darn.

  20. best part by mnemonic_ · · Score: 4, Funny

    'What the hell is "GNOME-gegl2.png"? "That's disgusting!"'

    1. Re:best part by feronti · · Score: 2, Informative

      Why, it's an extra sacred cow. No, really... in India, cows with extra legs are even more sacred than normal cows. I don't know if that's true for other deformities, and I did hear it from a friend who spent most of his trip to India high on hash, but that's what I've been told.

    2. Re:best part by ChristTrekker · · Score: 1

      Funny you should mention that. I just noticed it on my old LUG's web site today. (Look out for the Praetorians.) I never knew why (and nobody would tell me) why the favicon is a goat, either.

  21. Am I the only one ... by hayden · · Score: 1
    Who detests this drive towards "task based" interfaces? I find that it takes significantly longer to do anything that isn't explicitly spelled out by the interface. I always find myself searching through the options systematically because the task I want to do is something that's buried three screens deep, behind four hidden advanced option buttons and a moat of dire warning dialogs that promise all sorts of horrible things that'll happen to me if I dare continue. Then, in the next release, all the searching for what I want to change is now useless because the usability people tested a dozen people and decided that that option belongs in an entirely different task.

    I would prefer it if they'd have all the task based crap and then an advanced option for those people who can look for stuff on their own. Rather than having all the new fangled task based stuff and a two finger salute to the rest of us with an explaination of "it's easier". Not for me it bloody isn't.

    Maybe I'm just one of these oldies who believe you actually have to think (*gasp*) when using a computer.

    --
    Nerd: Derogatory term typically directed at anybody with a lower Slashdot ID than you.
    1. Re:Am I the only one ... by LostCluster · · Score: 5, Insightful

      In any menuing system, there is no rule that says that the menu has to be a true tree. There's nothing stopping you from having a main menu of "What are you here to do today?", and having the most popular functions being placed in more than one position on the interface.

      Doing it that way might lead to a more confusing set of decisions at design time, but the user will more often than not find themselves one click away from what they want to do next if you do it right. Afterall, it's easier to find any given option if it's "hidden" in three places instead of just one.

    2. Re:Am I the only one ... by FireBreathingDog · · Score: 0, Offtopic
      WARNING: Offtopic (-1)

      I've found the loophole in democracy.
      It's stupid people.
      Vast masses of stupid people.

      I suspect "stupid people" == "people who don't agree with you politically".

    3. Re:Am I the only one ... by AvitarX · · Score: 1

      I use alt-f2 in KDE

      and I am sure there is a similar in GNOME.

      The menues are only for when I am looking for something I don't know.

      FWIW

      --
      Wow, sent an e-mail as suggested when clicking on "use classic" banner, and got a fast response that addressed my msg
    4. Re:Am I the only one ... by Chagrin · · Score: 1
      Afterall, it's easier to find any given option if it's "hidden" in three places instead of just one.

      It's just a lot harder to find the one option hidden amongst the duplicates of others.

      --

      I/O Error G-17: Aborting Installation

    5. Re:Am I the only one ... by Anonymous Coward · · Score: 0

      Nope. There are stupid people on all sides.

    6. Re:Am I the only one ... by Anonymous Coward · · Score: 0

      I use alt-f2 in KDE

      and I am sure there is a similar in GNOME.


      There is. Thankfully it's alt-F2 =)

  22. Why emulate windows and not mac? by io333 · · Score: 4, Insightful

    Why isn't there an open source attempt to model what the folks in Cuppertino are doing? KDE and Gnome are both Windows copies. I think folks would switch in droves if they could get an open-source Mac copy to run on their PC hardware.

    I can't think of any incentive for switching from an XP interface to one that is almost as good as XP.

    1. Re:Why emulate windows and not mac? by LostCluster · · Score: 1

      Apple has since the begining of time brought in design consultants to work on every aspect of the user interface... meanwhile the geeks who design OSS projects absolutely want nothing to do with the design consultants. (The irony is that the stereotypical geek would love to date the stereotypical design consultant, but she won't go anywhere near him...)

    2. Re:Why emulate windows and not mac? by DeepHurtn! · · Score: 1
      I think folks would switch in droves if they could get an open-source Mac copy to run on their PC hardware.

      Yes, droves -- cuz there's such a huge demand for the proprietary Mac OS. That's why they outnumber Windows users twenty times over, right? ...oh sorry, it's actually the other way around, isn't it...

      I'm sorry, I really don't intend this as a Mac flame (honest!) -- but the reality is, the vast majority of desktops use Windows, and if you want your free desktop to have mass appeal, making it familiar to Windows users is the name of the game. Expecting a huge market for a free Mac-type OS when the original holds such a small share of the market (compared to Windows) just seems unrealistic to me.

    3. Re:Why emulate windows and not mac? by MoronGames · · Score: 1

      Actually, you can set up GNOME to have a dock similar to OS X's, and the menu bar also. GNOME gives a lot of freedom as to how you can use it. Of course, GNOME isn't as pretty as OS X.

      --
      hey!
    4. Re:Why emulate windows and not mac? by black+mariah · · Score: 1

      Gnome and KDE have both felt like a "not either one" amalgamation of lame Windows and Mac ripoffs to me. I don't see why they have to copy either interface style. It makes more sense, at least to me, to give Linux a look and feel of its own. I don't WANT my Linux and Windows boxes to behave the exact same. There are things about one that just don't work with the other's interface.

      --
      'Standards' in computing only impress those who are impressed by things like 'standards'.
    5. Re:Why emulate windows and not mac? by aixou · · Score: 5, Insightful

      This reminds me of when a friend proclaimed that he hated Linux (KDE to be specific), because it "feels like a shoddy copy of Windows"... It's funny for me to hear that from a Windows user, because that's how Mac users have felt for the past 10+ years in regard to Windows (shoddy copy).

      Seriously though, I really don't believe an OSS project could have the focus or resources to take on the task of keeping up with Apple's design. They might get the "look" right, but the "feel" is something much much harder to grasp. In the end all you'd have would be a dock clone, and a clunky interface. The Mac OS has always thrived on having the best UI consistency and a very intuitive feel, which is something that Linux just can't really compete with.

      Unix and Windows are much more similar to eachother than they are to the Mac OS. For one, both Win and *nix hide programs down deep in an arcane directory structure that you aren't expected to learn (you can, but most don't). On a Mac, you are expected to navigate the file system to access what you need (if you want to open an App for example, you open the Finder, go to the Applications folder and then open your app). Win and *nix don't really expect you to have to move to where you want ago, hence the usage of the Start menu and Shell PATHs which give quick access to what you need.

      An OSS project that copied the Mac would really be copying the Finder and the directory structure. In order to get the Mac feel down pat, you'd have to make the directory structure much more browse-friendly than it is. You can't expect grandma to navigate to usr, bin, and then select from a long list of programs what she wants. Unless a developer/distro with some major clout (i.e. one that wouldn't be completely shunned by the Unix world) decided to revamp the directory structure (or hide the standard tree in favor of a simpler user oriented one), I would recommend that *nix Desktop Environment developers stick the Windows-esque start bar clones that they already have.

      For now, if you want the Mac look and feel in a Unix environment, your only and best option is OS X.

    6. Re:Why emulate windows and not mac? by jdub! · · Score: 3, Insightful

      GNOME is generally closer to Mac OS than Windows, particularly given recent design decisions. We certainly DO NOT aim to clone either interface - we tend to think that the "not quite Windows" feeling has a strong, negative impact on training, worse than being obviously (and positively) different.

      Your distributor may set their GNOME defaults up to be familiar to Windows users, however.

    7. Re:Why emulate windows and not mac? by Anonymous Coward · · Score: 0

      Yes, droves -- cuz there's such a huge demand for the proprietary Mac OS. That's why they outnumber Windows users twenty times over, right? ...oh sorry, it's actually the other way around, isn't it...

      I know lots of people who would switch if Macs weren't so fucking expensive.

    8. Re:Why emulate windows and not mac? by poptones · · Score: 2, Insightful
      I find it funny when these "studies" say nonsense like "for open source to compete with windows it must handle these proprietary formats perfectly" - as if windows did that! How many times has YOUR browser been hosed by the bloated and buggy Acrobat? Anyone ever tried opening a powerpoint presentation in office97 that was created in office2k? Or for that matter opening a late model powerpoint presentation in microsoft's own powerpoint "reader" on a machine that doesn't have office?

      Open source doesn't have to do anything "perfectly" - and none of the competition does this either. What open source has to be is available - that's all. Because, after all, this is all that made windows "the market leader." The one thing that made windows what it is with a wink and a nod is built into the competition. No wink and nod needed - and as people find themselves increasingly sick of paying 100 bucks to the local geek to "clean" the web residue from their computer every six months, more and more will try it - and many won't turn back.

      I'm posting this now from a two hour old Suse kde desktop - just a quick note before I wipe it all out and go back (again) to mandrake. I just wanted to reply before all this gets lost to point out a couple of things.

      Having a dock does not make a mac clone to be sure - but neither does having an "explorer" browser and a window frame make a windows clone. And the reason some of us (like myself) don't use the mac (among other reasons) is because it, like windows, is just too limited. If I want a dock I have a dock - but I can make it dance any step I choose and I can make my desktop look and feel any way I choose. This is much harder on the mac and damn near impossible in windows.

      I don't care about a finder. I don't need a finder because when I install an app it's almost certain to be included in my path, which means all I really need to do to run it is invoke it by name. If I want a shortcut I make a shortcut and type the name of the app and whatever switches I want - so how is drilling down to the folder and clicking the app more intuitive? Just so I don't have to (shudder) TYPE something one time before using it?

      This is coming from someone who has had his own long and reluctant journey. Even now I still have a win2k partition on this machine because I was hesitant to make the complete switch - old habits die hard. But with the arrival of fantastic distros like Mdk10 and Suse9 and FC2 using windows increasingly feels "icky" - like driving around in a 1985 Taurus or something. Yeah, it works most of the time and it's familiar because the seat fits my ass after ten years at that wheel - but I hate being seen in public at that wheel and every time I step out of it I have to change clothes and shower because of the dirt and grease.

      Look: Grandma doesn't need a finder because Grandma doesn't have anything TO "find" except more arcade sites to occupy her time. Grandma doesn't install programs, gramma USES programs. Give grannie a desktop shortcut to a web browser that'll let her check her aol mail and play her pogo games and she'll be just fine. Give her all this in a computer that won't be brought to its knees by all the shit floating around those popup ads and grannie can die happy, a cigarette in one hand and her mouse in the other. Your only worry then will be how to clean up the rings left on the desk by her vodka tonics.

    9. Re:Why emulate windows and not mac? by DeathBunny · · Score: 1
      In order to get the Mac feel down pat, you'd have to make the directory structure much more browse-friendly than it is. You can't expect grandma to navigate to usr, bin, and then select from a long list of programs what she wants.
      How long has it been since you've used a Mac? Mac OSX has a /usr directory, a /etc directory, /bin, etc. just like any other unix. These unix directories are hidden from the Finder, but you can get to them from the command line. These Unix directories are supplimented by some additional directories such as /Applications. The /Applications directory for example holds GUI programs the user can click on to run.
    10. Re:Why emulate windows and not mac? by McDutchie · · Score: 1
      Why isn't there an open source attempt to model what the folks in Cuppertino are doing?

      ROX may be what you're looking for. While they say it's inspired by RISC OS (which I never used), it reminds me of Mac OS X (which I use) in a number of ways: extensive use of drag and drop, windows don't fill the entire screen, application directories, to name a few.

    11. Re:Why emulate windows and not mac? by iotaborg · · Score: 1

      You can't get anything like the dock in Gnome due to the windows-esque windowing order, i.e. task based instead of document oriented. That is to say, you cannot "switch" between programs, as in Gnome and in Windows, a firefox window and a pop up dialog from a different program take the same workspace level.

      As a Mac user, the lack of a clear hierarchal windowing system frustrates me when I work in Gnome at work. Switching between windows is more difficult than switching between programs i.e. on a Mac, however I find that Gnome is usable when virtual desktops are employed (which allows me to 'emulate' program switching). On the other hand, virtual desktops are near useless to me on my Mac.

      As for the menu system, you don't really get anything like OS X's menu bar as windows have their own menu bar. I don't really mind this that much, however you can increase a bit of screen space if there was a single shared menu bar.

      Speaking of menus, why did Gnome and all these programs have to emualte the horrible Windows shortcuts anyway? I.e. alt+f4 (long finger reach) to close a window, cntrl+c to copy (control using the pinky instead of alt using the thumb), etc. Sure, Gnome lets you customize some of the shortcuts, but it hardly holds among different programs (OS X has an incredible keyboard shortcut modifier). And then the whole clipboard fiasco, oh boy.

    12. Re:Why emulate windows and not mac? by Anonymous Coward · · Score: 0

      "Seriously though, I really don't believe an OSS project could have the focus or resources to take on the task of keeping up with Apple's design."

      They said the same thing about Open Source and modern drivers/hardware support, file systems, AA, True Type Fonts, audio and video codecs, apps and plugins yet they are easily approaching that level on all those fronts. If you think UI is a sacred cow that is untouchable, you are wrong.

      "They might get the "look" right, but the "feel" is something much much harder to grasp."

      I call BS

      "Unix and Windows are much more similar to eachother than they are to the Mac OS. For one, both Win and *nix hide programs down deep in an arcane directory structure that you aren't expected to learn (you can, but most don't)."

      Oh come on I remeber resource forks and the like on MacOS. No no similarities to the Windows and Unix way there. Hell under the hood apps are not launched the same way as Linux at all right?

      "On a Mac, you are expected to navigate the file system to access what you need (if you want to open an App for example, you open the Finder, go to the Applications folder and then open your app)."

      Ya just like going to the Programs folder.

      "Win and *nix don't really expect you to have to move to where you want ago, hence the usage of the Start menu and Shell PATHs which give quick access to what you need."

      Ya completely unlike the dock.

      "An OSS project that copied the Mac would really be copying the Finder and the directory structure. In order to get the Mac feel down pat, you'd have to make the directory structure much more browse-friendly than it is. You can't expect grandma to navigate to usr, bin, and then select from a long list of programs what she wants."

      So they need an easy and consistant and streamlined directory structure presentation layer. Yup that is impossible.

      "For now, if you want the Mac look and feel in a Unix environment, your only and best option is OS X."

      If it really is that good it will be adopted by some OpenSource distro and then copied just like RPM and DEB or LSB etc. Sorry but Apple is the new guy on *nix and if they can do it, the barrier to entry is not as great as you make it out to be. Really though (and I know this is going to get me flamed) but really I dislike OSX's UI and think it is just as bad as Windows XP's (both Classic and Luna) but for different reasons. It doesn't get in my way as much and uses less clicks to do the same things and is consistant but is confining and spartan in functionality. That opinion is after two years of daily use on my iBook and the rest on a T40 ThinkPad. Honestly though to me neither camp has found the holy grail. Then there is the Linux camp that is fairly bad but you know what, I would give it the most improved UI for the last two years running. If it can sustain its progress it will be better than OS X sometime in the next 4 years or so. If you don't believe me I'll scan a few dozen articles and letters from folks who said the Linux desktop would never reach Windows 98's level. It already has surpassed it in most regards. When it did, it did so by leaps and bounds not a slow steady pace.

      Now of course Apple and Windows will have new UI's by then but if you really love OS X now and think it is good enough, will you completly hate it or something better in four years?

      I could go for an improvement in all three and I think we are far from the last furlong in this race to satisfy users.

    13. Re:Why emulate windows and not mac? by dh003i · · Score: 1

      Yuck, the fact that you're forced to navigate directories in Mac OS SUCKS. Fortunately, they have the Apple menu, but those retards did away with that in OSX, where the Apple Menu doesn't include a list of most programs. Navigating through menus is much quicker than navigating through a file-system.

    14. Re:Why emulate windows and not mac? by Srin+Tuar · · Score: 1

      On a Mac, you are expected to navigate the file system to access what you need (if you want to open an App for example, you open the Finder, go to the Applications folder and then open your app).

      That sounds really unscalable- just as soon as you have more than a handful of "applications". Since it clearly cannot list every single installed program, it must only list commonly run gui applications. So it is in fact a menu stuffed into the filesystem.

      A user shouldnt ever have to deal with the filesystem outside of their home directory.

    15. Re:Why emulate windows and not mac? by aixou · · Score: 1

      How long has it been since you've used a Mac?

      I use OSX everyday and spend a fair amount of my time in the Terminal. I'm well aware that OS X has a standard (but hidden to the Finder) Unix directory tree.

      Mac OSX has a /usr directory, a /etc directory, /bin, etc. just like any other unix.

      I guess I was a bit vague when I said "you'd have to make the directory structure much more browse-friendly than it is". I didn't mean that you'd have to change all the directories around, but that you'd probably want to hide your typical Unix dirs from the filebrowser, and make Gui apps easily accessible and executable from the filebrowser (just like in OSX, which I tried to imply). In Unix, unlike OSX, GUI apps and command line apps reside in standard Unix paths (/bin /usr/bin etc). My point was something like this:

      * To emulate the Mac OS feel, you'd have to create a filebrowser that could execute GUI apps easily (e.g. opening firefox in konqueror).

      * As the current Linux directory structure stands however, this isn't feasible. Firefox (or the symlink to the shell script that executes it, if you want to get technical) resides in /usr/bin, and /usr/bin no matter how you cut it, is not a filebrowser friendly directory (I would never in a million years point my grandma to /usr/bin). I'm not saying you would need to do away with standard Unix directories, but it would be advisable to hide them from the filebrowser (ala Finder in OSX)

      * Currently, most Linux Desktop Environments emulate the Windows way of launching programs (a startbar clone that hides the true location of the programs), which works just fine for the present setup, but not for a Mac interface. Since a true Mac interface would be GUI driven, windowed apps would need to reside in a filebrowser friendly directory (e.g. /Applications).

      Five years ago, Apple faced the same problem that any would-be OSX Gui cloner faces today: wrapping a Mac interface (driven by a filebrowser) around a Unix core. I think they succeeded marvelously, but its certainly not an easy task to accomplish, and I don't believe that it is really feasible for an OSS project to do (see my first post) unless it was being spearheaded by a company with a lot of respect, time, and money.

    16. Re:Why emulate windows and not mac? by aixou · · Score: 2, Insightful

      That sounds really unscalable- just as soon as you have more than a handful of "applications".

      The "Applications" folder on my Powerbook contains 102 items, a very manageable and navigable amount imo.

      A press of the tab button in the terminal reveals that I have 1602 command-line apps.

      If I had to wade through a directory with 1704 (the sum of my command-line and /Applications apps) executable programs to find the GUI program I wanted to use, I would go insane.

      The way Apple laid it out is very practical, and might be an important pattern to follow as more and more 3rd party developers ship GUI driven apps to the Linux platform.

    17. Re:Why emulate windows and not mac? by coaxial · · Score: 1

      A user shouldnt ever have to deal with the filesystem outside of their home directory.

      You've never worked in a collaborative environment before have you? There's always shared directory trees, and they're never in home directory.

    18. Re:Why emulate windows and not mac? by Tim+C · · Score: 1

      How many times has YOUR browser been hosed by the bloated and buggy Acrobat?

      Acrobat takes down the web browser, and somehow that's Windows's fault?

    19. Re:Why emulate windows and not mac? by 10Ghz · · Score: 1
      KDE and Gnome are both Windows copies


      How exactly are they copies? because they have a taskbar like Windows does? Because they have windows like Windows does? Really, if things like that are what makes an UI "a Windows copy", then just about ALL UI's are "Windows copies" in one way or the other!

      OTOH, if you are referring to the fact that both try to give the user an integrated UI (and since you singled out the two desktop environments, I think you are referring to this), instead of mishmash of unrelated applications, then yes, they are Windows-clones. And I would in that case wish that there were more "Windows copies" for Linux!

      I can't think of any incentive for switching from an XP interface to one that is almost as good as XP.


      I use XP at work, and KDE at home. And I can tell you that using KDE is a breath of fresh air when compared to XP! For me, KDE is not "almost as good as XP", it blows XP away!
      --
      Lesbian Nazi Hookers Abducted by UFOs and Forced Into Weight Loss Programs - -all next week on Town Talk.
    20. Re:Why emulate windows and not mac? by MrHanky · · Score: 1

      It's interesting how every comment praising OS X gets modded up these days. Even insightful for spewing nonsense like 'I really don't believe an OSS project could have the focus or resources to take on the task of keeping up with Apple's design.' As if proprietary software has 'focus' and 'resources' as some magical property that is impossible to attain with other licensing models. I've got karma to burn, so I'll burn it while posting this from my Powerbook.

      KDE might look like a shoddy copy of Windows to the novice, because it's only vaguely like this "original'. It's not a copy, and has loads of features making it far more usable to the experienced user, while being not so different that it alienates the beginner.

      The same goes for OS X. Finding an app with the Finder isn't more effective than finding an app with a start menu, at least not for the beginner. I know, because I've been one, and a quite advanced beginner at that. My first task was to find Terminal.app so I could use 'file' to find out why Word couldn't open some .rtf file. Then I had to find the .rtf file I wanted to run 'file' on, but Terminal.app and Finder had quite different opinions on where the file could be found (yes, drag & drop works, but I'd closed the Finder window by then, since all the windows cluttered the desktop). The Finder has become a bit better with Panther, but before that, it wasn't any easier to navigate with than with Explorer or Konqueror (and it could be argued that it still isn't). After all, it just does the same thing as any other file browser, but without an 'up' button -- a great idea for browsing a hierarchy! Not that Finder really uses the directory structure, most of it is hidden from view. If you want to use OS X as a Unix workstation, your best option is to ignore Finder, because Finder hides all the Unix stuff in OS X.

      (OK, this was just a bunch of incoherent drivel, but the point is that OS X isn't perfect. I've used it extensively the last months, but I still prefer KDE.)

    21. Re:Why emulate windows and not mac? by Srin+Tuar · · Score: 1


      There's always shared directory trees, and they're never in home directory.


      Ah, collaboration done wrong: a shared directory tree.

      Do yourself a favor: learn about version control.

    22. Re:Why emulate windows and not mac? by theCoder · · Score: 1

      Acrobat takes down the web browser, and somehow that's Windows's fault?

      In the same way OpenOffice not being able to perfectly read a Word file is somehow Gnome's fault, or a great hinderence to its success. I think that was the OP's point.

      I'm not too impressed by this review, especially this comment (which the OP also hit on):

      If the Microsoft Word document someone emails the user must be opened in an application that does not display it correctly, the user will assume that the system is at fault.

      Then why do users blame me when I send them OpenOffice sxw files? Or blame me when I PGP/MIME sign my mail and their client doesn't know how to handle the signature? I think user's expectations are a little out of whack in that they expect Windows and MS software to always do the right thing (but they aren't surprised when it doesn't), and expect Linux to be broken and buggy. Now, I'm not immune to that -- I'm usually surprised when I can do something new in Linux with minimal hassle, but a lot of these usability studies assume a fundamental knowledge of Windows, and if the system isn't Windows like and doesn't mimic Windows software perfectly, it doesn't pass muster.

      Linux (and Gnome/KDE and other software) do not have to be clones of Windows to be good. In fact, I'd prefer if they weren't :)

      --
      "Save the whales, feed the hungry, free the mallocs" -- author unknown
    23. Re:Why emulate windows and not mac? by ViolentGreen · · Score: 1

      OK. I have been trying to refrain from posting to this topic but I am compelled to here.

      Like the XP interface (and colors) or not, it is consistant and fairly simplistic. The default fonts and text sizes are reasonable.

      I do not find this to be the case for KDE. The default theme gets in the way. The style selector shown on first load is a step in the right direction but it still doesn't do it for me. For me to use KDE, I have to sort through hundreds of the ugliest themes I have seen at kdelook.org to find one that doesn't get in my way. On top of that, I have to still adjust my fonts.

      I don't need this. If you all have time to completely configure every aspect of your system then that's great. I don't. With all its faults, Gnome works better for me out of the box.

      --
      Not everything is analogous to cars. Car analogies rarely work.
    24. Re:Why emulate windows and not mac? by wobblie · · Score: 1

      Please, next time someone says "KDE and GNOME" are copies of windows", be sure to note exactly what the fuck way either one of them is any-fucking-goddamn-way like motherfucking windows, 'cause I just don't see it. Not at all. Maybe it's because you're using some godforsaken linux distro (Red Hat, Sun JD, ad nauseam) that goes out of it's way to make them look like windows - now that is possible. Please look beyond that or make an attempt to see KDE or GNOME at their true defaults. Absolutely NOTHING, NOTHING like windows.

      Does windows have a panel? Nope.
      Does windows have multiple desktops? Nope.
      Does KDE or GNOME have stupid crap like drive letters, or "my computer"? Nope.

      I could go on forever, but I'm getting bored with this. Just stop repeating this lie and educate yourself. Just because the more popular distros are trying their damndest to make their desktops look like windows, doesn't mean they are. If they all tried to make KDE look like CDE (very easy to do), would you morons be complaining that KDE was a CDE knockoff?

    25. Re:Why emulate windows and not mac? by 10Ghz · · Score: 1
      I have to sort through hundreds of the ugliest themes I have seen at kdelook.org to find one that doesn't get in my way.


      The favourite toned-down style for KDE these days is Plastik. It should suit your needs. Keramik (the current default) wont be changed in a minor release, so it will be dropped in KDE4.

      On top of that, I have to still adjust my fonts.


      I have to do that as well. It takes me about 2 minutes to change them to my liking. I do hope that Helvetica will be dropped as the default font.

      If you all have time to completely configure every aspect of your system then that's great. I don't.


      You can't spare 15 minutes? OK, to each on his own I guess....
      --
      Lesbian Nazi Hookers Abducted by UFOs and Forced Into Weight Loss Programs - -all next week on Town Talk.
    26. Re:Why emulate windows and not mac? by Anonymous Coward · · Score: 0

      For me to use KDE, I have to sort through hundreds of the ugliest themes I have seen at kdelook.org to find one that doesn't get in my way.

      And I have to sort through hundreds of ugly themes to make gnome have something more interesting than a windows95 colorscheme. Your point?

    27. Re:Why emulate windows and not mac? by the+narf · · Score: 1
      But there is an 'up' button: Command-click on the title bar of any Finder window and it will show the hierarchy, where you can select the enclosing folder, or any folder up to the root. Also, if you have the Finder set to "open folders in the same window" mode, there's a browser-like set of "forward" and "backward buttons.

      Also. the Panther Finder lets you customize the button bar in each window to include a "hierarchy" drop menu icon that lets you get at this feature without having to reach for the Command key.

      In addition, Command-Up Arrow will show the folder containing the current folder if that folder is being displayed in List or Icon view. Command-Option-Up-Arrow will open a new window with the contents of the enclosing folder and will close the current window.

      Hope all this helps...

    28. Re:Why emulate windows and not mac? by MrHanky · · Score: 1
      Hope all this helps.

      It certainly does. Thanks!

      But all this also counters the claim that MacOS is so immediately intuitive -- many of the useful features of the GUI are a bit too well hidden for my taste (but hey, I said I like KDE, so that's kind of obvious, isn't it?). The command-clicking stuff is also just a crutch because the Mac lacks the right mouse button -- and that makes it less likely for a noob to command-click. You're not 'supposed' to do that.

      There are lots of thing I really like with MacOS -- the separation of window and app (close the window, but keep the app running in the dock), which annoyed me at first, because command-tab would only browse between apps, but later I noticed command- for browsing between the app's windows made this seem logical again (and a better way to do it).

      It's logical, but it's hardly any more intuitive than, say, Windows. But then Windows is just illogical at times, so MacOS clearly wins there.

      But OK, maybe the Finder is better than I thought it was. I didn't like it at all.
    29. Re:Why emulate windows and not mac? by the+narf · · Score: 1
      It also turns out that if you install a 3-button mouse (or a 2-button-plus-scroll-wheel model, for that matter) Mac OS X will happily use it.

      Left-click is normal Mac click.

      Right-click is the same as Control-click (brings up contextual menu if available at the spot under the cursor

      Moving the scroll wheel does what you'd expect -- scrolls in most apps (but not ones running under Classic unless a 3rd party extension is installed).

      Clicking the scroll wheel (as if it were a mouse button) will do "middle-button click" in X11 apps. (So you can use the "select-middle click" paradigm in xterms, etc that you might have beamed to your OS X system from other computers or running locally...

      The shortcuts for the various apps included in OS X are documented. Open Mac Help (from the Help menu) in the Finder, and type "shortcuts" into the Search field.

      By the way: have you discovered Exposé yet for dealing with highly-cluttered screens?

    30. Re:Why emulate windows and not mac? by MrHanky · · Score: 1

      Yes, I know how a mouse works in OS X, thank you very much. :-) It works as expected, which is a bit unexpected for a system that normally relies on a one button mouse: Why have only one button when three just works better? I also know how to use my one button trackpad like a three button mouse, and how to use it in X11 (I actually started learning Emacs in X11 on OS X -- the native LaTeX editors I tried were lacking quite a bit. This means I've used X11 in OS X a lot).

      I didn't mean to sound negative -- I like OS X a lot, at least Panther. It's just that the Mac zealotry on /. has become more dominant than the Linux zealotry, and it's often even more stupid (Gentoo fans excepted). Apple fans can be a bit like football fans: They follow their team no matter what, and think they're somehow better because they support just the right team. It's the "One True Way" attitude that annoys me so much.

      Exposé is a nice feature, but I much prefer not having clutter at all, i.e. virtual desktops. It looks much better, though. And it was one of the things that made Panther a whole lot better than Jaguar.

    31. Re:Why emulate windows and not mac? by the+narf · · Score: 1
      Apple sticks with the one-button mouse because the broadest target audience for Mac OS X is not people like you or me -- it's Aunt Tilly who just wants something (relatively) simple that she can use to surf the Web, write letters, send and receive photos, etc. I can't tell you how many Aunt Tilly-type Windows users I know who are utterly confused by right-clicking versus left-clicking.

      The problem in Windows is that there are operations that are very hard to do, if not impossible, without being able to right-click. On the other hand, there is no function in Mac OS X that requires right-clicking. It just makes those things easier for experts.

      I look at the Mac UI as being like an onion: It looks very simple and limited, and indeed can be used quite effectively by only learning a very small handful of operations, and with a very uncluttered UI. It's approachable. It's friendly. It's not intimidating the way Windows and the Windows-like Linux GUIs can be to newbies.

      The apparent superficial simplicity of OS X, however, belies the power and capabilities that lie underneath. Thus, as a new users gain experience and confidence using it, they can learn more of the shortcuts and more sophisticated features. In effect, as you peel back layers, you discover more and more things that let you work more effectively. I've been using Mac OS X since version 10.0, and Macs in general since 1986, and I still discover new hidden nuggets about the interface.

      And of course, once they've mastered everything there is to know about the GUI, there's the whole UNIX universe under the hood just waiting to be discovered.

      Yes, I sound like one of those blathering Mac evangelists. On the other hand, I've used an awful lot of computers in my 30+ years of dealing with them. Everything from 110-baud Teletypes connected to a DEC PDP-8/e to TOPS-20 to VMS to various UNIXes (with and without GUIs), plus CP/M, DOS, Windows, and Mac.

      The really funny thing about all this? If you asked me what my favorite OS was from a usability point of view, I'd definitely say Mac OS X. However, if you asked me what my most favorite UNIX variant was, my answer would be Tru64 UNIX. I won't elaborate on the reasons here, but most of them have to do with how well designed and implemented are its filesystems, clustering, and other high-end features. No other commercial UNIX OS comes close.

  23. Couple things I do not Like, by Anonymous Coward · · Score: 0

    First off they reccommend "a higher level of abstractation", which is sort of BS. You see it in 2 examples:

    1. They should hide the terminal.

    -- Nobody has to use it if they don't want. However a user interface can't be designed just for newbies. In order to be efficient you have to make it usefull. Terminals are very usefull. You need it still, and hiding it isn't a good idea.

    Lots of directions you face will, even for newbies , especially with troubleshooting would be like:
    type ifconfig in the terminal.
    type dmesg in the terminal.
    type ps aux in the terminal.

    This isn't difficult stuff. You open up the terminal and type it in.

    --2. This one realy showed me that some of their advice is completely worthless.

    They want to make the level of abstraction of error messages to be higher?

    HELL NO. You want the error messages to tell you almost exactly what is going on, you want to have even MORE information aviable. Ever use "mplayer"?

    The goal isn't to scare a user, it's to make it actually USEFULL.

    New users need help. They come to me, first thing I ask? "What was the error message?", if it's very abstract it's also very worthless.

    The guys who wrote this article obviously have quite a bit break from reality, and want to have computers be freindly, happy, and virtually useless.

  24. Will gnome die? by omar_armas · · Score: 3, Interesting

    I tried hard to use Gnome 2.6 as my primary desktop, but I gave up in favor of KDE.
    Some reasons:

    -Too slow
    -not so well integrated
    -doesn't feel a unified system(shortcuts, menus, etc)
    -Again, too slow. Every release it gets slower.

    The have changed enlightenment for sawfish, then for the actual wm.
    The same happened for the file manager: gmc, then nautilus
    And for the browser: galeon, nautilus, epiphany, now mozilla?
    A very poor control center. Example: try to add virtual desktops from the control center. It's impossible, it's hidden in the desktops applets.
    It's a mess, since the people funding the project dedicated to other things, Gnome seems to have lost direction.
    To me, Gnome is just a desktop bar, all the enviroment and other apps doesn't feel really integrated.

    Omar

    1. Re:Will gnome die? by Roguelazer · · Score: 0, Flamebait

      Wow. You think back a long way. Lemme see... Sawfish was the default WM in Gnome 1.4, and enlightenment was an option. Therefore, enlightenment must have been the default before that. Metacity has been the default WM since earrly in the 2.0 series.

      And are forgetting something about KDE? You complain about gmc (which hasn't been the filemanager for Gnome for several years. Around the same time, kde changed from KFM to Konqueror...

      And Epiphany is still thedefault browser. The progression was this, actually: Galeon->Ephiphany. Mozilla was never official, and nautilus isn't even a browser.

      And if I hear one more KDE user complaining about Gnome's slowness, I'm gonna be confused. Wait, I'm confused already. EVERYTHING about KDE and Qt is slow. One of Gnome's plusses is that Gtk is very snappy- and so therefore is Gnome.

      As for integration, I'll take the fact that I can use my Gnome apps in other WM's without waiting for a 10 minute *_init startup procedure, whereas KDE with its KParts and DCOP makes all KDE apps useless anywhere else.

      Finally, as for the Control Center, well, at least I can find applets. I mean, heck, KDE has what, a hundred control center applets? A new user (I upgraded from KDE 1.2 to 3.0- big step) needs to use the Search function to do ANYTHING.

      PS: Right-click on pager, hit Preferences. Pretty simple...

      PPS: Yes, I understand that this will be modded -1 Troll. Oh well. :/

    2. Re:Will gnome die? by Anonymous Coward · · Score: 1, Insightful

      What are you talking about? Seriously.

      If GNOME 2.6 is slow, take it up with your distribution.

      I've been running GNOME since before 1.4, and I find the speed of 2.6 fine on my 850mhz pIII (320mb RAM). Additionally, I find 2.6 the fastest of the 2.x releases (but I eschew gnome-terminal in favor of xterm because it is quite slow due to pango).

      As far as shortcuts and menus, I'm not sure what you're talking about. You do know about applications:/// right?

      Anyways, enjoy KDE. I've tried it on and off over the years, and I'd rather not use it.

      Er, and as far as people funding the project dedicated to other things, are you talking about Novell? They're only a small part of the people currently contributing, and they're more interested in mono. What about Red Hat and Sun who both base their desktop on GNOME? I'd say they certainly have vested interest.

    3. Re:Will gnome die? by Anonymous Coward · · Score: 0

      And for the browser: galeon, nautilus, epiphany, now mozilla?

      Galeon is Gnome based has never been part of the standard desktop. As for Mozilla, that certainly isn't a part of the desktop either, though some distros may use it as the default.

      Epiphany is the only browser to have been made part of the standard desktop release - before it, there was no standard browser.

    4. Re:Will gnome die? by TrekCycling · · Score: 2

      KDE is fast? Breaking news to me. I've been using Gnome since 1.4 IN SPITE of its usability problems because it doesn't require 256MB of RAM and run like a turtle hitting the bong. I agree that copying Windows is dumb, but most people use Windows, so maybe that's their thinking.

    5. Re:Will gnome die? by Moritz+Moeller+-+Her · · Score: 0, Troll

      > ... complaining about Gnome's slowness, I'm gonna be confused. Wait, I'm confused already.

      You are confused. Evidence:

      > EVERYTHING about KDE and Qt is slow. One of
      > Gnome's plusses is that Gtk is very snappy- and > so therefore is Gnome.

      Well at least gnome terminal sucks donkey balls. I have started it in icewm (neither KDE nor GNOME preloaded) and it took 25 sec to start! For a terminal! konsole took 5 seconds. (This is an old Athlon 600 MHz)

      The best thing about gtk apps is that you can use
      the gtk-qt theme, which gives those apps the refined KDE look.
      See here http://www.freedesktop.org/Software/gtk-qt

      --
      Moritz
    6. Re:Will gnome die? by nonmaskable · · Score: 1

      And if I hear one more KDE user complaining about Gnome's slowness, I'm gonna be confused. Wait, I'm confused already. EVERYTHING about KDE and Qt is slow. One of Gnome's plusses is that Gtk is very snappy- and so therefore is Gnome.

      I'm a KDE user myself (having last used GNOME at 1.4). After seeing so much discussion of spatial nautilus, I installed GNOME and lived with it for a week. I liked spatial, but KDE 3.2 is quite a bit snappier than GNOME 2.6. I didn't look into the reasons myself, but I have read that it's due to Gtk changes in recent years.

      All the other things I don't like about GNOME are still there but discussing them would be -1 troll, so...

    7. Re:Will gnome die? by lucas+teh+geek · · Score: 1

      -not so well integrated

      wtf are you talking about? gnome is beautifully integrated with gnome apps. oh... i think I get it, you 'tried' gnome, but wanted to use all your KDE apps instead of the nicely integrated gtk equivilants.

      --
      TIAEAE!
    8. Re:Will gnome die? by Anonymous Coward · · Score: 0

      I'll start using Gnome or KDE when they switch to developing on 80386 machines. 850 MHz + > 300 megs of RAM to run a basic desktop GUI? Give me a break. I have a fast machine and I'd rather be using that power for something else (like pr0n) ;-)

    9. Re:Will gnome die? by Roguelazer · · Score: 1

      s/refined/Fisher-Price And those figures are impossible. Konsole requires kde_init, which takes at least 30 seconds to start. I use gnome-terminal in rox (nothing preloaded) and it starts in 5-10 seconds.

    10. Re:Will gnome die? by Moritz+Moeller+-+Her · · Score: 1

      kdeinit takes more time the FIRST time after KDE is installed (or updated) because it (re)builds the ksycocache (the binary configuration database that lets gregistry=gconf look awkward). After that kdeinit takes no more than 3 or 4 seconds max on my Athlon-600MHz.

      I don't know rox very well, it is not in Debian. Isn't rox done in gtk? And is rox not a FILEMANAGER? Probably the session management of your WM reloaded all the gnome processes in the background.

      --
      Moritz
  25. Interested in knowing by timmyd · · Score: 2, Interesting

    Has anyone done usability tests on GNOME (or KDE for that matter) with respect to internationalization? Last time I checked, most applications are written just for the English speaker and typer. It seems like to get a good setup with all the programs in the appropriate language, you need to restrict yourself to a specialized distribution..which isn't a great option if you need to support more than one language.

    With gtk2's new input module support, it has made it easier to input languages which require a more complex method, but that is only limited to those gtk2 programs. So if you were using KDE, I think you would have to use input methods that talk through X, which are very unfriendly. On the other hand, it seems like windows has the advantage here of everything using the same toolkit which has pretty good internationalization support.

  26. Tests with five users by Anonymous Coward · · Score: 1, Interesting

    This is off-topic so you can moderate accordingly, but is there a similar limit for governments? For example, in science fiction there is often the assumption that a single world government is the most efficient, but perhaps some other number would actually be better. Competing economic systems and philosophies might actually be beneficial, so the fall of communism might not have been the unalloyed good fortune it seems -- after all, the space race is what actually pushed us to the moon.

    It seems to me this is what the Founding Fathers had in mind when they created the United States, to have several groups of people not only in cooperation but in competition with each other so new ideas would be continually generated and tried, but I'd be curious to see other's ideas if this comment is still visible.

    1. Re:Tests with five users by xenocide2 · · Score: 1

      For example, in science fiction there is often the assumption that a single world government is the most efficient, but perhaps some other number would actually be better

      Well, its not exactly science-fiction, but George Orwell predicted 3 superpowers in a gridlock. Of course, the prime goal of the warfare was to rid the world of their excessive capacity in meaningless landwars in africa and Asia. So perhaps the vision Orwell put forth doesn't qualify as "efficient."

      --
      I Browse at +4 Flamebait

      Open Source Sysadmin

  27. Comment removed by account_deleted · · Score: 1

    Comment removed based on user account deletion

  28. Re:I found the "Hesitant User" study most interest by BiggerIsBetter · · Score: 1

    What I found interesting was the expectations people had and that the results a) don't necessarily show Gnome only - font handling, system setup, etc. Also, the test subjects? I mean, you're given a system to test, and "experienced Unix user" is all set to download and install Mozilla? FFS. Finally, recommendation 5 appears to be written by someone with no clue about how the software industry works.

    --
    Forget thrust, drag, lift and weight. Airplanes fly because of money.
  29. Recommend to get rid of (useful) error messages? by ruckerz2k · · Score: 1

    Less common cases like the error message shown above should also be abstracted if possible. Knowing that the operation is not permitted offers little help to the unaccustomed user. GNOME already does an outstanding job in catching many of these types of errors and translating them into something users can understand. It is the hope of the reviewers that the developers continue in this regard. I dunno I prefer to have rather verbose error messages. Though it may not mean much to the common user, it can be quite helpful if they seek help from a more knowledgeable user. Besides, why change it? all you can (usually) do is click ok anyways.

  30. Re:Just Fucking Kill Gnome Off by sn0wman3030 · · Score: 0

    Send a message to that dimwit miguel that he's no longer welcome in th Linux world.

    I'm sure that would terrify him.

    --
    Life is offtopic.
  31. I was thinking of ditching XP... by danharan · · Score: 1

    At the risk of starting a flame-war (please, I know this is /., but there's no need for that), can anyone tell me if Gnome is more usable than KDE? Are they both putting the same amount of effort in making their desktops user-friendly?

    One of the more interesting things in that study was their list of tasks... Now that the problem is broken down in smaller pieces, it might be fun to test several designs in rapid iterations (tweak, test on 5 users, repeat) concentrating only on 2-3 tasks at a time. Oh- perhaps the most important question: how easy is it for people interested in usability to get involved in either project?

    --
    Information: "I want to be anthropomorphized"
    1. Re:I was thinking of ditching XP... by JanneM · · Score: 4, Insightful

      Are they both putting the same amount of effort in making their desktops user-friendly?

      I would say that Gnome has had it as an explicit focus for a lot longer than KDE, and has been working a lot more on various aspects of usability. One example is the (always ongoing) effort to make the desktop fully accessible to people with disabilities - an effort that pays off for the rest of us as well, in the form of a more consistent desktop and some fun toys (like screen readers) to play with :)

      As to which desktop is actually the better one for you - well, that's up to you, really. Try both for a time, and select the one you are more comfortable with. Or don't choose; alternate between both as the mood strikes you. Either desktop's applications work fine under both, after all, and interoperability between them is steadily improving.

      What you absolutely should do is to ignore all the flamewars and sniping on places like /. - most people dissing one or the other desktop are pretty clueless fanboys that only embarrass the mature users and developers of their chosen desktop.

      --
      Trust the Computer. The Computer is your friend.
    2. Re:I was thinking of ditching XP... by RedPhoenix · · Score: 1

      Caveat: I'm primarlly a gnome user.

      If you were a new computer user I'd suggest trying gnome. Of the several computer newbies I've introduced to Linux thus far, Gnome seems to be 'easier' for them to get around.

      Although both the Gnome and KDE teams seem to be equally interested in usability, Gnome has been lucky enough to snare some external companies who put a fair bit of time, money and effort into the task (most notably, Sun & Redhat).

      As you're a XP user though, I suspect KDE might be closer to what you're used to, and might be worth trying first. Perhaps, grab knoppix (which is KDE), and have a play.

      Red.

    3. Re:I was thinking of ditching XP... by Anonymous Coward · · Score: 0

      What you absolutely should do is to ignore all the flamewars and sniping on places like /. - most people dissing one or the other desktop are pretty clueless fanboys that only embarrass the mature users and developers of their chosen desktop.

      Wha! Clueless? Fanboys? I am a KDE fan and everyone knows Gnome sucks. For proof I only provide you the stupid 'styles' people dream up. WE only need one style, one way!

    4. Re:I was thinking of ditching XP... by xutopia · · Score: 1, Insightful
      Your question is perfectly valid. I enjoy generalizing things and I hope that this is a good way to express things.

      If you are an XP user you'll be accustomed to many Windows placements and ideas that have been carried over to KDE (start menu, placement of things in general). However KDE is cluttered and there is no central document that KDE developers can refer to in order to achieve proper usability. So they usually end up having applications with a lot of clutter. If you are familiar with usability tenets you'll know that giving users too many choices is the same as giving them none at all. Every option you give a user is a choice he has to make. Sometimes he doesn't want to make a choice, he just wants to get stuff done.

      Gnome has the Human Interface Guideline'. The document is a comprehensive guide which can be used to do "higification" on an application. I find that most Gnome applications tend to follow the HIG and the result is a more consistent desktop. It takes some getting used to for Windows users though because things aren't "in their place". However once you spent a week using Gnome you find it hard going back to Windows. Many say the same about KDE but my personal opinion is that Gnome is despite being different than XP and will need a bit more getting used is the more usable Linux desktop around.

      For anyone moving from Windows to Linux I recommend you arm yourself with patience and a good friend that can coach you through the change.

    5. Re:I was thinking of ditching XP... by bogie · · Score: 4, Insightful

      " However KDE is cluttered and there is no central document that KDE developers can refer to in order to achieve proper usability. "

      Let's be fair here. How many Gnome/GTK apps have their own File dialogs? Regardless or Gnome's HIG's, KDE's apps all tend to look and act like they were designed for one another. This is opposed to many of the marquee what I call "adopted" Gnome apps that don't integrate well with Gnome at all. Compare that with how Konq, Koffice, on Kontact work within KDE. KDE does in fact have more options, or what your calling "clutter" but overall its still more consistant then Gnome although that's finally started to change. Gnome also has the habit of making major interface changes between versions. Dialog boxes have been switched around and now the most fudemental way in which you interact with your OS ie file browsing has been turned on its head with Spatial. No warnings, no this is optional in 2.6 but will be switched on in 2.8 etc. KDE on the other hand has stayed consistant in the basic ways that matter for years now. The HIG's the Gnome devs go by are nice but they aren't some magic beans which have fixed all of Gnome's issues. Users from XP should try both and see what they like more, but I'll also say that IMHO KDE continues to be the more polished better managed project of the two.

      --
      If you wanna get rich, you know that payback is a bitch
    6. Re:I was thinking of ditching XP... by magefile · · Score: 1

      Try Knoppix (KDE-based), then Gnoppix (Knoppix, but GNOME rather than KDE). They're bootable CDs, so no need to install. I think GNOME looks nicer; but it's really a personal preference.

    7. Re:I was thinking of ditching XP... by MikeCapone · · Score: 1

      The best way to find out is to try both. Most distros come loaded with both (hey, they are free!) so do the testing yourself.

      Personally, I much prefer KDE. It's getting better and faster all the time, and after it's customized to one's liking, it's great.

    8. Re:I was thinking of ditching XP... by 10Ghz · · Score: 1
      I would say that Gnome has had it as an explicit focus for a lot longer than KDE, and has been working a lot more on various aspects of usability.


      That depends on what's meant by "usability". I gave GNOME a spin, and became frustrated when it seemed to constantly get in to my way. I had hard time making the system behave like I wanted it to behave. In KDE I don't have such problems, since I can easily alter the UI to be exactly what I want it to be.

      Like I have commented earlier in /., GNOME (or more precisely, it's developers) seem to think that they know best what the user wants. KDE doesn't make assumptions like that, but rather, they put the user in charge.

      As to which desktop is actually the better one for you - well, that's up to you, really.


      Agreed. While I found that GNOME is not my cup of tea, I can see why many people love it. The best way to find out which one is the rigfht desktop, is to try them both.
      --
      Lesbian Nazi Hookers Abducted by UFOs and Forced Into Weight Loss Programs - -all next week on Town Talk.
    9. Re:I was thinking of ditching XP... by 10Ghz · · Score: 1
      However KDE is cluttered


      Not really. Well it might be if compared to Gnome's ultra-mininalist style. But uncluttering KDE is NOT difficult. Really, it just takes few minutes.

      and there is no central document that KDE developers can refer to in order to achieve proper usability.


      What's this then?

      Every option you give a user is a choice he has to make. Sometimes he doesn't want to make a choice, he just wants to get stuff done.


      Really? So I'm REQUIRED to go through every single configuration-option KDE has to offer? Uh, no. While KDE has lots of options the user can tweak, I only touched handful of those when I configured the desktop to my liking.

      I find that most Gnome applications tend to follow the HIG and the result is a more consistent desktop.


      Well, I have found KDE and KDE-apps to be VERY consistent, so I fail to see the problem here.

      Many say the same about KDE but my personal opinion is that Gnome is despite being different than XP and will need a bit more getting used is the more usable Linux desktop around.


      For me, "usability" means "The UI acts and behaves the way I want it to act and behave. The UI must adapt to my style of working, and not the other way around". With Gnome I had serious problems making it work the way I wanted it to work. With KDE I didn't have any problems. I guess the root-cause for that is that GNOME assumes that it knows best what the user wants, whereas KDE doesn't make that kind of assumptions.
      --
      Lesbian Nazi Hookers Abducted by UFOs and Forced Into Weight Loss Programs - -all next week on Town Talk.
    10. Re:I was thinking of ditching XP... by sploxx · · Score: 1

      If you are familiar with usability tenets you'll know that giving users too many choices is the same as giving them none at all. Every option you give a user is a choice he has to make. Sometimes he doesn't want to make a choice, he just wants to get stuff done.
      I disagree. Make everything configurable but provide sensible defaults. Display the more important options first. Make a button which opens an extended dialog for the more intricate options.

      I use a mixed gnome/KDE environment (Gnome as my main desktop, and KMail and other stuff from KDE) and despite of mainly using Gnome, I think KDE got it right. Look at the print dialog. Not many options, but there is the small button in the lower left corner...

      Yes, maybe I'm in a very small minority but I sometimes use obscure options/features in programs. Over time, I get accustomed to them.

      Trying to keep features leads to bloatware? IMHO, bloatware is more the result of too tight coupling of the various modules behind the scenes. If features get removed and are instead available as plug-ins, everyone is happy and the main application remains small and stable.

    11. Re:I was thinking of ditching XP... by Tukla · · Score: 1
      If you are familiar with usability tenets you'll know that giving users too many choices is the same as giving them none at all.

      If this is the sort of illogical crap that usability "experts" believe, it's no wonder developers tend to ignore them.

  32. Certification by IceFox · · Score: 3, Interesting

    I like the idea of creating a HIG certification program of sort, but not for Gnome, but for all of the Unix/Linux desktop. Why? If you have a Gnome certification then of course core Gnome gnome apps will strive to be compliant and so will some others, but it wont really go farther than that.

    Maybe start a freedesktop.org project. This way open office, KDE, Gnome, SDL, wine (hehe), and other applications will be interested in making sure that their applications are compliant. It will probably be harder, but the payoff will be a hundred times better. Not only will you get Gnome apps all interacting with each other, but you will have all the rest of the Linux/BSD/Unix apps working alone side nicely.

    Another reason why this would be a good freedeskop.org project is because all of the other work that is being done there. Stuff like making sure your application uses the standard desktop icon names when referencing icons (so either Gnome or KDE icon sets work in both KDE and Gnome apps).

    Having a little list of current compliment HIG applications would be a major incentive for apps to get on that list too. Maybe it would even spawn a little compitition about keeping/getting all of their apps (kde/gnome/etc) compliant.

    -Benjamin Meyer

    --
    Do you changes clothes while making the "chee-chee-cha-cha-choh" transformation sound?
  33. "An usability"? That makes my fucking eyes bleed. by Anonymous Coward · · Score: 0, Offtopic

    Only precede words with the "an" article if the word in question starts with a vowel SOUND. Merely having a vowel as the first letter of the word is not a sufficient qualifier.

    The hard "y" sound, as in usability (yoosability) does NOT require the "an" article.

    For fuck's sake, just say it aloud, and you'll quickly realize it's stupid as hell. Fucking damned pedants who can't even get it right - that's all this world needs.

  34. The most anoying usability-quirk in gnome.. by Mr2cents · · Score: 1, Interesting

    They put buttons in the 'wrong' order.. Normally it's Ok/Cancel, with Gnome it's Cancel/OK!

    Aaaarg!

    --
    "It's too bad that stupidity isn't painful." - Anton LaVey
    1. Re:The most anoying usability-quirk in gnome.. by LostCluster · · Score: 1

      I don't know if either is more correct, but since most of the world is conditioned into expecting OK to come first, you'd better have a good reason for changing up the order or a lot of people are going to get annoyed, and having a reputation for annoying people is not a good thing.

    2. Re:The most anoying usability-quirk in gnome.. by JanneM · · Score: 3, Informative

      Nope, it isn't. Gnome does not use "Cancel" or "OK". If you find a dialogue that uses those, please file a bug report.

      What you have is: the safe choice to the left; the unsafe choice to the right; and other, less frequent choices in between.

      --
      Trust the Computer. The Computer is your friend.
    3. Re:The most anoying usability-quirk in gnome.. by Mr2cents · · Score: 1

      Exactly, it's like driving on the left/right side of the road. It's so banal you would expect no problem in reaching a standard. Yet in both cases it is proven wrong.

      For driving I can accept historical reasons, but Gnome is much younger than the 'OK goes to the left'-consensus.

      --
      "It's too bad that stupidity isn't painful." - Anton LaVey
    4. Re:The most anoying usability-quirk in gnome.. by JanneM · · Score: 1

      OK, I will buy a red and a green sock to remind me which is left and which is right. You'd think I'd know it after 35 years... It is the other way around, of course.

      --
      Trust the Computer. The Computer is your friend.
    5. Re:The most anoying usability-quirk in gnome.. by Anonymous Coward · · Score: 0

      Now you understand - by having trapped yourself - how people feel when using a mixture of KDE, GNOME and Motif applications. One time OK is on the left, another on the right. It's braindead and must be fixed and GNOME definately is in the underlaying side here.

    6. Re:The most anoying usability-quirk in gnome.. by JanneM · · Score: 1

      I trapped nothing. I confused which side is "left" and which is "right". Yes, I can be that disorganized, and no, don't trust me if I try to give directions...

      --
      Trust the Computer. The Computer is your friend.
    7. Re:The most anoying usability-quirk in gnome.. by tepples · · Score: 1

      but Gnome is much younger than the 'OK goes to the left'-consensus.

      Classic Mac OS came before GNOME, and it too put cancel on the left and the affirmative verb on the right.

    8. Re:The most anoying usability-quirk in gnome.. by trouser · · Score: 1

      also predates Windows, not that Windows should be taken as any kind of standard or example.

      --
      Now wash your hands.
    9. Re:The most anoying usability-quirk in gnome.. by transient · · Score: 1

      Shouldn't the safest choice be on the right? The rightmost button appears in the same place in every window, so it's the easiest button to locate and click. The position of the leftmost button depends on the number and width of the other buttons.

      --

      irb(main):001:0>
    10. Re:The most anoying usability-quirk in gnome.. by JanneM · · Score: 1

      It is.

      As you see in my other post here, I managed to mix up "left" and "right". And for my triumphant return engagement, I will not only mix up the names of my siblings, but also forget what day of the week this is!

      --
      Trust the Computer. The Computer is your friend.
    11. Re:The most anoying usability-quirk in gnome.. by transient · · Score: 1

      I suppose it would help if I read all the replies before posting my own. :-)

      --

      irb(main):001:0>
    12. Re:The most anoying usability-quirk in gnome.. by Snaapy · · Score: 1

      Personally I am big "cancel/ok" hater, but I think I can justify my reasons...

      Shouldn't the safest choice be on the right? The rightmost button appears in the same place in every window, so it's the easiest button to locate and click. The position of the leftmost button depends on the number and width of the other buttons.

      No. There are two different dialog cases: confirmation dialogs (yes/no/cancel, ok/cancel) and option dialogs (lots of stuff and ok/apply/cancel). Dialog sizes vary and buttons are mislocated anyway. However, usually the lower right corner is used for buttons if buttons cannot be centered for the dialog.

      The button order should be "positive actions" on left and "negative actions" on right. There is a simple reason for this. You read in all western languages from left to right. Also, in western ideology you expect the most positive option to come first.

      When you are doing something a more common use case is to execute the action instead of cancelling/preventing it. E.g. when you save file you usually want to overwrite, but still you might want to cancel if you have accidentally pressed a save button at a wrong moment. You are saving a file, press a save icon and suddenly pop-up dialog "should this file be overwritten". Then you start reading options from left to to right... you are seeking for "yes" and the faster you find it the better is the usability.

      And more about corners... according to Fitt's law every corner is equally good if the initial cursor position cannot be fixed. Optimal situation would be that the buttons would be located at the nearest corner of a mouse pointer, but jumping buttons would confure user. The lower right corner is best, because when you read from up to down, from left to right, the confirmation for choices is presented as a last item, after reading through all choices you are making.

      Just my 2 eurocents.

    13. Re:The most anoying usability-quirk in gnome.. by Spicerun · · Score: 1
      They put buttons in the 'wrong' order.. Normally it's Ok/Cancel, with Gnome it's Cancel/OK! Aaaarg!

      Can't say I have any sympathy for you. If you can't take a moment to actually read what's on the button before clicking it, you get what you deserve. I bet you'd have fun with the unregistered version of Winzip whereas everytime it is started, the license acceptance buttons are switched (ie-Don't Accept/Accept first time, Accept/Don't Accept next time, Don't Accept/Accept the 3rd time, etc.)

      By The Way, I'm a Gnome User of many years.

    14. Re:The most anoying usability-quirk in gnome.. by BigSven · · Score: 1

      Certainly the most annoying quirk is not the button order (I love it), it's the idea that dialogs should not have a "Cancel" button. While it is of course perfect to have settings from a dialog apply instantly, you still want to be able to back out your changes by using the "Cancel" button.

      Imagine you accidentally change a setting, it applies instantly and now you have no way to go back to the old setting unless you remember exactly what it was. That is a serious usability problem and IMO the HIG authors have been on some rather bad crack when they suggested to remove "Cancel" buttons all over the place.

    15. Re:The most anoying usability-quirk in gnome.. by Hognoxious · · Score: 1
      it applies instantly and now you have no way to go back to the old setting unless you remember exactly what it was.
      That's your broblem with 'Cancel'. Does it mean 'OK, on second thoughts don't do what I first suggested' or does it mean 'crivens! undo what I just did'? They're similar but not the same.
      --
      Confucius say, "Find worm in apple - bad. Find half a worm - worse."
  35. Verbose error messages by sbszine · · Score: 1

    I like giving the user a simple message, then adding a 'Details' button for the stack trace etc.

    --

    Vino, gyno, and techno -Bruce Sterling

    1. Re:Verbose error messages by multriha · · Score: 1

      So you're the guy that made me spend an hour trying to explain to my father what a stack trace was!

  36. Err, too late troll! by Anonymous Coward · · Score: 0

    I already started the flame war
    here

    get quicker to the draw dude.

  37. your Sig by geekoid · · Score: 1

    the plural for Ninja, is Ninja.
    You must now sing the Ninja song!

    --
    The Kruger Dunning explains most post on /. http://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect
    1. Re:your Sig by Anonymous Coward · · Score: 0

      If you toss in a [sic] the pedants will shut up.

    2. Re:your Sig by simm_s · · Score: 1

      A quick dictionary search at www.m-w.com (Merriam-Webster) states that the use of the plural form ninjas and ninja are both correct.

    3. Re:your Sig by Anonymous Coward · · Score: 0

      Personally, I use Ninjai. Like Virii or Hoppopotomi, etc.

      People sometimes look like I might cough up a hairball, but that's the way ti goes.

    4. Re:your Sig by Anonymous Coward · · Score: 0

      Why the hell would you quote YOURSELF anyway??? I'm so sick of seeing slashdotters with obscure out-of-context quotes from some 80's anime that NOBODY will understand, too. ARGH. time to start modding people down based on sigs.

  38. Be proud of who you are. Post as yourself. by Ilan+Volow · · Score: 4, Insightful

    Ali,

    While I completeley disagree with your feelings about where the GNOME project has taken things (I think they should have gone much further and totally flipped off the unix geeks and shouldn't have blindly copied so many of microsoft's mistakes), I do respect you for your decision to fork, as the GNOME guys have been complete and utter jackasses about many things (such as usability, or lack thereof). I have had the same idea as you, albeit to fork GNOME in a completely opposite direction with the Clarux project and making GNOME far more mac-like. While I totally disagree with what you're doing, I'm glad at least someone had the same idea, even if it does run counter to mine.

    One piece of advice to the opposition: the Free Software community says they promote freedom, but often, that's not the case. A while back, I created a fork of KDE that removed some really stupid usability problems the project had refused to deal with for years. I provided all my changes as source code people could download, I complied with the GPL, but Freshmeat refused to post the project because they considered it "only a patch". If you do something considered "significant" like modify someone else's code, it can be considered a distribution. But if you modify something that the Free Software community considers "insignificant", like the user experience, it's only considered "a patch". People in the Free Software development community might tell you "if you think you can do better, make your own version"; the thing is, they don't really mean it. So I'm warning you now, if you are really planning on forking a major desktop environment, you won't be able to rely on traditional community outlets for promoting it.

    Last piece of advice--post as yourself. Stop this silly oGaLaxYo/Anonymous Coward crap. Post as Ali Agaa, be proud of your opinion, and be proud of what you're trying to stand up for and accomplish (even if it is rather silly).

    --
    Ergonomica Auctorita Illico!
    1. Re:Be proud of who you are. Post as yourself. by 7-Vodka · · Score: 4, Insightful

      LOL dude,
      Since when does Freshmeat = the open source community?
      They are a 'unix program website' with every type of license included like proprietary stuff.
      If anything you should have tried sourceforge first right?

      --

      Liberty.

    2. Re:Be proud of who you are. Post as yourself. by Anonymous Coward · · Score: 0

      > If anything you should have tried sourceforge
      > first right?

      I avoid sourceforge at all cost. I have
      never seen a more disorganized and unituitive
      presentation of information in my life. Besides
      what percentage of projects a sourceforge are
      actually active and viable, 20-30 percent? As
      if I have nothing better to do than wade through
      however many abandoned projects litter source-
      forge. It ought to be called graveforge.

    3. Re:Be proud of who you are. Post as yourself. by Ilan+Volow · · Score: 0, Flamebait

      1. Pragmatic Issues

      a) SourceForge a the hosting site. Freshmeat is an announcing site. The two serve entirely different needs.

      b) The same people who run SourceForge (OSDN) also run Freshmeat. I couldn't trust OSDN to not delete announcements for my project. Why the hell should I give them the power to delete the disk space which contains all my work and any CVS commits from contributors?

      2. Broader Issues

      The interesting thing about the Open Source community is that they present themselves as a single entity when they talk about how they're united and taking over the world and how damned superior Open Source is. But the instant someone has a problem, whether that problem is something like the way they've been treated by the OSS community, usability problems, etc, the Open Source community dissolves into a random collection of people who accuse the person with the problem of criticizing a random collection of people, none of whom represent Open Source. And once they're done chewing that person out, they go back to being a "single entity" that considers itself united in its struggle to take over the world through its "better" method of creating software.

      Guerrillas and paramilitary death squads have similar "attack as one->disperse into a large anonymous crowd that can't be attacked->regroup->attack" MO's. And so do proprietary companies who try to deflect criticism by breaking the product up into a million vendors each of whom doesn't accept responsibility and blames the other vendor.

      It's ironic how more and more the Open Source community resembles the people they preach against.

      --
      Ergonomica Auctorita Illico!
    4. Re:Be proud of who you are. Post as yourself. by Anonymous Coward · · Score: 1, Insightful

      The interesting thing about the Open Source community is that they present themselves as a single entity when they talk about how they're united and taking over the world and how damned superior Open Source is.

      Rubbish. However SOME people may present the open source community I have no doubt at all that you KNOW that it's a disparate bunch of incividuals and organisations. Obviously "they" haven't ever presented themselves as a single entity. Some individuals or groups within them may have done. If you want to rail against particular statements by OSI or FSF or Linux Torvalds or Slashdot ACs or whoever then go ahead but pretending that you thought that open source really was some sort of single minded collective is stupid.

      Apart from anything else, you've identified yourself as part of this community, making amendments to open source software and distributing it. Did you think that you were subsumed into this single entity? Are you responsible for Freshmeat's policies? Are they responsible for yours? Try to get a grip on realirt.

    5. Re:Be proud of who you are. Post as yourself. by FooBarWidget · · Score: 1

      Yeah not all projects are still maintained. So what? How does the existance of other projects on SourceForge interfere with YOUR project? Are you scared other projects become zombies and magically kill off your project in the middle of the night or something?

      And you don't even know the number of Windows closed source freeware apps that go under every year.

    6. Re:Be proud of who you are. Post as yourself. by FooBarWidget · · Score: 1

      You can say the same thing about the Windows community. Or the Slashdot community. Or the OSnews community.

    7. Re:Be proud of who you are. Post as yourself. by Anonymous Coward · · Score: 0

      Ali is a crazy troll.
      http://geocities.com/aliakcaagac/

    8. Re:Be proud of who you are. Post as yourself. by scrytch · · Score: 2, Insightful

      One piece of advice to the opposition: the Free Software community says they promote freedom, but often, that's not the case

      Oh gosh, Freshmeat refused to list my variant, I'm being opressed. Look at poor poor me, oppressed by Freshmeat and the whole OSS community.

      When Sourceforge, Savannah, and Berlios all reject your project, you might have a point. All you are doing right now is whining.

      --
      I've finally had it: until slashdot gets article moderation, I am not coming back.
    9. Re:Be proud of who you are. Post as yourself. by 7-Vodka · · Score: 1

      Don't be so puerile. You know *very* well as given in your post that the Open Source community is not a single entity.
      For fuck sakes, the "community" can't even decide what "Open Source" really stands for. A lot of people who claim to be in this group don't even know the difference between 'Open Source' in general and 'Free Software' which is a much more well defined term.
      Anyone who claims that the OS community is a "single entity" is obviously misrepresenting the truth.
      You already know this.
      Yet what's funny, is that here you are criticising the "OS community" as if it were a single entity.
      Does that seem right to you?

      --

      Liberty.

  39. Need more than 5 users... by Anonymous Coward · · Score: 2, Insightful
    Too many of the users were familiar with Microsoft software. Are they testing usability or similarity to their previous experience. If they are testing similarity then by having most users familiar with Microsoft, they will get a pre-ordained answer -- the more it looks like Microsoft the better.

    Also, how about Chinese user, Hebrew user, Arabic user, to test language differences in the interface. How about blind user, disabled user? Even illiterate user? I am not joking. Check out the Simputer.

    1. Re:Need more than 5 users... by nutshell42 · · Score: 1
      Testing users who never sat in front of a PC before was valid 10 years ago. Today almost everyone is using a PC at least sporadically and in most cases that means Windows.

      While having people from different backgrounds makes sense if you limit yourself to only 4 users it makes equally sense to concentrate on Windows and Unix users because that are the backgrounds new users come from (Windows users: new to Linux, Unix users: *much* more likely to start using GNOME than a Windows user).

      --
      Don't think of it as a flame---it's more like an argument that does 3d6 fire damage
  40. Awesome by Nailer · · Score: 2, Insightful
    I want the Gnome guys to understand two things:

    • It doesn't matter if spatial nautilus is good or bad. Overriding people's existing preferences without asking them is always bad.

    • If you're being paid to work on Gnome for a business, do more of what that businesses clients want. Not less. Currently, most Red Hat staff/customers (who aren't Gnome developers) don't like spatial nautilus. A challenge for the Gnome devs is to either convince those people otherwise (by making it better or explaining its usefullness, not overriding people preferences). If they can't, it shouldn't be the default for EL4.
    1. Re:Awesome by YellowBook · · Score: 1
      It doesn't matter if spatial nautilus is good or bad. Overriding people's existing preferences without asking them is always bad.

      In this case, there were no existing preferences to override -- spatial navigation was a new feature. There was no choice to use spatial navigation in the old Nautilus; the feature wasn't there. The preference for spatial vs. browser couldn't have been being overridden if it didn't exist.

      And no, the "open every folder in a new window" option under the old Nautilus was not spatial navigation, so there would be no sense in following that preference.

      --
      The scalloped tatters of the King in Yellow must cover
      Yhtill forever. (R. W. Chambers, the King in Yellow
    2. Re:Awesome by Nailer · · Score: 1

      I'll rephrase, not using the term 'preference':

      Changing the default behaviour of someone's desktop without asking them (or even informing them) them is wrong.

      Doesn't change much.

  41. I choose to value post count less than you by tepples · · Score: 2, Insightful

    You can take their review as gospel all you want, I'll continue to read reviews from people that have withstood the test of time and had a bit more scrutiny.

    You can choose your reviews based on ad hominem criteria involving post counts; I'll choose my reviews based on the abstract and then weigh each conclusion based on the evidence that the review presents.

  42. Eeeewwww! by Anonymous Coward · · Score: 0

    That's sick. Moderate down, please.

  43. Look at it THIS way. by khasim · · Score: 3, Insightful

    The Linux kernel and the GNOME desktop did NOT GET IN THE WAY of the applications for those users.

    You're correct about too much time being spent on the applications. But that's how most users operate. They spend the MINIMUM time possible interacting with the desktop and the MAXIMUM time interacting with the applications. (Aside from playing with backgrounds and sounds. I hate webshots.)

    Personally, I think that a tiny bit of work on that study and the NEXT study would show Linux being incredibly easy to use even for novices.

    #1. Get rid of the unstable apps. Each icon that they click on MUST launch an application and that application MUST be the most stable of the bunch.

    #2. Populate the desktop with the apps they'll be trying to find (nothing like making it easy for them). This is what I do at work. And remove any other icons. They can put other ones there when they are more comfortable with the system.

    #3. Put the controls for changing the background and the sounds in a very visible location and name them something like "Cool effects". Then give them lots of pictures and sounds to choose from.

    So, the desktop would have the "My Computer" (or whatever) icon.

    The "My Network Places" (or whatever) icon.

    The "Recycle Bin" (or whatever) icon.

    The "Work applications" folder/link icon.

    The "Cool effects" folder/link icon.

    The "Games" folder/link icon.

    The "Help" icon (context searchable, etc).

    Also, once you've run through with each of the testers the first time, have them form small groups and run through the test again. In the workplace, they will talk to each other and share tips/hints/ways to install spyware crap/etc.

    Does the desktop facilitate or hinder that kind of human interaction?

    And toss in a screensave as a background option just to give them something that Windows doesn't do. :)

    1. Re:Look at it THIS way. by dtrent · · Score: 1

      Personally, I think that a tiny bit of work on that study and the NEXT study would show Linux being incredibly easy to use even for novices.

      This isn't a test they are trying to beat, it is an objective survey.

  44. er, we've got a gnome hacker here... spouting FUD by Anonymous Coward · · Score: 0

    Spewing anti-KDE nonsense. KDE is and has always been better at internationalization... it was written by Germans for heaven sakes! Stop spouting FUD, please?

  45. forgot one observation in conclusion by flacco · · Score: 0, Troll
    missing:

    "User #2 is a little bitch."

    don't tell me the F/OSS community doesn't understand usability!

    --
    pr0n - keeping monitor glass spotless since 1981.
  46. na, only the developer need test the code... by Anonymous Coward · · Score: 0

    screw users....

  47. Re:Just Fucking Kill Gnome Off by Anonymous Coward · · Score: 0

    Who the fuck cares about terrifying him.

    As long he stops damaging Linux with his crap.

    Get the little shit a job a Microsoft.

  48. Comment removed by account_deleted · · Score: 1

    Comment removed based on user account deletion

  49. That button order is a Windows artifact by Anonymous Coward · · Score: 2, Insightful

    Did you really mean Unix experts, or did you mean Windows experts?

    Do you have some justification to offer for your changes other than, "Windows does it that way?" And what does the way Windows does thing have to do with so-called Unix experts.

    I completely fail to understand what the big deal is with the Gnome button order. I have been a Windows user since Windows 3.1 and a computer user since many years before that.

    I have used Gnome. Until someone mentioned it on Slashdot, it never occurred to me that it was somehow difficult to understand the button order. In fact, the "button order" as an object of any thought or criticism had never occurred to me.

    Frankly: what is the problem here? Do you operate your computer in a dark, smokey room while wearing sunglasses? Or is your Gnome installation suffering from a misconfiguration issue such that buttonfaces are flat blank and you must guess as to their function?

    If you can make Gnome better, then by all means do so. But I'm just having a difficult time conceiving of how it might come to be that this is an issue for someone. Utterly mad.

    1. Re:That button order is a Windows artifact by Anonymous Coward · · Score: 0

      You might like to read the page that the Link is leading to then you might understand better. But it already looks like you are not the target audience here.

    2. Re:That button order is a Windows artifact by It'sYerMam · · Score: 1

      This is obviously a pretty stupid point. Any frequent computer user begins to remember where buttons, icons and menu items are, and hence develops a learned instinct to move the mouse towards them. When this is disrupted, you move the mouse to the wrong place and it takes more time. The thing is, when it's something as simple as button order, not really having a great deal of impact, why bother changing it, causing disruption, when there's barely any gain?
      Here the market benefits from familiarity, not diversity.

      --
      im in ur .sig, writin ur memes.
    3. Re:That button order is a Windows artifact by AigariusDebian · · Score: 1

      I tend to agree to the point of the parent. I have never seen button order of Gnome as a disadvantage.
      Now i tried to see, why, and it occured to me that:
      * confirmation on right side (in the end) seems more natural to me;
      * anyway my reflexes react more to button icons or button texts, NOT to their order;
      * confirmation dialogs are only placed in places when you should reconsider your action and thus the effort needed to recognise the button to press (which is easy anyway) gives you also the time to reconsider your choice;
      * it might be also wise to make button order random for the most dangerouse choices, like, when in Debian you try to remove an 'essential' package, the apt-get tool asks you to enter "Yes, I know what I am doing" (IIRC) instead of the usual "yes" or a simple Enter.

      (I couldn't adapt to spatial mode though)

    4. Re:That button order is a Windows artifact by mwood · · Score: 1

      Of course, if proper keyboard accelerators are provided, button order is immaterial.

      Seriously. I may choose to use the mouse for some things, but every time I am *required* to go grab the mouse I count it as a design deficiency. Unless I'm sketching, I shouldn't have to take either hand off the keyboard for *any* interaction with the software.

      There. Now you all have a common enemy. :-)

    5. Re:That button order is a Windows artifact by Anonymous Coward · · Score: 0

      It's not that "windows does it this way", its the case that pretty much every GUI since Xerox kicked the genre off has done it this way.

      It's not an issue for me, I'm quite happy with Gnome. Its obviously not an issue for you either and I'd have to agree that I never thought of it as a problem before it was mentioned here.

      Thinking to my time at work with non-techy users, I can see that it would be an issue for a large amount (vast majority imo) of computer users who would struggle with this being unfamiliar. Lots of people who don't understand computers so well do things based on experience (e.g. click file, click save as, type name in most obvious box, hit bottom left button rather than thinking "I need to save this to a file" and clicking whatever obviously does this action), they are now going to be constantly hitting the wrong option.

      Most users probably don't read all the options or look at everything on the screen, they either don't care for such detail or feel that they wouldn't understand them anyway. You have to remember that PC's are very much a mystical art for most of their users.

      If theres any good reason to do things this way then fine, point it out in the popup help dialog or make it known. Doing it just to be different is going to screw you up, GUIs are the way they are primarily because of years of UI research by various companies and its not usually wise to ignore that. I bet billions has been spent overall, use it to your advantage, the results are free to see!

  50. Because Apple will sue by melted · · Score: 1

    They even sue people for creating Aqua themes fer chrissakes.

    1. Re:Because Apple will sue by AceCaseOR · · Score: 1

      That's not entirely true. Apple sued for creating a theme for XP that was a duplicate of their theme for Aqua. Phrase these things better before you post, 'kay?

      --
      Zagreus sits inside your head, Zagreus lives among the dead, Zagreus sees you in your bed and eats you in your sleep.
    2. Re:Because Apple will sue by Anonymous Coward · · Score: 0

      Yes, I supposed we should always take things literally and argue semantics.

  51. moderate down by Anonymous Coward · · Score: 0

    this fella isn't a team player - being just like everyone else, and fallowing the direction of our supreme leader is necessary

  52. ore wa turoru by Anonymous Coward · · Score: 0

    troll!

  53. Re:I found the "Hesitant User" study most interest by Anonymous Coward · · Score: 0

    That's about the most sexist thing I've read for a while, and I think you're not a troll but somebody who doesn't realize how sexist and patronizing his words sound.

  54. Four Cancel|OKs in GST by tepples · · Score: 1

    Gnome does not use "Cancel" or "OK"

    This isn't firsthand info because the last time I tried GNU/Linux, it turned out my video card was incompatible with accelerated X11 for GNU/Linux, and my scanner was incompatible with SANE. Nevertheless, the first page of results from typing gnome into Google Images showed a Cancel|OK in GST's Users and Groups, Network, Bootloaders, and Runlevel dialogs. One should probably change those into Cancel|Save. Or are those old screenshots?

    1. Re:Four Cancel|OKs in GST by JanneM · · Score: 1

      They may be old, yes. In any case, GST is not currently part of the Gnome desktop (though it is being discussed right now if they are fit for inclusion into 2.8). If they become part, they would need to have that fixed, yes.

      --
      Trust the Computer. The Computer is your friend.
    2. Re:Four Cancel|OKs in GST by Anonymous Coward · · Score: 0

      If OK/Cancel is verboten, why does Gnome have special Borlandeque icons for those buttons?

  55. I've set up Lin..errr...spire on a couple of.. by the_rajah · · Score: 1

    boxes and it's not bad at all. I've used both the 4.0 and 4.5 versions. The click and run warehouse is exactly that. Click on the software you want to install and that's it.. the aps download and install without a hitch. I'm impressed. It's as close to a consumer Linux as I've seen.

    Disclaimer, though, I'm running SuSE 9.1 and loving it for the main machine at my desk at home. The day job office main desktop dual boots 98SE and Lindows 4.0. The 98 is for legacy DOS programs that won't run under XP or Wine.

    "Do the Right Thing. It will gratify some people and astound the rest." - Mark Twain

    --


    "Do the Right Thing. It will gratify some people and astound the rest." - Mark Twain
    1. Re:I've set up Lin..errr...spire on a couple of.. by Dave2+Wickham · · Score: 1

      Have you tried dosemu and/or dosbox?

  56. I'll give you that I'm not the target audience... by Anonymous Coward · · Score: 0

    ...but it just isn't true that the button order decision was made without consulting existing usability research and experts, or without discussion.

    I think it's great that you are aiming to remove the esound dependency, reduce the web of library dependencies, and generally reduce bloat.

    But can't this be done - by you - within or in participation with the GNOME community?

    For example, no one is going to complain if you can submit good GTK+ patches to improve performance.

    Just a suggestion.

  57. Keywords: Spatial and File Select by oddbudman · · Score: 3, Insightful

    Its lunch time so i thought I would throw my hat in the ring.

    I have been using Gnome 2.6 for i guess a few months now and I have to say it is excellent. I used to use fluxbox (a great WM) but to be honest I haven't really looked back.

    I use it nightly as a desktop workstation. I do everything on it from developing firmware for Atmel micros, GUIs in GTK2, web browsing, warez downloading and playing enemy territory.

    Gnome 2.6 is faily well intergrated these days. Generally a right click on something will bring up options with what you can do, Left click selects - its nice and predictable. Ctrl-C Ctrl-X and Ctrl-V work as they do in Windows - very cool.

    Straight after installation I could do drag and drop burning (good for making an mp3 cds for my car). Another thing that has me impressed are all the cool system tray apps that come with it. They are easy to add and handy too. Right now I have one for net, one for cpu and one for local weather. The Local weather one is awesome as I can always have my finger on the pulse.

    I can't say I like spatial browsing though. Not default at least. Personally I found it really frustrating. Its not like i didn't give it a go either - I had it in spatial mode for about a month. It spreads like a cancer across your workspace. Before you know it you have waaaaaay too many windows open. Hiding the address bar is pretty stupid too imho - it makes it really easy to get lost and confused (especially when spatial mode decides you need 3 windows open to traverse 3 directorys). Perhaps if spatial mode didn't open a new window each time (or swapped middle and left click functions), and showed where you were I wouldn't mind it as much. My problem with spatial browsing was solved when i turned it off :)

    Another dislike is definitely the file select dialog. Who makes a file select dialog where entering the text yourself is not an option? Would it really have thrown the file select dialog into chaos if it was included? Why make it so it is completely unintuitive for a computer user who has been using Windblows for years? Now a file select dialog with text entry and typeahead search on the files in that directory would be great default behaviour. (please don't tell me about the hotkey either - that is not intuitive)

    Generally though I think Gnome 2.6 is pretty awesome. It is the best Linux DE I have ever used and I will continue to use it. It is definitely a step foward for the Linux Desktop.

    1. Re:Keywords: Spatial and File Select by suffe · · Score: 1
      Hiding the address bar is pretty stupid too imho


      Down to your left you will see a little area indicating where you are in the filesystem. Granted it won't show the entire path unless you click it. Also, clicking one of the shown dirs will take you to that directory instantly.

      especially when spatial mode decides you need 3 windows open to traverse 3 directorys


      Clicking a directory with the middle button will close the current dir window and open a new for the one you just clicked. No spreading like cancer if you don't want it.
      --

      Karma: 2.71828182846 (Mostly due to small, fun pills)
    2. Re:Keywords: Spatial and File Select by lucas+teh+geek · · Score: 1

      I've also come from a fluxbox background, installed gnome2.6 last week to see why this "spatial navigation" thing was causing so much fuss. I'm also damn impressed. everything integrates so beautifully and its really a pleasure to use. on the topic of spatial naviagation, I cant say im a fan... it just brings back memories of windows95. never a good thing.

      --
      TIAEAE!
    3. Re:Keywords: Spatial and File Select by fusey_2004 · · Score: 1

      Agreed -- the buttons don't really bother me. It's the file select dialog that's keeping me on GNOME 2.4 -- there's no way I'm going to use one without text input. The old dialog had it working so well, especially as you could tab and get completion. I don't see why they had to change this to something that looks ugly and would be a pain to use. It wouldn't have been difficult to add a text entry box in and it can fit quite nicely (although the dialog still doesn't look as nice). In fact: filename = gtk_entry_new(); gtk_file_chooser_set_extra_widget(file_selector, filename); will add the entry box -- it just needs connecting in. The spatial dialog would also annoy me if I used Nautilus, but when I moved to GNU/Linux, I long ago found ls and co. to be far more efficient.

    4. Re:Keywords: Spatial and File Select by Anonymous Coward · · Score: 0

      Tab completion would be nice. jEdit has quite a nice file selector (i.e. definitely not the default Java one.. go take a look).

      But Ctrl+L gets you a basic text input for a path in 2.6 file selector. For some reason Ctrl+F also pops up a randomly floating text input to search in the current folder.

  58. Project GoneME-Silent Killer. by Anonymous Coward · · Score: 0

    "Not to mention his posts on osnews as ogalaxyo gave me the impression that he was a 12 year old kid who simply hasn't figured out how things work yet."

    Google for oGalaxyo or the text from one of his screeds. It gets more interesting, especially when one of the lead KDE guys ripped him a new one. I think oo is from Germany (might explain his lovefest with KDE, and feelings toward GNOME).

    1. Re:Project GoneME-Silent Killer. by Anonymous Coward · · Score: 0

      Jeff Waugh.. is that you ? who was the fag replying before you ? one of your minions ?

    2. Re:Project GoneME-Silent Killer. by merdark · · Score: 1

      Weird. I did google for oGalaxyo. I didn't realize he was such a KDE fan. If he loves KDE so much, why doesn't he just use it?

      Is this new project simply some Jihad against Gnome or something? Did he change his mind about KDE being the best?

  59. Improved usability by mrgsd · · Score: 1, Interesting

    1) Improve Task-Orientation
    One task that consistently stumped users, causing them to go into exploration, was the initial discovery of where the web browser resided. The seemingly obvious answer eluded users for seconds.

    I can't help but think that GNOME usability would shoot through the roof had they put a porn icon right on the desktop.
    --
    End Communication.
  60. How fast were the computers they used? by AtlanticCarbon · · Score: 2, Interesting

    You'd probably get some nasty comments about gnome's speed if you gave them middle-aged computers.

    Right now gnome's main usability problem is it's speed. That's the only reason I don't use it. I have a 900mhz Duron. Sure it's old but it runs wind32 and qt apps quickly-- quickly enough for most tasks. I hope gtk gets speed tweaks soon. (I've even heard people with recent CPUs saying gtk feels lethargic on their systems.)

    I know the study was aimed at the layout of the desktop and such but let's face it responsiveness is a big part of a user's experience.

    1. Re:How fast were the computers they used? by lucas+teh+geek · · Score: 1

      I have to disagree with this. I'm running Gnome2.6 on a PII 350Mhz (the 384MB of ram doesnt hurt performance any ;P its the one Doom3 requirement I meet) and it runs at least as nice as qt apps, if not better. windows feels quite sluggish on this same hardware, but i dont know if thats what you were refering to by "wind32".

      --
      TIAEAE!
    2. Re:How fast were the computers they used? by YellowBook · · Score: 1
      Right now gnome's main usability problem is it's speed. That's the only reason I don't use it. I have a 900mhz Duron. Sure it's old but it runs wind32 and qt apps quickly-- quickly enough for most tasks. I hope gtk gets speed tweaks soon. (I've even heard people with recent CPUs saying gtk feels lethargic on their systems.)

      Three words: memory, memory, and memory.

      Seriously, the processor is not the problem; GNOME is just RAM hungry. For a local nonprofit, I set up from spare parts a Celeron 450 machine with 256 Mb of RAM and Fedora Core 2. It runs quite speedily. 128 MB (per concurrent user) is probably about the bare minimum for a fully-loaded GNOME system.

      I don't think it's a gtk2 problem, per se. Try running, for example, xfce4 (a lighter gtk2-based DE) as your desktop environment on the same computer and see if it makes a difference.

      --
      The scalloped tatters of the King in Yellow must cover
      Yhtill forever. (R. W. Chambers, the King in Yellow
  61. Ha ha! by BollocksToThis · · Score: 2, Funny
    I'm amused by the actions of the experienced unix guy, because this is *exactly* what I do, every time I sit down in front of a linux desktop (and the first thing I did trying out MacOS X in a store):

    1. Opens terminal
    2. 'ls' in home


    (On MacOS X, step 1 was the hardest, because there's either no console icon by default, or the store had removed it)

    It doesn't matter what I'm trying to achieve, I always do this. Does anyone else do the same?
    --
    This sig is part of your complete breakfast.
    1. Re:Ha ha! by Anonymous Coward · · Score: 0

      Yes.

      Multiple times. :(

    2. Re:Ha ha! by Anonymous Coward · · Score: 0

      Sure. I do this whenever I get to any command whatsoever, beit DOS, AmigaCLI, cygwin, bash, polyFORTH, whatever. I even type 'look' as the first command into any text adventure game. I'm sure any baby on it's burstday, first thing it does is opens its eyes and sees whats out there. Only then does it start crying.

    3. Re:Ha ha! by Anonymous Coward · · Score: 0

      In MacOS X, Terminal.app isn't in the dock by default. Which is sort of reasonable from a "dumb user" perspective (consider that the linked article even suggests that GNOME should hide the terminal icon by default).

    4. Re:Ha ha! by kingstalemuffins · · Score: 1

      Yeah, I do the same thing. I usually don't even care what's in the directory, but you gotta give it the old 'ls' anyway. Well, I guess there are probably worse habits one could have.

    5. Re:Ha ha! by spitzak · · Score: 1

      Typing "ls -a" is even better. You can learn lots about how to get the desktop to do what you want by looking at directories whose names start with a period.

      Has anybody considered making home *be* the "desktop", rather than using a subdirectory called Desktop? That would really match the original design of Unix. It could just hide anything starting with period. Yes existing users would see a lot of clutter, but they may learn to stick it all in folders on the "desktop".

    6. Re:Ha ha! by Hatta · · Score: 1

      If you're just going to go to a terminal, why do you need a "desktop" at all? Or a "start menu"?

      --
      Give me Classic Slashdot or give me death!
  62. HIG certification by 0x0d0a · · Score: 5, Insightful

    Currently, the HIG (see above) is made available to developers for voluntary adherence. If more resources were made availCurrently, the HIG (see above) is made available to developers for voluntary adherence. If more resources were made available, the GNOME project could start a certification program to document compliance with the standard. This would allow users to seek out certified applications and know that these applications would integrate well with their existing desktops.able, the GNOME project could start a certification program to document compliance with the standard. This would allow users to seek out certified applications and know that these applications would integrate well with their existing desktops.

    Horrible idea. None of the good desktop interfaces out there have *ever* required certification. We know that it is not necessary to produce an easy-to-use desktop. Further, this will discriminate against those people that do not have money to pay certification fees, slow development of applications (as individual versions would have to each be certified), and slow evolution of the HIG itself. I am opposed, and think that any attempt to formalize a certification process as part of GNOME would simply lead to bad feelings, loss of good will for GNOME, and project fragmentation.

    Unfortunately, those who were not were just as quickly lost and confused. To maintain the abstraction, we recommend that it be removed from the view of the new user and kept in the application menu.

    There were a number of suggestions like these -- hiding advanced functionality. While this is a reasonable approach -- the terminal is still in the applications menu, and easily available and easily found by non-novice users -- it is also extremely important not to work too hard to hide functionality. One of the largest problems with GNOME 2.x (IMHO, of course) is that significant and valuable functionality has been hidden or deprecated in the name of more basic "easy to use" features. This includes two of my favorite pet peeves:

    * Viewport support (someone apparently decided that it was "confusing" to allow the user to have a window partly on one viewport and partly on another, so it was replaced with a number of virtual desktops). As a result of this technical decision, sawfish (which is not the newbie-recomended GNOME WM in any event) underwent significant negative technical change.

    * User-rebindable accelerators. In GNOME 1, unlike every other GUI that I know of, accelerator keys attached to menu items can be simply and easily rebound by highlighting a menu item and tapping the desired key combination. This is a phenomenally powerful feature that demonstrated that the OSS world really *does* enjoy new ideas and significantly improved the GNOME user experience. It meant, for the first time, that the user was not bound by the decisions of the application developer. KDE has a similar-but-not-identical feature that allows *some* menu item accelerators to be globally rebound (frankly, I'd like to see the synthesis of these two featurs). Anyway, some usability person decided that this could be confusing to a new user (fine, I'll buy that) and the solution presented was to entirely disable this feature and requires manually adding a line to a text file on a per-user basis, instead of simply providing a toggle button in an "Advanced..." dialog or something similar. As a result, few users know about or take advantage of this functionality.

    A remedy is needed for this situation. The answer could be an installation application that can speak to all of the popular distributions. It could be built in such a modular way as to allow new backends and functionality.

    This is a good idea, and should have been done a while ago. It's a bit disheartening to think that this will likely have a very limited subset of functionality and be used by most users, though.

    A solution to this problem that allows for applications to be downloaded from webpages an

    1. Re:HIG certification by Pentagram · · Score: 1

      Horrible idea. None of the good desktop interfaces out there have *ever* required certification.

      Arguably, there are no really good desktop interfaces out there.

      Further, this will discriminate against those people that do not have money to pay certification fees, slow development of applications (as individual versions would have to each be certified)

      The article doesn't suggest that it be made compulsory, or that fees should be paid for certification.

      That's a bad idea. Really. I can live with apt or something similar, where at least some checking has been done by the distro producer. A large number of Windows security problems come from click-to-execute/install things in MSIE or Outlook.

      How about if it was on a whitelist basis, like the Mozilla thingies?

    2. Re:HIG certification by anno1602 · · Score: 1

      KDE has a similar-but-not-identical feature that allows *some* menu item accelerators to be globally rebound

      Actually, you can globally rebind the globally defined accels, and rebind the per-application-accels on a per-application basis. And you can, should you want to, override the global setting on a per-application-basis.
    3. Re:HIG certification by 0x0d0a · · Score: 1

      Arguably, there are no really good desktop interfaces out there.

      That's arguing semantics. The point of the study was "check out Linux, see how usable it is". The golden standard used as a comparison, whether it's a good thing or not, Windows and Windows-based software. If the software is as usable as Windows-based software *and* free, then usability is "good enough" for most people out there. There were certainly references to MS Office in the study notes.

      The article doesn't suggest that it be made compulsory, or that fees should be paid for certification.

      Obviously, it can't be made compulsory (who is going to "make me" certify each release of my project?). But once something like this happens, either there is essentially failure of the system and nobody cares about certifying their software, or there is pressure placed on projects to certify their software.

      I can understand *why* these people suggest certification. They have an issue -- there are people working on projects that do not worry about the HIG, and these people want to provide an entirely consistent environment, and believe that usability people *must* be injected into the mix somewhere for HIG compliance to be ensured. I don't agree.

      In the Mac world, a bunch of UI people developed a good set of guidelines to use. There was no "Macintosh Human Interface Certification" from Apple -- applications naturally tended toward being compliant, because a violation of the guidelines was a *bug*. The developers produced good software with good interfaces.

      As for fees -- yes, I noticed that they avoided mentioning fees, and wondered if it might be deliberate. However, it's just not feasible to do otherwise. Who would fund constant usability testing for *every* release of *every* software package out there? It just doesn't happen.

      Certification is something you do when you have something that is not going to change for a while, where the latency of having something tested is acceptable, where the developer has interest in obtaining certification and where any deviations from certain requirements are catastrophic. None of this is the case with the user interfaces. OSS software releases are *frequent*. The overhead imposed by certifying each release of software would be a pain. Most developers work on software to benefit themselves -- having them go through a certification process is just excessive when it comes to requiring annoyances to allow others to use your work. Finally, poor usability (well, to a point) is not catastrophic. I have used many pieces of software that deviate from interface norms, as have other people, and they continue to function. Firefox does not use the native widgets of a platform -- it has its own interface. Lotus Notes does the same thing. Combine that lack of consistency with a few Windows apps that have stupid interfaces, and a not uncommon Windows business environment (that people learned how to operate without much problem) does not *have* very consistent interfaces.

      How about if it was on a whitelist basis, like the Mozilla thingies?

      It's still building an authorization and installation system up from scratch. You have to handle error-handling, dependencies, different architectures, logging ... I really think that this is more of a "I'm not used to the way this works" than a "it doesn't work well the way it is." Perhaps there's a need for an *easier to use* GUI front end for software installation -- perhaps synaptic isn't nice enough yet -- but I'm not convinced that there's a need to turn a web browser into a software installation system. I view software distribution systems like dselect and apt as an evolution away from the limited general-purpose approach of manually downloading and installing things from a website.

      With a software installation tool, it's easier for an admin to manage systems on a network (for example, if he knows that current gaim2 copies break with the existing network co

    4. Re:HIG certification by 0x0d0a · · Score: 1

      All of the accelerators, or just the common ones? I remember seeing some interface that let people set what "print" was -- if an item is in a menu in a KDE app, can I necessarily rebind the accelerator associated with it?

      If so, that's pretty cool.

    5. Re:HIG certification by orcrist · · Score: 1

      if an item is in a menu in a KDE app, can I necessarily rebind the accelerator associated with it?

      Yes. At least to my knowledge. I believe it's offered more or less automatically by virtue of the app binding to the appropriate KDE libraries, so there's no need to have HIG for that. That's what a lot of KDE-haters seem to ignore (or be ignorant of), many of the mechanisms for consistency in KDE are just that: mechanisms; not rules. By learning the technical side of programming a bona-fide KDE app (i.e. using the KDE libs), most of the consistency takes care of itself.

      -chris

      --
      San Francisco values: compassion, tolerance, respect, intelligence
    6. Re:HIG certification by brunes69 · · Score: 1

      Yes, settings -> Configure Shortcuts in any KDE application.

    7. Re:HIG certification by scrytch · · Score: 1

      > Horrible idea. None of the good desktop interfaces out there have *ever* required certification.

      Where on earth did they say "require"? They said "document". As in, "you can use the official ``Works With GNOME'' Logo if you pass these tests." and "Distribution FooLinux has committed to only placing certified apps on the default desktop and the panel".

      Come to mention it ... where'd the panel go?

      > I *don't* think that one-click-download-and-execution should ever happen in a web browser or email client.

      There are circumstances where it can be okay, but in general I agree with you. I also don't think the perceived need is so critical. A novice user need merely drag a package link from the web browser to their desktop then double-click it. If people more or less agreed on a standard icon for rpm links (and debs, and whatnot) like what is done with pdf files (the little acrobat logo), then the nature of these links would become second nature. Being prompted for the root password would also become second nature. Installing viruses this way could also become second nature, but the roadblock of being asked for the root password would at least limit it to the category of folks who fall for phishing scams.

      Now that Linux boxes can potentially let their end users royally hose them, have any of the desktop distros looked at packaging and simplifying snapshot and restore utilities like ghost? To say nothing of something like XP system restore points...

      --
      I've finally had it: until slashdot gets article moderation, I am not coming back.
    8. Re:HIG certification by Jon+Pryor · · Score: 1
      User-rebindable accelerators....

      This is still present in Gnome 2, you just need to know about it. Set the GConf key: /desktop/gnome/interface/can_change_accels to TRUE, either via gconf-editor or the command-line :

      gconftool-2 -t bool -s /desktop/gnome/interface/can_change_accels TRUE

      Behavior is similar to GTK 1.x. The one restriction I've seen (and I'm not sure if it was present in GTK 1.x) is that you can't assign an accelerator that's already in use. For example, for Help-> About, 'A' is already in use as an accelerator, so you can't re-use 'A' in that menu.

    9. Re:HIG certification by spitzak · · Score: 1

      A solution to this problem that allows for applications to be downloaded from webpages and installed directly would remedy the situations that occurred during the usability study

      I also don't like this. Unfortunatly Win32 has convinced too many people that an appliation has to be "installed".

      Here is what I would like to see:

      1. User goes to web page, sees kool new application, and clicks "download".

      2. This downloads a thing that looks like a file, exactly like they decided to download a .pdf or piece of music.

      3. They can double-click on the file (or the browser can offer to run it). This RUNS the appliation. It does not "install" it.

      4. If they hate the appliation they can quit, and they throw the file in the trash, and it is GONE!!!

      5. If they like it they can drag and drop it in a place so they can run it from a menu. They can drag it to a place so that all users can run it from the menu, this will require the root password. To remove it from the menus they drag it out of there, either into the trash, or to somewhere else to keep it.

      6. Any application that needs root privledges to run will fake it's operation as well as possible, so you can at least see what it does, and offer to install itself. This is done by calling sudo and asking for the root password. If the user does this the icon is moved to the root location. They can still "uninstall" by throwing the icon in the trash, if they have permission to do this.

      How to accomplish? This would be done with something similar to Mac "app" directories, though I recommend that no extension be used. Probably these are detected by having a particular file inside them. File browser would act exactly like these are single files. Running them would run a fixed-name program inside them (main?) and set argv[0] to the full pathname, and add the directory to the start of the LD_LIBRARY_PATH. All the information used in .desktop files would be placed inside these directories so just dropping it on the menu makes it work.

  63. What For by PenGun · · Score: 0

    I dunno I've tried em' both, KDE and GNOME. Every time I install a new slak I try one or the other.

    I always toast em' after a few days and just use my ancient WMaker configs. They are slow and I don't need my hand held. Rxvt comes up instantly and with a -e switch it starts any X program. WMaker's menu system makes 'roll-yer-own' menus pretty simple.

    I play a video by right clicking on the desktop, left clicking on Vids/AquaTeen/ATHF-Unremarkable-Voyage-44 .... it don't get no simpler.

    I think way to much effort goes into this stuff myself.

    PenGun
    Do What Now ???

    1. Re:What For by Hatta · · Score: 1

      I largely agree. I'm a fluxboxer myself, a simple hotkey and I have an aterm instantly. I barely use the rightclick menu and have turned the status bar off. But this got my attention:

      I play a video by right clicking on the desktop, left clicking on Vids/AquaTeen/ATHF-Unremarkable-Voyage-44 .... it don't get no simpler.

      Are you saying that file navigation is built into your window manager? Or do you have desktop icons that open a file manager? What file manager? I generally open an rxvt, hit tab a bunch of times, and run mplayer. Works well 99% of the time. Once in a while I need something graphical for some more "random access" tasks, usually getting organized. Rox filer I've found to be lightweight and configurable enough for those times.

      --
      Give me Classic Slashdot or give me death!
    2. Re:What For by PenGun · · Score: 0

      Yup file navigation with a designated executable for each tree.
      This is cramped 'cause the /. filters don't like the code.
      From WMakers WMRootMenu which defines em'

      (
      Vids,
      (
      AquaTeen,
      OPEN_MENU,
      "-noext /rip/vid/AquaTeen WITH rxvt -e nice -19 gmplayer -fs"
      ),
      (
      "Cartoon Planet",
      OPEN_MENU,
      "-noext /rip/vid/CartoonPlanet WITH rxvt -e nice -19 gmplayer -fs"
      ),
      (
      "Space Ghost",
      OPEN_MENU,
      "-noext /rip/vid/SpaceGhost WITH rxvt -e nice -19 gmplayer -fs"
      ),
      (
      "SG",
      OPEN_MENU,
      "-noext /rip/vid/SG WITH rxvt -e nice -19 gmplayer -fs"
      ),
      (
      "Real Ghost",
      OPEN_MENU,
      "-noext /rip/vid/RealGhost WITH /usr/local/RealPlayer8/realplay"
      ),
      (
      MusicVids,
      OPEN_MENU,
      "-noext /rip/vid/MusicVids WITH rxvt -e nice -19 gmplayer -fs"
      ),
      (
      Bikes,
      OPEN_MENU,
      "-noext /windose/vid/Bikes WITH rxvt -e nice -19 gmplayer -fs"
      ),
      (
      Dl,
      OPEN_MENU,
      "-noext /rip/dl WITH rxvt -e nice -19 gmplayer -fs"
      ),
      (
      "VCD",
      EXEC,
      "rxvt -e gmplayer vcd://1"
      ),
      (
      "Vid Off",
      SHEXEC,
      "killall -9 mplayer;killall -9 /usr/local/RealPlayer8/realplay"
      )
      ),

      I know of nothing that simple in Gnome or KDE.
      I can also fire up vids, tunes, whatever in the Midnught Commander (run it in rxvt) just by highlighting and hitting enter.
      PenGun
      Do What Now ???

  64. Re:Recommend to get rid of (useful) error messages by Kenard · · Score: 1

    I don't believe that the author was suggesting a less verbose, but a more descrpitive explanation of the error.
    An discription of "Divice could not be removed because divice is in use. Make sure no there are no open files and try again." or "Divice could not be removed because you do not have sufficent privileges." are more of what the author was suggesting.
    I don't think that a error stating "Error occured at 0x520F3BC0 0C 15 36 2B 3A 24 8F ..." being useful to anyone.

    --
    (appended to the end of comments you post)
  65. Why Bother? by Anonymous Coward · · Score: 0

    Neither Qt nor Gtk are X toolkits. They are
    psuedo X toolkits, i.e. they run on X but
    don't follow or use X mechanism for toolkit
    implementation. So, on an X platform, the
    quetion then becomes, why bother using either?
    Why not use Java (Swing) or some .Net equiva-
    lent? Barring some very peculiar or particular
    reason, you don't need either Qt, or Gtk anymore
    (on X). Write it in Java and you get both com-
    pile-time platform independence and run-time
    platform independence.

    Note: I'm not really a huge fan of the concept
    of VM run-time cross-platform anything. But this
    is one case where I think it makes sense. If you
    are *not* going to use X11 as X11, then go with a
    cross-platform (run-time) toolkit like Java Swing.

    Okay, yes, I know there are some places where Qt,
    or Gtk may be better suited. Embedded space
    perhaps. But I'm speaking in the more general
    sense here.

    1. Re:Why Bother? by kundor · · Score: 2, Insightful
      Have you ever tried programming KDE?

      It's sooo nice. Really. You can whip up a full web browser in about 5 minutes thanks to khtml.

  66. Re:MOD UP!! by Peter+Cooper · · Score: 1

    You can. There's a developer's edition. I downloaded a free copy of Linspire (officially) a few months ago, can't entirely remember how.. but it's doable. It wasn't that bad really.

  67. Changing WMs and DEs by olscratch69 · · Score: 1

    Not being a power user or computer guru I find this to be a bit silly. One of the main reasons I tried out Linux in the first place was the fact that there were so many different desktop "look and feels" included. I change Window managers a lot. Every couple of days. I stick mainly with KDE because it was my first desktop and I have it sort of figured out. It, to me it seems fairly easy to use. I like a lot of the others though. It all depends on what mood I am in at the time. Sometimes I feel like a "start button" sometimes I don't Sometimes I feel like desktop icons, sometimes, I don't. My favorite thing about Linux is the diversity. I have never been a fan of the way the Mac OS looks. I am sure it is a great OS but I am not that fond of the bubble gum cartooniness of the latest Mac OS. I am not that fond of the Linux WM's that try to emulate that look. I prefer a different type of look to my desktop. I am not sure how to describe it. Window managers like enlightenment, fluxbox, windowmaker and afterstep. They usually have a clean look to them.

  68. Bah... vote with your feet, then by cleverhandle · · Score: 1

    While I have some sympathy for your opinion, it is outweighed by one thing - put bluntly, GNOME's got balls. And I respect that a lot. Ever since 2.x began, they have taken their design goals and refused to let them be compromised by the hordes of bickering Slashdotters that can't live without their favorite features. Forcing people into spatial Nautilus is just another aspect of that - they push you into it because it's part of the project's goals. They have a vision of how the desktop should work and they refuse to dilute it by making everything an option. Like many others, I hated spatial at first and then grew to appreciate it. Their decision was a good one. If you truly dislike something, you have the source code - most behaviors are easily modified there if you're as hardcore as you proclaim to be.

    And if you don't like GNOME's design goals, then fine - use something else. KDE accomodates every preference in the universe - to the extent that you need a search function in the control panel. Or use Openbox - it's lean and has lots of neat gadgets. But don't waste your breath complaining about GNOME. Your comments won't come as any surprise to them.

    1. Re:Bah... vote with your feet, then by Nailer · · Score: 4, Insightful

      most behaviors are easily modified there if you're as hardcore as you proclaim to be.

      Where do I claim to be hardcore?

      And if you don't like GNOME's design goals, then fine

      Its not a matter of my own opinion - its a matter of our clients. I work for Red Hat in Australia and I can attest most of our clients don't like spatial mode. I'd like to have it either explained better (welcome to Gnome 2.6! We've included a new spatial mode! Its better for X reason! If you don't like it though, do Y!) or changed by default.

      As one can imagine, my opinions are my own and don't necessarily represent my employers.

  69. Fixing GNOME's speed by 0x0d0a · · Score: 1

    Right now gnome's main usability problem is it's speed.

    One significant improvement that would help many GNOME users would be to add jump scroll support to gnome-terminal.

    In xterm (or the even peppier rxvt), there is a limited number of refreshes that can happen a second. Internally, much text can go by between each screen refresh. This avoids huge numbers of unnecessary screen displays being done. You can easily cat tens of thousands of lines of text to rxvt almost instantly -- gnome-terminal takes a while to churn through all of them.

    1. Re:Fixing GNOME's speed by Anonymous Coward · · Score: 0

      I tried 'yes | head -10000 | cat -n' on xterm and gnome-terminal, both were about the same speed...as long as I was using the same (anti-aliased) fonts on both.

      Obviously xterm is faster when using the old font rendering code.

      And yes, I did have jump scroll enabled in the xterm. Unlike gnome-terminal, it flickered visibly, but was still no faster.

      One thing about gnome-terminal that I really do consider a problem is the fact that the terminal preferences don't include default size. That's just ridiculous. I know I can set it globally by editing a file, but of all the missing preferences in GNOME, that's the one I've looked for in every release I've tried.

    2. Re:Fixing GNOME's speed by 0x0d0a · · Score: 1

      I tried 'yes | head -10000 | cat -n' on xterm and gnome-terminal, both were about the same speed...as long as I was using the same (anti-aliased) fonts on both.

      This is true. This may involve flushing somewhere.

      If I try time find /usr/src/linux, I consistently get 11 seconds for gnome-terminal, a little over 1 second for xterm, and under a third fo a second for rxvt.

  70. Recommendations (and UI abstraction) by arrianus · · Score: 5, Insightful

    The recommendations don't follow from the user experience. Several don't necessarily follow, but I'll present the dominant problem here:

    Maintain the Abstraction from the Underlying System

    This is almost universally the wrong approach -- this is what Windows tries to do, and MacOS avoids. The key is to make the underlying system simple, and make the UI reflect that.

    The problem with abstracting the two is that it leads to bit rot. At some point, the Windows registry will think a file is in one location, whereas the file is actually in another. Or the UI will misunderstand the way that the 5 options in the configuration file should be presented as 2 options in the UI. Or there will be some underlying binary configuration file, with some option that's not available in the GUI, that somehow gets flipped, breaking the whole system.

    You very strongly don't want an abstraction. On the Mac, installing an application (I haven't use OSX, so my knowledge is based on the older versions) is as easy as dragging the folder onto the hard drive. To erase, you wipe it. On Windows, if you wipe an app like that, it'll leave bits and pieces of itself scattered throughout the registry, links in menus, DLLs in system folders, and dozens of other places. Worse, the uninstaller will often no longer work. Most clueless users, if they try to erase an application the wrong way, will end up with a semibroken system, since there are different levels of abstraction that do not maintain consistency.

    The whole Windows (and increasingly, GNU/Linux) approach of abstracting out underlying complexity is flawed. The trick is to eliminate the underlying complexity, and have a single set of simple structures that the GUI tools (or the users manually) operate on.

    When I first used Red Hat in '96, the types of issues that threw me were: I wanted to change the login text. I grepped for the old login text, found /etc/issues, and I edited it. It worked. I rebooted. It went away. It took me the longest time to figure out that an fucking script in /etc/rc.something/ was overwriting it. The information was stored in two places. I overwrote the wrong one, and boom. I was fucked. I stopped using Red Hat precisely because of the complex configuration scripts, which made the system fragile and ultimately, easy to break and difficult to use.

    This shows up a huge number of places -- especially in a heterogenous environment like GNU/Linux, you often have multiple configuration tools. I can download a half dozen Apache configuration tools. Very often, if you run one, then switch to another, the thing no longer works, since they edit different options in different ways.

    One way to implement this (presented in an oversimplified fashion) is to first design what you want the UI to look like. Once you know, you design the underlying structure to match. This is the opposite of what most GNU/Linux and Windows developers do, where they try to engineer the most flexible underlying structure possible, and then develop a UI on top of that. This doesn't necessarily lead to less flexible underlying structures -- it's just that to have a good UI, you want to give some thought to the user experience when designing the engine, and especially, the configuration files.

    1. Re:Recommendations (and UI abstraction) by goon · · Score: 1
      I wanted to change the login text. I grepped for the old login text, found /etc/issues, and I edited it. It worked. I rebooted. It went away.

      interestingly motd ~ works like this with /etc/issue and /etc/motd... you can edit your /etc/rc.d file as shown in the link but I just leave 2 lines blank.

      • $ vi /etc/motd
        # commented newline 1
        # commented newline 2
        this is your motd message here
        :wq! (to save & quit)
        $

      this should allow your motd to appear next boot into bash.

      --
      peterrenshaw ~ Another Scrappy Startup
    2. Re:Recommendations (and UI abstraction) by Anonymous Coward · · Score: 0

      This was in '96, so I eventually figured it out.
      But the fact that there's a LinuxGaszette article about it shows that it's a common source of user confusion.
      If you instead had a /etc/issue script that generated it on the fly, you'd avoid this entirely. In general, you want data stored in only one place. The biggest disaster, from a UI point of view, is the autoconf/automake/configure/make build system. You can perfectly well edit a file, fix a build error, rerun the build system, and have it overwritten. Users unfamiliar with it get screwed quite often, and there's a huge learning curve to learn each of the half-dozen tools needed. The problem is that make had shortcomings, so instead of fixing them or writing a proper build tool, someone wrote a tool to generate makefiles. Then, when that tool had shortcomings, someone wrote a tool to generate its input files. The overall mess you have now takes forever to learn.
      You run into even worse disasters with RPM and Debian package systems, where if the state of the system is different from what the package management thinks it is (if, for instance, you install proprietary X drivers without proper packages), you can be royally screwed. Uninstalling a package will remove some, but not all, files from the proprietary X server. Similarly, installing one may overwrite them. As complexity of inconsistency increases, the system bit-rots into oblivion.

    3. Re:Recommendations (and UI abstraction) by Anonymous Coward · · Score: 0

      Sounds like a similar rationale behind Naked Objects (http://www.nakedobjects.org/no-approach.html)

    4. Re:Recommendations (and UI abstraction) by IamTheRealMike · · Score: 1
      You very strongly don't want an abstraction. On the Mac, installing an application (I haven't use OSX, so my knowledge is based on the older versions) is as easy as dragging the folder onto the hard drive. To erase, you wipe it.

      That's actually a great example of why you're wrong - in MacOS X sometimes you drag and drop software, sometimes it uses the Apple installer, and sometimes it uses custom installers. Even Apples own software does not use appfolders anymore - the underlying system was too simple to meet peoples actual needs, and so they ended up with many different hacks around it reducing consistency overall.

      Worse, as more and more hacks were added to try and make the bundles/appfolders scheme functional enough, they managed to create security holes while they were at it. Witness the URL registration/LaunchServices mess. There's a saying: "make something as simple as possible, but no simpler". Apple made appfolders simpler than was really possible and Mac users are now paying the price.

    5. Re:Recommendations (and UI abstraction) by master_p · · Score: 1

      There needs to be an abstraction layer over the Posix standard...one that abstracts away all the peculiarities of Posix/Linux/Unix (peculiarities in terms of UI, not of O/S design). This layer will take care of the interaction of applications with the system, be it Linux, Unix, Windows or whatever.

      Then building a GUI on top of this layer will make the UI very easy, while at the same time it would be easy to work to the 'bare metal' of the O/S.

    6. Re:Recommendations (and UI abstraction) by Hognoxious · · Score: 1

      Those aren't problems to with abstraction per se; those are simply bad implementations.

      --
      Confucius say, "Find worm in apple - bad. Find half a worm - worse."
    7. Re:Recommendations (and UI abstraction) by DancingFool · · Score: 1

      Even Apples own software does not use appfolders anymore

      Umm...name one Apple-produced application that doesn't use a .app extension which is actually a folder with a bunch of stuff inside? I can't think of one. Or were you referring to something else?
      --

      --
      Adversity: That which does not kill me only postpones the inevitable!
  71. Stop listening to users by Proc6 · · Score: 1

    Should you build your UI based on feedback from the average Joe? I'd like to lay down while driving my car, but clearly designers think the best idea so far is sitting in an upright position. Grow a set, innovate the UI* and quit trying to clone Windows. * and by innovate I mean think tank concepts not geeky crap like why every "average joe" linux distro comes with 700 things theyll never run. YEAH, MAN I WANT THOSE NEATO EYES THAT FOLLOW MY MOUSE ON THE TASKBAR! sigh.

    --

    I'm Rick James with mod points biatch!

    1. Re:Stop listening to users by SegFault · · Score: 1

      The "Neato Eyes" applet is useful for multihead displays where the mouse has a lot of room to get lost. I can look at the "eyes" and immediately know what direction to look for the mouse. It is usually quicker than using the "move the mouse and scan the monitors until I see it" method alone. Especially when the desktop gets busy/cluttered.

    2. Re:Stop listening to users by One+Childish+N00b · · Score: 1

      Should you build your UI based on feedback from the average Joe?

      Yes, if you want the 'average Joe' to use it. That's the idea of 'desktop linux', right?

      'Innovate' all you want, but if it's not what the average Joe wants, Linux is never going to get the marketshare it deserves.

      --
      Dealing with lawyers would be a lot less tedious if they all looked like Casey Novak.
  72. Re:This fucking idiot should go home by some+guy+I+know · · Score: 1
    he's recommending reducing the role of Python in OSS.
    All he is saying is that Python should not have to be installed in order to build Gnome.
    I see nothing wrong with that.
    There are some people who don't use Python, and these people shouldn't have to install it just so that they can build Gnome.
    I am saying this as a person whose current favorite language is Python.

    I used to find myself similarly annoyed when I found that some project required Java to be installed in order to build something.
    --
    Those who sacrifice security to condemn liberty deserve to repeat history or something. - Benjamin Santayana
  73. Re:I found the "Hesitant User" study most interest by some+guy+I+know · · Score: 1
    I mean, you're given a system to test, and "experienced Unix user" is all set to download and install Mozilla?
    ???
    I have been using UNIX and UNIX-like systems since around 1980, and currently I use Mozilla as my primary browser (both in Linux and MS-Windows).
    What browser do you use?
    --
    Those who sacrifice security to condemn liberty deserve to repeat history or something. - Benjamin Santayana
  74. Example by Anonymous Coward · · Score: 1, Insightful

    A good example of this approach is the Linux kernel configuration system. Here, the configuration information is stored in a single, standard format. It describes what the configuration options mean, the dependencies, etc. Then, there can be a number of "dumb" configuration tools (make config/menuconfig/xconfig/etc.) that all work on the same underlying format, entirely consistently, and in addition, users can modify it by hand. This single file is used for everything in the build process. It is impossible for the file to be inconsistent, as it is handled.

    A bad way to do this would be to have a "Kernel Build Wizard," that was hand-coded for a dozen kernel options, and had its own expert system to set the remainder automatically, and that had it's own higher-level config file that built into a kernel config file. (The right way to do this would be to push the automatic information down into the kernel configuration language).

    Linus is brilliant, and always does things the Right way. Now if only the major distributors were as smart...

    1. Re:Example by denominateur · · Score: 1

      make 'menuconfig' has one huge usability failure in my opinion.

      If you select of the menu choices and want to go back to the main menu, you need to select EXIT rather than a back button. Certainly, in the context of power users this has no importance.. a new user however who is forced to recompile the kernel because he bought a new motherboard (or any other sufficient reason), would find that illogical.

    2. Re:Example by Anonymous Coward · · Score: 0

      To be fair, its hardly fair to go making usability suggestions about the kernel configuration tools. Joe Sixpack shouldnt be in the kernel messing about with it in the firstplace.

    3. Re:Example by Hognoxious · · Score: 1
      To be fair, its hardly fair to go making usability suggestions about the kernel configuration tools.
      Until developers start copying the behaviour into apps for end-users.
      --
      Confucius say, "Find worm in apple - bad. Find half a worm - worse."
  75. Frustration with "usability studies" by ky11x · · Score: 5, Insightful

    I'm beginning to get very frustrated by these usability studies because they all tend to make the same false assumption that "familiarity for new users" == "usability for all users."

    This is simply NOT true. Usability is a complex quality, and it is the result of compromises among often conflicting goals such as discoverability of options, reduction of keystrokes/clicks for common tasks, customizability where common base cannot be established, compatibility with competing interfaces, humaneness of interface after long-usage, accessibility, internationalization, etc. etc. How quickly New Users can discover and perform tasks is only one dimension of the usability scale, and one that's not even all that important except in a setting like public access kiosks or Internet cafes.

    Different OSes approach this problem differently, and where as Mac OS X has chosen to compromise all the goals with an emphasis on discoverability and tolerance after long usage, Windows has chosen to place a different emphasis on sacrificing flexibility for complex tasks in favor of making simple, repetitive tasks easy to accomplish. Both approaches have their advantages and disadvantages.

    The traditional strength of the various Linux desktop systems has been flexibility and customizability, with less emphasis on the other issues. I'm not suggesting that the needs of new users whose primary OS is not Linux in settings like Kiosks and labs should not be taken into consideration, but it should not be the ONLY consideration.

    Usability studies like this one emphasize the needs of new users with Linux as a secondary OS over everything else. Take this as an example:

    These extra areas (the desktop-reveal button, the workspace switcher, the file manger icon, the terminal icon, and the running application button in the top right) could be removed by default...

    This is the sort of recommendation that makes sense for kiosk machines (simplify the UI as much as possible and go for task-orientation), but it doesn't make sense for long-term usability. Removal of these features means that users will have to discover them and add them back in, and that plays into one of the weaknesses of the current Linux desktops: discoverability is relatively poor. This is a very shortsighted and pointless recommendation for a desktop system that is also meant to be used as a primary desktop system for many home users.

    I wish usability studies would really think about what usability is, over all and long-term, rather than just "can new users in a hurry get an email written?"

    1. Re:Frustration with "usability studies" by dash2 · · Score: 1
      I wish usability studies would really think about what usability is, over all and long-term, rather than just "can new users in a hurry get an email written?"

      RTFA. They tested four users, including one long-term unix expert who just did everything via the terminal.

    2. Re:Frustration with "usability studies" by nutshell42 · · Score: 1

      RTFA they tested a unix guy who was *new* *to* *GNOME*

      --
      Don't think of it as a flame---it's more like an argument that does 3d6 fire damage
    3. Re:Frustration with "usability studies" by twistedcubic · · Score: 1

      Why would an experienced computer person want to use Gnome?

    4. Re:Frustration with "usability studies" by nutshell42 · · Score: 1

      he didn't want to that usability guys dragged him kicking and screaming to their test pc, really =)

      --
      Don't think of it as a flame---it's more like an argument that does 3d6 fire damage
    5. Re:Frustration with "usability studies" by Khelder · · Score: 1

      You're right that usability includes more than just learnability by novices. However, I'm glad to see people studying learnability for Linux because it's something that's really hard for the developers to get right on their own (they know the software so well it's hard to see it with the midset of a novice). Also, programs for Unix and X are traditionally pretty expert-friendly, but often novice-hostile. So I think it's good that learnability is being studied, as a sort of balance.

      It would be better to call it a "learnability study" than a "usability study", though.

  76. Re:Couple things I do not Like, by Grant_Watson · · Score: 1

    "They want to make the level of abstraction of error messages to be higher?"

    Now I'm too intimidated to RTFA. You mean someone wants to read, "Gnome encountered a problem and had to close?"

  77. Re:gramer correction by Anonymous Coward · · Score: 0

    If you need a stupid feature like integrated voice recognition, try Mac OSX. I'm no longer a maccie, but it does have an integrated voice recognition service, which you can program to any name such as "COMPUTER" or whatever you want.

    But! we must wait until redmond "invents" the feature, no?

  78. Other bugs by Anonymous Coward · · Score: 1, Insightful

    It's not clear that the task-oriented approach is better -- my experience has been that most users don't want to do the recommended tasks, or want 10% functionality that's not in the recommended tasks, and so need to learn more of the system either way. Few people sit down at a computer once, use it for 15 minutes, and never use it again. Most people use a computer at least a few times a week, and it's important that those people can get things done. The addition of a "compose e-mail" task to the desktop buys very little in practice.

    Also, the breakdown into "new user" and "experienced user" is a little too broad. As an "experienced user," having to figure out how to reconfigure a dumbed-down GUI usually takes a few hours, and is often not worth it. I also don't automatically know where things in GUIs are located. When I first sat down at this Sun (running some CDE hacked up for ease-of-use), it took me about 15 minutes to find a terminal. It sucked. An intermediate user shouldn't have to spend half an hour figuring out common "intermediate user" tasks to make the system simpler for a new user, nor should they be assumed to be an "advanced user with a surplus of time" who can or wants to take the time to reconfigure the system, because some asshole decided new users would be confused by having the terminal in any ready-accessible menu, and hid it 5 layers down. There really needs to be a smooth gradient that balances the needs of all users, not just new ones. This should include very advanced users who don't have time
    to spend reconfiguring every machine they sit at.

    One way to solve this would be to have Gnome, upon first startup, be able to select one of several default suites ("Expert" "Intermediate" "Beginner", as well as some level of screen realstate used by Gnome vs. proximity of features).

  79. Either you want SUX, or you want ROX. by tepples · · Score: 1

    To emulate the Mac OS feel, you'd have to create a filebrowser that could execute GUI apps easily (e.g. opening firefox in konqueror).

    ROX-Filer managed to copy Mac OS X's app bundles.

    1. Re:Either you want SUX, or you want ROX. by parksie · · Score: 1

      I love these... pity a lot of them are wrappers around programs already in /usr/bin ... now if only GoboLinux would have installed for me *sigh*.

      http://www.hardline.org/moslix/ looks interesting in the future as well... I miss RO 3.11 :/

  80. Re:gramer correction by io333 · · Score: 1

    Oh heck, a mac I bought in 1992 (!) had voice recognition. It just never freaking worked. There's viavoice etc for the PC and they don't work either. Someday someone will make it work, and all the endless "desktop" arguments will be moot.

  81. Re:"An usability"? That makes my fucking eyes blee by Anonymous Coward · · Score: 0

    Maybe (s)he pronounces it "ooze-ability".

  82. Re:gramer correction by kundor · · Score: 3, Funny

    My Acer aspire from 1995 had working voice recognition. Worked like a charm. I could say "Shut down...yes," and it would shut down. I could say "Switch to Descent" and it would start Descent. I could say "Switch to Chess" and it would start Descent. I could say "Switch to CHESS you stupid computer" and it would shut down.

  83. 3x5 by mwvdlee · · Score: 1

    The link in the article advises on about three tests of 5 users.
    Whereas their own graph shows 15 users in 1 test would find 100% of the problem, 5 users would find only about 80%. Logic dictates that a second session with 5 users would find another 80% of the previously undiscovered 20%; 80+16 = 96% and a third would again find 80% of the left 4%, making just about 99%.
    Is there something wrong with their own data or with the logic of the advise?

    --
    Slashdot social media options: AIM, ICQ, Yahoo, Jabber and Mobile Text. Why no MySpace?
    1. Re:3x5 by nostriluu · · Score: 1

      You will never find 100% of the problems. There is no One Right Way to do things. That graph is .. a graph (eg math is rarely representative of Real Reality (tm), especially in the subjective realm). As the usability experts I work with explain it, and is mentioned in passing on that page (though the big misleading graph dominates) it is a matter of diminishing returns.

      Of course, you might also end up with 5 "duds" as usability subjects, and might not get some real insight until your 100th user. Unlikely, but possible.

  84. Re:I found the "Hesitant User" study most interest by BiggerIsBetter · · Score: 1

    I use Mozilla, but you missed my point. It's a desktop environment test session, and this guy's first thought is to download and install stuff which could reasonably be expected to be there. An Experience Unix user should have known that, but this guys's firing up the terminal and trying to do it all the hard way... and if you're there to test a desktop you shouldn't really be trying to avoid it via the shell or customise the install with your own software.

    --
    Forget thrust, drag, lift and weight. Airplanes fly because of money.
  85. Re:This fucking idiot should go home by raodin · · Score: 1

    If you want to compile (or use, in the case of interpeted languages) a piece of software which uses a certain language, you have to have that language installed. I can't see how thats something worth complaining about.

  86. Gtk/Gnome snappy? by Anonymous Coward · · Score: 0

    hello? Either you are still using gtk1.2/gnome1.4 or you are living on a different planet?!
    Today Qt/KDE is miles snappier than the turtle that is gnome...

  87. KDE Style Guide by Moritz+Moeller+-+Her · · Score: 1

    > However KDE is cluttered and there is no central document that KDE developers can refer to
    > in order to achieve proper usability.

    KDE usability is comparable to (if not IMNSHO better than) GNOME usability for several reasons.

    The technical framework of KDE is a lot more advanced than the GNOME stuff. Many things in the GNOME HIG are simply coded into the basic libraries of kdelibs and qt. Therefore ALL KDE apps follow the same look and feel automatically. In GNOME, a developer has to follow the HIG manually.

    Also the GNOME team has at times been arrogant and has ignored normal users' requests. Spatial browser mode, crippling configuration options.

    Some GNOME app developers (Ximian) just love Microsoft apps and copy them down to the last mistake. (Evolution)

    Finally there is and has been for over 5 years the KDE style guide, which has always been the central reference for all usability questions in KDE. It predates the praised GNOME HIG by two or more years.

    If you are interested look here:
    http://developer.kde.org/documentation/stan dards/k de/style/basics/

    --
    Moritz
    1. Re:KDE Style Guide by Anonymous Coward · · Score: 0
      or here

      dever

  88. KDE UI Guidelines by KlaymenDK · · Score: 3, Informative

    Just FYI, KDE has UI Guidelines too:
    * User interface design guidelines: http://developer.kde.org/documentation/design/ui/
    * KDE Style Basics: http://developer.kde.org/documentation/standards/k de/style/basics/

  89. funny by hitmark · · Score: 1

    i like the categorys:

    1. beginner/experimenter
    hmm, ok? is that the same as the hobbyist?

    2. beginner/hesitant user
    forced ex-windows user?

    3. advanced unix user
    now wtf is this person doing useing a desktop at all?i thought these people only looked at the console

    4. advanced mac user and system architect
    whats so special about being a mac user? and how does it help being a system architect?

    --
    comment first, facts later. http://chem.tufts.edu/AnswersInScience/RelativityofWrong.htm
  90. XMMS GOD DAMN WORKS IN KDE! by Anonymous Coward · · Score: 0

    Yes it does! You only need the Gnome/Gtk/whatever libs. I use XMMS regularly on top of KDE w/o problems.

  91. MOD DOWN THE LIAR by Anonymous Coward · · Score: 0

    there is no central document that KDE developers can refer to in order to achieve proper usability.

    FALSE. It even existed before GNOME's.

    Every option you give a user is a choice he has to make.

    RIDICULOUS. If the user doesn't like options, the defaults are perfectly good, and he doesn't need to change them.

    the result is a more consistent desktop.

    HILARIOUS. GNOME is more consistent than KDE? That's a good one.

  92. Ion3 by ultrabot · · Score: 1

    Just use ion3. it's apt-gettable in Sid, and has worked for me without a hitch.

    Tip for those who are about to create a multimedia set-top box - install ion. You want only minimal mouse interaction there, but still having X around enables use of vital software like streamtuner.

    --
    Save your wrists today - switch to Dvorak
  93. Re:MOD UP!! by Diamon · · Score: 1

    You mean like this? http://info.linspire.com/lindowslive/p2p.html

  94. As Inigo would say... by sfh · · Score: 1

    "The orthogonality of function from application to application is apparent." "The use of the icons, with few exceptions, aids the orthogonality of the interface" You keep using that word -- I do not think it means what you think it means

    1. Re:As Inigo would say... by Anonymous Coward · · Score: 0

      oops sorry i modded you down when i meant to mod you up. i am an idiot.

  95. Re:This fucking idiot should go home by smittyoneeach · · Score: 1

    I think there is a difference between healthy diversity and utter fragmentation.
    The march of F/OSS is impeded by the embarrassment of riches.
    For a random example, consider build systems. Besides autoconf/automake, how many others can you name?
    If I was Redmond, I'd be putting those cash reserves into funding hundreds of new, slightly incompatible, F/OSS projects on SourceForge. Them Indians may outnumber the cowboys, but, balkanized, they can't threaten the wagons...

    --
    Get thee glass eyes, and, like a scurvy politician, seem to see things thou dost not.--King Lear
  96. Stunning facts about GNOME by thinkfat · · Score: 1

    ... they use icons.

  97. Re:Getting rid of spatial mode / Communication by fforw · · Score: 1
    Its not a matter of my own opinion - its a matter of our clients. I work for Red Hat in Australia and I can attest most of our clients don't like spatial mode. I'd like to have it either explained better (welcome to Gnome 2.6! We've included a new spatial mode! Its better for X reason! If you don't like it though, do Y!) or changed by default.
    Usefull things first: Well, there are two ways to get rid of spatial mode :
    • Use the --browser command line option : (e.g.
      nautilus --no-desktop-nautilus
    • change the gconf key -
      gconftool-2 --type boolean --set /apps/nautilus/preferences/always_use_browser true
    ( The gconf key is likely to get a nautilus preferences setting soon )

    I tend to agree with you about the lack of communication between the gnome developers and their user base. Maybe the gnome developers should do some more "public relations" after new releases. or maybe the user base you just read the documentation carefully.

    --
    while (!asleep()) sheep++
  98. Re:This fucking idiot should go home by Anonymous Coward · · Score: 0

    The part of the Gnome compilation that requires Python could be rewritten in Bash. There is no good reason why Python should be required for this one, insignificant part of the installation.

  99. Program Installation... by rdc_uk · · Score: 1

    "The answer could be an installation application that can speak to all of the popular distributions. It could be built in such a modular way as to allow new backends and functionality. Alternatively, a standard application installation procedure could be created that is supported by the majority of distributions (perhaps in addition to the native methodology)."

    As a long-time Windows user, on and off trying to make a transition to Linux (as in tried several times, always reinstalled windows in the end) this is the single thing that jumped to my mind when trying Linux.

    Basically, how the **** do I install / update programs?!? (I know, I RTFM; but why do I have to read a different friendly manual for each distribution I trial run?)

    WTF is an emerge, and if its so great, why does only gentoo use it? What is an RPM? Exactly HOW do I install or upgrade on mandrake (realy; i have no idea!) What is a modprobe - and why should I need to know? For a desktop OS, _no_ configuration change should be commandline only... (like samba; I got it working no problems, but had to go to a root prompt and edit a file in vi - WTF?)

    All these rants and more should not go through the new adopter's mind, if Linux is to ever become a mainstream desktop OS - because average users don't RTFM (you don't have to if you want to be a dumb-user in windows/macos), and don't have friendly sysadmins to do the setup for them. /Rant

    thanks for your patience; feel much better now ;)

    1. Re:Program Installation... by leinhos · · Score: 1

      "The answer could be an installation application that can speak to all of the popular distributions. It could be built in such a modular way as to allow new backends and functionality. Alternatively, a standard application installation procedure could be created that is supported by the majority of distributions (perhaps in addition to the native methodology)."

      At some point a new user has to be introduced to totally new concepts -- Package management (a la RPM, dpkg, etc.) for instance. Also, the concept of what a distribution really is seems to be new -- The distribution is an attempt to standardize application installation and management (along with *alot* of other things). The reason one chooses one distribution over another is the overall structure and approach of the packagers (thus different distros like Debian, Redhat, and Gentoo). No one knows what works best, and it probably depends on who you are. Trying to "unify" all the different distos so that they all can use each other's packages is missing the point. That is addressed by the GNU build tools (gcc, make, autoconf, automake, etc). In most cases, all the distros rely on the GNU toolset to generate packages.

    2. Re:Program Installation... by rdc_uk · · Score: 1

      "Trying to "unify" all the different distos so that they all can use each other's packages is missing the point. That is addressed by the GNU build tools (gcc, make, autoconf, automake, etc)." I think, if you reflect, you'll find that you've missed the point. neither I nor the article mentioned having all the distributions use the same packaging system. Ever. The original article suggested a unified GUI to control (graphically) any of the varying install methods in some sort of "unified" method - that doesn't imply shoe-horning them all to use the exact same wizard / controls, just having a single application in the desktop system to drive the correct one. (Think: gnome/kde/whatever provides the very basic/generic controller, each distributor can write the specific handler for their distribution and add that to their install My comment was more a rant against the depth to which a NEW user has to read in order to first; find out what bizarre name this distribution has given to the mechanism for "Install New Program" or "Upgrade Installed Program" - hint; its never "Install Program"! And second the further depth to which I must plunge in order to do this; hint 2 "make all" is not a suitable install method in the 21st century - unless you are a sysadmin/nerd.

    3. Re:Program Installation... by Anonymous Coward · · Score: 0

      gentoo ?

      just type

      emerge -u appname

    4. Re:Program Installation... by rdc_uk · · Score: 1

      Ugh! some facts of computing for you all: "possible" != "useable" "rtfm" != "adequately explained" "i know how" != "accessible to general public" and finally "i can answer specific instance" != "generic argument discredited"

    5. Re:Program Installation... by DMadCat · · Score: 1

      Basically, how the **** do I install / update programs?!? (I know, I RTFM; but why do I have to read a different friendly manual for each distribution I trial run?)

      WTF is an emerge, and if its so great, why does only gentoo use it? What is an RPM? Exactly HOW do I install or upgrade on mandrake (realy; i have no idea!) What is a modprobe - and why should I need to know? For a desktop OS, _no_ configuration change should be commandline only... (like samba; I got it working no problems, but had to go to a root prompt and edit a file in vi - WTF?)



      Yep, I had the same questions when I first started using linux. I got frustrated and installed FreeBSD only to run into the same questions (though they were answered differently) so I started poking around to figure it out. It took me about 2 months of reading, digging around, and playing with various things (including different distros) to figure things out and find a direction.

      Oddly enough, I also had these same questions when I bought my first (pentium) computer back in '96. I'd been away from computers since the 286 era and had no idea what this Windows animal was.

      It took me about two months of digging around, reading a lot, and playing with stuff (including several reinstalls and by several I mean at least twice a week) to finally get a handle on it and figure things out. Now I can make most Windows OSs dance to my tune (insofar as is possible).

      The point? Most "dumb" users out there can barely answer those questions in Windows. All platforms have a learning curve.

      Windows claims to be the easiest to use but in truth that's only because it's been exposed to more people. My sisters can (with some accuracy) answer my Dad's questions about how to use Windows XP. The more people using it the more help you have.

      With Linux, once I found Linuxquestions.org and a few other sites, I got up to speed pretty quickly. I found there were alternate ways of doing things than in Windows but when you think about it they're really no less or more efficient. Just different.

      I use Slack and tend to prefer to compile from source when possible but I have the option to use the package installer to install pre-compiled binaries. More difficult than using Microsoft's Installer? Not particularly. Different, yes.

      Were I to have started out using Linux rather than Windows I might boot up Windows and wonder where in the hell I'm supposed to log in or how I'm supposed to compile my program's source code so I could install programs.

      I have a sister who answers my Dad's questions about AOL email but spent MONTHS running a computer that took literally ten minutes to boot and two just to open a program because she had absolutely no idea how to uninstall programs. Granted it's an old Pentium 266 running Windows 98 but after I saved her stuff, blew the old stuff away, and reinstalled Windows 98 it runs like a champ doing everything she needs it to. She still doesn't know how to uninstall programs simply because she doesn't want to know. If Windows is so simple and user friendly shouldn't it already know what she wants and do this stuff for her?

      To conclude, just because you're familiar with one environment doesn't mean it's any better or any worse than any other environment. It's just different. The more work you put into learning it the more you'll get out of it.

      Oh, and just to stay on topic, Spatial blows goats. The first thing I did after installing Windows was to make sure everything opened in the same window. The first thing I do in Mozilla/Firefox is configure tabbed browsing. If I could get every application/browser/everything to open in one tabbed window I'd be there! Multiple windows = Die die die!

      Thank you.

    6. Re:Program Installation... by leinhos · · Score: 1

      "I think, if you reflect, you'll find that you've missed the point. neither I nor the article mentioned having all the distributions use the same packaging system."

      Sorry, my mistake.

      The "'unified' method" issue is a valid one. Yum (an others like it) have made some progress to this end (yum talks redhat/mandrake rpms as well as debian pkg -- it also goes a long way to resolve dependancies and conflicts automatically). Wrapping yum in a gui would be nice. I would say that the problem is not with "installing programs", but with package management (packages may or may not contain "programs").

      I think, however, that many people get the terms "Linux" and "Distribution" confused (as well as "Desktop Environment", I suppose), and when someone says "Linux as a Desktop OS", they are really referring to a "Desktop Linux Distribution". Even if Windows and MacOS used the same kernel, you wouldn't (necessarily) expect the user experience to be the same. I suppose (which is your point) running the GNOME Desktop should have a unified interface to system-level configurations (including package management) across distributions, but that (hopefully) is what GNOME System Tools is all about.

  100. Re:This fucking idiot should go home by some+guy+I+know · · Score: 1
    If you want to compile (or use, in the case of interpeted languages) a piece of software which uses a certain language, you have to have that language installed.
    Except that no part of Gnome itself is written in or uses Python.
    (That is, an installed version of Gnome does not need Python.)
    One -- just one -- of the Gnome libraries has an installation script that is written in Python.
    The developer is rewriting the script in bash, so that Python is no longer necessary to install Gnome.
    The person to whon I responded quite rudely asserted that the developer was "a goodam idiot" for doing this.
    I think that he is wrong, and I wrote why.
    --
    Those who sacrifice security to condemn liberty deserve to repeat history or something. - Benjamin Santayana
  101. Hopefully by beforewisdom · · Score: 1

    Hopefully this review will have something nice to say so the Gnome team doesn't get embarrassed again by one of their developers whining like a spurned junior highschool diva and complaining about how the users just don't get it.

  102. Mozilla by some+guy+I+know · · Score: 1
    It's a desktop environment test session, and this guy's first thought is to download and install stuff which could reasonably be expected to be there.
    OK, gotcha, I misunderstood what you were criticizing.
    I read much of TFA, but only skimmed the actual test session logs/notes themselves.

    However, depending on the desktop, one of the first things that I might do is download the latest version of this, that, or the other thing.
    Before I did, though, I would check to see whether the latest version is already installed.
    if you're there to test a desktop you shouldn't really be trying to avoid it via the shell or customise the install with your own software.
    I would think that that would be one of the tests that should be done.
    How easy is it to install my own/other stuff?
    How well does my own/other stuff integrate with what's there?
    How easy is it to use several terminal windows, and switch between them?
    Etc.
    These are the kinds of things that some users of the desktop will be doing, so I see nothing wrong with this person doing them.
    It's as much part of the "usability" of the interface as any other part.
    --
    Those who sacrifice security to condemn liberty deserve to repeat history or something. - Benjamin Santayana
  103. File Requesters.. by polyp2000 · · Score: 1

    I am not trolling but i feel the need to say that I really am surprised none of the testers mentioned how bad the file requester is, it hasnt improved a great deal in the latest version. However i dont know what they might have been used to, I havent used windows for a while so it might be better in their eyes.

    There really is no comparison to the flexibility of the KDE file requester
    http://www.blackapology.com/downloads/f ilereq1.png

    I cant help but think that gnomes obsession with human interface guidelines and usability studies must be flawed in some way.

    The usability study while interesting is simply asking users to perform a number of functions. EG can you open a file or can you view a pdf or browse the web etc. How about "can you open a file that is tucked away deep in the bowels of the filesystem in some arbitrary directory" , id be willing to place money on the fact that the files these users were asked to open were located conveniently in the current path.

    Usability seems to be based on whether or not people can perform certain tasks and not whether the way those tasks can be improved. It is deemed a success if the tester succeeds in performing a set goal. A useability study should be about using a desktop in a specific capacity for extended periods of time. Only then will the annoying problems start to crop up.

    Nick ...

    --
    Electronic Music Made Using Linux http://soundcloud.com/polyp
    1. Re:File Requesters.. by jcupitt65 · · Score: 1

      You've linked to a shot of the gnome 2.4 file requestor. This is what the gnome 2.6 one looks like.

  104. Re:gramer correction by Hognoxious · · Score: 1
    voice recognition [...]Someday someone will make it work, and all the endless "desktop" arguments will be moot.
    Bzzzzt, wrong. For so many reasons.
    --
    Confucius say, "Find worm in apple - bad. Find half a worm - worse."
  105. Re:as a GNOME user by Anonymous Coward · · Score: 0

    GNOME freaking SUCKS. But, it's the best thing going for Linux. Everything in GTK looks like garbage, acts like garbage, and is completely incoherent mindless garbage. The desktop is teh SUCK, and very little works in any intuitive fashion.

    Try KDE, its much better!

    That said, absolutely NOTHING in any other desktop or window manager works in ANY kind of intuitive fashion.

    Most likely right, but some things are better than others.

    by the way, GTK 2.4.x's file-selection-dialog is a complete and total piece of shit.

    I have to agree with you here, its not much better in 2.6. And as its such a fundamental part of the desktop it doesnt bode well for the rest of it.

    And the fact that sometime in the 2.4 tree, windows that have no widgets appear with their titlebars on the right hand side, instead of on the top.. that's fucking stupid. Even stupider than when the previous behavior was to not have a titlebar/close widget at all.

    Man.. I'm glad I dont use Gnome

    Whomever designed this garbage is a fucking moron.

    I prefer to say that their Usability Studies are a waste of time and there obsession with Human Interface Guidelines is fundamentally flawed.

    And this is neither TROLL nor Flamebait, so suck it moderators.

    Maybe, maybe not but methinks you should try an alternative WM like KDE ... It is a lot better, in so many different ways.

  106. The "5 users is enough" idea is misleading by Halo- · · Score: 1
    The whole idea that "5 users is enough" for a UI is misleading. I'm far from an expert, but I am theoretically a trained "Cooper Interactive Design Engineer". (Woohoo, let's here it for a week and a half of classes and some books!)

    The problem is that you really need to build archtypical "personas" for each of the major "roles" which use the product. The way people use a product is greatly influenced by what they are doing with it.

    A product with only a few clearly defined use-cases, the number of required test users could easily be as low as five, but Gnome is really a lot more. These tests weren't just on the widget set, but on the applications which make up the Gnome Desktop. The way a programmer uses these is likely to differ from how a graphic artist uses them, which is likely to differ from how the average web-browsing user is going to use them.

    I'm not slagging on the study. Frankly I'm delighted someone is doing it, but Linux (and yes I know Gnome isn't just Linux...) tends to be an operating system which supports a broad spectrum of users.

  107. Re:I was thinking you are a tard. by Anonymous Coward · · Score: 0
    Sometimes he doesn't want to make a choice, he just wants to get stuff done.
    I disagree.
    As you're incapable of using one of the many possible methods (as illustrated) to distinguish excerpts from new content, why should we give any weight to your opinions on usability, or indeed anything?
  108. Because you CALL it Gnome 2.6 by Chemisor · · Score: 1

    > I don't blame that on Windows, I blame it on the
    > respective products. So why do so many linux
    > review sites do the opposite?

    Because when you talk about Gnome 2.6 you mean Gnome 2.6 AND all its default applications. When somebody tells you to "install Gnome" he means getting the applications too, because each desktop has its own associated suite of them. Gnome has its apps, KDE has its apps, and plain X11 has its apps, neither of which usually plays well with others. In Windows there is a very clear distinction between "Windows" and "Applications", even though "Windows" also includes little programs that come with it, like minesweeper. One does not imbue "Windows programs" with the same meaning as "Gnome programs" because every program runs on Windows.

  109. Comment removed by account_deleted · · Score: 1

    Comment removed based on user account deletion

  110. Freshmeat is faster by Chemisor · · Score: 1

    > Since when does Freshmeat = the open source community?

    Almost all OSS projects advertise on freshmeat, so I would say that the = is justified.

    > They are a 'unix program website' with every type
    > of license included like proprietary stuff.

    There is nothing wrong with selling your code. I would do it too if I had something anybody would buy.

    > If anything you should have tried sourceforge first right?

    Sourceforge is considerably slower than freshmeat and its search is far more primitive due to lack of proper categories. The slowness is actually my main gripe because on my dialup link it takes up to 30 seconds to load a single search result page, which makes the search pretty much unusable unless I already know approximately what I am looking for.

  111. A great acheivement for Open Source by Anonymous Coward · · Score: 0

    User #1: "Liked the fact the color showed up correctly, as did the table, in the PDF viewer".

    Is this really worth mentioning getting the colors right as a benefit? Isn't that kinda expected?

  112. Slashdot is definitely gnome-centric by Knights+who+say+'INT · · Score: 1

    Most of the things the users complain about Gnome in that study are already fixed in KDE. I mean, Gnome is attempting to do The Right Thing, not being easy to use. Hell, they did switch the positions of "yes" and "no" buttons, didn't they?

  113. A Couple Fundamentals of User Friendliness by freezin+fat+guy · · Score: 1

    Actually having the words "Applications" and "Actions" available for your clicking pleasure is already a useability improvement from just presenting a foot. There's nothing instinctive about clicking a foot! (or a K)

    We also have to make the nomenclature friendly. Names like "daemon" and even "ghostscript" are inappropriate. Great wars are fought over spiritual beliefs. Terms like "Services" are much more appropriate and better explain their purpose.

    I'll also throw my hat in the ring with those looking for a more standardized install method. I do like the simplicity of the OSX/ROX idea but it may be that someone comes up with a better solution.

    It is exciting to watch this all evolve isn't it? :)

  114. Thank you! by rd_syringe · · Score: 1

    I'm so sick of seeing people bitch and call the button order "wrong." It immediately singles out all the ignorant people for me.

    It's not wrong. It's just the Microsoft order you've been conditioned on. You guys claim that people prefer Windows simply because they're used to it, then bitch about Gnome's button order being "wrong." Apparently none of you realize it's been Apple's button order for quite some time and that you only think it's wrong because you a.) have been conditioned because of Windows, and b.) you haven't bothered using the damn thing for more than five minutes (where you'll immediately get used to it and realize why the order is more intuitive that way).

    1. Re:Thank you! by Pinky · · Score: 1

      Having used both mac and PCs I'm quite surprised anyone actually cares about dialog box button order. I find the close/minimize/resize (maximize)) button order differences between macOS 9, MacOS X and windows much more jarring.

      Then there are things like ctrl-q not quitting all apps and ctrl-w not closing all windows while alt-F4 does.. alt-tab working slightly differently between all platforms.. the tendency of auto-selecting everything in a field when activated.. copy-paste action having to do with the active selection... apps not bringing all relevent windows forward when one is activated... empty space in a List causing or not causing all items to deselect.. etc.. yuck... and people are complaining about button order.. woop teee dooo..

    2. Re:Thank you! by jschottm · · Score: 1

      I don't care what order the buttons are in, so long as I can make it consistant across every platform I use. I spend about 50% of my time in Windows, 40% in Linux, and 10% in OS X. OS X could easily have a larger portion, except that it's so annoyingly unconfigurable, and I spend as much time getting fustrated with it than being productive.

      The "right" way is how my muscle memory has been programmed, and for better or worse, that's the Microsoft order (despite going for 6 years barely using any MS products).

  115. This isn't a usability test ... by Larthallor · · Score: 1

    ... despite the name. It's a test to see how easily Windows and Mac users can apply their existing skills to using Gnome. Each user was asked to accomplish a task without being shown how to do it the "Gnome way".

    Seems to me that usability should be a measure of how quickly and easily tasks can be accomplished when using the operating system as intended, which implies that the user must know how to and be practiced in it's use.

    For instance, take the tested tasks and train users in how to accomplish them in the most efficient way available for each OS. Let them practice for some time with each. Then, do a timed test of how long it takes them to accomplish the task in each environment. THAT should be what we call usability.

    This is really a test of people's initial reaction to having to use a similar, but different UI with no training. How valuable is that? Let's see: you set someone, who may not feel exactly secure using a computer in the first place, in front of a new UI and say that they have to try to get some stuff done. When they try to do what's worked for them in the past and it doesn't work, are they going to feel good about that? No. They'll feel that either they or the UI are stupid. And, human nature being what it is, they will generally assume that it must be the new UI. ESPECIALLY if you tell them they are helping you test the usability of the new UI.

    How can the user take advantage of a better UI workflow if s/he is trying to do things the way it was done using the OS their used to?

    How can all users go (untrained) through the tests as quickly and easily as the UI they've been using for five frigging years unless the tested UI is essentially identical?

    I bet that if you showed them a tutorial video of how to accomplish all of the tasks and then asked them to try the tasks themselves, their reactions would have been much more positive. And, the researcher's recommendations wouldn't amount to "Hmmm, Gnome has more work to be done - it's not enough like Windows AND MacOS yet." Never mind that it can't be both. Instead, you'd have more helpful information like, "Gnome allowed users to reach a web page 17% faster than Windows. However, e-mail took 22% longer to use and needs some work."

    Intuitive is nice, but is all about making connections with things the user already knows how to do. That's why icons and terms like "trashcan" are considered intuitive. When GUIs were new, they were designed to work like real-world objects enough that people could get a clue. Now that most of the people (in the US, anyway) have used a computer to some extent for years, an intuitive computer task is one that works like Windows. So, if you want to be intuitive to ex-Windows users, clone the Windows UI. And, of course, that is essentially what has happened. In the case of this test of Gnome, you'll notice that the rough spots in the testing were in those areas where Gnome DOESN'T work like Windows.

    1. Re:This isn't a usability test ... by bradleyland · · Score: 1

      I can go from a VW to an Acura and I don't have to relearn how to use a car. I don't need specific training on how to operate an Acura. I make small adjustments. Difference like "discard" changes are easy to decipher in context. If you can't get past that, you're just plain computer illiterate. However, other tasks like installing (AND removing) programs should be much easier than they are on Linux and on the Mac.

      There's lots of headway to be made, and if you put the burden squarly on the user to "learn" the "GNOME way", you'll be having this same discussion 10 years from now.

  116. I concur by Crag · · Score: 1

    A user is only new to a tool once, but if the tool is any good the user will use the tool for the rest of her life, making the time spent learning the tool insignificant. Rather than making interfaces 'discoverable', I'd like to see interfaces made 'efficient' and augmented with a tutorial mode. There is no reason to combine tutorial mode with day-to-day usage mode. This applies equally well to software as to anything else.

  117. From a guy who just wants to use Linux by bradleyland · · Score: 1

    Hi. I know this is a very sensitive subject (as I can tell from the responses/debate raging here), but I'd like to make a plea from a plain old user's perspective. Would it be so bad if I could move from Windows to Linux without relearning every detail of my day to day computing needs? I'm not asking for a copy of Windows... well, maybe I am... what does it matter? I want to move away from Windows. I really do. The problem is, I've tried Linux several times in the past, and today I still run into the same problems I have in the past. Really simple stuff. How do I install a program? Ok, I discovered rpm's and even used a couple. Once the program is installed, where did it go? How do I start it? These things are really simple, and everyone is still arguing over spatial interfaces. My mother could never deal with this level of complexity. Consider this my plea. I dislike Microsoft from many, many perspectives. I paid the extra money to switch to a Mac at home because of this; however, I really enjoy building and customizing my own systems, so I keep a PC around for gaming and those occasions you just "need a PC". Plus, Apple is very fond of releasing new versions of their operating system every year and then not making program updates available to users with "old" versions. The upgrade cycle is going to bankrupt me. I would be happy to pay for Linux, and I would shout to all my friends and relatives from the rooftop if I knew of an alternative operating system that I felt confident they could use. I think that all of the issues brought up in this usability review hit the nail on the head. I'm hopeing deep down inside that the community will read and take to heart these considerations.

    1. Re:From a guy who just wants to use Linux by The+MESMERIC · · Score: 1
      It very much depends on which distro you are going for.
      Now I don't know if there are other distros apart from YellowDog that runs on a Mac.
      Assuming you want to install it on a Mac, otherwise you have more choice.
      Installing a standard program should be a breeze - many or most Linux distros - have a way to fetch a program for you and install it automatically (some graphicall other through the console:
      apt-get [name-of-program] (Debian + others)
      urpmi [name-of-program] (Mandrake)
      yum [name-of-program] .. etc (Yellowdog?)
      Most distros or distro-genre have this sort of "remote" installation.
      Many even resolve you the headaches such as downloading necessary extra programs to make it work (the so called dependancies)
      It's really not that bad.
      Problems will start only if you want to get that much more from the system. Installing the latest video driver, or compiling a program from source (perhaps to gain speed, or perhaps because it's a rare program published only as source).
      You might get mixed up trying to make things like Eclipse run - but I don't think you'd use it - its a development tool.
      NVU is another example, an HTML editor that may be attractive to some but is not readily compiled for all distros.
      Compiling is not that bad either; after the automatic "remote" installation (which should cover 70%) or Linux apps;
      the following 4 lines performed as root should cover some 20% more:
      tar xfz [program-source code].tar.gz
      cd [program]
      ./configure
      make && make install
      Scarier I agree.
      But for most of your basic needs you should be OK.
      Forums such as LinuxQuestions are pretty helpful and friendly towards new-starters (but it pays searching their database before posting stuff).
  118. Re:This fucking idiot should go home by raodin · · Score: 1

    Ah, I figured one of the apps actually used it after install. In that case, the dev made a bad choice, but really, its not a big deal.

    I didn't look into it too closely, since I use Gentoo - my whole system depends on Python.

    I still think its a pointless complaint, though. Yelling about having a language installed when you're compiling software, even if its only used for an install script, seems pretty lame.

  119. 3x5 is better by Nitish · · Score: 1

    Your mathematics is impeccable; 3 tests of 5 users each should, with those assumptions, find less of the original bugs than 1 test of 15 users. That isn't very rational, but when was math ever rational? :-)

    What you didn't consider, though, is that the designers make changes after every test with 5 users. So after the first test finds 80% of the problems, they are corrected, but perhaps some new ones are introduced. The new users find 80% of the original problems that were undiscovered, AND 80% of the new problems. And then there's another iteration.

    The advantage, therefore, is that you discover almost all the original problems and also get to try out possible fixes and uncover problems with the fixes

  120. Re:Couple things I do not Like, by bradleyland · · Score: 1

    No, but an error message with some context and a user friendly message would be nice. My mother does not understand mount or unmount. She would understand, "CD-ROM drive cannot eject because it is in use." Is that such a terrible thing?

  121. ion is great in MS Windows, too! by JCholewa · · Score: 1

    There are no fully featured, complete applications which mimic KDE/GNOME programs like Konsole or gnome-terminal -- that is, no console/terminal programs that support MDI so that you don't need to waste real estate on the task bar for each of the many command line boxes you might open in MS Windows. I eventually was able to get KDE working in Cygwin, but it's pretty slow on this 550MHz PIII.

    I set up ion (it took a *long* time to find a version that would compile on cygwin, though) in a fixed-sized X11 session and gave it konsole-like keybindings (so that I could Shift+Left and Shift+Right to move between terminal sessions. So it's like I have an MDI terminal app. It's normally bash, but I can also get it to run cmd.exe (though Tab completion and history is broken when I try to go into this mode).

    It's very cool. I also used ion in Linux when my Duron-800 system started having capacitor problems on its motherboard (it would crash out of Win32 and X11 sessions using full-fledged window managers). I learned a lot about getting full functionality of my system in regular tty modes (fbtv, fbxine, aumix and giFTcurs rule!).

    I haven't tried it in FreeBSD. I took too much perverse glee in having an employer give me carte blanche with respect to setting up our web/mail/wap/ldap/im server, so I was perfectly happy to load it up with a full KDE 3.2.3 and OpenOffice setup, even though it's a thousand miles away and not connected to a monitor(!).

    Disclaimer: I actually did set up the server well, and I'm very good with keeping it running, to the point where it's reliably saved the employees from the *other* servers we use.

    --
    -JC
    http://www.jc-news.com/coding/freedom/

  122. I'm glad I moved away from the Gnome / KDE debate by GedConk · · Score: 1

    Seeing how it will probably never end ;)

    So, I for one welcome our new Fluxbox Overlord !

  123. Use evilwm. by Anonymous Coward · · Score: 0

    Read the 1 page documentation on its keyboard shortcuts and you'll never use a different window manager again. Thinking about going back to KDE gives me heartburn.

  124. Comment removed by account_deleted · · Score: 1

    Comment removed based on user account deletion

  125. Re:MOD UP!! by Diamon · · Score: 1

    And which version would be free? I just tried the coupon code on all of them (as well as trying linspire as the coupon code) and it didn't work.