Slashdot Mirror


KDE And Gnome Cooperate On Interface Guidelines

An anonymous reader submits "Competing infrastructures may foster improvement in each desktop, but the Gnome and KDE hackers still know how to work together when needed. The Free *nix desktop has been improving quickly. Red Hat's unified desktop was controversial, but obviously the right decision for regular users. Now that KDE and Gnome have decided to combine their Human Interface Guides, it can be done right--by the developers themselves. Note: they also want to involve 'people working on other non-KDE non-GNOME HIGs.'" Update: 02/03 20:19 GMT by T : Apparently not everyone's browser can read http://freedesktop.org, so the initial link up there now sports a "www" as well. And it's .org -- sorry.

313 comments

  1. In a related story... by leviramsey · · Score: 3, Funny

    Presidents Bush, Chirac, and Hussein were found making out in a hot tub.

    1. Re:In a related story... by teamhasnoi · · Score: 0, Offtopic

      Ha! That's old news - they've been in bed together for a long time... ;P

    2. Re:In a related story... by diffuze · · Score: 0, Offtopic

      Odd how posts like:
      " Cats and dogs... Living together. Panic in the streets."
      gets modded as offtopic while posts like:
      "Presidents Bush, Chirac, and Hussein were found making out in a hot tub."
      are modded as funny.

    3. Re:In a related story... by leviramsey · · Score: 0, Offtopic

      Don't blame me... I liked the "cats and dogs" post....

    4. Re:In a related story... by Bunji+X · · Score: 1

      Thanks for sharing with us your formidable insights in world politics.

      --
      ---
      The combined human population is enough to feed every living tiger for app. 28000 years.
    5. Re:In a related story... by Twirlip+of+the+Mists · · Score: 0, Offtopic

      Welcome. For more goodness, be sure to check out Little Green Footballs every day.

      --

      I write in my journal
    6. Re:In a related story... by Bunji+X · · Score: 0, Flamebait

      Nice, they finally managed to gather all the morons on the net in one single site. :)

      Please post more hillarious links when you find them!

      --
      ---
      The combined human population is enough to feed every living tiger for app. 28000 years.
    7. Re:In a related story... by Twirlip+of+the+Mists · · Score: 0, Offtopic

      Hee hee. That's pretty funny. First I posted an anti-France comment. It went unmoderated. Then I posted a pointer to a warblog. It went unmoderated. But when I posted a comment calling Slashdot a "nest of anti-American collectivist nutcases," I got moderated as a troll!

      Remember, kiddies. If you value your karma, you will speak naught but good of Slashdot.

      --

      I write in my journal
    8. Re:In a related story... by Bunji+X · · Score: 1

      A few things you can learn here if you care:

      1) Slashdot may be based in USA, but is still an international forum. Don't think people of other nationalities will hail you for racking down on their country.

      2) Most of us non-Americans are not anti-American, we are just not as (hysterically) pro-American as you would like.

      3) Remember, kiddo. If you value your karma, you will speak naught before thinking.

      --
      ---
      The combined human population is enough to feed every living tiger for app. 28000 years.
    9. Re:In a related story... by Twirlip+of+the+Mists · · Score: 1

      1) On the Internet, international blah-blah is usually, not always but usually, a code word for "wrong-headed idiot." I'm sure there are as many smart people per capita outside the US as there are inside, but it doesn't seem like very many of them are posting messages on Slashdot.

      2) In order to qualify oneself as pro-American or anti-American, one must first know what the terms mean. Socialism, for example, is anti-American. There are many Slashdotters, both American and otherwise, who fail to understand this simple concept.

      3) Remember, kiddo. I say what I mean and post what I think, and let the karma fall where it may. Seems like more people agree with me than disagree with me, but I just consider that to be a happy coincidence.

      --

      I write in my journal
    10. Re:In a related story... by Bunji+X · · Score: 0, Flamebait

      1) Intelligence is not the same thing as sharing a specific political view, or nationalistic view for that matter.

      2) Who made you the judge of what is anti- or pro-American? I think a lot of American socialists would disagree with you.

      3) First complaining about lost karma, m.o.c., or whatever, then saying you don't care? I think we have a word for that kind of behaviour. It begins with "hypo" and ends with "crite".

      --
      ---
      The combined human population is enough to feed every living tiger for app. 28000 years.
    11. Re:In a related story... by Anonymous Coward · · Score: 0

      Blame it on the fact that half the people that visit this site are too young to even remember Ghostbusters. It's a weird feeling.

    12. Re:In a related story... by Twirlip+of+the+Mists · · Score: 1

      1) Not sharing views that are obviously correct is a sign of a lack of intelligence.

      2) I most certainly am a judge of what is pro- and anti-American. I am an American, which means I get to made those decisions for myself. I have been a student of history and political philosophy throughtout my life, so I feel I am qualified to make the judgments. This is a key differentiating factor between people of character, who understand that it's possible to know what's right and what's wrong, and moral relativists, who don't. American socialists, for example, can get bent.

      3) Please point out one-- one will do-- example of my complaining about lost karma. I made a remark about moderation up-thread, but as you'll note it was in the context of a "hee hee." That's hardly complaining.

      --

      I write in my journal
    13. Re:In a related story... by Anonymous Coward · · Score: 0

      "Presidents Bush, Chirac, and Hussein were found making out in a hot tub."

      Bush, Chirac and Hussein. That's what the parent stated. I don't see how this(parent) post more off-topic than the parent (parent parent) that it should be modded OT while the grandparent is modded funny.

    14. Re:In a related story... by Bunji+X · · Score: 0, Flamebait

      1) Saying that specific views are "obviously correct" would by many be considered the pure definition of stupidity.

      2) Shouldn't the fact that you have been a student all your life tell you something? Btw, having the ability to change points of view when proven wrong is not a character flaw, it's a strenght and... a sign of intelligence. (That said, I still won't buy your point of view of pro- and anti-american.)

      3) Wrapping complaints in a joke or a smile is the sign of cowards and hypocrites.

      --
      ---
      The combined human population is enough to feed every living tiger for app. 28000 years.
  2. Alternatives are still good by 3.1415926535 · · Score: 0, Offtopic

    As long as we always have things like Fluxbox in addition to KDE/GNOME, I'll be happy.

  3. KDE *and* Gnome co-operate? by IWantMoreSpamPlease · · Score: 0, Flamebait

    Hell must be frozen over now.

    --
    So rise up, all ye lost ones, as one, we'll claw the clouds.
    1. Re:KDE *and* Gnome co-operate? by Dan+Ost · · Score: 4, Informative

      I know this was probably ment in jest, but just
      in case you were serious, you should have a look
      at the various mailing lists. I think that you
      would find that there has always been a fair
      amount of cooperation between developers of the
      two projects.

      --

      *sigh* back to work...
    2. Re:KDE *and* Gnome co-operate? by IWantMoreSpamPlease · · Score: 1

      Yes, it was in jest, I have no idea what KDE and Gnome are, beyond a GUI...I only have heard that there are 'disagreements' from the /. crowd. I use BeOS myself and we don't have GUI problems :)

      --
      So rise up, all ye lost ones, as one, we'll claw the clouds.
    3. Re:KDE *and* Gnome co-operate? by Anonymous Coward · · Score: 0

      Yeah well at least people give a rats ass about our OS.

    4. Re:KDE *and* Gnome co-operate? by supun · · Score: 2, Insightful

      It's not the developers that get into KDE vs. Gnome battles, it's the users. Normally, developers on OSS project have a lot of respect for their "competitors."

      --
      :w!
    5. Re:KDE *and* Gnome co-operate? by The+J+Kid · · Score: 1

      What did you want?

      KDE *without* Gnome co-operate?

      --
      Moderation: +4. Modded 70% Funny and 30% Overrated. 100% Saturated.
    6. Re:KDE *and* Gnome co-operate? by Anonymous Coward · · Score: 0

      does have no usable applications count as a GUI problem?

  4. Oh dear god. by Kenja · · Score: 0, Flamebait

    Cats and dogs... Living together. Panic in the streets.

    --

    "Have you ever thought about just turning off the TV, sitting down with your kids, and hitting them?"
    1. Re:Oh dear god. by Tumbleweed · · Score: 1

      Ahem.

      "Cats and dogs, living together...MASS HYSTERIA!"

    2. Re:Oh dear god. by Twirlip+of+the+Mists · · Score: 1

      Ahem.

      Venkman: This city is about to face a disaster of biblical proportions.
      Mayor: What do you mean, "biblical?"
      Ray: We mean real wrath-of-God type stuff. Plagues, darkness--
      Winston: The dead rising from the grave!
      Egon: Forty years of darkness! Earthquakes, volcanoes--
      Venkman: Riots in the streets, dogs and cats living together, mass hysteria!

      --

      I write in my journal
  5. Check that URL? by esnible · · Score: 0, Redundant

    http://www.freedesktop.org/ works.

  6. We're losing sight of the important issue. by OpCode42 · · Score: 5, Funny

    We're losing sight of what the most important issue is here. Should a unified desktop be called GNODE or KNOME?

    1. Re:We're losing sight of the important issue. by Dr.+Smeegee · · Score: 5, Funny

      How about KMODE?

      What is it about that acronym that sounds familiar?

    2. Re:We're losing sight of the important issue. by La+Temperanza · · Score: 4, Funny

      G-NODE - the quasi-mythical IP that brinks geeks to orgasm when pinged.

      --

      --
      est modus in rebus
    3. Re:We're losing sight of the important issue. by Anonymous Coward · · Score: 0

      "Should a unified desktop be called GNODE or KNOME?"

      It should be called KDE. All traces of gnome should be purged from the internet at the earliest opportunity. Anyone who dares mingle the pure, sweet code of KDE with the demented, idologically tainted effluent code that is gnome shall face the wrath of the net.gods!

    4. Re:We're losing sight of the important issue. by perdelucena · · Score: 0

      I used to send fax through fax/modem using kmode, whatever that means.

    5. Re:We're losing sight of the important issue. by asv108 · · Score: 1, Insightful
      If RMS had any say in the matter it would be:

      KDE/GNOME

      So then all the people in favor of calling Linux GNU/LINUX can say they are running the KDE/GNOME window enviroment on the GNU/Linux operating system. Lets all try to make the name structure as akward and complicated as possible to deter normal people from trying OSS let alone pronouncing it.

    6. Re:We're losing sight of the important issue. by Anonymous Coward · · Score: 0

      ughh.. that's disgusting, i don't want to hear about geeks having orgasms.

    7. Re:We're losing sight of the important issue. by orcrist · · Score: 1

      SGKMODS - State Gnome/KDE Municipal Open Desktop System.

      (with apologies to John Belushi and Dan Akroyd)

      -chris

      --
      San Francisco values: compassion, tolerance, respect, intelligence
    8. Re:We're losing sight of the important issue. by Anonymous+DWord · · Score: 1

      MEN+KEG=OD

      --
      "If he thinks he can hide and run from the United States and our allies, he's sorely mistaken." Bush on bin Laden
    9. Re:We're losing sight of the important issue. by sssk · · Score: 1

      heh How 'bout COMMODE :)

    10. Re:We're losing sight of the important issue. by Anonymous Coward · · Score: 0

      GNU/Desktop!

      -RMS

  7. Get XFCE involved.... by Anonymous Coward · · Score: 0, Offtopic


    They are a great minimalist "desktop environment" and should get a say in all this.

    -

    1. Re:Get XFCE involved.... by Anonymous Coward · · Score: 0

      That's a window manager, not a desktop.

    2. Re:Get XFCE involved.... by La+Temperanza · · Score: 1

      XFWM is a window manager. XFCE is a desktop.

      --

      --
      est modus in rebus
    3. Re:Get XFCE involved.... by Wdomburg · · Score: 1

      >That's a window manager, not a desktop.

      Funny, the author disagrees with you:

      XFce is a lightweight desktop environment for various UNIX systems.

      The window manager (XFwm) is only a component of the entire package.

      Matt

    4. Re:Get XFCE involved.... by fault0 · · Score: 1

      Well, XFCE is pretty much a straight clone of CDE. Any apps written for XFCE should be similiar working/looking to their CDE replacements.

      GNOME and KDE, however, bring in inspiriation from a variety of sources, and thus need to have their own guidelines.

  8. Well... by DwarfGoanna · · Score: 4, Insightful

    People wondered what impact Apple and their interface would have on the other 'nixes. I am pretty stoked to see what comes of this. We could be looking at the golden age of desktop 'nix right around the corner. If KDE/Gnome can just come up with something unique and useful , and chuck the Win98-ish crap....

    --

    "You know why you do not see me styling wit my homies? Because I have no homies!!" -Mojo Jojo

    1. Re:Well... by Anonymous Coward · · Score: 0
      Well you'll get the usual answer, there is GNUstep, and what I'd like to understand is why it was shunned in favor of another windows clone. I.e., why this:

      RS: GNUStep I think is sort of --

      LE: It's a framework.

      RS: It's a framework, and I guess it, you know, I think it interoperates with Gnome now, and there's lots of people on that, so...

      NM: I've been using WindowMaker for a long time now. That's, that's the window manager for GNUStep. And I know that there's a page called GnomeMaker, which is how to get Gnome and WindowMaker together, so... It proves that they are working together.

      RS: So, uh, I don't if WindowMaker is build using GNUStep. I think it just works with GNUStep.

      [General assenting noises]

      But I think that uh, I think that uh, GNUStep works on their stuff to make it work with Guile and interoperate with Gnome. I think. I'm not sure how far they've gotten. Uh, I don't give, uh, I don't give GNUStep as our focus. It's something some people work on because they like NextStep and they want something like that on top of... I'd be happy to have them working on it, but, uh, that's not the GNU project's desktop focus.

      Gnome is the project's desktop focus.

      RM: There's a current editorial by Jim Dennis urging the Gnome and GNUStep people to join forces in some fashion. I haven't read it yet. [Then maybe you should pipe down, Rick!]

      RS: Wholly I agree. I've been talking to the GNUStep people all the time, saying it's important to work well with Gnome. And I, I don't remember exactly what they said, but my vague memory is that they said, "Yeah." So I don't think that there's any need to, to cajole people. I think that they are working in that direction already.

      Can the new HIG even accomodate GNUstep, or is it just doomed to converge to a windows HIG?
    2. Re:Well... by ajs · · Score: 4, Informative
      If KDE/Gnome can just come up with something unique and useful , and chuck the Win98-ish crap

      This is exactly the opposite direction from what is being done, and for good reason. Right now, the focus is not on re-inventing everything, but figuring out where the common elements of GNOME and KDE's HIG's can be merged, and also where they are unique. Then an effort to merge those last chunks can procede by actually changing the two where appropriate.

      Also, you may not realize just what an HIG is. It actually has very little to do with what you *see* so much as how you see it. Check out the GNOME HIG for more details. This specifies things like what buttons you should put on an alert dialog; when you should use modal vs non-modal windows; default keyboard shortcuts and menu names; etc.

      If all you want is a more BeOS, MacOS, etc. looking desktop, or even a totally unique look, you can do that within the constraints of the HIG of either GNOME or KDE.

      From the announcement:

      Having a shared document will also allow us to start looking at commonalities between the documents and perhaps create common chapters or sections on basic guidelines and lessons that are desktop and toolkit-independent (e.g., accessibility and internationalization tips, general usability principles).
    3. Re:Well... by Anonymous Coward · · Score: 0

      >
      > If KDE/Gnome can just come up with something
      > unique and useful...
      >

      Yes, we're still waiting. How long have they been
      working on this stuff?

    4. Re:Well... by dfj225 · · Score: 1

      Why would they want to chuch the Win98-ish crap or try for something totally unique when what they have now works just fine? I think that if you look at the current situation of the GUI as a whole, most GUIs will have many similarities. Things turned out like this for a reason. If people find a Win-98ish GUI to be the easiest or most efficient, then why try for something else?

      --
      SIGFAULT
    5. Re:Well... by vague · · Score: 1

      One of the most basic and important lessons in HCI is this:

      Don't try to be unique for the sake of it. Don't be unique for small improvements. Familiarity is so powerful that small (percieved) improvements are dwarfed by it. Uniqueness is not a virtue, the drive for it is your bane.

      --

      -
      Listen. Strange women lying in ponds distributing swords is no basis for a system of government.

  9. They are missing the ~experts~ on UI design by SirCrashALot · · Score: 3, Funny

    Microsoft!! Look at the beauty of XP. MS Linux:)

  10. uniformity is good by Anonymous Coward · · Score: 2, Insightful

    One of the thing that is really bothersome about Linux Applications is that they all operate differently. Dialog boxes are arranged strangely, different Window Managers put different buttons for managing different windows in different places. There are way too many save and open dialog boxes, with more appearing each time a Developer writes a new Linux Application.

    The situation is quite a bit better if you settle on KDE or GNOME. Each one has user interface guidelines. The problem is still pretty acute, though, since neither one ships only (or even mainly) with programs that conform to their respective user interface guidlines! And of course most third party applications conform to the guidelines in the same way that Krap and Garbage conform to the formal dress guidelines for a wedding.

    It is very encouraging that KDE and GNOME are working to standaradize their guidelines throughout Linux. It would be a lot better for the two if Applications from one didn't look like they fit into the other, but at least familiar buttons, dialogs and shortcut keys would operate in the same manner. This is almost as encouraging as it was discouraging when Apple decided to throw away their excellent interface guidelines and develop new and bad ones for OS X.

    1. Re:uniformity is good by noshellswill · · Score: 0

      Window manager ? What's a window manager ?? Besides 6-finger web-toe dweezles, does anybody care ??? I'm not marrying the fscking thing, so whether or no it has got a beautiful "liver" does NOT interest me.

  11. NOOOOO!!! by Anonymous Coward · · Score: 5, Funny

    What's next, vi & emacs developers frolicing in the fields after a nice picnic? Then what? What fuel have we then for the flame wars?!?

    1. Re:NOOOOO!!! by bob670 · · Score: 2, Funny

      We can always crack on Red Hat for trying to make money=)

    2. Re:NOOOOO!!! by Guppy06 · · Score: 4, Funny

      "What fuel have we then for the flame wars?!?"

      BSD is dying.

    3. Re:NOOOOO!!! by Anonymous Coward · · Score: 1, Funny

      We can always fall back on 1 versus 0. There'll always be fools who prefer 1.

    4. Re:NOOOOO!!! by jdgreen7 · · Score: 0, Offtopic

      Here's what's next!!!

      Venkman: This city is headed for a disaster of biblical proportions.
      Mayor: What do you mean, biblical?
      Ray: What he means is Old Testament, Mr. Mayor... real Wrath-of-God-type stuff. Fire and brimstone coming down from the skies.
      Venkman: Rivers and seas boiling!
      Egon: 40 years of darkness, earthquakes, volcanos.
      Winston:The dead rising from the grave!
      Venkman: Human sacrifice, dogs and cats, living together... mass hysteria!

      Courtesy of http://www.moviesounds.com/gbusters.html :-)

    5. Re:NOOOOO!!! by frodo+from+middle+ea · · Score: 1

      Vi and emacs ???
      Its like comparing apples and oranges..
      Vi is an editor period. emacs I still haven't figured out what it is ...
      :wq

      --
      for the last time people, I am "frodo from middle eaRTH", not "middle eaST".
    6. Re:NOOOOO!!! by talesout · · Score: 1

      What would your precious '0' be without '1'? I'll tell you, it'd be nothing. That's right, nothing. Come to think of it, it's still nothing. And belief in nothing makes one weak. So comeon. Don't be a moron. We all know one is superior to zero. How can nothing be superior to something? It's just not possible.

      --


      Bite my yammer.
    7. Re:NOOOOO!!! by sryx · · Score: 1

      Actually I think Vi and EMacs developers should be bound and gagged so they can't interfere with any discussion on Human Interface Design! :P
      -Jason

    8. Re:NOOOOO!!! by sean23007 · · Score: 4, Funny

      BSD is dead.

      Is this supposed to be a flame war, or what?

      --

      Lack of eloquence does not denote lack of intelligence, though they often coincide.
    9. Re:NOOOOO!!! by ajs · · Score: 1
      I disagree, though you may have been attempting humor.

      vi and Emacs are products of the era in which they were built, and both were considered excellent UIs for the day. Given today's advances in UI design, I find it interesting that those two are still the best ways to edit text. There *should* be better, but there simply isn't. There are some basic reasons for this that are interesting and fly in the face of a lot of UI design:

      [note: I'm talking about Emacs as a text-editor, which is a fair slice of its functionality to discuss, though certainly not all of it]

      Both editors were designed in an era when the mouse wasn't an option. This means that even given recent modifications to add mouse support in vim and Lucid Emacs (GNU Emacs had primative mouse support first, but Lucid modernized it, and much of their work was merged back into GNU Emacs, though not all, hence Lucid's transition to the even-today-maintained XEmacs) in the last 10 or so years, they still remain useful when your fingers never leave the keyboard.

      The other thing that both of these do that puts them head-and-shoulders above many related tools is interaction with external programs. In vi or Emacs, I can send a portion of a document through any external program I want and read back the result into the original document. Here's an example in vi:
      !Gsort -n +2
      This sorts the lines from the current position to the bottom of the file based on the numeric value of the third column. To add this feature into the editor would be fine (Emacs can do this actually), but if an external tool already knows how to do it, why not take advantage of that fact?
    10. Re:NOOOOO!!! by ActiveSX · · Score: 2, Funny

      emacs I still haven't figured out what it is ...

      It's an operating system with a mediocre text editor and insane interface. It makes Windows XP look like BeOS.

    11. Re:NOOOOO!!! by Anonymous Coward · · Score: 0

      Hey, its -5vdc V's +5vdc I'll have you know!

    12. Re:NOOOOO!!! by Wolfier · · Score: 1

      Gates and Stallman working together towards a license for all software...

    13. Re:NOOOOO!!! by noshellswill · · Score: 0

      Didn't you forget "... and trucked down to the LaBrea Tarpits, where an angry mob of Lusrs gleefully ..."

    14. Re:NOOOOO!!! by Anonymous Coward · · Score: 0

      What's next? Bill Gates publicly apologises to Linus Torvalds and GPLs Windows and Office.

    15. Re:NOOOOO!!! by fredrik70 · · Score: 1

      an OS? bah! It's a way of life!!!

      --
      if (!signature) { throw std::runtime_error("No sig!"); }
    16. Re:NOOOOO!!! by bushboy · · Score: 1

      No, your sense of reality is dying.

      Time to wake up.

      --
      A slashdotting - you get the stick first and then the carrot !
  12. Obviously right == controversial? by Mendax+Veritas · · Score: 1, Flamebait

    If Red Hat's decision had been "obviously right", it wouldn't have been "controversial".

    1. Re:Obviously right == controversial? by yomahz · · Score: 2, Insightful

      If Red Hat's decision had been "obviously right", it wouldn't have been "controversial".

      You can never please everyone :)

      Wow, I'm being shot at from both sides. That means I *must* be right. :-)
      -- Larry Wall

      --
      "A mind is a terrible thing to taste."
    2. Re:Obviously right == controversial? by Anonymous Coward · · Score: 0

      He said that it was obviously right for regular users. You may disagree with that (or not) but it's perfectly possible for something to be obvioously right for regular users and still controversial amongst irregular users.

    3. Re:Obviously right == controversial? by andrewski · · Score: 1

      How do you figure? Or does using "quotes" make your "arguement" "valid"?

    4. Re:Obviously right == controversial? by gwernol · · Score: 4, Insightful

      If Red Hat's decision had been "obviously right", it wouldn't have been "controversial".

      Timing is everything. Lots of ideas that we come to believe are "obviously right" are indeed highly "controversial" when they are first put forward. Obvious examples include almost everything Einstein wrote, Darwin's theory of evolution, Copernicus' theories of astronomy, Newton's laws of gravity. Indeed most major scientific advances were controversial when introduced.

      So I disagree. Red Hat's decision can be both obviously right (especially in hindsight) and controversial.

      --
      Sailing over the event horizon
    5. Re:Obviously right == controversial? by arglesnaf · · Score: 1

      Well, if you look at the link at the bottom of the site, this cooperative desktop project is being hosted by Redhat.

    6. Re:Obviously right == controversial? by EnVisiCrypt · · Score: 1

      Yes, because blue curve is *so* similar to declaring that the sun is the center of the solar system. ;)

      --


      *everything* is Orwellian to cats.
    7. Re:Obviously right == controversial? by Ozan · · Score: 1

      Lots of ideas that we come to believe are "obviously right" are indeed highly "controversial" when they are first put forward.

      No. "obviously right" means nothing else than "everybody agrees that this doesn't need a proof at all".

    8. Re:Obviously right == controversial? by Citizen+of+Earth · · Score: 2, Insightful

      Timing is everything. Lots of ideas that we come to believe are "obviously right" are indeed highly "controversial" when they are first put forward. Obvious examples include almost everything Einstein wrote, Darwin's theory of evolution, Copernicus' theories of astronomy, Newton's laws of gravity. Indeed most major scientific advances were controversial when introduced.

      "I have never seen a statue of a committee."

    9. Re:Obviously right == controversial? by cybermace5 · · Score: 4, Insightful

      No, the actions of a small company regarding a minor change of a secondary component of an opensource non-mainstream operating system

      *breaths in*

      is nothing at all like a major scientific discovery, or theory. The look of the Linux desktop is not something we all have to agree on, nor can it be proved to be a truth of some sort.

      In fact, the look of the Linux desktop holds no disadvantages for opposing camps. There are no consequences for those who do not realize "the truth," and therefore room to continue the argument into infinity. Much like those toilet-paper roll arguments and thermometer spats that can cause rifts in familes for fifty years. Since the issue is non-scientific and illogical, neither party has to come over to the other side, and pride ensures that they never will.

      By the way, the paper goes over the top so it's easy to reach.

      --
      ...
    10. Re:Obviously right == controversial? by carlos_benj · · Score: 1

      Well, when you deal with irregularity everything makes you cranky.....

      --

      --

      As a matter of fact, I am a lawyer. But I play an actor on TV.

    11. Re:Obviously right == controversial? by carlos_benj · · Score: 1

      Hmmm. Examining both your post and the parent I'd say that quotes neither make the argument valid nor the spelling correct.

      --

      --

      As a matter of fact, I am a lawyer. But I play an actor on TV.

    12. Re:Obviously right == controversial? by Anonymous Coward · · Score: 0

      True. I think word he was looking for should have been "apparently" or "probably" or something... there's nothing obvious at this point about choice being right or wrong.

    13. Re:Obviously right == controversial? by Doomdark · · Score: 1
      True, but I dont think enough time has passed since their decision, nor is their significant consensus about it being "the right thing", to really call it "obviously right".

      One could argue that it "seems to have been right thing to do" or "apparently it was right thing to do", but it's hardly fair to say "it was obviously right".

      --
      I like paying taxes. With them I buy civilization -- Oliver Wendell Holmes
    14. Re:Obviously right == controversial? by Derek+S · · Score: 1

      Only if you "don't bathe regularly", or "scare little children".

    15. Re:Obviously right == controversial? by agrippa_cash · · Score: 1

      I am reminded of Schopenhauer's observation: "All truth goes through three stages. First it is ridiculed. Then it is violently opposed. Finally, it is accepted as self-evident."

    16. Re:Obviously right == controversial? by ActiveSX · · Score: 1

      By the way, the paper goes over the top so it's easy to reach.

      (+1, "Obviously Right")

    17. Re:Obviously right == controversial? by Mendax+Veritas · · Score: 1

      No, using quotes indicates that I was quoting directly from the story, you idiot.

    18. Re:Obviously right == controversial? by orcrist · · Score: 1

      Gee, that reminds me of Carl Sagan's observation: "They laughed at Columbus, they laughed at Fulton, they laughed at the Wright brothers. But they also laughed at Bozo the Clown." ;-)

      -chris

      --
      San Francisco values: compassion, tolerance, respect, intelligence
  13. Whatever happened to "best fit" by amigaluvr · · Score: 3, Interesting

    Best Fit is when something is made so that it is as good as it can be, not when it is weighed down by things that are unnecessary

    The idea of human interface guidelines is restrictive from the start. Nobody know's better than the coder who codes and application how it should work. Having guidelines written beforehand that should say how it works doesn't make complete sense.

    Look at apple and their rejection of tabbed browsing. Thats something that has adapted from systems that work well, yet they're saying "no not on our turf".

    Then turn around and the apple web site is all tabbed anyway. Websites have better interfaces as they are made to fit each purpose.

    Each application needs freedom. Having them all with exactly the same system is like a monoculture.

    1. Re:Whatever happened to "best fit" by Gortbusters.org · · Score: 1

      This is true, it almost breeds monoculture... a mono-techno-culture. On the other hand, usability concerns are real. If you're a technician assigned to debug/setup/repair some piece of equipment, you have billable hours. If you spend too much time going through a clumsy interface the client is loosing money.

      Seconds saved for one task, for hundreds of technicians, for thousands of hours worked equates to big money.

      --
      --------
      Free your mind.
    2. Re:Whatever happened to "best fit" by Anonymous Coward · · Score: 0

      NINNLE Linux solves this problem.

    3. Re:Whatever happened to "best fit" by Dan+Ost · · Score: 5, Insightful

      I don't agree.

      In my experience, the coder is the last person
      who should be designing the user interface for just
      about anything beyond command line tools.

      Let the coder design the interface between the
      code and the UI, but let someone with more
      relevent training and experience design the UI.

      --

      *sigh* back to work...
    4. Re:Whatever happened to "best fit" by Anonymous Coward · · Score: 0

      Absolutely. Without some level of consistency across apps, there is a substantial amount of people-time wasted on the slowdown needed to cross from one mode of thought to another. It's noticeable when switching from Windows to MacOS to KDE, without having to then deal with every app working slightly differently according to the unique group of coders who created it.

      The slowdown may only be something small like 5%, but taken that across every user in ever organisation and it adds up. Combine it with tech support issues and you're multiplying again and again. Those were the bad old days.

      Fortunately, all apps packaged for NINNLE linux are re-interfaced, using ninnle's own wrappers. There's no more consistent UI in a linux distro

    5. Re:Whatever happened to "best fit" by sporty · · Score: 4, Interesting
      Best Fit is when something is made so that it is as good as it can be, not when it is weighed down by things that are unnecessary

      There's a problem with best-fit. Sometimes, you wind up with two interfaces on two different systems, that use similar widgets, but do totally BAD things. For instance, a simple good thing.

      I hit google.com, the cursor is defaulted to the search box. It speeds up my day by a fraction, but I like the convienence of not having to tab a bunch of times. Well, i never counted, because I noticed the behavior.

      Now for a bad one. My school uses something called WEBSIMS. You login, you can see your bill, and register for courses. It's a type of middleware. The one thing it does that pisses me off, only because it is the odd-man-out, is when I finished typing in my fixed-length id number, it auto tabs to the password field. I usually fill out forms, hitting tab to go to the next field. It makes for quick input for me, since I'm a touch typist. Now when websims login page does that to me, i wind up hitting tab, and going not to the next field, but to a button. Great, now i have to shift-tab or use the mouse. It's annoying since it's unexpected behavior.

      Guidelines are good. They get people to do things consistently, so menu's, buttons and widgets are used in some similar fashion. Some guidelines don't work out. Apple's no-tabbed-browser is just one thing they stick by. Nothing wrong with that. They just don't use MDI very often, if at all. That's their rule, you don't have to follow it, but for the sake of consistency, it's advised not to.

      Having your systems all behave in similar fashions isn't a monoculture unless they all do the save behavior in the same fashion down to a tee. Guess what I'm saying, it's not so black and white. Restrict some things but give enough freedom to do things right.
      --

      -
      ping -f 255.255.255.255 # if only

    6. Re:Whatever happened to "best fit" by teks0r · · Score: 2
      Nobody know's better than the coder who codes and application how it should work.

      I would have to disagree. Much software (and especially free software, seem to have interfaces that leave something to be desired. The coder knows the program, and appreciates the project from a very functional point of view, but they tend to lose sight of the usability of the interface.

      I'm not saying that coders aren't good at designing human interfaces, but from my experience it's often more beneficial for someone else altogether to design the HI, from the perspective of an "outsider."

    7. Re:Whatever happened to "best fit" by patter · · Score: 2, Interesting

      Nobody know's better than the coder who codes and application how it should work.

      Yeah right, so we should just let everyone make their own decisions on what order menus go in? Or perhaps you'd like to go back to early GUIs (kinda) like Windows 3.1 in which every applications file dialog was different.

      Sorry, most programmers don't have a hot damn clue when it comes to users. We're too far removed from the average luser's problems.

      All it took for me to have to 'help' lots of users in some environments was for some application to have something 'relocated' because the programmer knew best.

      Users don't want clever, they want consistent, move one item in a menu because you 'know better' and you render your application unusable to the vast majority of users.

      Guidelines should be negotiable, but Apple who's really always had a leg up on the competition has consistency from what little experience I have with them above all else. At least in the basic things like where things are in the interface.

      Once the platform has established an idiom, if we're too dumb to figure it out as programmers or think we know better, we need to be slapped down.

      Yes, I'd agree about _some_ websites. However, I've seen enough that cause me trouble to say that that freedom is a bad thing. ;).

      --
      -- If at first you do succeed, try to hide your astonishment. -- Harry F. Banks
    8. Re:Whatever happened to "best fit" by MobyDisk · · Score: 4, Interesting

      I highly recommend that you:
      1) Spend some time training end users how to use basic tasks such as GUI stuff (copying files, moving windows) then try office apps (word processors, spreadsheets) and you will be amazed. Alternatively, take a good course on user interface design, or Medical Informatics. The average user cannot recognize something as a check box, unless it the same as the ones they know. Even bits of shading and color can make them unable to recognize the screen as anything other than colors. It just "looks to complicated" and they turn off their brains.

      Apple realized this long ago. MS hasn't (hence, Windows XP was born). There are a great many articles available at the ACM Digital Library regarding user interface design and experiments. There are certain user interface rules are that pretty much accepted as fact, since they have so much research behind them. Apple is very consistent at following them, which is why people think Apples aer easy to use, even though most techies look at them as really being the same. It's the subtleties that we don't see. A quick list from my memory:

      - Dynamic menus are always slower than static menus
      (You know the rearranging menus in Office 2000/Windows 2000?)
      - Vertical scrolling is easier than horizontal scrolling
      - Multimodal interfaces are faster if they are properly paired
      (Ex: Keyboard=okay, Mouse+Keyboard = excellent, Joystick+Keyboard=bad)
      - Consistency is more important than feature set

    9. Re:Whatever happened to "best fit" by use_compress · · Score: 1

      I agree with you... The interface for Winamp written by the Nullsoft coders is nonstandard yet quick and intuitive. However, the interfaces of 99% of the skins written by outsiders have inscrutable interfaces. This phenomenon is observable in just about every other skinnable application. Thus, while the coders generally know how to make a good interface, the users are mostly clueless.

    10. Re:Whatever happened to "best fit" by m0nkyman · · Score: 2, Insightful

      From a development point of view you may be correct. From a user's viewpoint you are dead wrong. It doesn't matter if your project has a wonderful UI, if it is different from the way everything else works, the user ends up wasting time learning how to do things your way.
      Consistency in the UI makes ALL programs easier to use. rather than the current smorgasbord of the linux desktop, where inevitably, you spend the first hour of using a new program figuring out how the damn thing works.

      In contrast, on the mac, I KNOW that certain items are always going to be in the same place. muscle memory tells me how to save a file etc. Linux's command line functions have a similar consistency. How many times have you typed 'somecommand --help' without reading a man page to discover that it would work. How would you like a program that used '--options' instead. I'd be irritated.These little things add up over the course of a work day.

      'Best Fit' has to be applied to the user experience as a whole, not just any one single application.

      cheers!

      --
      ~ a low user id is no indication I have a clue what I'm talking about.
    11. Re:Whatever happened to "best fit" by WinterSolstice · · Score: 1
      No kidding. Look at Open Office on Mac compared to Office X on Mac. Microsoft completely integrated into the style guidelines, and the Open Office stuff looks like some ancient OS/2 or Windows 3.1 app.

      I am a developer, but I think that UI design should be handled by artists. When coders do all of it, you get things like twm and Win 3.1, not things like Enlightenment, Aqua, and Win XP.

      Of course, some people like that kind of thing, I guess.

      -WS

      --
      An operating system should be like a light switch... simple, effective, easy to use, and designed for everyone.
    12. Re:Whatever happened to "best fit" by carlos_benj · · Score: 1

      Yes, I'd agree about _some_ websites. However, I've seen enough that cause me trouble to say that that freedom is a bad thing. ;).

      I don't know about that. That freedom allows some folks to cobble something together in such a way that when you first bring up one of their pages you can say, "Whoa! What's this bozo trying to do here?!" and not waste any time on their site.

      --

      --

      As a matter of fact, I am a lawyer. But I play an actor on TV.

    13. Re:Whatever happened to "best fit" by ajs · · Score: 2, Informative

      I have to disagree. First, a good HIG does not constrain you to do the wrong thing for your application, but rather gives you a sense of how best to fit into a particular paradigm. From there, you can do what you need to. A classic example of where this is important is the current trend in "media players" like Quicktime from Apple, WinAmp, XMMS, Microsoft Media Player, etc. They all try to look as snazzy as possible, at the cost of good user interface design. I can't count the number of times I've been at a party where some geek with good intentions put up an XMMS or WinAmp-based juke-box for people to play music with and all of the non-techies would give up after a few minutes because they couldn't decipher the UI.

      If those applications had followed the UI guidelines for the platforms they run on, they could still have had all of the features, all of the great flexibility, but they didn't need to have pseudo-round volume sliders, non-standard title-bars that do application-local window management, context-sensitive menus that don't have commonly-performed operations, out-of-the-box unique font selection, out-of-the-box unique color selection, etc, etc.

      That kind of awful behavior is what makes a desktop unusable (and certainly if more apps go the "branded UI" route, dekstops will become totally unusable).

    14. Re:Whatever happened to "best fit" by Anonymous Coward · · Score: 0

      That's grant, coming from someone calling himself "Amigaluvr". The golden age of Amiga user interfaces came when we finally got some standardized gadgets ('widgets', if you speak X). The ASL library, especially the standardized file requester, was a gift from heaven.

      Yes, by all means let us have restrictions on applications! Please! We honestly do not *need* different file requesters for every single application. We do not need 500 types of buttons, all looking different, all doing the same job.

      Down with ugly, difficult to use, non-standard GUI's!

      The Amiga styleguide said this: "First make it work. Then make it beautiful." It was right - these things are not mutually exclusive.

    15. Re:Whatever happened to "best fit" by noshellswill · · Score: 0

      Coders? Know ??? Ha..hahahaha. Coders are 6-finger drooling mutants who can't get a Twinkee stuffed in sidewaz in place of their thumbs. Code yes -- suck out that random braintwitch -- then toss the bas*ards into liquid nitrogen. That'll stop that irritating scripty swill. Finish the job - frozen solid, freeze-dried and left in the Gobi Desert on fishpaper.

    16. Re:Whatever happened to "best fit" by Anonymous Coward · · Score: 0
      The average user cannot recognize something as a check box...

      This is a misnomer. No one with minimal experience using a desktop, a real user in the sense of having used a computer, would be confused by a checkbox. Someone with no experience certainly would, but so what? The ultimate goal of the desktop can't be dumbing down to the lowest common denominator. We don't demand the same of bicycles, cars or power tools, why computers?

    17. Re:Whatever happened to "best fit" by Grab · · Score: 1

      Excuse me, have you seen any media player? They all produce some fancy user interface, they're all non-standard, and they all suck. Generally they try to emulate something physical like a CD player or a PDA, and this makes them crap bcos user interfaces do not transfer across media very well. The most intuitive media player I've ever seen is the Windows CD player.

      Claiming "websites have better interfaces" makes me think you've not seen many websites. The really intuitive websites tend to have the same interface - drop-down menus, pushbuttons, etc, in fact the same interface that you'd get from your desktop! Others scatter random links around, things don't do what they say, and things you don't expect to be links actually are and are important.

      The purpose of user interface guidelines are that by now, everyone has used Windows or similar interfaces, and everyone knows how these work. If you change this so that your interface works in unexpected ways, everyone's hard-learned skills with a user interface go out the window and they have to relearn. This is BAD. If your users have to spend the first week trying to get familiar, you're not going to get any users doing this out of choice if they can use another program which *is* familiar. It doesn't matter if it has a zillion features, it'll die. Word stomped WordPerfect, a more powerful program, bcos Word was easy to use and the WordPerfect team never got their interface sorted.

      Coders will, and do, add user interface stuff which is horrific to use, just bcos it "seemed a good idea at the time" or "looks cool". Useability is a massive field with vast quantities of research, and coders don't have the time to become expert in it. The idea of guidelines is to pass across the ground rules so that coders don't produce total crap, which *very* often happens. If you think coders will always produce a good interface, you really haven't downloaded many programs!

      Grab.

  14. Who's with me... by DenOfEarth · · Score: 5, Funny
    This is just great...I can't believe they want to combine the human interface guidelines into one document for everyone. What's happening to the open source community, people? Let's start a new project aimed at making things back the way they are supposed to be, with a different interface for every window, just like the command line has different forms for every command.

    it's a bummer that sarcasm is so hard to write via text

    1. Re:Who's with me... by Hell+O'World · · Score: 1

      Oh I know what you mean. It's SO hard.

      To be honest, getting this comment posting program to display the tags was actually kind of a pain.

    2. Re:Who's with me... by TV-SET · · Score: 1

      While command line is certainly different for most of the programs, you still can expect to find --version and --help options working. And that will get you started pretty fast. :)

      --
      Leonid Mamtchenkov ...i don't need your civil war...
    3. Re:Who's with me... by Flamerule · · Score: 1

      [pedant]Many of us use square equivalence class brackets instead of angled vector brackets.[/]

    4. Re:Who's with me... by Anonymous Coward · · Score: 0

      No, just hard to write well.

    5. Re:Who's with me... by Anonymous Coward · · Score: 0

      it's a bummer that sarcasm is so hard to write via text

      Indeed, without this comment I wouldn't have guessed that you were being sarcastic.

  15. mistaken by Boromir+son+of+Faram · · Score: 4, Informative

    Actually, they are just hosting both of the sets of guidelines on the same site, not agreeing on one set of guidelines for both toolkits. In the end, this is a good thing, because the two widget sets are radically different on a few key points, making agreement on human interface guidelines fundamentally improbable.

    It is a sign; the free desktop guidelines were sent to us to aid in our defense.

    --

    Boromir, son of Faramir, King of Gondor and Minas Tirith
    1. Re:mistaken by Anonymous Coward · · Score: 0

      Not just in the same site but also in the same XML document. The reason for this is they want the authors too look at the similarties and merge them. They also want to look at the differences and see if they can eliminate them. In the end 100% agreement will not happen but it will lead to a better experience for those who use both KDE and GNOME software on the same desktop.

    2. Re:mistaken by ajs · · Score: 4, Informative

      Incorrect. They are combining the two documents into one, with sections that conflict annotated in XML such that either document can be viewed as a stand-alone. Then they are going to work on the differences.

      Read the announcement on the mailing list archives.

  16. may i suggest a starting point.... by Anonymous Coward · · Score: 2, Informative

    start here

    finally ego's are starting to subside and we are working together. i have dreamt about this for years, a common human interface guide, that will work consistently. i do not need 100 differnt ways to do something.. nor do i need 100 different widget sets. i just want something that works the same way every time

    1. Re:may i suggest a starting point.... by ajs · · Score: 1

      But you will certainly get 100 different ways to do something and 100 different widget sets.

      You may also get common user interface standards, but that has little or nor bearing on the above.

      Also, pointing to Apple as an example good HIG is probably not the moral high-ground it once was, given recent software from that company (e.g. the latest Quicktime) pointedly ignores such things....

    2. Re:may i suggest a starting point.... by bninja_penguin · · Score: 2, Insightful

      finally ego's are starting to subside and we are working together. i have dreamt about this for years, a common human interface guide, that will work consistently. i do not need 100 differnt ways to do something.. nor do i need 100 different widget sets. i just want something that works the same way every time
      I agree, you don't need 100 different ways to do anything, you only need MY WAY!!!!

      --
      For those who describe their systems as 'boxen', do you order multiple 'boxen' of corn flakes also?
    3. Re:may i suggest a starting point.... by Anonymous Coward · · Score: 0

      Brush metal now has it's own guidelines.

      Brush metal on mac behaves the same as aqua except it has a different texture and you can click on any empty area of the window and drag. Thats all.

  17. What? by Anonymous Coward · · Score: 1, Insightful

    You're joking, right?

  18. TROLL ALERT by Anonymous Coward · · Score: 0

    Red Hat's unified desktop was controversial, but obviously the right decision for regular users.

    It was neither the obviously correct decision, nor the correct decision. Give me a vanilla KDE desktop any day over the monstrosity that is Blue Curve.

    1. Re:TROLL ALERT by Anonymous Coward · · Score: 0

      So your opinion makes for the correct decision? Idiot.

    2. Re:TROLL ALERT by Anonymous Coward · · Score: 0

      It takes away from the fun if you identify your posts as trolls right in the subject line. Next time be a little more subtle, you'll get more bites that way. Hope this helps.

  19. Maybe they'll both read... by alispguru · · Score: 1, Redundant
    --

    To a Lisp hacker, XML is S-expressions in drag.
    1. Re:Maybe they'll both read... by Anonymous Coward · · Score: 1, Insightful

      that's a good point. Apple's Human Interface team has spent more than a decade of *serious* effort aimed at interface design.

      Why re-invent the wheel? Why not just adopt Apple's guidelines as-is? Or is the point of this exercise to just try to cobble together in a year or two a set of guidelines that aren't half as good as what has already been developed?

      For some reason i'm having flashbacks to a time when we had 20 billion crappy ftp clients for linux instead of one really good client that folks cooperated on... oh wait, that's today...

      I saw one poster criticize Apple for "not invented here syndrome", but Apple's got nothing on the open source movement. Years of competition in desktop environment's of all things should be a hint as to who really needs to deal with some issues...

    2. Re:Maybe they'll both read... by Anonymous Coward · · Score: 0

      what, and get both their asses sued into oblivion by Apple for 'stealing' their guidelines?

    3. Re:Maybe they'll both read... by prockcore · · Score: 1

      Yeah, and then maybe they can toss it all out the window and make all their new apps Brushed Metal too!

    4. Re:Maybe they'll both read... by generic-man · · Score: 3, Informative

      Not likely. Apple stopped reading those guidelines years ago.

      --
      For more information, click here.
    5. Re:Maybe they'll both read... by ajs · · Score: 1

      Which apple breaks left, right and sideways in the most recent Quicktime players. Guess no one is immune to shinny-over-substance. :-/

    6. Re:Maybe they'll both read... by Pius+II. · · Score: 2, Informative

      Maybe you should just read the Gnome User Interface Guidelines (http://developer.gnome.org/projects/gup/hig/1.0/) , which could easily win an award for the most blatantly obvious copy of someone else's original work (i.e. they are almost identical to the Apple HIG). At least they exchanged the graphics; having Aqua windows in there probably would have been _too_ obvious.
      I'm really glad that those guidelines are actually being implemented, because that makes Gnome really easy to use (as opposed to KDE, which seems to try and imitate MS. I hate those "Yes, No, Cancel" dialogues).

      http://developer.gnome.org/projects/gup/hig/1.0/wi ndows.html#alerts-confirmation

    7. Re:Maybe they'll both read... by Anonymous Coward · · Score: 0
      That's a bad point. Apple don't even follow their own guides (brushed metal, custom widgets).

      While your post sounds ok, for someone who isn't an interface designer, to anyone in the industry it sounds ridiculous.

      Akin to putting Windows CE in a nuclear power station. It's sounds good to people who don't know computers only.

      But then I realised that you're obviously not a user interface designer and neither are half the posts here and that you're talking about something you don't know about to those who don't know either.

      +1 informative!

    8. Re:Maybe they'll both read... by Anonymous Coward · · Score: 0

      Maybe because Apple's current implementation is 99% brain-dead? Just what I want: an OS geared towards a one-button mouse, lots of horizontal lines, and little colored blobs in my titlebars that do something important but give no real visual clue about their purpose, trashcans that turn into disc-eject icons only after I click on the disc. Sorry, but any edge Apple used to have as a result of superior UI design is completely null at this point. They've gone completely for form over function and it shows.

  20. Correct Freedesktop.org link by Anonymous Coward · · Score: 0
    1. Re:Correct Freedesktop.org link by Iguanaphobic · · Score: 1

      Totally. This is a good example of where a consistant implementation would help. Either let us use domain.com and www.domain.com or one or the other. But not one sometimes, but not the other or the other sometimes, but not the one. Aaargh!! Try this one: adobe.com

      --
      Fascism should more properly be called corporatism, since it is the merger of state and corporate power.
    2. Re:Correct Freedesktop.org link by Anonymous Coward · · Score: 0

      I thought the whole www/no www thing was server side (at least I have to set it as an alias in my httpd.conf). Not true?

    3. Re:Correct Freedesktop.org link by Iguanaphobic · · Score: 1

      Yes true. It is up to the webmaster of the domain. But it shouldn't be.

      --
      Fascism should more properly be called corporatism, since it is the merger of state and corporate power.
  21. Reading too much into it? by spells · · Score: 2, Insightful
    When I read the overview I thought they were working together to produce a single guideline, however the article talks about multiple guidelines combined into a single reference document.

    At least it will be possible to quickly identify the differences between the guidelines now, but not as much as I hoped for.

  22. The worst possible people to do the UI... by CountBrass · · Score: 5, Insightful

    are the developers.

    They think and know too much about *how* the system is *implemented* rather than how it will be *used* - which is a very different thing. They tend to be function oriented rather than task oriented.

    On the plus side, having UI design guidelines is a good start and at least it gives something that can serve as a basis for discussion.

    --
    Bad analogies are like waxing a monkey with a rainbow.
    1. Re:The worst possible people to do the UI... by snofla · · Score: 1

      And open source users who think they have a clue about user interfaces. That's why most open source applications have so many options.

      --
      i don't like style guides
    2. Re:The worst possible people to do the UI... by Anonymous Coward · · Score: 0

      Whoever designs the UI is, by definition, one (or more) of the developers.

    3. Re:The worst possible people to do the UI... by Anonymous Coward · · Score: 0
      Mozilla is the worst case of this. There are so many poorly thought out options... in Mozilla it's become the way of conceeding an argument-to put it in as an option.

      Mozilla's biggest task isn't the software bloat - it's the interface bloat. There's been a slow growth in anger against the Mozilla interface bloat, but unfortunately we're not learning from Phoenix :(

    4. Re:The worst possible people to do the UI... by WindBourne · · Score: 1

      A number of ppl doing guidelines are NOT developers or are weak developers. Hence the reason why the guidelines are being pushed.

      --
      I prefer the "u" in honour as it seems to be missing these days.
    5. Re:The worst possible people to do the UI... by Daengbo · · Score: 1

      Eat your own dog food, man...

    6. Re:The worst possible people to do the UI... by Khalid · · Score: 1

      Yes indeed this is very insightful, but the people doing usability studies, at least for KDE are not developers, they ar emainly KDE users.

    7. Re:The worst possible people to do the UI... by Malcontent · · Score: 1

      Unfortunately the non developers are all to content to stand in the sidelines and ridicule the developers.

      Where are the GUI gurus, the artistic types, the aesthetes when it comes time to roll up your sleeves and get to work?

      --

      War is necrophilia.

    8. Re:The worst possible people to do the UI... by Anonymous Coward · · Score: 0

      So those who can't control the direction of those who can? Developers are the heaviest users of interfaces on the planet, simply writing them off is idiotic. Accuse them of being too far ahead of the curve maybe. A cooperative effort would be better solution.

    9. Re:The worst possible people to do the UI... by Anonymous Coward · · Score: 0

      nicely said.

      the usability guys in general just
      like to spend there time argueing
      and never really come up with any
      nice concensus. oh, theres are a few
      exceptions though, yes, you guessed
      it, developers on the usability crew :)

      Alex

    10. Re:The worst possible people to do the UI... by IamTheRealMike · · Score: 1
      Yawn. I know it's fashionable to claim that developers and engineers have no sense of aesthetics, can't do good interface design, have no sense of form factor.

      I'm bored of it. It's clearly garbage. There are lots of things in the world, designed by "engineers" and "developers" that are well designed and thought out, from the perspective of the user. The idea that you need two different people, one to do the UI and one to do the code, is just, well, so so wrong. There are some beautiful cars out there, but the design is very much constrained by what is an efficient, aerodynamic design etc.

      The fact is, that "open source developers who don't get usability" is just a stereotype. It's about as relevant as "all Mac users are elitist snobs". Traditionally open source developers haven't thought much about usability, but with the recent pushes in that area that's completely changing. Often now when I browse mailing list archives, the lists are full of quality discussions on how to make the best interface. The developers themselves are doing this, and sometimes the results are inspired. Stuff like HIGs are very useful for this, because it provides valuable guidance. The same people can do both things, and do them well.

      They think and know too much about *how* the system is *implemented* rather than how it will be *used* - which is a very different thing. They tend to be function oriented rather than task oriented.

      Please explain this. I have no idea what function and task orientation is. I know that some people are good at writing software, and think through how it will be used as well as how it will work. I know others aren't so good at it. I know pidgeon-holing people like that doesn't make sense.

      You see, you can't separate implementation and interface. It just doesn't work. Witness the various ideas that Eugenia has over at OSNews. Some of them are good ideas, that should be implemented. A lot of them are stuff that simply doesn't make sense implementation wise (why exactly should we embed icons into the binary directly again?), or haven't been thought through: appfolders for instance always leave me with sticky questions nobody wants to answer, but she demands them all the same.

      So, people are equally guilty of this, both "interaction designers" who basically invent a user interface based on often a rather vague set of ideas but don't give any thought to whether it's actually implementable, and then the developers who just implement whatever seems technically right and don't bother considering UI issues.

      On the plus side, having UI design guidelines is a good start and at least it gives something that can serve as a basis for discussion.

      Right, absolutely. That's an area that IMHO KDE has been lagging behind, the KDE Style Guides, other than being very hard to find, don't make things as clear as the Gnome HIG does, so discussion on kde-usability seems to be to be often quite free floating, whereas stuff on gnome-usability is more, is this HIG compliant as well as "how well does this work". Things get done quicker that way.

  23. Bad link...thanks... by QwkHyenA · · Score: 1

    Apparently FreeDesktop's web admin doesn't know what a ServerAlias directive is.

    --
    LFS. Have you built your system today?
    1. Re:Bad link...thanks... by ahaning · · Score: 2, Funny

      Directive ServerAlias
      Syntaxe : ServerAlias hôte1 hôte2 ...
      Contexte : hôte virtuel
      Statut : noyau
      Compatibilité : ServerAlias est disponible à partir de la version 1.1 d'Apache

      La directive ServerAlias défini un nom secondaire pour un hôte, utilisable dans le contexte d'hôte virtuels nommés.

      Voir aussi : Hôtes virtuels sur Apache


      I'm not surprised.

      --
      Withdrawal before climax is very ineffective and those who try this are usually called "parents."
    2. Re:Bad link...thanks... by Anonymous Coward · · Score: 0
      The editors excuse the behavior thusly: "Apparently not everyone's browser can read http://freedesktop.org, so the initial link up there now sports a "www" as well."

      Bullshit. If the people who run freedesktop.org aren't smart enough to at least do a redirect page to www.freedesktop.org, then they shouldn't be on the web. And come to think of it, they aren't.

    3. Re:Bad link...thanks... by Anonymous Coward · · Score: 0

      Where's the rule that says your base domain name absolutely must resolve to your webserver?

      Sure it's generally good practice, but if a site is not planning on having their name passed via word of mouth what does it matter if they only way you can get to their site is via the www CNAME?

    4. Re:Bad link...thanks... by Anonymous Coward · · Score: 0

      How do you know that their admin doesn't know about the ServerAlias directive? The reason you can't hit freedesktop.org in a browser is because they do not have their DNS setup to resolve freedesktop.org. Apache has nothing to do with it.

      In the eternal words of Red Foreman.... "jackass!"

  24. None too soon! by teamhasnoi · · Score: 3, Funny
    As a mac (os X) user at work and a XP (GASP!) user at home, this news comes none to soon. This is what will get linux ready for dumbasses like me to use on the desktop.

    I love how everything in OS X seems to be well thought out; XP on the other hand, may have been assembled after the MS Christmas party, you know the one where Ballmer dry humped Bill's leg and everyone laughed, got fired, and re-hired in the same night.

    I hope that linux can get moving with the standardized (yet infinitely customizable) interface. Maybe throw in those spiffy vector icons (eye candy!), some way to never visit the CLI if I don't want to, and a way to make configuration eaiser.

    But I digress. A standard desktop will only encourage linux. Those who want to run the u1tr4 l33t desktops can still do so, and the people who just want an easy alternative to windows will have one. Or buy a mac :)

    1. Re:None too soon! by stor · · Score: 1

      > Maybe throw in those spiffy vector icons (eye candy!)

      Too late:

      http://librsvg.sourceforge.net/images/spheresand cr ystal.png

      Yes it looks a bit hackish at the moment but you can see the potential. Could be _very_ nice.

      There are claims now that librsvg can render svgs as fast as libpng can render pngs.

      Cheers
      Stor

      --
      "Yeah well there's a lot of stuff that should be, but isn't"
  25. Desktops.. by grub · · Score: 4, Funny


    So for many, many months I was using my OpenBSD machine thinking "Man oh man this looks like Windows. It even has a Start menu." Everything worked exactly as a Windows machine except for pokey games and the slight lags I'd notice once in a while.

    My dream was shattered when I realized I was just VNC'd to my Windows machine.

    --
    Trolling is a art,
    1. Re:Desktops.. by Anonymous Coward · · Score: 0

      Must have been a real bitch getting your floppy to work.

  26. Sort of off-topic by Anonymous Coward · · Score: 1, Interesting

    But I hope that application designers will work to ensure that their applications are tiled window manager friendly. Popping up new windows is harmful to the interface, and screws up the display in tiling window managers like ion.

  27. sure hope not.. by Anonymous Coward · · Score: 0

    because not everyone likes gay porn, especially Apple's style

  28. Bitstream Vera the default font? by PRR · · Score: 5, Interesting

    Since the Bitstream people were kind enough to be the first to donate a good TTF for use with Linux, would it be likely that Gnome/KDE would standardize on Bitstream Vera as the default (true type) font for their desktops?

    1. Re:Bitstream Vera the default font? by be-fan · · Score: 2, Insightful

      Yuck. TT fonts suck. There is no point standardizing something that really should be a user option. There is actually a danger in doing that. Wheras before the app designer had no clue what font the user was going to use, and designed accordingly, if you standardize it (like on Windows) then app developers get lazy and people who have much nicer looking fonts (me) get screwed over.

      --
      A deep unwavering belief is a sure sign you're missing something...
    2. Re:Bitstream Vera the default font? by Anonymous Coward · · Score: 0

      Yea, TT Fonts suck ... ... because you can print them and they look the same as on the screen ... ... that just fucking sux. And anybody who uses them is ignorant and fucking stupid.

    3. Re:Bitstream Vera the default font? by be-fan · · Score: 1

      First, we're not talking about printing, we're talking about a screen font. This is a thread about HIGs, remember? When was the last time you printed out your KDevelop window?

      Second, TT fonts suck for screen fonts because the hinting process is so complex, that the resultant fonts are only good at a certain range of DPIs (on my 133-dpi LCD, bytecode hinted TT fonts look really bad) and good fonts can only be made by a small set of typography companies. High quality postscript fonts, on the other hand, are much more widely available, and with new AA-optimized hinters, look much better at a wide range of resolutions.

      --
      A deep unwavering belief is a sure sign you're missing something...
    4. Re:Bitstream Vera the default font? by doorbot.com · · Score: 1

      There is no point standardizing something that really should be a user option.

      Exactly. An OS never needs such frivolities as default settings. The user should have to adjust all their settings in binary, via assembly code built on their own compiler. No one needs standards, like TCP/IP or 8 1/2" x 11" paper. Just think how much better off we'd all be if things like the metric system weren't holding us back (although I think the Stone Cutters are keeping the metric system down). Yes, now the user has ultimate freedom.... choose your own protocol, paper size, and system of measurement. Compatibility be damned!

      </sarcasm>

      You do realize, don't you, that you can always change the default settings! Geeze. By the way, if you don't like it, don't use it.

    5. Re:Bitstream Vera the default font? by be-fan · · Score: 1

      Obviously, you didn't read my post very carefully. Standardization is great when it doesn't affect the user experience. However, having a standard font or UI look can lead to app developers who don't take into account users that have different settings, and hard-code values. This is a major problem in Windows. I have a 1600x1200 15" LCD, and Windows looks just plain weird with a 133-dpi font setting. KDE looks more or less completely normal. It would be great if it was just a matter of a default that could be changed without consequence, but standardizing on fonts is just a bit too dangerous for something so personal.

      --
      A deep unwavering belief is a sure sign you're missing something...
    6. Re:Bitstream Vera the default font? by BEHiker57W · · Score: 1

      It's the Stone Cutters and the Egg Board, up to their usual antics again.

  29. Minor Gripe by gotw · · Score: 1

    This post was confusing for me "obviously the right decision for regular users" I'm not sure if that is meant in the real meaning of the word, people who use regularly or used to mean normal. I think it's the second. It's a little nitpickey, maybe I'm just confusing myself

  30. people actually care? by diablobynight · · Score: 1

    Wow I suprised to see how many posts there were to this article, I mean does anyone really care? So their combining, were they so different that this will cause any form of true annoyance?

    --
    Anonymous Cowards - Oh God, How I hate you
  31. Perhaps this is an Ask Slashdot... by thatguywhoiam · · Score: 4, Interesting
    But this seems as good a place as any...

    I'm a graphic designer who's done a lot of interface design, as well as being an avid follower of human-computer interface trends and issues.

    Does anyone have any suggestions as to how someone like myself would help contribute to an Open Source project? While I am not a programmer by any means, the interface is definitely somewhere that can use some help in all the Linux distros I've seen and used.

    Also, being a Mac person, I don't really know which direction to turn in; i.e. does Gnome need help? Debian? etc. Any suggestions would be greatly appreciated.

    --
    If Jesus wants me it knows where to find me.
    1. Re:Perhaps this is an Ask Slashdot... by LinuxGeek8 · · Score: 2, Interesting

      If you want to give feedback, or help out with design an interface, you could join a mailinglist of Gnome or Kde, I assume both projects have mailinglists for this.
      You could also join the mailinglist of a distro, and see if the installer, or the config utilities need some suggestions. I'm not sure if the debian distro would be a good choice, most of their tools are not graphical, but of course they have an interface.
      Maybe the best thing is to just join a mailinglist of a project with which you can feel attached. If you like Gnome, and have something with it, it will make it interesting for you. As a mac person, Gnome might be that for you, the Gnome2 interface is modelled more after the mac than the Kde interface.

      --
      Well, don't worry about that. We can get you back before you leave. (Dr. Who)
    2. Re:Perhaps this is an Ask Slashdot... by Roberto · · Score: 4, Informative

      Well, you can do it like this. I will give a KDE example, because I am more familiar with it.

      a) Start using KDE
      b) Find an app whose UI you think needs work
      c) Politely contact the app author, offering your help
      d) Don't barge in saying "hey, fool, this is how it's done" ala Eugenia Loli-Queru from osnews.com
      e) Try hacking a better UI through Qt designer (it's pretty easy, and if you are lucky, you won't even need to rebuild the app).
      f) Volunteer to take bugreports regarding UI for that app
      g) Don't propose changes that would involve huge refactoring and throwing away of code. If you do, noone will care, and you will be frustrated.

      That is about it.

    3. Re:Perhaps this is an Ask Slashdot... by Laven · · Score: 1

      Mike Harris of Red Hat mentioned that the XFree86 project is looking for a designer for good alpha blended mouse pointers. I don't know if this is still the case.

    4. Re:Perhaps this is an Ask Slashdot... by tdvaughan · · Score: 1

      Try Slicker at Sourceforge.

    5. Re:Perhaps this is an Ask Slashdot... by CoughDropAddict · · Score: 4, Insightful

      I'm a graphic designer who's done a lot of interface design, as well as being an avid follower of human-computer interface trends and issues.

      You are a precious resource!

      Does anyone have any suggestions as to how someone like myself would help contribute to an Open Source project? While I am not a programmer by any means, the interface is definitely somewhere that can use some help in all the Linux distros I've seen and used.

      I'm an open-source author, and my experience says that some projects care about this kind of stuff and some don't. By and large I think you'll find that the software that is part of the major desktops (KDE and GNOME) is developed by people who are much more in tune with this kind of thing. They have a vision of a slick, easy-to-use, well-integrated desktop, and usability is important to them.

      More independent apps can go either way: sometimes it will be a small group of developers and users who are happy with things the way they are and fairly resistant to usability improvements. Mplayer is a good example of this. They are most concerned with the raw power of the program, and don't care much that there is no GUI support worth mentioning, and they expect you to be compiling from source. If you ask questions they'll tell you "man mplayer, it's all in there." There's no point in approaching a project like this, they're just not concerned with UI or usability issues and your suggestions will fall on deaf ears.

      Other times independent projects are concerned with usability, and the project I work on, Audacity, is one of them. UI issues are frequently discussed, mockups created and refined. We are receptive to UI suggestions.

      So my advice would be to find a few applications that interest you that you think would be receptive to suggestions. Come up with a few ideas for improving these applications, and approach the developer list with them. Maybe create mockups of your ideas and link to them from your email. Gauge the response to determine whether you think you would work well the the developers or not, and if so you're started!

      Also, being a Mac person, I don't really know which direction to turn in; i.e. does Gnome need help? Debian? etc. Any suggestions would be greatly appreciated.

      Hmm. Plain old non-developer users are most likely going to be using KDE and/or GNOME (and their associated applications), so Linux usability in general is most greatly increased when these applications become more usable. On the other hand, both of these projects already have a pretty good handle on usability, and have somewhat firm ideas about their plan for how they will achieve usability. So you would probably encounter more inertia approaching applications like this, and you would have to become more deeply involved to really be able to accomplish anything.

      I'm just making this up, but probably the applications that could use the most help are KDE or GNOME applications that are farther from the core of these desktops. Don't look to Abiword, Galeon, Kword, or Konqueror. Look for lesser-known but promising applications that have a good technical basis (programmers who know what they are doing) but not much thought into the UI yet.

      Another strategy is just to use Linux for a while and see what you are drawn to. If there's something that nags you about the interface to a program you use regularly, bring it up to the developers and propose a solution.

      I hope you manage to find a project that can use you!

    6. Re:Perhaps this is an Ask Slashdot... by ajs · · Score: 2, Informative

      Check out the GNOME HIG and the effort linked to by this article to combine with KDE's interface guidelines. Certainly those are good places to start.

    7. Re:Perhaps this is an Ask Slashdot... by Lussarn · · Score: 0

      Was that rant on mplayer really necessary...

      Othewise, good points.

    8. Re:Perhaps this is an Ask Slashdot... by baryon351 · · Score: 1

      Please do submit this as an ask-slashdot. I'm in much the same boat, but with little training. I'm just very graphical, very interested in humancomputer interfaces, and it's just one of those things I'm known to rant on quite a bit by people who know me :).

      I'd love to see the concept of good UI design kept in the forefront of the minds of the OSS community.

    9. Re:Perhaps this is an Ask Slashdot... by sl0w · · Score: 0

      This may be the stupidest idea ever but...

      Being a graphic designer you have an edge on those of us who end up doing the coding half the time. Enlightenment has one of the most edgy design elements i've seen in the *nix world. KDE and GNOME have the fluffy stuff while being extremely functional. (I converted to KDE from blackbox, I feel I know the spectrum pretty well.)

      Use your creative juices and make some mock-up screenshots with your ideal looking desktop. Make sure to integrate various IM's, Office suites, browsers, and the like. Take existing screenshots where people have obviously taken countless hours to customize to the smallest detail and work from there.

      Programmers are amazing people with amazing talent, we just lack creativity sometimes when it comes to original, artistic, creativity. NOT TO SAY OUR CODE IS NOT ART, OR CREATIVE.

    10. Re:Perhaps this is an Ask Slashdot... by Sri+Ramkrishna · · Score: 1

      Join the mailing list on www.freedesktop.org. Click on "Getting Involved" and join the xdg mailing list.
      I think that would be the best more "general" way of providing feedback. I'm sure someone on the list can get you going.

      sri

    11. Re:Perhaps this is an Ask Slashdot... by Sri+Ramkrishna · · Score: 1

      Actually, talk to Seth Nickells. He's one of the authors of the HiG project. I'm sure he can help you out.

      sri

      (goggle on his name, you'llprobably find his email address)

    12. Re:Perhaps this is an Ask Slashdot... by CoughDropAddict · · Score: 1
      Was that rant on mplayer really necessary...

      That was in no way a rant. I just wanted to prevent "thatguywhoiam" from becoming frustrated at trying to improve the usability of a project like mplayer. I don't think you can really dispute these facts:
      • the top priority of the mplayer developers is the raw power of the program
      • an intuitive, easy-to-use user interface is not a priority
      • the mplayer developers are basically hostile to efforts to make binary packages of mplayer, therefore expecting end-users to compile from source. This clearly demonstrates the low priority of making mplayer easily usable by laypeople.

      I myself use mplayer because it is powerful. I am not anti-mplayer. But mplayer would not be a good project to approach with usability improvement ideas.
    13. Re:Perhaps this is an Ask Slashdot... by Natalie's+Hot+Grits · · Score: 1

      My suggestions are a little different than the others, but I just want to tell you another perspective that might have been overlooked.

      Career wise, you seem to be a graphics designer. Now, I'm not a computer scientist or computer engineer, but I do know how to program (basics) and I know more than one language. I have found that even if your job isn't to program, knowing how to do it, and knowing a few languages, will dramatically help your understanding and marketability in this particluar jobmarket. You need to be able to communicate with the developers in a way that both of you are on the same ballpark. Developers like to have a say in how their program is used, and trying to develop the most efficient interface to an application is not possible without the developers cooperation. Likewise, developers must work with the graphics designers to be able to provide in the application what the designers need to make the efficient UI.

      The other suggestions are great, and if you are just wanting to toy around with open source programs, and help to improve them somewhat, then thats fine. But my suggestion that would be IMO a wise career move would be to learn how to program.

      It's easy to sign up for a couple programing classes, or just buy a book and learn. I am not going to suggest which language to start with, because everyone has their preference. Computer engineers and computer scientists know better what languages can do what tasks with the most readability and structure and with the least work. However, I can say that if you wanted to help a project such as KDE, learning C++ and Python would be your best bet. If you wanted to help GNOME, you should probably learn C. The final step is to familiarize yourself with the standard toolkits on their respective platform (QT for KDE, GTK+ for GNOME).

      That is all it takes. Once you know the basics of programing, and if you happened to learn C++, helping improve KDE applications would be that much easier, and more developers would be willing to take a look at a patch which made their application conform to the UI Guidelines on freedesktop.org before they will be willing to read criticism on what they need to do and need not to do in their UI.

      If your not willing to learn to program, probably the best way to help improve a project like KDE in the UI area would be to submit detailed bug reports explaining what needs to be changed in order to conform the application to the freedesktop.org guidelines.

      Or, maybe you should contact freedesktop.org and see if they need help developing these guidelines.

      --
      Two infinite things: your stupidity and mine. But I'm not sure about the latter. If my sig offends you, I'm sorry.
    14. Re:Perhaps this is an Ask Slashdot... by Grishnakh · · Score: 1

      I think some of this is a distribution issue. For instance, in SuSE 8.1, MPlayer is readily available in pre-compiled form as part of the standard distribution. Other mainstream, recent releases may be the same way. I've seen many open-source projects like this which only provide source code on their project website (or very outdated binaries contributed by other people), but mainstream distributions supply compiled versions. In short, you should first look to your distribution (SuSE, RedHat, etc.) for open-source software, and only get it from the source if 1) you need the source code itself, 2) your distribution doesn't have it, or 3) you need a newer version than your distribution has. But in these cases be prepared for it not being as easy.

      As for the MPlayer UI, MPlayer seems to be designed like many open-source programs, where the engine is separate from the GUI. I usually use Mplayer from the command line, but a GUI is available with "gmplayer". This seems to have several skins available, which are quite different in appearance. Perhaps the problem is that the core developers of MPlayer are more concerned with the engine, and not many people have stepped up to work on the UI. I would encourage interested people to do so.

    15. Re:Perhaps this is an Ask Slashdot... by gnugnugnu · · Score: 1

      http://mail.gnome.org/archives/usability/

      have a read, get an idea of what goes on and maybe sign up.

    16. Re:Perhaps this is an Ask Slashdot... by mennucc1 · · Score: 1

      I co-author a software gtkmorph if you wish to give an help, may you try the GUI? thanks in advance

  32. The comment links to www.freedesktop.COM by Anonymous Coward · · Score: 1, Informative

    Should be .org. .com is some crappy ad site.

  33. Linux: harmony and understanding by carrox · · Score: 1

    Linux: harmony and understanding
    http://comic.escomposlinux.org/ecol-07-e.png

    1. Re:Linux: harmony and understanding by ma++i+ude · · Score: 1
      http://comic.escomposlinux.org/ecol-07-e.png

      Does anyone else think the funniest thing about the comic is that it's typeset in MS Comic Sans?

      --
      You can't shut us down! The Internet is about the free exchange and sale of other people's ideas!
  34. correct the correction by chrysrobyn · · Score: 3, Informative

    Please note the corrected URL points to www.freedesktop.org, while the old one was freedesktop.org, NOT freedesktop.com.

    If we can't keep the org/net/com/new TLD of the day straight, how can we expect others who just want it to work to keep it straight?

  35. freedesktop.org != freedesktop.com by stevenj · · Score: 3, Funny

    A hint to the Slashdot editors, who somehow managed to forget to proofread their post and URLs for the first time in memory. What is happening to Slashdot's high journalistic standards?

    --
    If a thing is not diminished by being shared, it is not rightly owned if it is only owned & not shared. S. Augustine
    1. Re:freedesktop.org != freedesktop.com by D'Arque+Bishop · · Score: 1
      A hint to the Slashdot editors, who somehow managed to forget to proofread their post and URLs for the first time in memory. What is happening to Slashdot's high journalistic standards?

      You're new around here, right?
    2. Re:freedesktop.org != freedesktop.com by PunchMonkey · · Score: 1

      For a second there I thought you said "What is happening to Slashdot's high school journalistic standards?".

      --
      I'll have something intelligent to add one of these days...
    3. Re:freedesktop.org != freedesktop.com by Herkum01 · · Score: 1

      What is happening to Slashdot's high journalistic standards?

      Which ones? They ones that are in relation to a star writer from the Washington Post, or the ones related to Matt Druge report(Monica Lewinsky)!

  36. NO! by Anonymous Coward · · Score: 0

    We KDE users will never mingle amongst you gnome-using elitist beardie weirdies! gnome is dead, long live KDE!

    1. Re:NO! by xutopia · · Score: 1

      because of ignorant people like you Windows is on 95% of desktops out there. It's high time that efforts are put in the same direction. When using Linux is easy for the average Joe Blow we'll have a better world.

    2. Re:NO! by Anonymous Coward · · Score: 0

      because of ignorant people like you that 95% of obvious sarcasm is ruined out there. It's high time that efforts are made to pull the pole from your ass. When obvious jokes are understood easily by self-righteous people who fly off the handle, we'll have a better world.

    3. Re:NO! by Anonymous Coward · · Score: 0

      " because of ignorant people like you Windows is on 95% of desktops out there."

      Because of the gnome-tainted like you, there is desktop confusion. Accept KDE as the one true desktop or be destroyed!

  37. Re:They got the hint by commodoresloat · · Score: 4, Funny

    Or perhaps they got the hint from OS X.

  38. Error in correction by wowbagger · · Score: 2, Informative

    The URLs ares
    freedesktop.org and www.freedesktop.org

    not freedesktop.com and www.freedesktop.com

    which seem to be placeholders for a domain squatter.

    1. Re:Error in correction by wandernotlost · · Score: 1
      freedesktop.org does not exist. If it works for anyone, it's because their browsers are adding 'www.' when they find that it does not exist.
      $ host freedesktop.org
      freedesktop.org has no A record (Authoritative answer)
  39. Re:They got the hint by arglesnaf · · Score: 1

    Or if you look at the bottom of the page, the site is hosted by Redhat. Perhaps the same people who had the hint at Redhat tried to move the effort out into the community in general.

  40. Dear Mr Moderator by dlb · · Score: 0

    The truth hurts, doesn't it?

    Love,

    ~dlb

  41. link doesn't work? by raix · · Score: 0, Flamebait

    It works great in IE :) tee hee

  42. Re:They are missing the ~experts~ on UI design by terkozer · · Score: 1

    begin sarcasm;
    Hey, MS is releasing a version of linux soon too. Check out their website..
    MS Linux
    end sarcasm;

  43. Hosted by the makers of blue curve by thinkliberty · · Score: 4, Interesting

    http://www.freedesktop.org/ Website hosted by Red Hat, Inc. Is this a cry for help? They need to fix the abomination that is blue curve?

    1. Re:Hosted by the makers of blue curve by fault0 · · Score: 1

      It's pretty much run/hosted by Havoc Pennington.. Not sure if Redhat itself is officially involved in such activities or not.

      Anyways, it's good that they are doing this. Bluecurve was a nice start, but it's just a theme.

  44. Re:They got the hint by Gortbusters.org · · Score: 1

    Well OSX didn't take their software and straighten it out, like a teacher and the students.

    --
    --------
    Free your mind.
  45. Wrong link by poincaraux · · Score: 1

    The link at the end of the story that points to freedesktop.com should probably point to freedesktop.org (or even www.freedesktop.org since the non-www version seems to cause trouble for some people). Unless, of course, slashdot really meant to provide some free advertising to the lucky folks at freedesktop.com.

    1. Re:Wrong link by janda · · Score: 1

      Or, they might be pissed off at them, and are working on the "accidental" slashdot effect.

      --
      Karma: Food Fight (Mostly affected by Date Plate).
  46. Thanks Timothy! by fobbman · · Score: 4, Funny

    "Update: 02/03 19:56 GMT by T: Apparently not everyone's browser can read http://freedesktop.com, so the initial link up there now sports a "www" as well."

    Appreciate that. I'm stuck with this low market-share browser that couldn't handle the URL. Appreciate the bone.

  47. This can only be good . . . by Eric+Damron · · Score: 4, Insightful

    This can only be a good thing for both desktops. It will also make life easier for programmers who wish to support both desktops.

    It shows that KDE and Gnome can have healthy competition while at the same time, work for a common goal, unlike unhealthy competition where one tries to be incompatible in the hopes of gaining an advantage. It is too bad that some proprietary companies don't understand the long-term benefits of healthy competition verses unhealthy competition.

    --
    The race isn't always to the swift... but that's the way to bet!
  48. UI Review by Anonymous Coward · · Score: 1, Informative

    Hello readers,

    Please allow me to introduce you my UI review which I've written a couple of days ago. It explains various aspects of the current GNOME GUI situation and illustrates them by using a bunch of pictures. I think posting this here is a good idea so you as programmer get a sight of the whole situation that personally I see. This text has been discussed with the members of the GNOME germany community on IRC and various other members of the GNOME community that work directly or indirectly with the modules on CVS. It has been read, verified and signed to be a good source of information. I really like to encourage you to read this so you can avoid problems within your future projects if you see the system as a whole. This text can be found here and was sent to the mailinglist which can be read here and last bot not least OSNews.com announced it big on their mainpage where many people can read and comment about it here. A copy of the text has been sent to Bill, Callum and Seth.

    In case you read the text already. Let me encourage you to read it again because I made some heavily updates to it (also verified by the community).

    Greetings.

    oGALAXYo

    1. Re:UI Review by prepp · · Score: 1

      interesting, is this "atlantis" web browser availible?

      --
      "There is hopeful symbolism in the fact that flags do NOT wave in a Vacuum " --Arthur C Clarke
  49. Subliminal??? by mobiGeek · · Score: 1
    How much was /. paid for this ad? :-)
    Update: 02/03 19:56 GMT by T:Apparently not everyone's browser can read http://freedesktop .com...[sic]
    --

    ...Beware the IDEs of Microsoft...

  50. Please. by yobbo · · Score: 1

    A UNIFIED THEME FORMAT.

  51. Finally the KDE Team stopped being crying Babies by Anonymous Coward · · Score: 0, Insightful

    Finally the KDE Team stopped being crying babies. I've always thought that it was very unprofessional for them to whine constantly about how Redhat had it "in for KDE". The problem with Linux is it needs a common desktop with different themes. I don't want two different control panels.

    I think the web browser should be Mozilla, the office suite should be Open Office, email client Evolution, and NOT a bunch of substandard incompatible(i.e. you cant cut and paste between KDE and Gnome apps). I DON'T like Koffice and the rest of the garbage BUT I DO like KDE's Graphical User Interface more than Gnomes.

    This is a very good step, because we should take the best from KDE and Gnome and combine it into one effort.

  52. What we really need is by Anonymous Coward · · Score: 0

    A shared compound document model across both platforms!

  53. Why do you need anything more than fvwm2 ? by Anonymous Coward · · Score: 0

    Or twm for that matter. Do you really want bloated eye-candy in exchange for efficient
    functionality offered by fvwm?. Hell will freeze over before I install Gnome or KDE.

  54. Re:They are missing the ~experts~ on UI design by josh+crawley · · Score: 1

    Think that's funny? Get a load of this.

    http://www.microsoftlinux.com/

    And the guy's serious. Makes a good point too.

  55. Timothy, that is a bad link by John+Harrison · · Score: 2, Informative

    freedestop.com is not freedesktop.org

  56. Ok/Cancel button locations by Anonymous Coward · · Score: 1, Insightful

    As long as the agree on the ordering of "Ok" and "cancel" in the bottem right corner of a window, I'm happy.

  57. browser? by Lxy · · Score: 2, Informative

    Too bad Timothy has no idea WTF he's talking about.

    Apparently not everyone's browser can read http://freedesktop.com

    Not only is freedesktop.com -NOT- the site in the article, but the browser has nothing to do with it.

    $ ping freedesktop.org
    ping: unknown host freedesktop.org
    $ ping www.freedesktop.org
    PING freedesktop.redhat.com (66.187.233.246) from 192.168.0.3

    Under Timothy's logic, my version of BASH can't read it either. I'd better upgrade to Windows Explorer or something more "standard".

    Timothy:
    It's a server config issue. Whoever admins freedesktop.org (Redhat apparently) doesn't understand Apache config well enough to allow requests for http://freedesktop.org. Is it you by chance?

    --

    There is no reasonable defense against an idiot with an agenda
    :wq
    1. Re:browser? by Anonymous Coward · · Score: 1, Insightful

      It has nothing to do with their Apache configuration.
      The reason you cannot ping freedesktop.org is because freedesktop.org is not setup in their DNS entries. Only www.freedesktop.org is setup.

    2. Re:browser? by Lxy · · Score: 1

      you are correct. How who's the idiot :-)

      --

      There is no reasonable defense against an idiot with an agenda
      :wq
    3. Re:browser? by jesser · · Score: 1
      Apparently not everyone's browser can read http://freedesktop.com

      Not only is freedesktop.com -NOT- the site in the article, but the browser has nothing to do with it.
      Mozilla has a feature where it guesses that a www is missing from a user-typed URL when a hostname doesn't resolve. IE, Netscape 4, and Opera 7 for Windows all don't have this feature.

      Mozilla also has a bug (159742) where the same guessing triggers if you click "open link in new window" on a link in a web page, which might explain how the incorrect link in the submission got past the editors.
      --
      The shareholder is always right.
    4. Re:browser? by Anonymous Coward · · Score: 0

      "How who's the idiot" so quotable ;)

    5. Re:browser? by Lxy · · Score: 1

      *hides* :-)

      --

      There is no reasonable defense against an idiot with an agenda
      :wq
    6. Re:browser? by labratuk · · Score: 1

      Actually it was whoever set up their dns. They didnt tell it to send port 80 requests to the root domain to freedesktop.redhat.com.

      --
      Malike Bamiyi wanted my assistance.
  58. RedHat saves face by Anonymous Coward · · Score: 0

    Of course, this is just a way for RedHat to move over to the KDE without getting egg on their face.

  59. Second hand crap.. by XaXXon · · Score: 4, Insightful

    I've got a friend of mine -- who should really be commenting on this stuff himself, but seems to have fallen from the face of the planet -- who is (was?) highly involved in some Gnome development.

    He was always talking about how SUN funded all these usability studies on Gnome and basically neudered it. They basically LCD'd (lowest common denominator, not liquid crystal display) the whole environment. This is part of the reason that KDE looks like crap under RedHat -- since all the cool stuff was taken out of Gnome, and RedHat wanted Gnome and KDE to look very similar, guess what happened to all the KDE features... *poof* gone.

    It really seems like KDE is doing the right thing.. and this is painful for me to say, being a big RedHat fan (while it's unrelated, I work right down the street from them), but I really feel like they're stuck in a common big-business problem of "Well, we dumped all this money into it, so we can't stop using it or we'll look really dumb."

    I agree on unifying the desktop.. but man, RedHat did a job on KDE.

    1. Re:Second hand crap.. by minkwe · · Score: 1

      Could you stop beating this dead horse already! ?

      --
      "Fighting terrorists with millitary might is like killing a mosquitor on your Dad's forehead with a rifle."
    2. Re:Second hand crap.. by IamTheRealMike · · Score: 1
      He was always talking about how SUN funded all these usability studies on Gnome and basically neudered it. They basically LCD'd (lowest common denominator, not liquid crystal display) the whole environment.

      Good on them. GNOME 1.4 was a mess, sorry, but it was. Did you actually read those usability studies? One of the participants actually laughed out loud when they saw the choices available for a clock applet: "Clock", "Another Clock", "JDBC Binary Clock", "AfterStep Clock".

      4 clocks! The mind boggles. They didn't "neuter" it, they brought it back under control and introduced some sanity into it.

      This is part of the reason that KDE looks like crap under RedHat -- since all the cool stuff was taken out of Gnome, and RedHat wanted Gnome and KDE to look very similar, guess what happened to all the KDE features... *poof* gone.

      That's nonsense. Name me features that were removed. No, making the default browser Mozilla instead of Konqueror is not "removing features", as far as the end user is concerned, it's adding them.

      It really seems like KDE is doing the right thing..

      Right with regards to what? Don't get me wrong, KDE is doing a fine job in providing a featureful desktop, but loading up on the features and preferences is not the right way to go for most users if you ask me. See the new improved and cleaned up control center? What, pray tell, is the difference between:

      "Theme Manager", "Style", "Icons", "Colors", and "Window Decorations".

      OK, so the last 3 are fairly obvious, but what do the other two do then? I've used KDE dammit, and I can't even remember. I think one of them is buttons/controls theme, but I don't really recall, and it's hardly obvious is it.

  60. Re:Error in correction - sorry by timothy · · Score: 1

    Left the corrected version previewed but saved in a tab. Since I'd previewed, and it looked fine to me, I was wondering what the comments were talking about. Braintremor, sorry.

    timothy

    --
    jrnl: http://tinyurl.com/c2l8yr / foes: http://tinyurl.com/ckjno5
  61. Re:Wrong link - sorry by timothy · · Score: 1

    No, I just left it in a tab after I previewed, didn't realize I hadn't updated / thought I had. Sorry!

    timothy

    --
    jrnl: http://tinyurl.com/c2l8yr / foes: http://tinyurl.com/ckjno5
  62. Browser doesn't support the link? by Anonymous Coward · · Score: 0

    So browsers are now supposed to support URL's for DNS names that don't exist?

    ping freedesktop.org
    ping: unknown host freedesktop.org

  63. Prediction by Anonymous Coward · · Score: 0
    Let's assume that this effort by our friends at KDE and GNOME is wildly successful. It still won't make any difference in the Big Battle against MS for the desktop.

    Why? Simple: The KDE/GNOME problems aren't even close to being a problem for the mainstream Windows users. The barriers keeping them from converting to Linux are app and data compatibility and availability, and the pain of migration.

    While I applaud this effort, it will only benefit those already on Linux. It's equivalent to trying to get people to convert from gas to electric cars by offering them better floor mats in the new vehicles.

  64. www? by bellings · · Score: 1

    No-one's browser should be able to read "http://freedesktop.org/", since no nameserver returns an A or CNAME record for the domainname "freedesktop.org"

    Can someone explain why a browser would be so broken that it would return a page for a domain that simply doesn't exist?

    --
    Slashdot is jumping the shark. I'm just driving the boat.
    1. Re:www? by Anonymous Coward · · Score: 0

      Over to you, Bill....

    2. Re:www? by fault0 · · Score: 1

      Actually, Mozilla is broken enough to have this feature, while IE isn't.

    3. Re:www? by Anonymous Coward · · Score: 0

      Some browsers append www if they have problems finding a server.

  65. artsd and esd (and oss) by vlad_petric · · Score: 4, Insightful

    I'm just wondering why they don't start by uniting the sound systems ... having two interfaces is not so bad, as long as they interoperate reasonably well. And by that I mean the very basics, like clipboard and sound. Uniting the sound API shouldn't be that hard, and moreover should reduce the nuissance of killing/restarting artsd everytime I want to use sound within a gnome application .

    --

    The Raven

    1. Re:artsd and esd (and oss) by lmfr · · Score: 1
      artsdsp esd
      should work. The other way around doesn't seem to work, though...
  66. thanks for not reading either one! by Anonymous Coward · · Score: 0

    dumbass, if you had read a single thing put out by KDE + GNOME you would have realised that both looked carefully at every major published style guide out there including BeOS, Next, Apple, Sun and even Microsoft.

  67. they have you dumbass. by Anonymous Coward · · Score: 0

    why can't slashdot posters read before they run their fucking mouths?

  68. How about common SVG implementations? by Anonymous Coward · · Score: 2, Interesting

    A few stories ago (on /.) librsvg was mentioned, and how great the gnomedesktoplooks with it. We might be ready to start building icons, widgets, themes, ... for svg,itwilllook great,but it could be better...

    How about putting KDE's and Gnome's heads together to think how to create themes, icons, ... and store them in the file system (think about config files too here) so both KDE and Gnome can use a common base of SVG themes.

    We're all (both KDE and Gnome) just starting to get SVG working, get it done right now!

  69. Good to hear but.... by Happy+Coder · · Score: 1

    Maybe they will both agree to use less memeory as well. I have a box with about a GIG it in and I have seen both KDE and Gnome eat 750M.

  70. Now if only we could fix the X Clipboard by Anonymous Coward · · Score: 0
    I have converted several friends to Linux and one of the hardest concept is teaching them how to copy and paste with X.

    "See, use Ctrl+C (sometimes?), but if you're in a console, just highlight it... But don't highlight anything otherwise, or you'll lose whats in your clipboard".

    And what about PASTING! Highlighting to overwrite in one sequence copies what you highlighted to your clipboard (overwriting your precious clipboard text)! GFD! Mozilla got around this by using a special key sequence to highlight the entire location bar without copying it, but what about EVERY OTHER TEXT BOX YOU USE!!!! </rant>

    1. Re:Now if only we could fix the X Clipboard by Guy+Harris · · Score: 4, Informative
      "See, use Ctrl+C (sometimes?), but if you're in a console, just highlight it... But don't highlight anything otherwise, or you'll lose whats in your clipboard".

      Those are two different mechanisms; Ctrl+C is "copy to clipboard", and you then paste from the clipboard, but "just highlight it" is followed by the middle-mouse-button "paste current selection".

      I'd personally be a bit annoyed if Ctrl+C in a terminal window copied the selection to the clipboard rather than sending a ^C down the pseudo-terminal to interrupt the current program - but I'd be similarly annoyed if it did that in the terminal windows on a certain non-UNIX operating system as well. (In that OS, at least in the 5.0 version of the "New Technology" flavor of that OS, you can either select "Edit->Copy" on the window menu or, apparently, use the "Enter" key - I guess "Enter" acts as a CR/LF only if nothing is selected.)

      And what about PASTING! Highlighting to overwrite in one sequence copies what you highlighted to your clipboard (overwriting your precious clipboard text)!

      Not in any desktop that implements its primary and clipboard selections according to the X clipboard explanation, which says "selecting but with no explicit copy should only set PRIMARY, never CLIPBOARD."

      The problem here is that people have gotten confused about what the "clipboard" is. The clipboard is not what selecting something with the mouse changes and not what your middle mouse button pastes. Selecting with the mouse changes the primary selection, and the middle mouse button pastes the primary selection. "Copy" copies the primary selection to the clipboard; merely selecting something doesn't, it just changes the primary selection to refer to what you selected. "Paste" inserts the contents of the clipboard in place of the current selection (which could be a "zero-length" selection, in which case it amounts to inserting at the point of the selection, e.g. insert at the text cursor in a text window).

      (As I remember, the KDE people spoke of them both as "clipboards" when discussing the KDE 3.0/Qt 3.0 change to make the primary selection and clipboard work that way, in order to, I guess, avoid confusing people whose brains had become too locked into the notion of the middle mouse button pasting some kind of "clipboard"; however, the X11 Inter-Client Communication Conventions Manual calls the primary selection PRIMARY and the clipboard CLIPBOARD.)

    2. Re:Now if only we could fix the X Clipboard by Anonymous Coward · · Score: 0
      I'd personally be a bit annoyed if Ctrl+C in a terminal window copied the selection to the clipboard rather than sending a ^C down the pseudo-terminal to interrupt the current program
      Agreed. So using a key (control) that sends CLI signals, to also trigger GUI events, was a major M$ fuckup. So why do GNOME and KDE copy it?! Apple, for one, uses another key for the GUI instead (command), and so there is no such collision in Terminal.app.
      And what about PASTING! Highlighting to overwrite in one sequence copies what you highlighted to your clipboard (overwriting your precious clipboard text)!

      Not in any desktop that implements its primary and clipboard selections according to the X clipboard explanation, which says "selecting but with no explicit copy should only set PRIMARY, never CLIPBOARD."

      The problem here is that people have gotten confused about what the "clipboard" is. The clipboard is not what selecting something with the mouse changes and not what your middle mouse button pastes. Selecting with the mouse changes the primary selection, and the middle mouse button pastes the primary selection.

      So what?!

      Who cares if it's called PRIMARY or CLIPBOARD? The end result is the same: a user is merrily copying and pasting with one method, only to find that, sorry, it shall break down when it comes to overwriting. Talk about interface consistency...

    3. Re:Now if only we could fix the X Clipboard by Guy+Harris · · Score: 1
      Who cares if it's called PRIMARY or CLIPBOARD? The end result is the same: a user is merrily copying and pasting with one method, only to find that, sorry, it shall break down when it comes to overwriting. Talk about interface consistency...

      The only method you can copy and paste with is the one involving the clipboard; you cannot cut and paste with the middle mouse button, you can only paste-current-selection. When phrased that way, it's pretty obvious why you can't overwrite - the "current-selection" part is a bit of a giveaway, as overwriting is pasting something on top of, err, umm, the current selection, which is what the middle mouse button pastes.

      I suspect a LOT of the confusion would disappear if:

      1. there were few applications (or maybe no applications) that support middle-mouse-button paste-current-selection but don't support clipboard-based cut/copy-and-paste;
      2. people no longer spoke of selection changing the clipboard or the middle mouse button pasting the clipboard or of the paste-current-selection stuff being "copy and paste";

      as then people wouldn't expect the middle mouse button operation to behave like "cut and paste".

      Middle-mouse-button paste is a very useful operation. One should not, however, be particularly surprised that it doesn't support replacing one selection with the other, given that what it pastes is the selection.

      (That's why I do care what the selections are called; blurring the distinction between cut/copy-and-paste and paste-current-selection can lead to people being surprised that you can't use paste-current-selection to do all the things you can do with copy-and-paste.)

    4. Re:Now if only we could fix the X Clipboard by Anonymous Coward · · Score: 0
      I suspect a LOT of the confusion would disappear if:
      1. there were few applications (or maybe no applications) that support middle-mouse-button paste-current-selection but don't support clipboard-based cut/copy-and-paste;
      2. people no longer spoke of selection changing the clipboard or the middle mouse button pasting the clipboard or of the paste-current-selection stuff being "copy and paste";
      1: Yes! In other words, have something that works for overwrite always work consistently. Then paste-current-selection is welcome gravy--but not otherwise. And it's still far from true of current distros even in their default state.

      2: For developers, yes. But for users, they could care less about such terminology. I took your post to mean that they should know the difference before being allowed to sit at a machine, and that's what I'd take issue with.

      Thanks for the clarification.

    5. Re:Now if only we could fix the X Clipboard by Guy+Harris · · Score: 1
      1: Yes! In other words, have something that works for overwrite always work consistently. Then paste-current-selection is welcome gravy--but not otherwise. And it's still far from true of current distros even in their default state.

      It's not an issue of the distribution, it's an issue of the applications and of the underlying toolkit, etc.. If application X doesn't have cut/copy/paste operations, it's probably because the developer didn't bother implementng it or the widget they're using doesn't support it.

      The KDE User Interface Guidelines suggest in the predefined shortcuts section, and the GNOME Human Interface Guidelines suggest in the standard application shortcut keys section, that Ctrl+C be used for "copy", Ctrl+X be used for "cut", and Ctrl+V be used for "paste"; however, I don't know whether they suggest that those operations exist in the first place.

      They also don't suggest what to do in those (probably rare) cases where using those keys for those purposes wouldn't necessarily be the best idea. I'd vote for a right-mouse-button menu that offers Cut, Copy, and Paste; I'm not sure why Microsoft didn't do that in the NT 5.0^H^H^H^H^H^HWindows 2000 Command Prompt window - perhaps that's fixed in NT 5.1^H^H^H^H^H^HWindows XP.

      2: For developers, yes. But for users, they could care less about such terminology.

      OK, as long as "developers" includes anybody who writes documentation - and anybody who tells their friends how to use the system, etc..

      I.e., the users would care about the terminology if it confused them, for example if it let them to think that selecting text on the screen automatically caused it to be copied to the clipboard, so that if they used Ctrl+V the stuff they selected, rather than the stuff they last copied with Ctrl+C or cut with Ctrl+X, would be pasted, and so that they thought that selecting stuff automatically discarded what they'd copied to the clipboard in favor of the new stuff.

    6. Re:Now if only we could fix the X Clipboard by Anonymous Coward · · Score: 0
      It's not an issue of the distribution, it's an issue of the applications and of the underlying toolkit, etc.. If application X doesn't have cut/copy/paste operations, it's probably because the developer didn't bother implementng it or the widget they're using doesn't support it.
      Your reasoning is a developer's reasoning, so you identify (technically) where the problem lies. Yes, it's in the applications. But seeing that it be solved (in a minimal, functional set of apps) is, to me, an issue for the distros -- something that I'd hope the effort under discussion will solve.

      Lest this seem vague, here's an example in SuSE 7.0. (Sorry, dunno if it's changed in later versions, this is what I've got right here to double check what I'm saying.)

      Do Edit > Copy (or ctrl-C) in Mozilla, Edit > Paste (or ctrl-V) in Nedit. Nothing happens. Same with Kedit. Only right-click works.

    7. Re:Now if only we could fix the X Clipboard by Guy+Harris · · Score: 1
      But seeing that it be solved (in a minimal, functional set of apps) is, to me, an issue for the distros -- something that I'd hope the effort under discussion will solve.

      The distributors might not entirely agree with that. They might not be willing to supply modified versions of those applications (or toolkits) in the name of consistency, as that means more stuff to maintain and sync with the upstream software.

      They might be willing to support efforts such as freedesktop.org, and let them try to encourage consistency, and they might even be willing to pay some developers to contribute code upstream.

      Do Edit > Copy (or ctrl-C) in Mozilla, Edit > Paste (or ctrl-V) in Nedit. Nothing happens. Same with Kedit. Only right-click works.

      7.0 is an older release, and at least some of that problem is due to the disagreement between older (pre-3.0) versions of Qt and GTK+ in the interpretation of the clipboard. SuSE's list of press releases speaks of 7.1 coming out in early 2001, and doesn't speak of 7.0 at all in 2001 (their archive doesn't appear to go back further than 2001); Qt 3.0 came out in October 2001, according to the Trolltech press release archive, so SuSE 7.0 was probably incapable of being bundled with a KDE release that included Qt 3.0 as it appears that no such release existed at the time 7.0 came out.

      That means that KDE was, unfortunately, simply not going to play well with many applications when using the clipboard.

      The inability of Mozilla and Nedit to play together is somewhat more of a surprise; I don't know where Mozilla uses GTK+ rather than rolling its own widgets, but the GTK+ parts should work together with Nedit, as Nedit uses Motif, and Motif uses the same interpretation of the clipboard as GTK+.

      In the case of Mozilla and KEdit, it's not as if there's some configuration file that the SuSE folks set up incorrectly, and if they'd just fixed that those two apps would work together. The same is probably true of Mozilla and Nedit. It's also not as if they could've hopped into the time machine and shipped SuSE 7.0 with KDE 3.0....

      Perhaps these are just technical details, but, regardless of whether a user wants to hear the technical details or not, they sometimes control whether the user's problem can be solved, when it can be solved, and how it can be solved.

      Ultimately, much of the reasoning has to be developer's reasoning, because unless the developers can do something about the problem, and do so, the problem isn't going to get solved.

    8. Re:Now if only we could fix the X Clipboard by vague · · Score: 1

      Gee, I'm not dumb, I'm probably extremly computer literate, and I've been using X for a few years, and I still hadn't figured that one out. Thanks for informing me, but something is seriously wrong with that approach. It might look and feel tasty to experts, but it's a seriously complicated and messy way to have two slightly differing ways of doing what is, in most respects, the same thing.

      It's cute, and knowing what's really going on even I might find it useful, but seriously don't expect my mother to get it, ever. And as long as the middle mouse button is used to paste, she won't be able to ignore it either, she'll just be terminally confused. I know I've been.

      Do you have any idea about how many of the complaints about X copying/pasting that comes from this issue? I'd wager it's a huge part of them. This, if nothing else, should be a hint...

      --

      -
      Listen. Strange women lying in ponds distributing swords is no basis for a system of government.

    9. Re:Now if only we could fix the X Clipboard by Guy+Harris · · Score: 1
      Thanks for informing me, but something is seriously wrong with that approach. It might look and feel tasty to experts, but it's a seriously complicated and messy way to have two slightly differing ways of doing what is, in most respects, the same thing.

      Well:

      1. the cut/copy-to-clipboard and paste from clipboard approach is probably nto going away any time soon, given that it's the way things work on Windows and MacOS;
      2. maybe the middle-mouse-button paste-current-selection can be made to go away, but not without a lot of complaints;

      so if it is the case that the problem can only be fixed by getting rid of one of the mechanisms, I wouldn't hold my breath waiting for the problem to be fixed.

      I'm also completely unconvinced, at this point, that getting rid of the paste-current-selection mechanism is necessary.

      And as long as the middle mouse button is used to paste, she won't be able to ignore it either, she'll just be terminally confused. I know I've been.

      She'd only be confused if she knows about it and has trouble understanding it; I'm unconvinced that either will necessarily be the case. Heck, give most users of desktop UNIX+X two-button mice and turn off the "click both buttons to emulate the third button" option by default in the GUI, and they won't even be able to use it. Those of us who can handle paste-current-selection can order 3-button mice and still use it.

      Do you have any idea about how many of the complaints about X copying/pasting that comes from this issue? I'd wager it's a huge part of them.

      I wouldn't wager that without more data. I'd bet a huge part of it comes from the fact that some applications and toolkits don't implement cut and copy as "cut/copy to the clipboard", but instead change the primary selection, and implement paste as "paste primary selection" rather than as "paste clipboard"; if so, as KDE 3.x displaces earlier versions of KDE, a lot of that will go away.

    10. Re:Now if only we could fix the X Clipboard by vague · · Score: 1

      I'm still confused, because Netscape 4.7whatever that I currently use under Solaris doesn't even adhere to the standard I guess. Which leaves that one fairly useless for me.

      I know this is historical baggage, and I know it's not going away. But I can still complain about how much I wish it would =) I have mostly used Unix with three button mice (Sun hardware) so maybe you're right.

      I'm still confused but cut-n-paste. But now I at least know how it ought to work.

      --

      -
      Listen. Strange women lying in ponds distributing swords is no basis for a system of government.

  71. Not to nitpick, but... by Anonymous Coward · · Score: 0

    RedHat's unified desktop was not controversial. The damage they did to KDE was. If KDE and Gnome functioned and looked exactly the same, few if anyone would have a problem. The problem is when RedHat removes features and abilities from KDE that are available in Gnome, which creates the impression that Gnome is a better desktop. "Unified" is a euphemism--what they actually did was CREATE differences that didn't exist before.

  72. KDE/Gnome have an opportunity to improve on Apple by FreeUser · · Score: 4, Interesting

    Why re-invent the wheel? Why not just adopt Apple's guidelines as-is?

    Because Apple's 1 button mouse is an affront to humankind.

    Seriously, Apple's interface is nice, and they will likely borrow a plethora of good ideas from Apple, but they should not adopt their standard "as is" without question. There are bozo aspects to Apple's interface, the one-button mouse being the most obvious (and before you suggest Apple doesn't need additional mouse buttons, think again. They've had to cobble on the equivelent functionality in a much less intuitive fashion ... by requiring users to hold down the apple key while pressing the mouse button for operations that in the UNIX or Windoze world would use the right mouse button).

    Finally, they can have my single clock middle-button paste feature I've enjoyed under X all these years when they pry it from my cold, dead fingers. Windows and Apple do not make cutting and pasting text nearly as easy as X ... so even the X Window System, which so many love to deride and hate, offers an improvement over Apple and Windoze.

    Focus follows mouse is another example of a feature common in X window managers, lacking in Windoze, and certainly not the default (if available at all) under Apple OS.

    So, while Apple has much good to offer, they are not the be-all, end-all of GUI interfaces, anymore than Microsoft, KDE, Gnome, Enlightenment, or any other particular entity is. They come to the table with a great deal of experience, and a great deal to offer, but God(tm) they are not.

    --
    The Future of Human Evolution: Autonomy
  73. Mac OpenOffice very beta by dmaxwell · · Score: 3, Informative


    Work is underway to give OpenOffice first a Quartz interface then a full Aqua interface. The current OpenOffice for the Mac depends on X11 and is clearly labeled as a "Developer's Pre-release".


    OpenOffice on OS X only exists in it's current form so that the backend code (common to all ports - filters and so forth) can be debugged insofar as the non-GUI parts don't like Darwin. Once the core is solid and clean on Darwin then it will get an interface that is more pleasing. If they had to make a native interface for it before doing anything else, it would take much longer for a solid OS X port. The roadmap is here.


    You're larger point may be valid but the OSX port of OpenOffice (as it currently stands) is not a valid example.

    1. Re:Mac OpenOffice very beta by WinterSolstice · · Score: 1
      Ok, fair enough. But, I must contend that many projects (especially open-source) get stuck into a state where the GUI takes a back seat to features or stability. It happened to WordPerfect for a long time. It happened to 3D Studio Max, and it happens every day to many more applications. Developers or PMs say "hey, this is buggy", or "I need this to do this". Rarely do people stop and say "Wouldn't this be better if I spent some money on UI R&D?".

      -WS

      --
      An operating system should be like a light switch... simple, effective, easy to use, and designed for everyone.
  74. Multiple dsps by dmaxwell · · Score: 1

    Some sound cards have multiple dsps. I believe the Soundblaster Live! has one super dsp that can be multiplexed into a number of devices. Perhaps a Live user can elaborate. I use an ES1373 based card in my home rig that has a full record and playback dsp0 and a playback only dsp1. I usually have artsd running on dsp1 (I don't use any apps that record through arts) and I leave dsp0 open for whatever. The ES1373 helped with my hassles in that regard quite a bit.

    1. Re:Multiple dsps by Ambassador+Kosh · · Score: 1

      I have an sblive and I don't notice problems with any apps. I think it is 16 or 32 devices that can open /dev/dsp without any problems. So with a card like that you can have artsd running, open apps that talk to the sound card directly, run games etc and it doesn't have any errors. It has a hardware mixer for that.

      I REALLY like how well it works. You just run apps and the hardware does its job. It seems to me that all of these sound mixers we have now are just to provide software solutions to a hardware problem. I would like to see some software layer written like arts that both gnome and kde could use that would dump directly to the sound card to do the work if possible and if not then it could mix it itself that way we have a standard interface that all apps can use and don't waste hardware that can do the job.

      --
      Computer modeling for biotech drug manufacturing is HARD! :)
    2. Re:Multiple dsps by Natalie's+Hot+Grits · · Score: 1

      This is exactly the problem with artsd. It currently has no hardware capabilities. Everything it does is in software. If i have a $10,000 card that can have /dev/dsp opened 23048032498 times, artsd can use 1 of them, and you fall back to "software" mixing.

      In my opinion, the correct behavior is as you described it. Have the sound daemon allocate the hardware resources, and if there aren't enough, fall back to software mixing.

      For example: Imagine i have a EMU10k1 sound device. I can open /dev/dsp up to 32 times. What if i have 33 applications that want to send sound to the device? Using arts' method, I must mix all that sound in software. Using a proper sound daemon, I would send all the streams to the daemon, and it would prioritize the hardware opens on /dev/dsp to the applications that need it, and the applications that won't be bothered using a software mixer can be mixed in software as the 32nd channel.

      Running a 3d game through artsd while at the same time running your desktop sounds (ICQ, IRC, etc etc etc...) into the same software mixer IMO isn't a clean solution, and it essentially dumbs down all sound cards into a $5 SB16. This is wastefull.

      --
      Two infinite things: your stupidity and mine. But I'm not sure about the latter. If my sig offends you, I'm sorry.
  75. Re:uniformity is good-Split personalities. by Anonymous Coward · · Score: 0

    To a certain degree,yes. I would like to see a loose coupling between look and behavior. The previous article about SVG could help in the look department since all desktops are basically circles,squares, and rectangles in various permutations. Our desktops are presently in a state of flux, hence the various desktops you see. By seperating the two we also make it easier for UI designers to make changes without being programmers, and programmers to make changes without being as heavily involved in the look (someone still has to handle "behavior"). Better tools for both could eleminate many of the look and feel issues we constantly have to deal with, and also makes it easy to play "what if..." with the desktop without as heavily a penalty one presently pays.

  76. Good point... by srussell · · Score: 1

    However, I'd debate that it was not only not "obviously right", but that it may not even have been "right", full stop.

  77. DOOOOOOD! by applejacks · · Score: 1

    vms developers dranking beer with unix developers, C and C++ developers smoking pot, droping acid, watching pr0n... mass hysteria... Armagedon...

  78. Re:Finally the KDE Team stopped being crying Babie by Anonymous Coward · · Score: 0
    If you phrase it like that then it's too easy to start arguments about defaults. It's better to talk about it as that a desktop should give software a way of accessing the default browser, email, etc.

    That way the defaults chosen are up to distro makers.

  79. So they have seen sense by pxpt · · Score: 1
    At long bloody last!

    I don't know about you lot but I have been waiting for a long time for the two factions to decide to cooperate.

    Having two competing desktops has been useful and productive in the past due to forcing each other to go just that extra mile in an attempt to be better than the other lot. Unfortunately nowdays, it has become increasingly counter-productive in winning over users to the GNU/Linux system.

    The old pioneering days are over, it is time to pat each other on the back for a job well done and get merging (or at the very least cooperating) to ensure a coherent user interface.

  80. Re:They got the hint by Domingos+Neto · · Score: 0
    I wonder why it took so long for them to realize that.

    Having multiple desktop environments is a Good Thing. But having them incompatible with each other, as well as their applications, is a serious bad thing.

    Of course it isn't the only thing that holds the regular user away from Linux, but that's another subject.

  81. Is Aqua white pinstripe or brushed metal? by ChaosDiscord · · Score: 1

    I've been wondering about that. MacOS X makes consistent use of the bright, clean white pinstripe look that defines Aqua. Now many of their new apps use the brushed metal look. Can't Apple pick one and stick with it? They're both nice, but seeing both on screen at the same time is a bit jarring. Perhaps their are two rival graphic artist teams fighting for domination within the company? (And I suspect that many of these applications are independently reimplementing the brushed metal look, a great way to ensure that each app looks and behaves slightly differently from everything else.)

  82. Re:KDE/Gnome have an opportunity to improve on App by Anonymous Coward · · Score: 0

    focus follows mouse is possible in windows..
    if you download and install TweakUI (available on MS's website) you can get that option..
    it's the 1st thing i do whenever i get a new windows installation :)
    TweakUI is available for Win98, WinNT, 2k and XP .. so unless you're completely f**ked and need to use Win95 ( a version of which you may still be available online, i think ms no longer has on their site.) , then you can have various niceties that you miss from X-Windows in MS operating systems :)
    though, i will admit that i think ffm (focus-follows-mouse) shoudl be the default :)

    --vat

  83. Just warning you ahead of time by Ilan+Volow · · Score: 1

    There's a reason why there's a such dearth of people doing usability for open source software.

    In general, both GNOME and KDE developers usually do an excellent job of chasing away people with UI design abilities. There's this attitude among the developers that HCI is a far less important endeavor than, say, something technical like programming. And the developers will let you know it every step of the way. The developers also tend to have the attitude that principles of cognitive psychology (the things you need to exploit in an interface to make it very usable) are a load of bull or nothing more than just one person's opinion. It won't matter how many journal issues you might cite. You can't reason with people who think that Fitts' Law is a TV show about lawyers.

    Also, if you're a mac person, it's really going to annoy the hell out of you that GNOME and KDE developers refuse to believe that microsoft is capable of making really bad UI design decisions. One of people in charge of this new-fangled GNOME/KDE truce told me that Microsoft UI design incompetance was "a myth". Guess he never saw multi-row tabs.

    One thing you want to do is to look at the first year and a half of the "gnome-gui" list (that was the main gnome usability list for awhile) versus the GNOME usability mailing list of today. Notice how the first year or two of the old mailing list had people from a wide variety of UI design backgrounds who brought really good usability ideas to the table. Over the last several years, the GNOME usability movement has degenerated into a "hackers good ole boys club" consisting of a bunch of linux programmers who seem like they'd rather be spending their time in vi writing bash scripts.

    Until there's a good direction to turn to, a distro or open source project that actually values the input of usability folks, you're probably best off staying where you are. The current batch of projects and distributions are committed to shooting themselves (and their end users) in the foot.

    --
    Ergonomica Auctorita Illico!
    1. Re:Just warning you ahead of time by fault0 · · Score: 1

      > Over the last several years, the GNOME usability movement has degenerated into a "hackers good ole boys club" consisting of a bunch of linux programmers who seem like they'd rather be spending their time in vi writing bash scripts.

      Which is I guess why GNOME 2 is vastly more usable than GNOME 1.x (uggggggghhh) was?

  84. just one request by Tom · · Score: 1

    I have just one request for whoever is going to tackle this task (and it won't be an easy one):

    Please stop copying windows.

    Just because windows does it doesn't mean it's not total garbage. Go to Nextstep, to Apple for examples. Copy from the people who know what they're doing. Take the good parts from windows and leave the crap behind.

    We will all thank you so much. If we wanted windows, we'd be running it.

    --
    Assorted stuff I do sometimes: Lemuria.org
    1. Re:just one request by fault0 · · Score: 1

      That isn't exactly a good migration path for people who are currently running windows (95% of the computer users in the world.)

      It's a good idea to copy good things from windows, which both GNOME and KDE do.

    2. Re:just one request by Anonymous Coward · · Score: 0

      The original poster suggests copying the good parts of Windows too. What he's complaining about is that they copy the bad parts. "Good" and "bad" aren't as subjective as you'd think--just ask yourself "would anyone in their right mind do it this way if they hadn't learned it from Windows?" If the answer is no, that's "bad".

      Examples: single-click is nearly useless, except on the web, where double-click is useless. Main system menu pops out of the bottom of the screen but every other menu in the whole OS comes from the top of the screen. And so on. All of these bass-ackwards features can be disabled, but really, why shouldn't you have to ENABLE things that don't make sense?

  85. Re:They are missing the ~experts~ on UI design by WindBourne · · Score: 1

    Cool. So instead of taking 6 or 4 years of getting to where we are, it will now take 20 and we will have to allow for major viruses and worms.

    --
    I prefer the "u" in honour as it seems to be missing these days.
  86. Re:They got the hint by fault0 · · Score: 1

    Or perhaps it was a reaction to rh8 messing up their software (doubt it, havoc is a rh employee, and he's involved with this)

  87. Apple has programmers by krogoth · · Score: 1

    Does that mean that Apple is bad at UI design?

    KDE isn't only coders, and Gnome is probably the same.

    --

    They that quote Benjamin Franklin on liberty and safety deserve neither.
  88. Go with the brushed metal! by doorbot.com · · Score: 1

    homepage.mac.com/max_08/themes/brushed.htm

    I have to wonder too... it seems Apple threw the HIG out to the pinstriped window. No wonder I don't like the default MacOS X interface. Give me MacOS 9 any day... now, with a good theme (see above link) MacOS X is quite nice.

  89. Now if only the user could understand... by doorbot.com · · Score: 1

    The problem here is that people have gotten confused about what the "clipboard" is. The clipboard is not what selecting something with the mouse changes and not what your middle mouse button pastes. Selecting with the mouse changes the primary selection, and the middle mouse button pastes the primary selection. "Copy" copies the primary selection to the clipboard; merely selecting something doesn't, it just changes the primary selection to refer to what you selected. "Paste" inserts the contents of the clipboard in place of the current selection (which could be a "zero-length" selection, in which case it amounts to inserting at the point of the selection, e.g. insert at the text cursor in a text window).

    I'm sorry, what?

    I consider myself reasonably computer literate, and I was completely confused by this explanation. If I have to read this twice to understand how the X clipboard works, the average user is never going to understand why Control-C doesn't work...

    1. Re:Now if only the user could understand... by Guy+Harris · · Score: 1
      I consider myself reasonably computer literate, and I was completely confused by this explanation. If I have to read this twice to understand how the X clipboard works, the average user is never going to understand why Control-C doesn't work...

      Is the "average user" going to be using an terminal window at all? Presumably much of the reason for the desktop GUI environments is to allow users to be able to use {pick your favorite UNIX flavor} without having to use the CLI. If they're not going to be using terminal windows, they're not even going to know that control-C doesn't mean "copy" in such a window.

      All a user who uses only the GUI would need to know is that:

      1. there's text you select, and there's a clipboard, and they're not the same thing;
      2. "cut" copies the currently-selected text in the window you're in to the clipboard and then deletes the selected copy;
      3. "copy" copies the currently-selected text in the window you're in to the clipboard but leaves the selected copy alone;
      4. "paste" pastes the clipboard in place of the currently-selected text in the window you're in, if there is any, or inserts it at the current insertion cursor of the window you're in, if there is no currently-selected text;
      5. the middle mouse button pastes the currently selected text at the current insertion cursor in the window you're in.

      Anybody who can't understand all but the last clause of that is going to have trouble with cut/copy-and-paste with X or with Windows or with MacOS, as that's the way all their clipboards work. The last clause would be a problem only with X, as the other GUIs I mentioned don't have middle-mouse-button paste-current-selection.

      As for the users who would use the CLI, all they'd need to know is that, for better or worse, terminal windows don't support control+C - or most of the other control+{key} operations - because they pass those key combinations to the terminal as if the user'd typed control+{key} at a dumb terminal. They either have to use mouse-based copy and paste, as they can't use control+C and control+V, or, on X, using middle-mouse-button paste-current-selection.

  90. Re:Finally the KDE Team stopped being crying Babie by Grishnakh · · Score: 1

    Your problem is that you don't understand that not everyone has the same preferences as you. There's a lot of people (even here on /.) that would readily tell you that everyone should standardize on Windows, that the web browser should be IE, the office suite should be MS Office, email client Outlook, and everything else should be by MS as well and all independent software vendors should either go down the tubes or be bought up by MS until there's only one software vendor in the whole world.

    Luckily, we still have some choice left, and it seems to be growing every day. Some people actually like Konqueror, Koffice, Kmail, or even other programs like Opera, VIM, and elm.

    What KDE and GNOME seem to be doing, which they should, is standardizing the UI guidelines so that KDE and GNOME applications aren't radically different from each other (in needless ways), and so that it's easier for people to use GNOME applications on KDE, and vice versa. I applaud them for this first step, and I hope they'll work together even more in the future to make their environment work together better. Some possibilities, off the top of my head, would be to have look-n-feel settings apply to all applications, and for printing to work seamlessly between them too.

  91. About the "Brushed Metal" Apps by Ian_Bailey · · Score: 1

    It's funny you bring up those few apps that are 'unique' in the way that they deviate from the Apple norm. They have a brushed metal appearence.

    The core guidelines were formed at a time when the Desktop model was all-important, and each window contained a document.

    Now, the brushed metal apps were originally designed to be used in contexts that have "real-world examples". This was mainly in the form of a VCR or Radio for QuickTime and iTunes, respectively.

    However, with some additions such as Safari and the Address Book, Apple is (perhaps unintentially) creating a new paradigm, the 'Application'.

    Unlike the traditional 'document' windows, these windows do not consist of a single edited file, but instead provide an interface to interact with some sort of dynamic system (such as a music library, the www, or Saved Addresses). These windows are entirely different from documents, and are more often than not used for read-only access to these collections of files.

    In fact, I believe that some distinct difference between these 'applications' and 'documents' should be a requirement for any GUI. You do not interact with these different models in the same way, so they should be distinguishable by the user.

    1. Re:About the "Brushed Metal" Apps by Anonymous Coward · · Score: 0

      QuickTime Player is a media player. In theory, I should be able to double-click a media file, have the media player open up and look just like any other application on my system. Instead, QuickTime nags me to buy the "Pro" version before popping up a completely nonstandard window that provides as little information as possible.

      Safari is a web browser. A web browser is meant to display web pages without making its own UI too intrusive to the user. Internet Explorer, OmniWeb, Chimera, Konqueror, Galeon, etc. succeed at this. Safari fails.

      iTunes is a music player. Like all current music players, it uses a nonstandard interface and insists on cataloguing everything in sight. Kudos to Apple.

    2. Re:About the "Brushed Metal" Apps by Anonymous Coward · · Score: 0

      Brushed metal IS a standard interface. Apple has the APIs built into the OS.

      When the developing the interface using Cocoa's drag and drop interface builder (objective C rocks BTW) there is a simple checkbox "Textured Window" (basically brush metal).

      These windows act EXACTLY the same with two differences: different texture, and you can click anywhere on the window and drag.

    3. Re:About the "Brushed Metal" Apps by gea · · Score: 1
      I agree completely, and I think it is intentional on Apple's part. Even the original Mac had at least one window that didn't really fit the "everything is either a document or a container of documents" model, namely the control panel, and that's part of the reason the control panel was confusing for people.

      So now Apple has decided to have two window styles; pinstripe for docs and brushed metal for apps. As for Safari, if you think of the web as a delivery system for multimedia content, it makes sense for Safari to look like a player rather than a document viewer.

  92. Like Matthew Thomas by Pseudonymus+Bosch · · Score: 1

    Matthew Thomas has been criticising UI aspects in Mozilla.

    --
    __
    Men with no respect for life must never be allowed to control the ultimate instruments of death.
    GW Bu
  93. Not eaten but used by Johan+Veenstra · · Score: 1

    How much of that 750M is buffer, and how much is cache. Now tell me again how much MB were used by KDE or Gnome. Unused memory is wasted memory.

    Johan Veenstra

  94. The IE should take care of the HIG rules. by Kplusplus · · Score: 1

    After Gnome and KDE come to terms on what the new HI guidelines should be they should then create a new weel defiend API in which most of the functionailty is pre-defined according to HI Guidelines.

    On Mac OS X using Cocoa or Carbon, Interface Builder takes care of almost all the HI issues, though you can still violate HI guidelines if you try hard enough, Everything from layout to spacing is pre-defined.

    Personally, I feel this would get developers to make Apps that actually follow these new guidelines since the developer had a tradeoff of gaining a rapid GUI development platform that follows UI guidelines as well as having to write less code to do it.

    From experience, the Interface Builder provided with the Mac OS X developer tools is the greatest GUI development tool, i have ever had the pleasure of working with, if KDE/Gnome provides me with something similiar I would consider doing development on the linux platform again.

    --
    -"I'm one of those Mac people that will break a bottle on the bar and hold it to your throat for bad-mouthing my system"
  95. Re:the answer is by Anonymous Coward · · Score: 0

    What is this "usability" you speak of? I've never heard of it in all my years of Linux GUI programming.

  96. Err... actually, you are wrong by Anonymous Coward · · Score: 0

    Apple started using TrueType fonts on their OS because Postcript fonts where never thought to look good on screen. That's where the hinting (and probably other features of TTF) come from. As I understand, and been told from friends in the graphic design market, TrueType fonts are, on the other hand, worse for printed works.
    I agree thought that on Linux TTF fonts don't look as good (althought that might change with the release of freetype 2.1.4), but that has nothing to do with the font format.
    I would prefer the use of OpenType that promises the best of both worlds and more, but well, meybe in the future...

    1. Re:Err... actually, you are wrong by be-fan · · Score: 1

      Not quite. TTF fonts on Linux look identical to TTF fonts on any OS, if you've got the bytecode hinter enabled. *However* font hints are optimized for monochrome display (non-AA) and for low resolutions (70-100dpi). On high res screens or with good anti-aliasing/sub-pixel renderers, font hints actually make things look worse. This is why Apple pretty much ignores all of the TT hints and Microsoft's Cleartype ignores some of the TT hints. Cleartype in particular achieves good results by treating the TT hints as real "hints" (in the standard TrueType mechanism, they're not so much hints as explicit directions). In Postscript fonts, the hints have been high level "hints" and new autohinters (like those in the latest version of FreeType2) have been able to achieve very high quality results on a much wider range of display media.

      --
      A deep unwavering belief is a sure sign you're missing something...
  97. Re:KDE/Gnome have an opportunity to improve on App by Anonymous Coward · · Score: 0

    I have used the TweakUI focus-follows-mouse mode. The problem is that no Windows software expects the "window manager" to work like that, and as a result you get a lot of display glitches and other unexpected behaviour.

  98. What The World...Needs Now....Is Lub, Sweet Lub.. by Bowie+J.+Poag · · Score: 1



    Involving the entire community in every aspect of an HIG debate is a recipe for disaster. More on that in a moment.

    If you ask me, the community would be better served by a building a unified theme standard first. Any attempts at building a unified HIG will be meaningless until this is done first -- You cant institute change from the inside out. You have to work your way from the outside in. I mean, think about it --- Your apps will be pretty, but having inconsistancy outside of the app will defeat the whole purpose of having it in the first place.

    Neh, but what do I know. I tried to make this dog and cat live together in '98 and got burnt at the stake for suggesting that Gnome employ consistant design principles. ;)

    What will ultimately work will be a series of guidelines developed and issued by a small, protected group of people (NOT coders) working and debating in private, while ocassionally asking the community et al for their input. Taking all the little details and laying them bare for the public's parousal is a sure fire way to see that your ideas get completely enbalmed in red tape. Mark my words -- Design by a 10,000 person comittee will fail. Design by a 5 person comittee with dedication and honest intentions will succeed, and marvelously so.

    Cheers,

    --
    Bowie J. Poag

  99. Typeset by gonzotba · · Score: 1

    Subtile humour, I call it :) Anyways, it was changed long ago. Check the latest comic strips.

  100. flamebait? by Anonymous Coward · · Score: 0

    wtf? Sounds like somebody's taking things a bit too seriously around here...

  101. Re:What The World...Needs Now....Is Lub, Sweet Lub by Booie+Paog · · Score: 0

    no, you got burned at the stake because you presented an unproductive, insulting voice.

    red tape is a term used when ineffective people meet with resistance. that resistance is there to make sure dumb ideas don't get thru the weed-out process.

    design by a 10000 person committee ? what does the number of people have to do with it. maybe you mean to say that design by a large committee
    hasn't, in the past, agreed with YOU ? i think that's what you really mean when you say that, as you cross your arms and stamp on the floor, tears running down your cheeks.

    i'll help you (yet again) on this...if you don't listen to it...well, i tried.

    when you are a jackass to other people, insulting, condescending, and/or being not nice, then those people are most likely not going to want to work/talk/play with you. that's why they haven't thus far, in the past, for any extended period of time.

    when you find yourself alone with your desktop/development ideas, consider that this could be the case.

    and also, by claiming that you're NOT this big of a jerk in real life, that it's all a put-on...that's a cop-out, and irrelevant.

    i'm sorry if you:

    a- had a bad childhood
    b- lost your job
    c- someone broke up with you
    d- your mom/dad was mean when you were little
    e- have for whatever reason a chip on your shoulder

    but these are not valid excuses for being an immature jerk. you have posted someone's personal info (again, not mine) many times over.
    for what ?
    "punishment" for calling you a jerk ?
    boy you sure showed him, didn't you ? hope you're proud of yourself.

    how about trying to contribute something insightful to the discussion ? or would that be too hard ?

  102. Last Post! by alpg · · Score: 0

    "A fractal is by definition a set for which the Hausdorff Besicovitch
    dimension strictly exceeds the topological dimension."
    -- Mandelbrot, "The Fractal Geometry of Nature"

    - this post brought to you by the Automated Last Post Generator...