Slashdot Mirror


Red Hat Explains Stance on KDE/Gnome Desktop Changes

An anonymous reader writes "A lot of people are angry over the changes RedHat has done to KDE and Gnome in their latest beta, code-named Null. They have basically "nullified" all the default themes and settings with which each desktop attempts to posture for more users. Instead, there is now a beautiful unified look. To explain RedHat's stance, Owen Taylor writes this piece here. I hope that RedHat successfully forces both Gnome and KDE to become compatible with one another which would result in the creation of a single desktop. This would be the greatest gift to the Linux world."

200 of 520 comments (clear)

  1. Hmmm... by cuvavu · · Score: 2, Funny

    Begun the flame-war has!

  2. Why do we need "one unified" desktop? by ishpeck · · Score: 4, Informative

    I, for one, like the different options we have in terms of desktop environments. I don't want either KDE or GNOME to go away.

    I think the different desktop environments are important the way it's important to have variation in the gene pool.

    We can only attain perfection through variety.

    --

    "If I were to ask you a hypothetical question, what would you like it to be about?"

    1. Re:Why do we need "one unified" desktop? by kylus · · Score: 4, Insightful

      I, for one, like the different options we have in terms of desktop environments. I don't want either KDE or GNOME to go away. I think the different desktop environments are important the way it's important to have variation in the gene pool. We can only attain perfection through variety.

      You like the variety. I like the variety, likely most of the Linux users on /. here love the variety. But honestly Joe Windows, who's never touched Linux before in his life, will be scared to death of the variety and totally confused and terrified of trying to set things up or be left wondering which desktop is the 'right' one to use. I don't think Red Hat did this for the Linux veterans; I think it was done to advance Linux as a desktop solution and make it less daunting for new users to make a switch. The variety will always be there for the people that know how to find it and set it up, but this could be a good start towards introducing Linux to more people.

      --
      --Kylus
      Idiot-proof something, and Life will build a better Idiot.
    2. Re:Why do we need "one unified" desktop? by Ian+Wolf · · Score: 2

      Your options are unaffected. Neither one of them is going away. The desktop environments remain different. The article basically explains that all of the modifications are largely cosmetic and now the only difference between desktops will be things like speed and stability NOT themes, menus, and config options.

      --
      "The words of the prophets are written on the Slashdot walls."
    3. Re:Why do we need "one unified" desktop? by bobaferret · · Score: 5, Insightful

      I'm tired of variety! Some days, I come to work, and I just want the damn thing to work. I'd like the perfect background, and themes. All the menu options would be well thought out, and in the right spot etc. I realize that this will never happen, but I get really tired of having everything non-standard and haveing to recreate my desktop whenever a new version comes out. There is sooo much choise out there that it takes forever to become educated in enough different areas to trully be able to function most effectivly. Just let the community reach some sort of consensus on what is the best in an area an include in a distro. I used to follow hardware (workded for a white box computer store) every day. But it just got old. I just want the phreak'n thing to work,have a little eyecandy, and some best of breed apps so that I can get on with my job. Where I have 10 zillion other dicisions to make regarding HW/SW etc.

      -jj-

    4. Re:Why do we need "one unified" desktop? by N3WBI3 · · Score: 2, Funny

      The more time spent with Sorority girls the better.. you can make a video Sorority Girl PC's gone wiled

      --
    5. Re:Why do we need "one unified" desktop? by puppetluva · · Score: 3, Insightful

      I may be in the minority here, but. . . here goes.

      I don't want Joe Windows on Linux and I don't want Linux development coopted by the desire to make it "easy enough for someone's mom to use". I don't want to use the same computer my mother uses because we use them for very different things. She, like most people, want a glorified typewriter. She, like most people's mothers, calls people she knows (like me) to fix her computer or teach her to use various functions(I'm what makes the computer "easy to use").

      Maybe there should be a seperate "Glorified Typewriter" edition of Linux, so the rest of us don't have to be bothered.

      Here's what it needs: A web browser, open office, an off switch, bookmarks to calendaring and webmail.

    6. Re:Why do we need "one unified" desktop? by foobar104 · · Score: 2, Flamebait

      Oh, whatever. The "diversity is good" defense is often invoked to explain why there are fifty different window managers for Linux. It's a crock. Having both KDE and Gnome means that half the desktop developers out there are wasting their time. Rather than having one desktop that sucks hardly at all, we have two that each suck somewhat.

      "Perfection through variety" is only meaningful in the aggregate. That is to say, not at all.

    7. Re:Why do we need "one unified" desktop? by swillden · · Score: 3, Insightful

      Rather than having one desktop that sucks hardly at all, we have two that each suck somewhat.

      I don't say that you're wrong, but it's certainly not clear that you're right.

      Your statement assumes that (a) there are a fixed number of developers interested in working on Linux desktops, and they're split between KDE and GNOME; and (b) that there is no beneficial competition between the two groups.

      It appears to me that most GNOME developers are C programmers and that most KDE developers are C++ programmers. Yes other language bindings exist for both environments, but most of the work is done in those two. In my experience as a programmer working with other programmers, most of us have a pretty clear preference for one style of development. I, for example, prefer the ability to abstract myself further and further from the machine that C++ gives me (balanced against performance, of course). Others find all of the layers of abstraction confusing and distracting and prefer to work in the much simpler C environment.

      Given that programmers have a preferred style and environment, it seems clear that many would feel more comfortable working on one desktop or the other. Thus, I don't think it's likely at all that if, say, KDE disappeared, all the KDE developers would hop over to that grungy mess called GNOME, or vice versa, with appropriate disparaging adjectives.

      As for (b), well, that's hard to say. My only comment would be to point out that the world has discovered that competition is good for the consumer. It's not clear if the same benefit arises when the two projects are competing for the pleasure of having more users rather than the pleasure of having more users' dollars, but it certainly seems possible.

      --
      Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
    8. Re:Why do we need "one unified" desktop? by Eccles · · Score: 2, Insightful

      We can only attain perfection through variety. Indeed, I think each distro should rename all the various shell commands. cp could become copy, dup, xerox, canon (I think they outsell xerox copiers now), mimeograph, clone, etc. depending on your distro. Seriously, differences are useful for exploring what is the best of several alternatives, but often the differences are not useful, they just differ because making things identical would require a fair bit of work. It would be better to get things all using the same system, and then optimizing and extending that system.

      --
      Ooh, a sarcasm detector. Oh, that's a real useful invention.
    9. Re:Why do we need "one unified" desktop? by bockman · · Score: 2
      I like variety, too.

      But I also would like that, when I decide to switch from cool DextopX software to hyper-cool DesktopY software, DesktopY recognizes my old DesktopX settings (menu, background, MIME-types, icons ...).

      For that to happen, the various desktops should standardise on common infrastructures, at least for the shared functions.Done that, I don't care if each desktop has its own look-and-feel.

      FreeDesktop.Org is helping going this way, but it looks like it is a long way.

      --
      Ciao

      ----

      FB

    10. Re:Why do we need "one unified" desktop? by SJS · · Score: 3, Insightful
      Good example.

      Alas, this says more for just sticking with MicroSoft Windows interface.

      I went thru this last year with a demo of a software tool. The salesmen called me up and said he'd walk me thru the demo if I had the time; so I did.

      Problem # 1:
      Me: I click on the download link and nothing happens.
      Them: Shift-click.
      Me: Still nothing. Half-sec (alt-U) Ah! It's a javascript redirect. I don't do Javascript.
      Them: You can turn it on in I.E. by...
      Me: One, I'm not using IE; Two, I'm not going to enable Javascript just because your web developer feels a need to replace perfectly good hrefs with something that does exactly the same thing if you have scripting enabled, and nothing otherwise.
      Them: Um, lemme talk to a tech...

      A couple of days later the salesman emails me, and gives me a "direct" URL to the Solaris version of the software. I d/l it, read the README, follow the instructions, and install it.

      Problem #2:
      Them: Now, double-click on the installation icon.
      Me: One, there isn't any such thing, and two, it's installed.
      Them: There's no icon?
      Me: No, this is a Unix machine, and I'm not using a window manager that shows disk icons, and I refuse to use a file manager.
      Them: But it's installed?
      Me: Yes.
      Them: How?
      Me: I read the instructions in the README.
      Them: Oh.

      And then we tried to actually do the demonstration...

      Problem # 3:
      Them: So click on the "Start" button...
      Me: I don't have a start button.
      Them: Um, you don't?
      Me: Nope. You'll notice that I downloaded the Unix version. How about I just type in the name of the program from an xterm?
      Them: Um, will that work?
      Me: Apparently so, as it's now running.

      Now, one of the "features" of this product was that it was supposed to be able to find "dangerous coding habits" and syntax errors, and it came with a bunch of code to demonstrate these bad habits.

      Problem # 4:
      Me: Okay, example 3 compiles and runs. Now what?
      Them: Now bring up Notepad...
      Me: No notepad.
      Them: ...um, I mean wordpad...
      Me: No wordpad either. Remember, this is a UNIX machine.
      Them: You just go to the Start menu...
      Me: No start menu either.
      Them: Well, how are you going to edit (path)?
      Me: Thank you....I am now editing (path). What now?
      Them: Select (foo) and hit control-X, then type (bar).
      Me: You mean replace (foo) with (bar)?
      Them: Ummmm, yeah.
      Me: Done.
      Them: Good. Now go to the File menu and select "save."
      Me: No File menu. But it's saved.
      Them: Now click on (button).
      Me: Done. Nothing happens.
      Them: ...and you'll see a dialog that says, um, what did you say?
      Me: Nothing happens.
      Them: Try again.
      Me: Okay...done. Nothing happens.
      Them: Did anything show up in your system tray?
      Me: What's a system tray?

      It turns out that *any* source file that I touched with a Unix editor would kill their product. But that's beside the point -- a "consistent interface" means Microsoft Windows.

      --
      Pick One: http://www-rohan.sdsu.edu/~stremler/sigs/sigs.html (Note - disable Javascript first!)
    11. Re:Why do we need "one unified" desktop? by Metrol · · Score: 3, Interesting

      Maybe there should be a seperate "Glorified Typewriter" edition of Linux, so the rest of us don't have to be bothered.

      As I'm reading through the various posts on this topic I can't help but wonder why more folks such as yourself aren't using FreeBSD or perhaps Gentoo Linux. I've been using FreeBSD as my primary desktop OS for over a year now with KDE. No OS branding to be found anywhere. Every part of it is directly (aside from minor patches) from the KDE source. The same being true for Gnome if that's your preference.

      Having tried previous version of Suse, Mandrake, and a much older version of RedHat (6.1) I've come to the personal conclusion that I can't deal with all the OS branding. Upgrading apps is FAR harder, and updating the actual desktop environment seems to break all kinds of vendor specific configure tools. Well, unless you go and purchase a new CD.

      I'm presently upgrading a friend's laptop to KDE 3.0.3 also running on FreeBSD. No funky vendor specific apps to break, it's about as pure a version of KDE as you can get. It's compiling from source now, and I have no doubts that when it completes everything will be up and running as well as it was under 3.0.1.

      The upgrade process...

      Delete all of KDE
      pkg_delete -rf qt*

      Install it from source
      portinstall kde3

      And that's it! As I understand it, Gentoo has a very similar type of package management.

      The point is, there are plenty of solutions for those not wanting any vendor mucking around with their desktop experience. For the "blinking 12:00 on the VCR" crowd RedHat is trying to tweak things in for them. It's a different market, and one probably closer to where Microsoft's core market sits these days.

      --
      The line must be drawn here. This far. No further.
    12. Re:Why do we need "one unified" desktop? by nathanh · · Score: 2
      Having both KDE and Gnome means that half the desktop developers out there are wasting their time.

      NOBODY is wasting their time if they enjoy what they're doing.

    13. Re:Why do we need "one unified" desktop? by evbergen · · Score: 3, Interesting

      The problem is that some programmers tend to forget that to design is all about making choices. As that is a difficult activity, people tend to just 'make it a config option' and forget about the issue.

      But people, configurability is good, but *putting the burden of 90% of UI design on the shoulders of the poor user* is not.

      Indeed, because everybody effectively creates his own destkop environment because so little attention has been given to the *actual, practical, day-to-day, real-world* usability of the defaults, no effective feedback is provided to UI developers. The few advances in the field that are made are way too fragmented. This is a terrible waste.

      We should strive to be able to build a *good, beautiful* UI. Not to demo the latest alpha blending feature, if it's ugly and confusing as hell. We should lean from Fitt's law, from people like Jeff Raskin, from Windows and MacOS 9, from OS X and X Windows and from people's gripes about all of those.

      And, let's learn from Unix. We should build this UI using /Unix/ technology (that is pipes, sockets, processes, read, write, select, ioctl, mmap), and not with Corba, our COM-like thingy of the day or other funky fat binary interfaces, and not with multithreaded dlls that do not want to choose whether they are a process or a library. Let's not reinvent the OS in a very crappy and un-unixy way merely because we're building a GUI, for chrissakes. I really don't think the requirements of GUIs are so unique that that's needed. A module interface that allows each and every method in each and every every object to call each and every method in each and every other object in the system does not give any modularity, sorry. Think again. That's old-fashioned linking, worse, effectively going back to the days of single address space OSes by linking every application to every other, and that doesn't get you anywhere if you want to make standard, stable, secure component interfaces.

      You don't want to have 'more' to have a funky ad-hoc RPC interface so that it can be called by 'ls', or do you? We may need to extend the pipe concept if it's to limited for GUI app-to-app interfaces, but let's do that then, without resorting to plain, unrestricted RPC all the way. Please.

      Let's keep it simple, and let's make it beautiful.

      --
      All generalizations are false, including this one. (Mark Twain)
  3. Unified Desktop by Animgif · · Score: 5, Insightful

    I couldn't agree with RedHat's statement any more. I definately feel that a unified look and feel is something that Linux has always needed. People need to be able to look at a system and recognize it. You can always recognize Windows by the look of it, as it should be for Linux. Users need this to use Linux. If you want people to use Linux for their desktop they must first feel comfortable with it...

    --
    ------ This has been provided as a public service! ------
  4. How dare they ? by MosesJones · · Score: 5, Funny

    A standard desktop ? Then how will all the prima-donna point out how their desktop is so much better because of this or that bell and whistle.

    What a horrible idea, leveling the playing field and have a standard theme that concentrates on usability and then a pure battle of abilities to determine who underpins it. If there can be no differentation in terms of buttons and icons then how would people judge if not by "see-through windows" v "tear-off tabs" and other such pointless arguments and wars.

    Terrible concept, concetrate a team on a decent standard theme, and then have competition for the best engine behind it....

    Umm wait, isn't this in effect the same as the Video card market where standards have led to the engines (the cards) being bought and swapped purely on the grounds of ability, sure each has "special" instructions, but for 99% of applications no one cares.

    Oh and isn't it the same as the PC market, one instruction set, AMD v Intel.

    Oh I see, thats what they want, what a great idea now I understand.

    --
    An Eye for an Eye will make the whole world blind - Gandhi
    1. Re:How dare they ? by justsomebody · · Score: 2

      Maybe by concentrating more power into one solution. As much as I like variety I must admit that having one desktop would be better.

      I don't say any of desktop solutions should go away, they should collaborate by using same low level ingredients. (vfs, sound, applets, clipboard). I would like to select a theme in nautilus and have the same mime types in konqueror (or select in konqueror and have nautilus supporting y selection).

      By leveling the low level part of desktop there would be much wider options to write professional looking applications that would not depend on desktop you use. (example: burn a cd and watch your user set icons all across the software, no matter what desktop)

      --
      Signature Pro version 1.13.2-3 release 83.5 beta3try7 after-breakfast edition
  5. This is a Good Thing by restive · · Score: 4, Insightful

    This is a positive thing, for the reasons RedHat is stating; namely that many users don't want to make a decision between "this one" or "that one". How many times have people whined on /. that Linux will never make it to the desktop because there are too many tweaks things the users need to learn.

    This is RedHat's way of making Linux more appealing to the end user. Good for them.

    If you don't like it, do what I do and run Slackware (or other distro of choice), but bravo for the RedHat folks. This is a positive step.

    1. Re:This is a Good Thing by Mr_Silver · · Score: 5, Insightful
      This is RedHat's way of making Linux more appealing to the end user. Good for them

      Indeed, because if the desktop is more appealing then more people will use it and if more people use it then companies will start to consider it a viable market for software (applications and drivers) and when there is greater support for Linux then more people will move to it because it has the applications they want and so on and so on ...

      Microsoft are already doing Linux a favour with their licence changes, but that doesn't mean that we should expect people that are brave enough to change to come to the Linux side (at the moment, I'd say they're more likely to go to Apple, as they have consistency and ease of use down to a tee)

      --
      Avantslash - View Slashdot cleanly on your mobile phone.
    2. Re:This is a Good Thing by KjetilK · · Score: 3, Interesting
      I agree! Free software is about freedom, also for commercial vendors. They are free, just like J. Random Hacker to tweak it to suit their needs, and the needs of their customers.

      I'm a KDE user myself, and I think the KDE folks will also come to the conclusion that RH isn't doing anything nasty when they think more about it.

      However, I do not agree that Linux needs a Single Unified Desktop. On the contrary, the competition now is good. It allows more room to experiment, it allows for different developers to have different priorities.

      And it allows vendors to choose the best parts from each project to provide a unified desktop in their product. Or, leave the choice to their customers if customers want choice.

      --
      Employee of Inrupt, Project Release Manager and Community Manager for Solid
    3. Re:This is a Good Thing by Ian+Wolf · · Score: 2

      However, I do not agree that Linux needs a Single Unified Desktop. On the contrary, the competition now is good. It allows more room to experiment, it allows for different developers to have different priorities.

      I'm not certain if by this you mean Red Hat's move is creating a "Single Unified Desktop" in that it is changing the backend side of KDE and GNOME to be similar, so I'll respond as if that is what you mean. Instead of creating a "Single Unified Desktop" I would say that Red Hat is giving the appearance of a unified desktop. It's largely a semantic nitpick, but it would seem that a few people on /. today seem to think that Red Hat is rewriting KDE to behave like GNOME or vice versa.

      --
      "The words of the prophets are written on the Slashdot walls."
    4. Re:This is a Good Thing by krogoth · · Score: 2

      If they really want a standard, why not just say "KDE is our main desktop" (RH would probably chose GNOME of course)? If it's missing anything, they can always modify it (and hopefully contribute their changes to the project). Now, not only do Red Hat customers have two main desktops to chose from, their choice is almost entirely irrelevant! Please explain to me how this helps anyone.

      --

      They that quote Benjamin Franklin on liberty and safety deserve neither.
    5. Re:This is a Good Thing by under_score · · Score: 2

      FWIW, I don't use linux on my desktop for the following reason: KDE vs. Gnome.

      Also, FWIW, I'm perfectly capable in every respect of using linux effectively (I'm a software engineer, I run FreeBSD and linux servers, I use lots of Open software).

      So there's a real data point.

      I don't want to accidentally choose the wrong desktop/application API because I rely completely on my personal workstation. I spend 12 hours/day in front of a computer programming, using email, writing, budgeting etc., and I want as close to zero risk in terms of my app choices as possible. KDE vs. Gnome is still a very risky choice for me to make.

      I have recently moved off of MS Office since OpenOffice.org matured to 1.0. I recently moved away from JBuilder since Eclipse matured to 2.0. I am attempting to move away from other proprietary solutions. Unfortunately, my OS/Desktop is still Windows. That will change as soon as there is no choice left about a linux desktop _and_ the desktop is mature.

    6. Re:This is a Good Thing by fader · · Score: 2

      I don't want to accidentally choose the wrong desktop/application API

      You do realize that no matter which desktop you're running, apps from the other will run flawlessly, right? Or were you just trolling?

      --
      - fader
  6. Re:Insane by caluml · · Score: 2, Insightful

    If RH don't like this then why don't they just drop the one(s) they don't want people to use?

    Then we'd get the "Redhat is Microsoft" arguments, and people saying that they're reducing choice, stiffling competition, etc, etc.

    Why is MS or AOL powerful? Because they are simple, and have lots of users. We need to get more people using Linux.

  7. It's About Time by syntap · · Score: 4, Insightful

    I think Red Har has recognized that look and feel unification is a prerequisite to corporate entry. I understand the usual ./ user's opinion that desktop uniqueness is cool, but when you're a corporate help desk manager with a limited budget you don't need 2500 desktops looking different. It makes training more difficult too. The similarity of desktops is how MS can easily have people upgrade from Win98 to NT to 2000 to XP... the desktops are the same and retraining cost is minimal. Good for Red Hat!

    1. Re:It's About Time by Software · · Score: 2
      similarity of desktops is how MS can easily have people upgrade from Win98 to NT to 2000 to XP
      I agree with most of your post, but the part above is incorrect. XP, by default, has a very different desktop than the other Windows variants, though it can be configured to run with the "Classic" interface which is quite similar. The 2000 interface is also different than the NT / 9x interface, though not radically so. How does this apply to what RedHat has done? I'm not really sure. Perhaps the best way to put it is that Microsoft has evolved and improved the desktop, which is a good thing if you're hooked on their software. Let's hope RedHat and others do the same to KDE and Gnome.
    2. Re:It's About Time by spitzak · · Score: 2
      I got it, it's ok for MicroSoft to have 2 different interfaces because the IT department can force one.

      However, it is not ok for Linux to have 2 different interfaces, even though the IT department can force one.

      All makes sense to me. No wonder Linux sucks and Windows rules.

  8. Re:Insane by RobertNotBob · · Score: 3, Insightful
    Your choice is still there (unlike M$). Change whatever you want. If you are worried about this, then you probably know how to change it AND, you are not the kind of person who is going to write to their tech-support people with a UI question.

    If you have to support a product, standard look-and-feel is a good thing for you. If you allow advanced users to change whatever they want, good for us.

    Where is the problem?

    --
    ___ I don't respond to Anonymous Cowards, and I Never Mod them UP.
  9. Re:Insane by kylus · · Score: 5, Insightful

    So, basically their reaction to users having a choice is to try and negate that choice by making the options as similar as possible. How very MicroSoft!

    I think you're missing the point here. The idea is to unify a desktop solution so that people who are familiar with MS (read: most of the world) are not terrified of trying to configure a Linux box. I don't see this as MS-like. I see this as a step in advancing Linux as a desktop solution.

    The whole point of having KDE/GNOME/WindoMaker/Et al is to allow people to pick the one that suits them.

    Very true. If the experts who are used to Linux want it, they should still be available 'untouched' for them to install and configure. But let's face a fact here: RedHat is becoming the easiet of the distros to install and configure; making the setup and configuration less daunting for newcomers is a step in the right direction.

    If RH don't like this then why don't they just drop the one(s) they don't want people to use?

    Don't you think that this is more MS-like than trying to unify their desktop components? To just drop packages they don't like would be a true method of negating choice. THAT would be a step in the wrong direction.

    --
    --Kylus
    Idiot-proof something, and Life will build a better Idiot.
  10. Re:screens pls! by frenchtouch · · Score: 5, Informative

    You can find some right here: Red Hat 'Null' Beta screens.

  11. There is nothing stopping the user by bovinewasteproduct · · Score: 2

    There is NOTHING stopping the user from installing either one of these packages from source. Sure, you loose some of the laziness factor, but..

    Sure, if Red Hat said "Installing anything but our software voids your support", you might have a case. But in this case?? No...

    BWP

  12. Hopefully this won't be necessary soon by Telex4 · · Score: 5, Interesting
    What RedHat have done is really pretty insignificant. They've create a new artwork set that is applied by default to both KDE and GNOME so they look similar by default, and they've modified some codee here and there so they behave in a more similar fashion. In effect, they have made the first step towards making the two major desktop environments more compatable.

    Note: they have not taken away any user choices. You can still completely change your KDE/GNOME appearance, perhaps even back to the KDE/GNOME defaults. The only things that might bug users are the changes they've made to the code, but we don't yet know what they are, or how significant they are, so we'll have to wait and see.

    I for one would welcome it. I'd change my themes straight away, because I've spent far too much boredom-time making my KDE3 desktop look exactly how I want it. But I also had to spend quite a while getting GNOME and GTK+ apps to look right so they almost blend in with my KDE3 apps and desktop.

    The final goal here is of course compatability in themes. I.e. you download and install a KDE theme, and you can then make your GTK apps look identical, either with the same theme, or a mirror package. It's something even RMS has proposed, and something that will make life a lot more pleasant for those aesthetic pedants like myself, without taking away any of the choice we have in desktops and looks. Hopefully RedHat will find a constructive way of using these code modifications to help the KDE & GNOME projects achieve this "integration".

    1. Re:Hopefully this won't be necessary soon by Arandir · · Score: 2

      What RedHat have done is really pretty insignificant. They've create a new artwork set that is applied by default to both KDE and GNOME

      This is not what Redhat has done. If that's all it was then no one would be bitching about it. All they would need to do this would be menuconfig, some artwork, new KDE widget and kwin themes, and changes to various .desktop files. But that is not what Redhat has done. A unified desktop may be their goal, but they are attempting to achieve it by gnomifying KDE. And they are gnomifying KDE is distinctly uncourteous ways.

      Here's an example of Redhat's lack of courtesy: They disabled the KDE About Box. Now users cannot easily know what license an application is under, nor who the author is. Frankly, this borders on a GPL violation, but no matter, the discourtesy is by far the greater sin.

      Another example is Redhat's failure to submit changes to the code base to the code base authors. This is an egregious sin. It doesn't violate any licenses, but it is very rude. If a code change is an bug fix, then community citizenship says that you should submit the fix to the author. If it is not a bug fix, then you have in essence forked the code, and community citizenship says that you should alter the name of the package so that the user knows they aren't running the original version.

      Note that is wasn't until after the KDE developers complained that Redhat decided to make the bug dialog redirect bug reports to Redhat instead of KDE.

      Finally, in a brazen display of disrespect, they put their head GNOME guy in charge of "fixing" KDE.

      Okay, I can see you still don't get what the problem is. Let me offer you an analogy. LinuxMall wants a Unified Linux, instead of all these disparate distributions. That way they don't have to worry about customer confusion, and can offer a single meta-distribution. Step one is to remove the Redhat logos from Redhat. Step two is to make linuxconf look like YaST. Step four is to rewrite RPM without naming it or submitting the changes to Redhat. Oh, by the way, they hired Debian to be in charge of the retrofit.

      --
      A Government Is a Body of People, Usually Notably Ungoverned
    2. Re:Hopefully this won't be necessary soon by Ed+Avis · · Score: 3, Insightful

      Surely it's best to change the bug-reporter to send bugs to RedHat and not KDE, since RH are distributing a modified version. There would be many more complaints if the KDE team started getting deluged by bugs which were actually caused by RH's changes... better to have Red Hat, as the 'vendor', take the effort to work out which are problems with their distribution and which bugs in KDE.

      --
      -- Ed Avis ed@membled.com
    3. Re:Hopefully this won't be necessary soon by ivan256 · · Score: 3, Interesting

      Frankly, this borders on a GPL violation

      Bullshit. You're in violation or you're not. This is clearly NOT violation. About boxes are stupid anyway.

      Another example is Redhat's failure to submit changes to the code base to the code base authors. This is an egregious sin. It doesn't violate any licenses, but it is very rude.

      Bullshit again. I work commercially with lots of GPLed software every day. We make changes, and we don't submit the changes back... until we're done! When we have a beta product, and beta quality modifications we keep them internal. When we're sure the changes represent the quality we like, only then do the changes go back. Have patience. They haven't released the product yet.

      If they decide to fork, then that's fine too.

      in a brazen display of disrespect, they put their head GNOME guy in charge of "fixing" KDE

      Hmm, put their most experienced GUI guy in charge of packinging up and "redhatizing" a GUI. What a horrible decision. (Not)

      If you don't want people customizing and redistributing your software, then don't make it customizable or redistributable. If you don't want people changing your software to, say, look like gnome, then license it apropriately. Either you believe in free software or you don't. It's very simple.

      Let me offer you an analogy. LinuxMall wants a Unified Linux, instead of all these disparate distributions. That way they don't have to worry about customer confusion, and can offer a single meta-distribution. Step one is to remove the Redhat logos from Redhat. Step two is to make linuxconf look like YaST. Step four is to rewrite RPM without naming it or submitting the changes to Redhat. Oh, by the way, they hired Debian to be in charge of the retrofit.

      How many distros out there started by taking redhat and changing the logos? Mandrake, Turbo, LinuxPPC, YellowDog, Caldera... Plenty of others I'm sure. They may have deviated significantly now, but they all started in the same place. You don't hear redhat bitching.

      BTW, if you plan to accuse me of being a RedHat or Gnome fanboy, you may care to peruse my previous posts first. I use Debian, and I have other issues with redhat (like when they take GPLd software and change the title and copyright notice before releasing it, or when they ship documentation for said program with the new name even though the documentation isn't under an open license, all without giving any credit to the owner anywhere much less in an about box). I also think that "desktop environments" are a waste of cycles, memory, and pixels. They all suck.

    4. Re:Hopefully this won't be necessary soon by Arandir · · Score: 2

      Bullshit. You're in violation or you're not. This is clearly NOT violation. About boxes are stupid anyway.

      Clause 2c of the GPL might apply in this situation. I am not saying it does, because I am not a lawyer, but the way I read it, it's damn close.

      And about boxes are not stupid. They are a GUI application's primary means of informing the user of authorship, copyright and licensing terms. To deliberately block an application's call to display copyright and license information is extremely problematic.

      If they decide to fork, then that's fine too.

      Of course it is. But there are commonly accepted ways of creating a fork. But only if they don't dump the responsibility of supporting the fork back on the original developer. That was what Redhat was doing until KDE raised a stink about it.

      --
      A Government Is a Body of People, Usually Notably Ungoverned
    5. Re:Hopefully this won't be necessary soon by Telex4 · · Score: 2

      It strikes me that you would have the KDE Project produce proprietary software, to allow you the kind of control you want over it, if it didn't mean the death of the KDE Project.

      One of the points of Free Software is that it allows people to do exactly what RedHat have done. Changing the look and feel of KDE to make it more similar to GNOME is their right, until the various licenses KDE uses. You may not like it, but so what? There's no discourteousness here, just you and other KDE people wanting KDE to look exactly as you'd have it, everywhere. Blimey, go to kde-look and whine at everyone who has gone to great lengths to make their set-up look like GNOME, Windows, MacOS, Solaris, etc. I repeat: "Gnomifying" KDE is their right. Leave them to it, or change your licenses.

      The about dialogue boxes are, perhaps, a little silly. I can see it making things a little less confusing for the newbie, but then on the other hand I can't see them being that confusing in the first place. But if this is the main problem, lobby RedHat over it, and don't attack the whole idea.

      So they haven't submitted code changes yet. Maybe they're not ready to? Maybe they're still in betaor alpha stages! What's that? You say this whole project is part of a still-in-beta distro? Oh, well there you go then. I'm sure that they will return the modified code *when they are done*. They have to upon request, but RedHat have usually been good to the community, so I don't see why they won't now. As I said on my original post, let's hope they find a good way of doing this, to help both the KDE and GNOME projects.

      And please.... "they put john in charge of chess club when he's always preferred backgammon". You are so childish if you think it is disrespectful to put a GNOME guy in charge of making KDE more "gnomeish". If LinuxMall wanted to do that, then they can, and if they suceed, and beat the competition, then they've done a lot of good, both for themselves and the Free software community. I bet you didn't whine when Gentoo took FreeBSD's "portage" system, merged it with Debian's "apt", and extended them both to make their own portage system.

      And for the record, I use KDE, I dislike the look and feel of GNOME, and also the default look of KDE ;-) If I had theskill to screw around with the source to change certain things, I would too.

    6. Re:Hopefully this won't be necessary soon by ivan256 · · Score: 2

      From the GPL section 2c: "when started running for such interactive use"

      If they had a splash screen that displayed the authors and copyright, then they would be in violation. About boxes are not covered. The about box is certainly not the only way to determine the license, and it you care enough about what the license is, you would be able to find it. (I hope this doesn't make people start including splash screens, because unless the splash screen is there to inform the user that the program is taking time to load in the background, splash screens are evil.)

      They are a GUI application's primary means of informing the user of authorship

      Authorship is irrelevent, and like I said, the license and copyright are still available to those who are interested enough to look for them.

      That was what Redhat was doing until KDE raised a stink about it.

      If they made it impossible to find the original maintainer by removing the about box, then how were they pushing support back on said maintainer for the modified release? It seems to me like there were some people who were really digging for a reson to be upset with redhat about this without coming out and saying "we're pissed because gnome 5ux0r5, and you made us look like them."

      Is there any way that redhat could blur the lines between Gnome and KDE witout starting a flame war? If you ask me, they should hve just picked one of the two and not shipped the other one.

    7. Re:Hopefully this won't be necessary soon by Arandir · · Score: 2

      Authorship is irrelevent, and like I said, the license and copyright are still available to those who are interested enough to look for them.

      Authorship is very relevant to the author. Just ask any author.

      Without the about box, a user of a KDE application has only two means of determining authorship and licensing. Drop down to the command line with the --author and --license switches, or downloading the source just to look at the COPYING file. Both are somewhat viable options, but not even close to the convenience of the about box.

      But that all begs the question. Why even get rid of the about box to begin with? Does it violate some obscure UI design guideline? I can see no possible reason to disable the dialog. As the old saying goes, if about boxes offend you, you don't have to display them.

      If they made it impossible to find the original maintainer by removing the about box, then how were they pushing support back on said maintainer for the modified release?

      Because they didn't (originally) modify the bug report dialog. And aboutbox type information isn't in there anyway.

      Is there any way that redhat could blur the lines between Gnome and KDE witout starting a flame war?

      Yes. Create a common look and feel. On the KDE side this would have involved new widget and kwin themes, and changes to certain .desktop files and startup scripts. Removing the aboutbox would not have been necessary. Renaming crucial services would not have been necessary. And sending bug reports straight to KDE would have been hunky dory.

      --
      A Government Is a Body of People, Usually Notably Ungoverned
    8. Re:Hopefully this won't be necessary soon by Telex4 · · Score: 2
      Well for the record, a lot of people have moaned about the retheming of KDE in the style of GNOME, so for many that is a problem.

      And you didn't address the point that I, and many others, have risen which is that it is often custom to finish off code modifications before reintegrating them with the main codebase. In fact, in the article from which this thread began, the RedHat guy pointed out that they have created a new branch of the KDE cvs base fr the packages they are modifying.

      The about boxes are not silly, because they are the primary means for a KDE application to notify a user of their legal rights with regards to the software. What good is Free Software if the user doesn't know it's Free?

      Not exactly. There is still an "about" window for each application, and that still shows the license for that particular application. There is also still an "about KDE" about box somewhere that gives license information for KDE as a whole. So users will still know their legal rights with regards to the software.


      So to summarise:

      • RedHat are giving back source modifications
      • RedHat are doing this in the customary way
      • RedHat are giving credit to the KDE project in their documentation, and in KDE itself (though perhaps a little less than is default in KDE)
      • RedHat are still displaying licenses in software
      • you have presented no valid case against them other than you personally believe them to be discourteous
      The guy in charge is the guy who called KDE "crapland".

      And?

  13. Pictures of their desktop by Mr_Silver · · Score: 3, Interesting
    You can find pictures here

    I have to say, it does look very nice and I (being in the "lets have one desktop and do it right for the sake of consistency and adoption" camp) will definately be installing it when it is released.

    --
    Avantslash - View Slashdot cleanly on your mobile phone.
  14. Re:Insane by rppp01 · · Score: 5, Insightful

    -sigh-

    Look, RedHat is right on this one. Finally, after years of frustration, someone might just drag linux kicking and screaming into the desktop market.

    I swear, linux does not want to be mainstream. Sure, everyone talks about how they want their favorite OS to be taken seriously on the desktop, but no one wants to take the steps necessary to do it. I like choice, don't get me wrong. But most users do not give a shit about choice. They want AOL and MS Word. They want the start button. Fine, give them the start button, give them an MS Word clone. Let the world view linux with this perspective: a solid OS that 'just works' with a standard interface and standard applications that work as well as those on Windows. And for those who want to do more, we have other "versions" of the OS that allow other desktops, applications and such.

    To sit here and rip them for 'taking away choice' is just ignorant and, well, stupid. Please, people. I like WindowMaker, but I also know what we need to make linux work outside of the server room and the geek's bedroom. Don't forget, programs like 'switchdesk' exist for a reason. Those who want to use it, and those who can use it, are not prohibited from it.

    Bravo RedHat. Lead linux into battle for the server and desktop. Let everyone else follow. I need to get back to my kernel compile, now. :)

    --
    They stuck me in an institution, said it was the only solution, to...protect me from the enemy, myself
  15. Greatest gift to the linux world???? by Rahga · · Score: 2

    I started out making this a long and winded post, but instead, deleted it and will just say this:

    In my opinion, competing desktops will breed innovation and evolution. We need one unified desktop like I need a hole in the head. A few years ago, if all car makers joined forces to make one type of car, we'd all be driving a Yugo. If there was no Macintosh, we'd all be stuch with Windows 2.0 in the office.

    I loathe people who want to treat everything as if it were a zero sum game. :)

    1. Re:Greatest gift to the linux world???? by (void*) · · Score: 3, Insightful
      RedHat needs to sell to corporate customers, who want a uniformity of look. RedHat is exercising it's freedom, granted by the Free Software licenses to make a product it's cusomters want. If you don't want it, don't be a RedHat customer. Tweak your own desktop, or use some other distribution.


      If you look like Microsoft and Apple, they tie the user experience to the choice of OS. That Linux allows us to choose, is exactly what makes Free Software good. If you don't agree with RedHat, at least learn to respect that their decisions. They have been contributing code, and good software so far. At least LET them exercise their freedom to please their customers.

    2. Re:Greatest gift to the linux world???? by OS24Ever · · Score: 2

      No, we'd be stuck with the Macinotsh 128k with MacWord.

      Mac came first in your analogy.

      And we'd be driving Ford Pinto's

      --

      As a rock-in-roll Physicist once said, No matter where you go, there you are.

    3. Re:Greatest gift to the linux world???? by SerpentMage · · Score: 2

      Are the competing desktops competing or just copying each other? Innovation breeds from when somebody decides to do things differently. LINUS did that with LINUX in that he created an OS developed by the masses, with some new OS concepts. Ok not that many but a few. What is truly different between GNOME and KDE other than a few API's and themes? Not much. They are all clones of each other.

      --

      "You can't make a race horse of a pig"
      "No," said Samuel, "but you can make very fast pig"
    4. Re:Greatest gift to the linux world???? by Oculus+Habent · · Score: 3, Insightful

      The problem with your logic is that much of the innovation is a backlash against/breaking with the standard.

      Apple incorporated a number of additional features over time that were tweaks. The Menubar clock, the Apple-delete command, the Launcher, Spring-loaded folders, Internet Settings, Stickies, PPP support - All of these were available as add-ons before Apple incorporated them. They were made because people wanted something the standard didn't offer.

      Microsoft responded by adding many of these same features to their OS.

      On a side-bit, Apple did this mostly by purchasing the software from the makers, Microsoft wrote their own versions and prevented competitors from being used (e.g. The Windows XP Personal Firewall).

      Without a standard against which to work, innovation is much slower. The people at PARC with made the first GUI did so roughly (brute force rendering, etc) and apple took their standard and crafted something else. Microsoft followed in Suit. And Linux GUIs are based heavily on Windows (Call it what you want, it's a Start Button).

      --
      That what was all this school was for... to teach us how to solve our own problems. -- janeowit
  16. Does anybody realy care about two desktops? by Jondor · · Score: 2

    Those who don't care, don't care. Pick a default desktop and make it as good as possible. Newbies use what you give them until they get a reason to disagree.

    Those who care, do so for a reason and are not going to appreciate this unification stuff..

    --
    Nobody expects the spanish inquisition!
  17. Have your cake and eat it too? by d3xt3r · · Score: 5, Insightful
    Everyone from Gnome and KDE who are complaining about Red Hat's excellent decision to unify the desktops for end user experiece really just wants to have their cake and eat it too.

    The real reason everyone likes to have multiple desktop environments is for choice. The choice to develop applications with the toolkit of your choice. This is great because, as everyone loves to say around here, "this is what makes Linux great, choice and freedom."

    But as with all choices to diverge, rather than unify, someone suffers. Up unitl now that has been the end user -- the person all this software was written for in the first place, or is it? KDE and Gnome are great, but they offer two different window kits, two different looks and feels, and two different user experiences. This is bad for the end user. If I am KDE die hard and want to use a Gnome application, I can, the only problem is that it's going to look and feel like a Gnome app on my KDE desktop. And if I was a Gnome user the above situation would be reversed, you get the idea.

    The point here is that Red Hat has done a great service to the KDE and Gnome teams. They have taken two incompatible, entirely different desktops, and unified them for the benefit of the end user.

    Let's not forget that Linux is about freedom not only for the developer, but for the end user. Well written applications are designed with the user in mind. If the KDE and Gnome teams want to contribute to the Linux/*nix community in a truly free and open maner, they will see this move for what it is: a change to allow developers to continue to innovate in the way they see fit, using the right tools for the job at hand, all while improving user experience. That's what it's all about. Right?

  18. #the only look you need _ by DrSkwid · · Score: 3, Funny

    a few others

    $bash>
    ;
    c:\>

    nothing else necessary

    --
    There are places where the networks are not touching,and there are places where they are-Boeing's Lori Gunter
  19. Taylor presents his case well but issues remain by hillct · · Score: 2

    The arguments are presented in an articulare, well reasoned way. They are reasonably persuasive from a business perspective, both for Redhat and for promoters of Linux Desktop adoption, however I'd expect to see a rebutal from each of the KDE and Gnome projects vary soon; each of which will probably say the same thing, that they agree that their two projects should colaborate more to bring the look and feel into alignment, however it is not Redhat's place to undertake this.

    If Redhat is to take this on, then other distributions of Linux will suffer due to their newfound 'inconsistency', and while this may be a reasonable approach for Redhat, it is something to be avoided from the perspective of the Redhat and Gnome projects since their software is provided with virtually all Linux distributions so in order to gain the greatest market penetration they should be acting in support of all distributions. I'm certain these rebutals will be ariving soon and I look forward to reading them.

    --CTH

    --

    --Got Lists? | Top 95 Star Wars Line
  20. Re:Insane by Oculus+Habent · · Score: 3

    Exactly. RedHat isn't taking away your ability to choose. If you want something to be different, change it. In the meantime, All the people who need standards to survive int he computer world can enjoy a little more of Linux than they could before.

    Here's a bad computer-car analogy. If the Microsoft car has a steering wheel, and the Linux car has a numeric keypad (which undoubtably can do more), most people couldn't drive the Linux car.

    RedHat is trying to push the Desktop Linux by making different GUIs work the same. This is known as "standards."

    The real issue here is while there was a display manager that became the standard, these should have been something on interface design long ago.

    We live in a world of standards, and yet the one thing that needs the most standardization is the one thing people push to have the least.

    Free the GUI!

    --
    That what was all this school was for... to teach us how to solve our own problems. -- janeowit
  21. Choice and Red Hat by Kourino · · Score: 5, Insightful

    11 comments, and most of them are people grumbling about how Red Hat is squeezing choice out of the hands of the user. But really, is this true? What RH has done (from what I hear, I don't chase bleeding-edge distros, usually) is just change the way things look. They've provided a different default appearance. How is this worse from the default appearances provided by the GNOME and KDE teams? (RH's arguments for why it's better are in the article, you should read it :3 )

    It's not like Red Hat is releasing modified versions of GNOME and KDE that don't let you customize the appearance; then, only then, would the complaints about choice be founded. The people who really care about the difference between GNOME and KDE probably do so on reasons deeper than 'the default theme looks cool'. (Personally, I don't really like either of the default appearances that much ^^; ) So, when nagora asks "If RH doesn't like this, why don't they drop the one they don't want people to use?" the answer is: they don't care what you use, but they want the defaults to look reasonably similar, because they know that people who really don't *want* their default theme either know how to change it or probably have settings that they'll import anyway.

    Remember who Red Hat's intended market share is: the corporate environment. A lot of people I've talked to recently agree that RH's biggest 'ins' are (or should be) for office workstations. Lots of places implement a baseline standard that they want to look the same, but that people can customize if they want to (as long as they don't spend hours tweaking it). This is the mentality that RH seems to target. Yes, this isn't for everyone, but that's the point ... there are plenty of good distributions out there, and many more choices out there if you really really don't like it. But no-one said you have to use Red Hat. (Although I could understand concerns about RH-isms creeping into LSB, but nobody's brought that up.)

    Remember, RH == vendor for corporate enviroments. Corporate environments like standard desktops, so this move makes sense in Red Hat's perspective.

    1. Re:Choice and Red Hat by Epeeist · · Score: 3, Interesting

      > It's not like Red Hat is releasing modified versions of GNOME and KDE that don't let you customize the appearance;

      I can't speak for GNOME. However, they have modified the code for KDE. This seems to be the main reason that the KDE developers are upset. They are not sure whether they will be responding to bugs in the vanilla version, or the one that RH modified.

    2. Re:Choice and Red Hat by (void*) · · Score: 3, Insightful
      So basically, these guys have no idea about the implications of Open Source? That anyone can release modified versions of code, even if they don't like it?


      It's not like they are morally obliged to fix any and every problem with their code.

    3. Re:Choice and Red Hat by prockcore · · Score: 2

      "However, they have modified the code for KDE. This seems to be the main reason that the KDE developers are upset."

      Well KDE can either change to a proprietary license, or go to hell.. I really don't care which.

    4. Re:Choice and Red Hat by Arandir · · Score: 2

      Well KDE can either change to a proprietary license, or go to hell.

      The KDE developers aren't concerned that Redhat is modifying their source code. Instead they are concerned that Redhat is not exercising common courtesy when they do so. There is a big difference.

      The two primary concerns in my mind are Redhat's removal of the KDE About Box, and their forking of the code base without renaming it. The former means that no user can know who wrote an application or what license it is under unless they look at the source code. The latter means that bug reports from Redhat users are valueless.

      --
      A Government Is a Body of People, Usually Notably Ungoverned
    5. Re:Choice and Red Hat by dvdeug · · Score: 2

      The two primary concerns in my mind are [...] their forking of the code base without renaming it. [...] The latter means that bug reports from Redhat users are valueless.

      Since when hasn't this been true? Every distribution provides custom patches to software. Debian patches every printing program to use libpaper, even if the author would prefer to use LC_PAPER. And yes, this makes certain bug reports from Debian users worthless. That's why Debian tries to funnel all bugreports through its bug tracking system. Red Hat does the exact same thing; changing things to make it work better, and trying to handle bugreports locally.

      Should GCC complain because Apple and NetBSD and Debian all apply different patches to the compiler to get to work right for them? Should they tell Apple to break their driver ABI because GCC core doesn't want to include the ugly hack in CVS, or tell them they can't call it GCC because of that small patch? This is just part of free software.

    6. Re:Choice and Red Hat by Arandir · · Score: 2, Informative

      That's why Debian tries to funnel all bugreports through its bug tracking system.

      But with Redhat, they did not change the bug report dialog to forward bugs to Redhat until AFTER some KDE developers complained. It's okay to fork the code, just don't expect the original developer to support your changes.

      Should GCC complain because Apple and NetBSD and Debian all apply different patches to the compiler to get to work right for them?

      Debian and NetBSD send their patches on to to GCC developers. I suspect that Apple does as well, but if they don't then it's up to Apple to support their version. Redhat did NOT send their patches to KDE, but until KDE called them on it, expected KDE to support the Redhat version.

      --
      A Government Is a Body of People, Usually Notably Ungoverned
    7. Re:Choice and Red Hat by prockcore · · Score: 2

      "The two primary concerns in my mind are Redhat's removal of the KDE About Box, and their forking of the code base without renaming it. The former means that no user can know who wrote an application or what license it is under unless they look at the source code."

      That's not true at all, in fact it's FUD spread by the KDE devs. The "About KDE" box has been removed.. the About box hasn't. The About box lists the Authors and the License, the About KDE just pointed to a bunch of "hooray for KDE" crap, which was *exactly* the same in each app.

      The authors names and license are still in RedHat (null).

      As far as the "forking" is concerned, I hardly think that adding a theme, and removing About KDE (the only changes there are, mind you) qualifies as a "fork".

  22. Re:Insane by ip_vjl · · Score: 4, Insightful

    The whole point of having KDE/GNOME/WindoMaker/Et al is to allow people to pick the one that suits them.


    The whole point of having different linux distos is to allow people to pick the one that suits them.

    Don't like what RH is doing? Pick a different distro. Don't like what any of them are doing ... roll your own.

  23. Re:Unified Desktop by Anonymous Coward · · Score: 3, Insightful

    I can recognise Windows by the fact that it is bland and ugly. I can recognise a GNU/Linux or FreeBSD desktop no matter what window manager is being used; I'd used just about all of 'em. Let Red Hat do what it wants with its distro; if you don't like what they do, then switch to Gentoo or FreeBSD. Red Hat is not Burger King, and "Have it your way" isn't one of Red Hat's slogans. So if you want Linux made your way, make it yourself.

  24. This will drive many people insane... by kris · · Score: 5, Insightful

    The idea is: What looks the same behaves the same.

    Which is not the case with current Gnome and KDE. And probably never will be.

    I have different desktop themes and backgrounds at work and at home for a reason. My mind and my fingers automatically switch passwords and procedures, because without conscious effort I recognize the different environment and switch to different trained behaviour. Also, the few Gnome programs I am using look decidedly different than the KDE stuff I am using, and this helps a lot. Looking different, I do not expect the Gnome stuff to operate like the KDE grouping around it, and automatically treat it differently.

    Kristian

    1. Re:This will drive many people insane... by GauteL · · Score: 2

      I've heard this argument quite a lot of times, and I just have to ask:

      How do they behave differently?

      Lots of GTK+ apps behave differently, but they still share the same widget look. For instance Balsa and Evolution both work differently, but they share the same widget-look.
      What Red Hat has done is to unify the widget look for Qt and GTK+, so the most really relevant issues are how do Qt-widgets behave versus GTK+ widgets?

      I do not really know of any differences. Does the drop-downs behave different? Does the scrollbars behave really different? GUIs have become rather unified in behaviour over the year. If Qt and GTK+ widgets still behave differently, then they really need to be unified. Perhaps the unified look will be a big drive factor to make this happen?

      BTW. I know KDE and GNOME behaves differently, I'm talking at the widget level here.

  25. Two points missed-- by Speare · · Score: 5, Informative

    There are two points Owen didn't strike home with a sledgehammer, so I'll say them:

    First, those users who already know they PREFER the "old look" of KDE or GNOME can configure their new Red Hat Linux 8.0/Null++ to regain that old look. The Red Hat "Bluecurve" work is almost entirely artwork and menu organization, both of which can be re-themed or re-edited by any user who wants to. This change is to remove a bewildering either-or choice that paralyzes many newcomers.

    Second, Owen didn't mention that a huge area that BOTH desktops need to strive to improve is accessibility. It's vitally important for Linux to make inroads into the highly regulated Government sector. GNOME2 is laying groundwork for major gains in accessibility, thanks to partnering research by folks at Sun and other places. KDE needs to work hard on being accessible too. Features like Sticky Keys are just a start. Supporting limited-vision users and other areas is a must. Both desktops should do what they can, so that the best approaches can be adopted as standards.

    --
    [ .sig file not found ]
    1. Re:Two points missed-- by SubtleNuance · · Score: 2

      This change is to remove a bewildering either-or choice that paralyzes many newcomers

      this is a very excellent point, new users will arrive with a Gnome / KDE that look very similar... now, they might like some wm or other, or maybe GTK theme or somesuch that looks sexy, or simple or whatever TO THEM, but they arrive at all the (still existing) GNU/Linux Desktop GUI opportunities all the same..

      when new users are forced to make the choice that seems somewhat arbitrary (at that point (the beginner, newbie)) that it seems confusing.. more capable users will discover Bonobo and DCOP (and other real fundemental KDE/Gnome differences) in due time.. but why force the issue..? and why make a few icons an issue..? dont like something, well, they can change it.

      Further, think of some of the more cluefull (l)users you know with-regards-to their W2K or WXP systems... some of them will take what MS shipped, decide its ugly and change it, with themes, screenies, desktop-backgrounds (whatever) while others will use the standard look-feel.

      less cluefull users will encounter a desktop that is farmiliar -- and because they are LESS CAPABLE and DONT UNDERSTAND their 'puter all that much, this IS A GOOD THING - they will not be needlessly alarmed.
      While other users, who want to trick out their desktop will still do so...

      Another way to think of it is this: a new user chooses "KDE" as the default at installation; will they ever arrive at the Gnome opportunities if they lock themselves and their discovery into the KDE world and vice-versa? What RH is doing is making the 'starting' point as similar as possible - this actually expands the users options in future.

    2. Re:Two points missed-- by Speare · · Score: 4, Interesting

      Braille is useful to the few people who have learned it. I know some blind computer users who use braille.

      Braille is NOT useful to the huge numbers of people who have not learned it. This includes those with limited vision, those who have limited sense of touch also, and those who became sight-impaired late enough in life that learning Braille is not a viable option.

      I wrote a nice utility for Windows called Dragnifier. It's donate-ware. It is a taskbar applet that can be attached to any hotkey, and will show a magnifying glass that moves with the mouse. It magnifies whatever is below the lens as the user drags the mouse. Quick, convenient, natural to the user. Easier than a lot of other magnification options out there, from the letters I get. I wrote it because I like to see pixels when doing detailed artwork. I was flooded with positive response from the limited-sight communities. There's a lot of senior users out there who don't see very well.

      I'd love to make Dragnifier for X Windows and Gtk2. As I learn more of the X API, I'm sure I'll develop it.

      Audible monitors (text-to-speech) need to be integrated into the standard application toolkits in such a way as to have almost zero burden on application authors.

      Tactile and audible mice are still being developed and experiments show there are some cool things to be done with them.

      Lack of eyesight doesn't equate to lack of visualization. To limit the blind solely to Braille and Speech is to isolate them from the rest of the society which advances into new visualization methods every year. Think creatively about "visualizing" existing applications in new ways.

      --
      [ .sig file not found ]
    3. Re:Two points missed-- by Speare · · Score: 2

      Not really. Plug and Play is disruptive and undermines solid IT best practices in large pools of centrally-managed desktop boxes. The users shouldn't need to install new devices unless the user's specific task is to install new devices. Let the IT folks install devices in a consistent and managed way. Don't let the users screw up their desktop by adding their not-work-related devices without help or oversight by the IT folks.

      --
      [ .sig file not found ]
    4. Re:Two points missed-- by Speare · · Score: 2

      No, I agree that plug and play is and should be an important part of getting new users to adopt Linux at home. The kudzu facility is a start on that approach.

      But it won't breed adoption into governmental use, which was your claim. Government users and managers should follow IT best practices, or else they're wasting taxpayer dollars. Every time Senator Frobnitz' speechwriter adds an iPod to a Linux box, it (1) risks that the computer doesn't function because that combination is unproven, and (2) risks that various laws are being broken because that combination hasn't been authorized.

      --
      [ .sig file not found ]
    5. Re:Two points missed-- by Rick_T · · Score: 2

      > I wrote a nice utility for Windows called
      > Dragnifier. It's donate-ware. It is a taskbar
      > applet that can be attached to any hotkey, and
      > will show a magnifying glass that moves with the
      > mouse. It magnifies whatever is below the lens as
      > the user drags the mouse.

      Sounds a lot like xmag, actually. As far as I can tell from your description, the only difference is that you need to click on what you want xmag to magnify.

      A brief hack of xmag might do exactly what you want...

      --
      -- Rick
    6. Re:Two points missed-- by Suppafly · · Score: 2

      Sounds a lot like the magnifier that is built into windows as well..

    7. Re:Two points missed-- by Arandir · · Score: 2

      This change is to remove a bewildering either-or choice that paralyzes many newcomers.

      If this choice is bewildering, then perhaps those newcomers would be happier with Windows or OSX.

      I mean that seriously. First of all, it isn't an "either-or" choice, it's an "one, the other, or both, or neither" choice. Second, if Redhat wants to remove this "either-or" choice, then they had better start retheming Windowmaker, Blackbox as well. And dump Galeon in favor of Mozilla, or vice versa. And dump Star/OpenOffice in favor of Gnumeric/Abiword/etal, or vice versa.

      If a user is going to get confused by seeing a GNOME application running on top of a KDE desktop, then they will also get confused seeing GNU Emacs running on top of GNOME. Maybe Redhat should start retheming GNU Emacs, changing its keybindings, and reworking its menu.

      --
      A Government Is a Body of People, Usually Notably Ungoverned
  26. The reason for the bad feelings is... by 10Ghz · · Score: 2

    That Red Hat pours alot of money in to GNOME, while they give hardly any support to KDE (in fact, they seem to refer KDE as "Crapland" (according to the Red Hat bug-report where they talked about renaming apps and removing the "About" box)). And now they seem to be turning KDE in to GNOME-clone. It's understandable that KDE-developers and users are less than enthusiastic about it.

    FWIW: I'm a KDE-user but I support competition between the desktops. In fact, I'm going to give GNOME2 a shot in the near-future.

    --
    Lesbian Nazi Hookers Abducted by UFOs and Forced Into Weight Loss Programs - -all next week on Town Talk.
    1. Re:The reason for the bad feelings is... by Wdomburg · · Score: 2

      > That Red Hat pours alot of money in to GNOME,
      > while they give hardly any support to KDE (in
      > act, they seem to refer KDE as "Crapland"
      > (according to the Red Hat bug-report where they
      > talked about renaming apps and removing the
      > "About" box)).

      It was a leaked piece of internal mail, not a public bug report. A single employee expressing an opinion in a single piece of mail != Red Hat. How hard is that to understand?

      Matt

    2. Re:The reason for the bad feelings is... by Wdomburg · · Score: 2

      >It was my understanding that that single employee
      >was the guy Redhat chose to lead the KDE rework.
      >If that's the attitude by the guy in charge, I
      >don't expect much from Redhat's fork of KDE.

      Do you have an evidence to back this up? All of the references I've seen state "a developer" and nothing more. Well, putting aside conjecture and conspiricy theories.

      Matt

    3. Re:The reason for the bad feelings is... by Arandir · · Score: 2

      A LinuxAndMain article has some references.

      --
      A Government Is a Body of People, Usually Notably Ungoverned
    4. Re:The reason for the bad feelings is... by Wdomburg · · Score: 2

      > A LinuxAndMain article [linuxandmain.com] has
      > some references.

      The article states nothing beyond "said to have been written by a Red Hat employee".

      So, again, where's the indication that this was "the guy Redhat chose to lead the KDE rework"?

      Matt

  27. This makes it RedHat by ceswiedler · · Score: 2

    They're trying to make an OS called RedHat 8 which happens to be based on the Linux kernel and other free tools. I think it's a great decision on their part. It's very similar to what Apple did with OS X.

    No one has a reason to complain; despite anyone's accusations, RedHat is still an open-source operating system. I personally wouldn't have a problem if they stopped giving away the OS for free via FTP. There's certainly no requirement that they do so. They are a company which has a product which they are trying to make money from. If you feel that RedHat is simply making money from other people's work, by packaging together free applications: go get those applications on your own, and make your own distro (or choose a completely free, volunteer distro like Debian). RedHat does an enormous amount of work assembling and testing those applications, and customizing them into a unified OS. They deserve to be paid for that work.

    1. Re:This makes it RedHat by Junta · · Score: 2

      That is a ridiculous statement. They basically made iconsets and themes and some shortcuts different than the defaults. They did a few more feature enhancement patches than they have done in the past, but it is all trivial.

      OSX has at its core a BSD kernel and a development platform centered around gcc, but most of the system is proprietary and closed source.

      RedHat is still Linux with glibc, the GNU utilities, XFree86, and other stuff with slight modifications. The changes in RedHat 8 do nothing to hurt compatibility with other distributions. In fact, moving to the more acceptable gcc 3.2 helps cross-distribution situation. The system behaves essentially identical to everything else under the hood.

      OSX, on the other hand uses Quartz, for example. Completely closed, with a lot of features that are different from X. applications written for Quartz aren't really helpful for other non-OSX systems by any stretch of the imagination...

      --
      XML is like violence. If it doesn't solve the problem, use more.
  28. Re:Insane by Ian+Wolf · · Score: 3, Insightful

    Frankly this is a win - win situation. Red Hat now has a more well-rounded desktop with a more unified feel that they can sell to corporate customers. Furthermore, has anything really changed? Red Hat's KDE desktop was a piece of crap, and their Gnome wasn't much better. I've never met a Red Hat user who didn't tear out one or the other and replace it with either the latest build of their favorite desktop or something entirely different. Hell, the first thing I do when I install a new Red Hat box is install Ximian. You have the same choices you had before, today.

    --
    "The words of the prophets are written on the Slashdot walls."
  29. How about this option? by cluge · · Score: 2

    RH should include a default KDE and default Gnome desktop for those that want it (those of us that want it can handle the custimization). Call this an advanced set up feature for those that require it. I'm quite used to many of the KDE feature set personally, and use gnome apps in my desktop. If I cannot easily or reasonably setup a default KDE env, then I will go elsewhere for my distribution. I will also make that recomendation to others.

    Consider this RH, I've been using your product since before 4.2, I've been paying for it since 6.2 (I felt you deserved my bucks) If I can't easily install my favorite WM during the install process, you will loose this customer.

    cluge

    PS: Yes, you have managed to cripple some of the neater features of both desktops or at least hide them, and you have also turned out an ugly compromise.

    --
    "Science is about ego as much as it is about discovery and truth " - I said it, so sue me.
  30. Good and Bad by Epeeist · · Score: 2, Insightful

    A unified look and feel is fine, as is a common mechanism to change it regardless of the underlying desktop system.

    Where I think Red Hat have made mistakes (by incompetence, rather than malignly) is by modifying code rather than commissioning the GNOME and KDE teams to do it on their behalf. What they have generated are Red Hat GNOME and KDE desktops. In doing this they have antagonised developers and made both their own and the vanilla desktops more difficult to support.

    They have also made maintenance more difficult, KDE 3.1 is due out shortly. This means that all the changes the RH put in place will have to be repeated. If they had engaged the developers in the first place this would have been much less likely to happen.

    While there are mujahadin on both the KDE and GNOME desktops, the developers seem to have a relationship of friendly rivalry. By taking the lead on this RH could have facilitated better interworking between the two systems.

    1. Re:Good and Bad by jspaleta · · Score: 3, Insightful

      Where I think Red Hat have made mistakes (by incompetence, rather than malignly) is by modifying code rather than commissioning the GNOME and KDE teams to do it on their behalf. What they have generated are Red Hat GNOME and KDE desktops. In doing this they have antagonised developers and made both their own and the vanilla desktops more difficult to support.

      And what happens if the developers decide to ignore the code change requests Redhat wants? All Redhat can do in this case is make the changes and submit the patches....and wait for the developers to incorporate the changes if they so desire.

      The hacking of the Gnome and KDE codebases is no different than the hacking Redhat does to apply patches to the kernel tree for instance. How many kernel patches that get applied to commercial distro kernels? How long would Redhat have to wait to see a stock kernel with ALL the patches they apply to be bless by linus? Do the kernel developers get mad when Redhat patches a stock kernel on their own?

      For whatever reason whether it be long standing grudges or just the fact the Redhat has a different vision and motivation than the desktop developers...Redhat decided to make some patches. If Redhat submits those patches to the developers on the main branch..Redhat has done all you can really ask of them to do. We don't expect every person who comes up with a kernel patch to talk it over with Linus before they create the patch, do we?

      Sometimes the lines of communication break down and you have to do things yousekf to get what you want. Sometimes its a simple matter of manhours and the people you'd rather work on it don't have the time. Sometimes is a decision to make experimental changes that others disagree with....
      many reasons as to why patches for code get made.

      The underling issue here is about control, who has control of the codebase. The people complaining about the changes Redhat has made, and the politics of the situation around those changes, miss the whole point about the GPL. People don't have to play nice in OSS to innovate. What matters in the end is whether or not Redhat has created a better KDE with their changes. If they haven't..then they wasted some valuable manhours in development time...but if Redhat's changes catch on in the userbase then it doesn't matter how the changes were made now does it? If the original project want to pick up the patches they can...and it would be a shame to see any contributions that provide new features that users like stay out of the main project because of some politics...and in the end that situation only hurts the main project...and not Redhat becuase Redhat will be seen as the innovator.

      -jef

  31. Re:Insane by Ian+Wolf · · Score: 2

    Let me also add, that historically I am a GNOME user, but I regularly use KDE3 for:

    1) To learn it.
    2) Asteroids :)
    3) Because its there.

    There are great many things I like about both desktops and I will probably use both for the rest of my life. This move by Red Hat could make my life much easier.

    I know I'm not alone either.

    --
    "The words of the prophets are written on the Slashdot walls."
  32. Re:What is confusing by randomErr · · Score: 2

    Only one distro is reducing the # of choices, not the whole community. Beside DOS still has a ton of desktop's in production.

    Head over to FreeDOS.org and see for yourself.

    I love tweaking MS because we all know every product is still just a DOS shell, even NT. If you don't believe me, click Start then Run. Then type the word 'command' in the Open box and see what comes up.
    >C:\WINDOWS\

    --
    You say things that offend me and I can deal with it. Can you?
  33. Blue Screens by Oculus+Habent · · Score: 2

    Maybe it's my connection, but it seems that the screenshots were slashdotted.

    --
    That what was all this school was for... to teach us how to solve our own problems. -- janeowit
  34. Re:I don't like it by randomErr · · Score: 2

    Don't like it, don't use it.

    --
    You say things that offend me and I can deal with it. Can you?
  35. Story is bogus by 0x0d0a · · Score: 5, Informative

    The anonymous submitter wrote "RedHat successfully forces both GNOME and KDE to become compatible with one another which would result in the creation of a single desktop."

    Where did he manage to get this idea caught in his head? Merging the desktops? RH is just trying to make the two interoperate as best they can in their own release from a UI standpoint.

    If RH don't like this then why don't they just drop the one(s) they don't want people to use?

    You still *can* pick KDE/GNOME/whatever. RH chose a *theme* that makes them look alike. A *theme*! God, where did everyone lose sight of that? Ximian chooses a different theme than the GNOME default as well...are *they* evil, sadistic bastards too?

    I still can't figure out why this is news. It wasn't back when the story was first posted, and nobody cared except for about four people on the KDE forums (mostly the ever-vocal Mosfet).

    My guess is that publicizing this is a UnitedLinux initiative to make RH look bad, since I can't figure out a single other person who has anything else to gain by blowing this as out of proportion as it's gotten. Who *cares* about RH's default theme? Change your theme! Use WindowMaker if you want! This has no impact whatsoever on you!

    1. Re:Story is bogus by mccalli · · Score: 2
      The anonymous submitter wrote "RedHat successfully forces both GNOME and KDE to become compatible with one another which would result in the creation of a single desktop."

      He wrote no such thing.

      He wrote: "I hope RedHat successfully forces both GNOME and KDE to become compatible with one another which would result in the creation of a single desktop."

      Quoting out of context is often used an excuse, but that's not to say it doesn't actually happen.

      Cheers,
      Ian

    2. Re:Story is bogus by pjrc · · Score: 2
      In a nutshell, the "other side" of the issue is that unpaid developers deserve their work to be recognizable as theirs, and not to be superficially altered to appear as if it were written by other well-known developers.

      To quote a particularly one-sided phrase:

      Who *cares* about RH's default theme?

      I personally don't (as long as it's reasonably good), but I think it's pretty obvious that some people do care very deeply, and it isn't too hard to guess who they are.

      It's almost certainly advocates on one desktop... generally users who've made an emotional investment in the progress of their desktop of choice (eg, "my dad can beat up your dad")

      This group or people might also include real developers, who've worked long unpaid hours conjuring their code from raw ideas. Far above ordinary users, unpaid developers deserve some recognition for their work. It's grossly unfair (and against the license) to take a developers name off the product, whereever it reasonably appears. Many reasonable people feel it's also unfair to dramatically change the appearance of a developers work, particularly in a manner which makes it appear in a style commonly associated with other well-known developers.

      Redhat likens the issue to advertising on race cars, which is an effective analogy at belittling the developer's reasonable expectation that their unpaid work will be recognizable as their (as opposed to being superficially changed to appear as if it had been written by someone else).

      The core issue is between recognition for unpaid developers and ease of use for end users.

      This slashdot discussion is filled with comments from end users and non-developer open-source advocates, who apparantly can't see the other side of this issue. I hope some of those people see this comment or others like it, because the "other side" of this issue is important.

      I am a developer (mostly firmware, though I've contributed in small ways to some "normal" free software projects). I can speak from experience about some of these issues.

      It's easy to get burned out or disillusioned as a developer writing free software. A little rejection goes a long way. The thought process goes something like "well fine, if they don't appreciate my efforts, I'll go do something else". Most of the developers are unpaid, and while getting famous (even if only among the geek community) isn't a major goal... loosing some recognition you once had can be a major disappointment.

      All you linux advocates, please consider this trade-off. Sure, better ease-of-use and gui integration will help end users and the adoption of these desktops into the mainstream market......

      .... but at what cost? Some temporary flame wars among vocal users are no big deal, but if real developers become disillusioned, it could really hurt the long-term future. A lot of developers have poured a good part of their lives into this software. They deserve respect and recognition. Look and feel of their software is a part of that. How to balance integration for end users against developers legitimate expectation to be recognized for their work is a difficult question.

      I hope Redhat and other distros make wise decisions. I also hope other slashdot readers will see this comment amoung the flood of "end user intergration is the most important factor" and reconsider what effect this branding might have on developers. It's easy to forget (as many posts here have) that all this great software is written by real people, mostly unpaid, who have real emotions and likely will have opinions about their software being comsetically altered to appear like programs associated with different developers.

  36. Re:It's worse than I thought! by Ian+Wolf · · Score: 3, Insightful

    Um, actually that would exactly be the open source process. If you don't like it you change it to something you do and redistribute the code. That is exactly what its all about.

    --
    "The words of the prophets are written on the Slashdot walls."
  37. common sources for graphics and icons by iplayfast · · Score: 2

    I think that having comon sources for graphics and icons is a great idea. This seems to be the thrust of what Red Hat is doing. I don't know how often I've tried to find an Icon that is hidden inside of .directories for either kde or gnome.

    I'm even thinking of switching back to redhat ;)

    (currently a gentoo/mandrake dual boot user)

  38. FINALLY! I've Been Waiting For This For Years. by Bowie+J.+Poag · · Score: 2, Insightful



    As unremarkable as it appears on the surface, this may very well be the most significant milestone in Linux's history -- the first step towards a unified desktop appearance.

    Whether you like or not, the rest of the world doesn't want "freedom of choice" when it comes to their desktop appearance. They want freedom from choice. They want familliarity. They want sensibile designs. They want a look and feel that will still apply from one machine to the next. They do NOT want pointless bells and whistles like having sideways titlebars and 18 different ways to unminimize a window. They just want to sit down, do their work and move on.

    We are not the average user.

    All a user should ever need to be concerned with is just that -- getting the job done. In no way whatsoever should they even know about (or even CARE about) the fact that their apps may be provided by two completely different toolkits. Thats our concern, not theirs.

    A lack of continuity in the appearance of the Linux desktop has been one if not THE largest stumbling block in Linux' acceptance on the desktop. It all starts there. Say you're a company trying to offer Linux support for their products --- You cant show snapshots of a Linux desktop in the manual, because they all friggin look different! You cant even explain it in text, because "Go here and do this" can often mean two holly and distinctly different things, depending on if youre using KDE, or GNOME, or God knows what.

    Windows has a distinct face to it. So does the Mac. So does AIX. So did the Amiga. So did the Atari ST. So does even friggin Solaris! But Linux? No. The Linux desktop, up until now, is a schitzophrenic mess of different personalities dictates by the whims of individual users.

    You guys have no idea how important this evolutionary step was. And I, for one, cannot applaud RedHat enough for having the balls and the smarts to take it.

    Cheers,

    --
    Bowie J. Poag

    1. Re:FINALLY! I've Been Waiting For This For Years. by Arandir · · Score: 2

      Mechanically, changing wallpapers affects nothing, but, changing window layouts affects everything. Some things should remain unalterable. The basic layout and appearance of a window is one of those things.

      So why must Redhat be at the forefront of this UI revolution? After all, no other operating system enforces this, even for their own software. Look at Quicktime under OSX. Look at Windows Media Player under Windows. Heck, just look at MSOffice!

      I hear a lot of people claiming that users won't use Linux (BSD, Solaris, etc) until there is a single look and feel for every application. Yet these same users appear to be quite happy running Word alongside MediaPlayer or WinAmp alongside Quicktime or RealPlayer.

      But the best example is the internet. Every webpage has a different interface from the next. Yet last I heard the web was the hottest thing since Grandma started baking those special brownies...

      --
      A Government Is a Body of People, Usually Notably Ungoverned
  39. Re:I don't like it by __aahlyu4518 · · Score: 2

    but the whole reason Gnome was created was people didn't like KDE. KDE users use KDE cause they don't like Gnome.

    So you don't like redhat... so you run something else... problem solved. You gave the answer yourself !

  40. Re:screens pls! by Speare · · Score: 2

    More screenshots from my desk:

    I've done customization of terminal window settings and wallpapers, but the rest of the stuff you see is all Red Hat Linux (null) Bluecurve on GNOME2.

    --
    [ .sig file not found ]
  41. Mandrake too by InodoroPereyra · · Score: 2
    Texstar was nice to put some screenshots of the upcoming Mandrake Linux 9.0. Now take a look at the menus in GNOME and KDE. For instance, see the "mandrake10.jpg" and "mandrake02.jpg" Mandrake is also providing a similar menu structure for both desktops.

    And this is good . This is actually what a distribution is supposed to do . Put software together, configure, etc., save the user the hundreds of hours it would take her or him get the damn thing working and looking good. Make it easy to the user to get work done with the damn thing.

    Linux is getting better and better. Thank you KDE, thank you GNOME, thank you GNU, kernel folks, RedHat, Mandrake, Debian and so on ...

  42. Re:This is a Good Thing, but remember ... by egghat · · Score: 5, Interesting

    ... that Redhat was the major force behind Gnome, which came into existence *after* KDE (because qt wasn't completly free and open). They were the single most important distro to support Gnome instead of KDE, which has been chosen by almost all other distro makers as a default. Remember when Mandrake entered the market and basically was a Redhat with KDE? Mandrake's success told Redhat a big lesson.

    So it's kind of hmmm strange, that nowadays Redhat tries to nullify the difference between KDE and Gnome.

    But let me state it again: I think, we don't need two desktops. So every move to make those beast more similar is welcomed.

    Bye egghat.

    --
    -- "As a human being I claim the right to be widely inconsistent", John Peel
  43. Thanks. by digitect · · Score: 3, Insightful
    (A re-post of my gnomedesktop.org comments.)

    I appreciate Red Hat's concern that the community understand and approve what they are doing in this effort. However I think the community has been far too cynical in its reaction.

    Being a for-profit company I have long been surprised that Red Hat hasn't done this type of thing more often. There's no requirement that everyone be in agreement with one group's efforts--this is Open Source! Our montra is that if you don't like something, you are always free to do it your own way.

    These are the type of freedoms that take away your reasons to complain. Were we in any proprietary system, we would be at the mercy of the implementor. But as it stands here, our only limitation is time and money. These are precisely the same resources Red Hat is trying to steward just to stay in business. (Let alone, turn a profit!) So it appears we are all on the same footing.

    I wish individuals would stop complaining about someone else deciding to exercise their freedom. Life is hard, you can't always get what you want. Be happy that your rights aren't taken away. Sure we might not all like Red Hat's decisions in integrating GNOME and KDE. I'd be certain that not all on Red Hat's own desktop team are 100% happy about some of the individual decisions either.

    Just be thankful that Red Hat has even bothered to inform us of what they are doing. Obviously they are interesting in maintaining community support, but everyone should take note that this is our privilege, not our right. Certainly, Red Hat has a lot to gain by working with the community as opposed to against it or in some dark shroud of secrecy. But there is no requirement that they do this.

    In all, this is a great start on something both sides have long pondered. Frankly, both GNOME and KDE have been slow to make this type of move, although discussed much for a long while. Thank you Red Hat for once again taking the lead on a tough task, and thanks Owen for so kindly explaining how Red Hat is has decided to implement its business strategy.

    --
    There is no need to use a SlashDot sig for SEO...
  44. Squish the fruit slowpoke Ed boy. by Graymalkin · · Score: 4, Insightful

    That "Linux is about choice" argument is getting a little stale boys. Choice is having options available to you. The ability to use both KDE and GNOME apps on the same system is condusive to having choice. However if you're stuck with two incompatible systems how productive are you REALLY going to be when you use those systems to do more than tinker on them? Red Hat moving in this direction is forward thinking and in my opinion intelligent. Consistancy is important not just for novice computer users but experienced ones as well. Most experienced users of any type of computer commit certain actions to reflexive muscle memory, when two different programs act similarly that is one less set of motions to memorize or confuse when you're in a hurry.

    There's also the important fact that GNOME and KDE are open source. I can fork both projects right now and do what I want with them. Anyone can which is the nature of the GPL. Whining because someone took your code and extended it makes the concept of open source seem a bit retarded doesn't it. People want source code for everything and it all ought to be open and free but as soon as someone changes something all hell and whining breaks loose. Red hat could have tried to contribute their changes back into both respective code trees but why should they wait? Should everyone stick with inferior kernel VM systems until they are officially included in the release tree? Come on.

    --
    I'm a loner Dottie, a Rebel.
  45. Sounds like they're trying to give KDE a fair shot by WebMasterJoe · · Score: 5, Insightful

    I get the distinct impression that the Red Hat team is trying hard to not push their biases onto their users. It's fairly clear the Red Hat's developers are more adept with Gtk+/Gnome than Qt/KDE, and there's nothing wrong with that - if they were better at Qt, we'd still be having this discussion.

    When you realize you have a bias towards one group, you have two options - defend your bias and try to convince others, or work extra-hard to give the other team a fair chance. I think Red Hat is trying to give KDE a fair chance because the whole idea of Linux is to give users the right to choose.

    Maybe I was just sucked in to Red Hat's PR speech, but I really have to agree with their philosophy of providing a nearly identical UI on both WM's. It prevents novices from choosing one over the other just because of configuration differences such as single- vs. double-clicking icons. It annoys me to no end when a user tells me he/she didn't like product A because of a default setting that happened to be set differently in product B. In doing this, Red Hat may have made KDE "act like" Gnome, but I believe that it is inadvertant, just because the Red Hat team has gotten used to settings more typical to Gnome.

    Having said all that, though, think about this: If you know the difference, you can change it. If some guy who knows nothing about Linux doesn't know the difference, will he care?

    --
    I really hate signatures, but go to my website.
  46. The Real Power of Open Source by tarsi210 · · Score: 4, Insightful
    You people!

    The real power of Open Source is NOT:
    • A variety of applications
    • Multiple configurations
    • Configurable kernels
    • Source code available
    • Community of users
    The real power of Open Source is that, despite whatever the default configuration of a system might be, you can customize it any way you want!

    I really don't care if the standard Linux desktop starts to look and act like Windows in default configurations. In fact, I encourage it. It's the only way Linux will go corporate, companies will start making software for it, and support for things like hardware and drivers will finally become what they need to be.

    As long as it retains the ability to be as configurable and adjustable as it is right now, I'm a happy man. So what if your kernel comes configured generically for every piece of hardware in the world? If you have the know-how, configure it yourself. Recompile the software, the applications, the windowing system...write your own drivers, apps, utilities. Colorize your bash prompt. Interface with the toaster.

    Remember: With Linux there is Choice. Microsoft never even bothered to give you one. Keep that philosophy in mind and we'll be all good.
  47. Re:I'm with RedHat on this one by rosewood · · Score: 3, Informative

    I started using Ximian the day it came out, and I enjoyed it. Then, I realized it ate a lot of my menus that RedHat or I had installed and didnt play very nice in letting me re-add them. Sadly, Ximian really locks down the menus to just a few programs, which can be a real pain in the ass when you still know of only 1 way to do things.

  48. Re:Insane by Ian+Wolf · · Score: 2

    Have you seen what they've done? They just changed the default look of the desktop, which in my opinion still looks very much like KDE! Nothing has really changed, its still KDE and its still GNOME, the only difference is that Red Hat made their KDE default desktop look the same as their Gnome desktop, which in my opinion looks more like KDE than anything else.

    --
    "The words of the prophets are written on the Slashdot walls."
  49. Re:Insane by SerpentMage · · Score: 2

    Have you also forgotten the fact that in Germany computer users tend to be more rabid? And that people in Germany tend to do things for the principle, which may or may not be practical (BTW I should know I am German). Add that to the fact that many in Germany consider Microsoft as monopoly and you have a principle, which attracts users. Also do realize that 5% is about the same number of people who vote for the Greens, Communists and FDP (Liberals). And none of these parties are mainstream.

    I do not think it is a silly game. What is silly is to start an application from KDE in GNOME or Vice-Versa and have an entirely different look.

    --

    "You can't make a race horse of a pig"
    "No," said Samuel, "but you can make very fast pig"
  50. making it look the same means more les probs? by Vodak · · Score: 2, Insightful

    If Redhat needed to make the two desktops look and act alike because of support why not just start work on one official Redhat desktop environment? I mean simply making the two look similar is fine and dandy but there are still different probs between the two completely different desktops.

  51. Re:screens pls! by SerpentMage · · Score: 2

    OH MY GAD! A desktop that I can acutally use. A desktop where I do not have to be a LINUX guru to figure out how to change the font or keyboard settings.

    OK, I am being sarcastic, but I think the point is that LINUX looks COOOOOOLLLLLL!!!

    --

    "You can't make a race horse of a pig"
    "No," said Samuel, "but you can make very fast pig"
  52. Re:Insane by rosewood · · Score: 2

    I think Redhat should have done this a long time ago for now I don't see how MS could blow the desktop market unless our friend Pal is as bad as some people think it will be.

    Linux needed to be ready for prime time before the roll out of win2k to have gained real market share.

    Look at AMD. When Intel hit its lumps, AMD was ready to capitalize. When MS has hit their LUMPS and lumps and lumps, Linux has not been exactly poised to capitalize.

    This seems to be the step in the right direction, I just think that a simple check box on install could take care of anyone's questions about this.

    By default, the redhat theme, unles on install you say otherwise!

  53. Oh, the horror! by TrentC · · Score: 2

    Where I think Red Hat have made mistakes [...] is by modifying code rather than commissioning the GNOME and KDE teams to do it on their behalf.

    My God, you're right! How dare Red Hat take Free/open-source code and use it the way the licenses mean for it to be used?

    If KDE developers are going to whine about Red Hat modifying code that the KDE developers damn well gave them the right to modify, then they're definitely in the wrong business.

    Forking code is prefectly natural in the open-source world. There are a few forks of the Linux kernel (probably more in various in-house projects around the world), you have GNU emacs and XEmacs, etc., etc. Generally, this is a good thing, as new ideas get tested out without needing the "blessing" of the official code tree maintainer. (As I recall, the original USB support started off as a forked project without Linus' blessing, until something usable was available.)

    All Red Hat has done is forked the KDE and GNOME desktops to create a unified look for both of them. Yes, Red Hat will have to redo all of their changes when KDE 3.1 and GNOME 2.0.2 come out. That's their perogative, and I'm pretty sure they realized what they were doing when they made the decision.

    It boils down to three options:
    1) Learn to use Red Hat's desktop environment
    2) Replace Red Hat's with another; it probably wouldn't take long for some enterprising people to create a set of RPMs from the "official" KDE/GNOME releases
    3) Start using a different distribution; maybe rolling your own is the best answer if you want things exactly your way?

    Jay (=

  54. The only people that actually give a damn are ? by bushboy · · Score: 2

    So correct me if I'm wrong here - a small amount of people got all bitchy about this and they are more than likely in some way attached to either the Gnome or KDE projects ?

    Redhat are attempting to unify Linux and make it something your marketing department could use - anything wrong with that ?

    If you don't like it, don't use Redhat.

    Personally, I like what Redhat have done - it means I don't have to spend a ton of time fiddling around with all sorts of useless widgets and can get work done right away.

    Not all of us want animated buttons, x-term backgrounds, slide-out menus etc.

    --
    A slashdotting - you get the stick first and then the carrot !
  55. Re:Unified Desktop by rseuhs · · Score: 4, Insightful
    So essentially you say that we all should run one desktop dictated by a single distributor.

    No, this is not what we need. Just like we don't need a "unified" CPU-maker and a "unified" PC-vendor we don't need a "unified" Linux distribution.

    If we would need that, we would all run Macs now.

    DOS/Windows is so entrenched because:

    • People are used to it
    • OEMs have to take great risks by installing anything that is not Windows.
    • All the software is there

    RedHat having their great "unified" desktop won't make Photoshop run on it, it won't void the contracts OEM have with Microsoft and it won't make people forget about Windows.

    However, both KDE and GNOME are usable enough and similar enough so that a Widnows user will have no problem using it (especially if you choose the Windows-config on your first login in KDE.) so that is already solved.

    What we still need is:

    • a WINE that works reliably
    • OEMs preinstalling Linux

    I'm putting big hope in Codeweavers to produce a usable Wine that is easy to install and works with most office-software. - On all distributions, not only on RedHat.

    and not distributors playing monopoly-unification games and reducing inter-distribution interoperability.

  56. Re:Insane by rosewood · · Score: 2

    To blame Red Hat for the current US Linux Desktop share is totally illogical. There have to be more contributing factors, such as US BASED MICROSOFT on why the desktop share is where its at...

  57. It's more than look and feel by henben · · Score: 2, Interesting

    A unified "look and feel" is one thing (probably a good thing), but I hope they will address the deeper interoperability problems between KDE and Gnome apps, and config problems in both. In particular, I'd like cut and paste between apps to work 100% reliably. I'd like Quanta not to use an illegible font (A.D. Mono) just because it's alphabetically first and something has monged the config files. In fact, why do distros ship with illegible fonts in the first place? I'd like a single "Control Centre" rather than a KDE Control Centre, a GNOME Control Centre and a $DISTRO Control Center (which from the article is something they're trying to do). I could live without apps looking exactly the same way as long as they play together nicely.

  58. Your kidding right? by kanotspell · · Score: 2, Interesting

    "I hope that RedHat successfully forces both Gnome and KDE to become compatible with one another which would result in the creation of a single desktop. This would be the greatest gift to the Linux world." I fail to see how this is such a gift, the desktops are different but not *that* different, just enough to give some nice variety. Since when does the linux world want to limit choice. Perhaps all the distros should merge to one unified, down the middle, bland, not-specifically-good-at-anything version. Oh wait that already didn't work. Come on Hemos, choice and variety are what it's all about. I really hope that comment was just a troll.

  59. Re:Unified Desktop by Animgif · · Score: 5, Interesting

    No, I don't think that we should all use the same distro from the same distributor. What I do think is that if Linux is going to succeed in the consumer market, then there must be a noticable face for the consumer to identify with. This is what Windows has done. Most users couldn't tell you the difference in the versions of Windows, other than the newer on is prettier.

    In contrast to what you say above, I do think that a unified face will allow more software to be ported to Linux. As companies see that the market is maturing, they will be more likely to take the jump to a linux version because there is less risk to there bottom line. You have a chicken and egg fiasco, which will come first, products or customers? I definately feel that this more identifiable "version" of RedHat Linux will go far is helping the cause. Consumers will now be able to focus on making linux work for them, instead of making Linux work.

    --
    ------ This has been provided as a public service! ------
  60. Re:I don't like it by Oculus+Habent · · Score: 2

    I know this will make people scream.

    If the desktop environments were less concerned with getting the greatest share of users in Linux and more concerned with:

    A) Standards
    B) Interoperability

    the Linux GUI market would be a better place.

    What the hell happened to standards? Everything else has a damn standard, why not the interface?! I'm not saying the standard should outline The Interface, but it should make it easy for users to switch from one to another. Yes, there are different environments which different GUIs are better and worse for. But that doesn't mean that they can' be similar enough to not have a "transition period" for those who aren't familiar.

    Maybe we should be building a common interface with functional subsets that could be switched easily - same feeling but different format for various uses. Gaming, Graphics, Business, Children, etc. Of course, this would require a few things:

    1) People willing to work together and not just argue.
    2) Developers who are willing to sacrifice some control for better function.
    3) A Damn Miracle.

    --
    Well, I'm done.

    --
    That what was all this school was for... to teach us how to solve our own problems. -- janeowit
  61. "Desktop" is not what you think it is by ajs · · Score: 2

    If you look at what Red Hat has done, it's very clever, and really is aimed at adressing what you just said.

    What are the top things that "desktop" users the world-round will want to do?

    1. Web Browsing
    2. Document editing
    3. Email

    There are some other things such as calendars, contact management and spreadsheets that are hugely popular, but I think the above three items cover what 99% of the computer-using population does 90% of the time (if we're not counting games).

    Those three things (and the things that I've mentioned as "alsos") are all done using the same applications under Red Hat regardless of which desktop system you use.

    This has annoyed KDE folks because Red Hat chose the Gnome-friendly apps for this purpose, but to be fair, there wasn't really any choice. Evolution is far-and-away the best groupware suite for Linux/BSD. Mozilla too is hard to beat on anything but speed, and in terms of end-users speed loses to wider compatability with complex Web sites.

    Personally, I thank Red Hat for making this hard decision. It's time that the free software desktop world grew up and started to work together instead of trying to play "my feature is bigger than your feature".

  62. Good step for Redhat by The_DoubleU · · Score: 2

    I think this is a good idea from Redhat. If you don't like it change it. But by making a "standard" desktop Redhat can deliver much better support to new users. I'm working at a helpdesk. And you you can't tell peopel to start application X, you have to guide them step by step. Start, programms, application X. By making a standard desktop Redhat will improve their support for new users and these new users will keep using linux.

    --
    What power has law where only money rules.
  63. Re:screens pls! by Karn · · Score: 2, Insightful

    Excuse me, but what's with your blind hatred of Redhat? Is it because they have a positive income that you hate them now?

    If they wanted to get rid of KDE, they'd get rid of KDE.

    Idiot.

    --


    Why do I keep typing pythong?
  64. Re:Insane by rseuhs · · Score: 2
    I do not think it is a silly game. What is silly is to start an application from KDE in GNOME or Vice-Versa and have an entirely different look.

    I'm so sick of that nonsense.

    When you start ICQ in Windows, you have an entirely different look - whoowhoo!

    WMP in Windows - different look! OMG!

    Winamp in Windows - different again! THE HORROR!

    Quicktime in Windows - again different! THE CONFUSION! (and also in MacOS, BTW)

    Just start any game - all are differnt! ONLY A COMPUTER FREAK COULD USE THAT!

    If anything of your "everything has to be the same" were true, there would be nobody using ICQ or Winamp and only a tiny fraction of elite computer users would be able to play games.

    ... which quite obviously is not the case. On the contrary, specialized apps seem to do quite well compared to their "standardized" counterparts.

  65. Ready for aunt Tilllie by sl956 · · Score: 2

    I installed Null 7.3.94 beta three weeks ago. For the first time ever, I thought :
    Maybe the time has come for my old mum or my non-geek friends to switch to linux!
    The major reasons were :
    • flawless hardware detection and config (including the wheel of the mouse)
    • out-of-the-box anti-aliasing (it IS important for newcomers)
    • and above all the Gnome/KDE integration with a smooth clean unified theme
    Don't forget it's only a default setup. If you're enough of a geek to not like it (I am), you should be able to change it in less than 5 mn.

    On a side note, that version is not stable enough to be really usable yet (two X-windows crashes in the last three days). You should wait the real 7.4 to give it to aunt Tillie.
  66. Re:screens pls! by swordboy · · Score: 2

    *That* worked great. Thanks for posting that at the top of a slashdot thread.

    --

    Life is the leading cause of death in America.
  67. Blinders by Jobe_br · · Score: 2

    It stuns me to see how many naive and narrow-minded people post to slashdot. Ferkrisakes. Guess people don't truly understand what RedHat is ... a business. They're trying to increase their user base (the *paying* user base) - to do that, they listen to their *paying* customers and do some research into what would make other people switch to RedHat. Simultaneously, they'll try to cut their own costs so as to increase profit margins - something that shareholders typically enjoy.

    Does this mean that Linux enthusiasts can no longer customize their install of RedHat? No ... it simply means that GNOME and KDE will look like REDHAT out of the box, not like GNOME or KDE. Don't get the panties in a wad about it - its not that big a deal.

    I imagine that RedHat sees a good deal of competition from Apple at the moment ... Apple already has the desktop market (for those not afraid to switch from Windows) and is gunning for the server market - which RedHat has a pretty decent handle on, so far. With these changes, RedHat is gunning to win over some of the folks out there that just want to get some work done, and not have the interface stand in your way.

    Its a good thing, just think about it and please, for the love of Slashdot, stop bellyaching!

  68. Lack of Unification Killed My Linux Desktop by al3x · · Score: 5, Insightful

    I am (was?) a more die-hard Linux user than most on Slashdot. I still love Linux on the server. But the split between GNOME and KDE, and therein between GNOME 1.x and 2.x, prompted me to drop Linux as a desktop platform in favor of Mac OS X. Without focusing on the platform I switched to, let me explain.

    When actually trying to get work done, and not simply tinker around, having essentially three different widget sets and standards is a nightmare. I wasn't even using GNOME or KDE as a desktop; I used fluxbox. But some of my GNOME apps looked one way, the 2.x ones looked another, and the KDE apps yet another. Then comes trying to remember the keyboard shortcut conventions: do I shut this down with ctl-Q, ctl-x, alt-q, alt-x? On top of all this, there's the bloat of carrying around libraries for all three widget sets, and all their dependencies (and I still had a pretty stripped down install; I was running Gentoo).

    Day-to-day, this made for a truly unpleasant, unproductive, and frustrating desktop experience, without even getting into issues of stability. Many will toot the horn of diversity and choice, but in this the GNOME/KDE split is simply a massive hassle for new and experienced users alike. I'm the secretary for my college's Linux User Group, and explaining the differences between all the desktop environments confuses new users into a catatonic state, leaving them so confused they don't know where to go for what.

    I won't say that Linux can never succeed on the desktop. It just needs a shitload of work, and and the demolition of this KDE/GNOME barrier.

    1. Re:Lack of Unification Killed My Linux Desktop by PigleT · · Score: 2

      Why do you complain about applications you've chosen to install?

      The last thing I'd want is some silly argument "oh dear, the GUI sucks, therefore linux sucks" - because putting all your eggs in one visual basket is just what M$loth and Apple have done, and now they feel they have to protect "the Aqua look", and suchlike stuff.
      Bunch of crap. Variety wins, every time, and if you don't like how the application works, don't install it!
      Gnome has its look, KDE has its look and feel. If you only want one thing, only install one.

      "I won't say that Linux can never succeed on the desktop. It just needs a shitload of work,"

      No, it needs the luser-base to either wisen-up and learn to use something for what it's worth *before* complaining, or to piss off and use Windoze where they belong.

      I've been running GNU/Linux on my desktop for the last 4.bit years, I don't need someone telling me I'm doing the impossible - they should get to grips with emacs with Gnus, vim, vi on a bunch of other OSs, galeon, Konqueror, multi-gnome-terminal, zsh, and a whole host of other toys I use interchangeably on an hourly basis, then refrain from criticizing my chosen way of working.

      --
      ~Tim
      --
      .|` Clouds cross the black moonlight,
      Rushing on down to the circle of the turn
    2. Re:Lack of Unification Killed My Linux Desktop by pjrc · · Score: 4, Insightful
      I am (was?) a more die-hard Linux user than most on Slashdot.

      Ok, die-hard linux user....

      But the split between GNOME and KDE, and therein between GNOME 1.x and 2.x, prompted me to drop Linux as a desktop platform

      Not!

      This inflamatory message (yes, mod me down, yadda, yadda) is let you know that your seld description is far from "die-hard linux user". Sorry, you're just not. It matters not that you're a secretary of your local LUG.

      Among the many things that come to mind associated with a "die-hard linux user" are:

      • Often installs "bleeding edge" unstable software, if only to know what's coming next and submit timely bug reports to developers
      • Recompiles software and/or kernels for optimum performance
      • Tends to be an developer on at least some project in at least some capacity, perhap minor tweaks or helps with writing or correcting documentation
      • Extensive use of command-line... primarily uses gui to manage multiple shells
      • Writes perl or shell scripts to automate most tasks
      • Values privacy and/or security (disables cross-site cookies, uses ad-blocking proxy, monitors unexpected outgoing traffic with firewall, etc)
      • Values philosophy of free/open-source software (perhaps in general, or perhaps strongly aligned with the GPL or BSD approach)

      Not all of these apply to all die-hard linux users, but there is a general trend here.

      Above all that, anyone who could reasonably be considered a "die-hard linux user" appreciates that the linux desktops and particularly their applications are still in their formative stages. Whereas a consumer-oriented individual looks upon bugs and deficiencies and decides to switch to a mature and polished commercial project, the "die-hard linux user" appreciates the tremendous project and even in the absence of activly contributing (even in small ways like timely bug reports on the unstable bleeding edge), at least feels a sense of "being there" as it happens.

      So the point of this little rant, is that "Lack of Unification" didn't kill your linux desktop. You killed your linux desktop when you deleted it. That's your choice to make... my only gripe involves you calling yourself a "die-hard linux user". It didn't all look the same, nice and pretty, and parts of it didn't work similarly to other parts, so you dropped it and went to the highly polished, but commercial closed-source MacOS-X desktop. How "die-hard" is that??

    3. Re:Lack of Unification Killed My Linux Desktop by PigleT · · Score: 2

      "There's no good reason to require you to have windows looking at acting in four different ways on the same desktop!"

      There is no requirement to have 4 different windowing systems in place at once.

      "Redhat was trying to fix that."

      No, they were pandering to the likes of you folks who install "workstation" setup and then wonder what you're doing with it. There's nothing that needs fixing at all other than a bunch of windoze-heads with no clue what they're talking about.

      --
      ~Tim
      --
      .|` Clouds cross the black moonlight,
      Rushing on down to the circle of the turn
  69. Choice by Capt.+Beyond · · Score: 2, Insightful

    Choice is why I moved to using linux. Choice is why I never install gnome desktop. Choice is why I can use KDE, or Window Maker, or Fluxbox whenever I feel the need.

    You can merge Gnome and KDE into one desktop over my dead liquid cooled boxes pump!

    --
    -- "Perceptions create reality. By changing your perceptions you change your reality."
  70. Re:I'm with RedHat on this one by N3WBI3 · · Score: 3, Interesting
    This configuration is a great idea, I see a great deal of pissing and moaning about the fact Redhat has applied their own theme to KDE/Gnome, get over it its a theme.

    If you dont like it change the theme yourself, or dont install it with the distro go out get the source and compile it yourself.

    I love linux on the desktop (I use fvwm), but when I tried to set it up for a friend she went nuts becuase it was too much of a change for her. Linux has come far enough that there is no excuse for this, I spent about a day and a half tweeking it (Gnome) for her and now she loves it.

    --
  71. Re:Unified Desktop by 4of12 · · Score: 3, Insightful

    I couldn't agree with RedHat's statement any more. I definately feel that a unified look and feel is something that Linux has always needed.

    Yes, I think so, too.

    For far too long I've watched two extremely talented and desktop teams produce excellent software and haven't seen as much cooperation and collaboration as I would like. Being open source projects, both teams have the advantage of being able to more easily "steal" good ideas from the other team. I think that's great.

    I'm really glad not only that Red Hat, whose market size in Linux matters, is taking the initiative to draw the two desktops closer together, but also that the two desktops are open source and that Red Hat even has the ability to do this kind of unification.

    That is, while they don't perhaps realize or care much about it, I, for one, am happy that both Gnome and KDE are unifiable.

    That's a great thing.

    I wouldn't even care to speculate how much needless user pain there has been between proprietary desktops (win32 and Mac) that absolutely positively would never be merged simply because they're closed source and used as marketing weapons.

    --
    "Provided by the management for your protection."
  72. Convergence blocks innovation by Tune · · Score: 2

    > I hope that RedHat successfully forces both Gnome and KDE to become compatible with one another which would result in the creation of a single desktop. This would be the greatest gift to the Linux world.

    Would it? I agree that technically speaking it would be great to have a single API and a single (though configurable) UI combining the best of both worlds. But notice that this is only tempting because GUI developments (on a conceptual level) have been tame an converging for the last couple of years. Wrt. the Gnome, KDE, Windows 98 & XP looks and feels there have been some small changes here and there but hardly any innovative stuff. Many core developers in gnome, kde and M$ team would (or should) admit they have fairly modest ambitions in UI design - merely copying the neat stuff they see others do.

    Now would not "the Linux world" REALLY benefit from more dary designs? I would happily trade some compatibility to gain the divergence necessary to see some more innovative and radically new designs.

    Slick example: OS X.
    Geek example: XCruise-file browser.
    More generally: get some GUI professionals to do GUI design (sorry, no offence intended)

    --
    The most likely way for the world to be destroyed, most experts agree, is by accident. That's where we come in: we're computer professionals, we cause accidents -- Nathaniel Borenstein

  73. Why KDE people might not like this by ChrisWong · · Score: 4, Informative
    My speculation on why, from the perspective of KDE, this sort of thing is upsetting:

    • KDE credits removed from "about" boxes. The article admits that they do not (yet) have a policy to give KDE or Gnome due credit.
    • Code fork. The article mentions code modifications. This means it will be hard to get comparable updates when new versions of KDE appear. Given Red Hat's abysmal record with providing new KDE RPMs, users will be stuck with an obsolete version of KDE.
    • Gnome favoritism. The article admits that Red Hat does a better job with Gnome than KDE, yet will not let KDE be itself.
    • Application hiding. Menus dinkered to favor non-KDE apps.
    1. Re:Why KDE people might not like this by Rich · · Score: 4, Interesting

      The Gnome favourism isn't a problem, that's their decision. The main problem which you've missed is that have modified the names of the service types (so you'll find that if you download a 3rd party app as source it may well break). They've also changes the linker options used to load plugins which will caused weird crashes due to symbol name conflicts (eg. I doubt the Flash plugin works in Konqueror now because it has a name-clash with the OpenGL libraries). Needless to say we're less than happy about this, especially when Owen is claiming he want KDE and Gnome to compete on stability.

      Basically it is obvious that the RedHat guys have made these changes without actually understanding what they were doing. Personally, I will be dropping any bugs reported by RH users as I won't be able to test them properly.

      Rich.

    2. Re:Why KDE people might not like this by GauteL · · Score: 2

      The first two are reasonable. The other two are not. Red Hat is totally entitled to favor whatever desktop-system they want. SuSE and Mandrake favor KDE, Red Hat favor GNOME.

      When it comes to application hiding, Red Hat is totally entitled to offer what choices they think are best to the user. Red Hat thinks Mozilla and openoffice are better than Konqueror and Koffice, and can show the user whatever applications they want to. They could remove Konqueror and Koffice totally if they wanted to, but they haven't done that.

      The fact is that Red Hat has done just about the same things to GNOME as they have done to KDE. Galeon, Abiword and Gnumeric are secondary to Openoffice and Mozilla in Red Hat (null).

      The look and feel of KDE is not turned into GNOME, they have both gotten a new common look. The icons are actually much more KDE-like than GNOME-like.

      Why is it that only KDE-users have complained?

    3. Re:Why KDE people might not like this by fault0 · · Score: 2

      > Why is it that only KDE-users have complained?

      I'm sure some GNOME developers/users are less-than-enthusiastic as well. The major reason for mentioning number 3 is that KDE seems to pride itself with good integration, and has been historically more integrated as a desktop environment than something like GNOME.

      I don't agree with what RedHat has done, but I both understand why they've done it and defend their right to do it.

      The number one problem I see with much of the malinformed complaining by _some_ KDE users is that RedHat has it in for KDE. There is a significant portion of RedHat users who use KDE, and RedHat obviously doesn't want to piss them off. You are correct in saying that they did basically the same things to GNOME. I don't see why these complainers don't get this fact.

      More troubling, however, is probably RedHat's renaming of service types to remove the "kde-" part. Not only are some of these changes flat out unnecessary, but can break third party applications.

      Essentially, they are making it hard on themselves, because KDE 3.1 will come out soon, and you know KDE 3.2 is gonna come soon after that ;)

  74. Re:Unified Desktop by rseuhs · · Score: 5, Interesting
    No, I don't think that we should all use the same distro from the same distributor. What I do think is that if Linux is going to succeed in the consumer market, then there must be a noticable face for the consumer to identify with. This is what Windows has done. Most users couldn't tell you the difference in the versions of Windows, other than the newer on is prettier.

    Oh, not another one explaining the success of Microsoft. Face it: Microsoft is successful because IBM gave them the OS-monopoly in 1981. Everybody would have been successful with that, even Microsoft which never really did anything other than following the market. Microsoft has delayed the wide adoption of a GUI (every other major platform had a GUI long before 1990, but Windows 3.1 was the first usable GUI for DOS and came in 1993), they delayed the wide adoption of the Internet (In the early 90's Bill Gates himlelf said that "Internet will never be popular" and "The Internet? We are not interested in it") and PDAs (Go! invented the first PDA, Microsoft killed them with a lot of FUD and PenWindows which came out 2 years afterwards - which was dropped after Go! went bankrupt. Great, eh? PenWindows only use was to kill a company, advancing technology was not really important for MS)

    So please stop telling me Microsoft's great secret of success. In real life, Microsoft is one of the most chaotic and incompetent companies.

    Microsoft's only interest is maintaining the status-quo. The only reason we have Windows now is because everybody else already had a GUI for years and Microsoft had to follow.

    In all new markets like Webservers for example, Linux is doing great - better than Windows. In all old markets where people have tons of programs and documents to lose, Linux doing not so good.

    We need backwards-compatibility or WINE. Everything else is already there.

    In contrast to what you say above, I do think that a unified face will allow more software to be ported to Linux. As companies see that the market is maturing, they will be more likely to take the jump to a linux version because there is less risk to there bottom line. You have a chicken and egg fiasco, which will come first, products or customers?

    Customers.

    I definately feel that this more identifiable "version" of RedHat Linux will go far is helping the cause. Consumers will now be able to focus on making linux work for them, instead of making Linux work.

    Nonsense.

    Currently Joe installs Linux and either stays with it because he likes it better or drops it because doesn't run.

    How will that change? RedHat's GUI will be as new as stock-KDE for Joe (only uglier), so why should Joe be more likely to keep using it?

    RedHat won't enable Linux on the masses' desktops. Codeweavers will.

  75. Re:What is confusing by randomErr · · Score: 2

    Umm, no. NT is DOS based with a GUI on top. Most services still load in DOS. The only thing about NT is that command interpter forces the GUI to autmagically load.

    Check out ReactOS if you don't believe me.

    --
    You say things that offend me and I can deal with it. Can you?
  76. Getting "real" KDE by ChrisWong · · Score: 2

    For those who have been playing with the beta: what's involved in transforming KDE-rh back into "pure" KDE with all the defaults? The article mentions some code changes. The menus have been changed. Would I have to manually edit the menus, dialogs, links etc or is there a "gimme plain KDE" option?

    Chris

  77. Great Idea.. by Suppafly · · Score: 2

    I for one think this is a great idea. No one is forcing you to use redhat, and no one is keeping you from changing the look and feel of your desktop, but at least the initial install of a redhat distro will have a consistant look. Its good to see redhat making a move like this as they are one of the biggest linux distributors today. Mandrake has been doing similar things although instead of making kde and gnome look the same, they have just branded them both with mandrake logos.

  78. Exactly how is this a bad thing? by erat · · Score: 3, Insightful

    Reading some of the posts here you'd think that making a graphic desktop look a certain way cripples power users. Unless the Linux power user community has gone completely wuss, power users should still be able to do whatever they damn well please with whatever software they install on their systems.

    If you don't like what Red Hat's doing, swap out their desktop for the one you want. If you don't like the theme, put in another one. Or simply don't use Red Hat. It seems simple to me.

    All of this makes me think back to when Caldera decided to make KDE its default desktop environment to the point of removing pretty much all the WMs they used to ship. Lots of folks cried "You're dumbing down Linux! How dare you force people to use KDE!". How making KDE the default desktop affected peoples' ability to pull up an xterm, I haven't a clue.

    And to the KDE developers who pissed and moaned over Red Hat changing their precious code, try reading the license under which KDE is distributed. Last time I checked, people were allowed to alter GPL'd code in whatever way they wanted and re-distribute their version provided they made their patches available. I don't recall the GPL saying "you can change the code all you want as long as you don't change anything from the way we distributed it". You chose the license, sunshine. If you don't like what Red Hat did, cry me a river but don't expect me to sympathise with you. I'm not a huge fan of Red Hat (truth be told, I don't like their products at all), but what they're doing is something you and the GNOME folks have been allowed WAY too much time to take care of but did not. Both teams dropped the ball (or at least dragged your asses), so don't whine when someone else steps in and does the right thing. If you want it done your way, stop complaining and do it.

    'Nuff said.

  79. Competition Makes Good Products by Etriaph · · Score: 2
    We live in a capitalist society, where competition forces others to improve their standards while you move to improve yours in counterpoint. This is how you get two bodies being sure they don't let the public down by trying to out-do the other guy.

    The trouble with RedHat (in my opinion) doing this is that they're going to end up having a mismatched desktop that will not in any way be representative of either one. I'm perfectly happy using only KDE applications. I think the only GTK apps I use are GIMP and grip. So why, when I upgrade to RH8.0 will I have to have Mozilla as my default browser? What the hell good is that to me? I like Konqueror.

    To comment on what you said about "making a unified desktop for Linux", I would have to say I disagree in two ways. I'm pretty sure RedHat doesn't have brain control over Miguel de Icaza and Matthias Ettrich. If I were either of them I wouldn't let a distro dictate the OSS desktop, considering the other distros and unices these desktops run on.

    I'm also pretty sure that if the Linux desktop did unite the quality would likely drop off in some cases. It's good to think about that. Besides, I'm not really cognizant of GNOME very much. I really don't pay attention to the project or it's apps because I spend most of my time using Qt/KDE applications. RedHat won't be my distro of choice come RH8.0. I'd rather switch to Mandrake.

    --
    "It's here, but no one wants it." - The Sugar Speaker
  80. Re: Simply illustrates the flexibility..... by King_TJ · · Score: 2

    I see this as a complete non-issue. Both environments tout their flexibility in configuration, right? Well, here you have a vendor (RedHat) making full use of that. How often can a GUI perfectly emulate a competing GUI on any platform? Look at all the half-baked attempts to turn Windows GUI into a simulation of someone else's favorite user interface.

    If they managed to make Gnome and KDE work and look identical, I'd say that speaks volumes about the power of both GUIs to allow custom configuration.

    Surely, any Linux "power user" that is primarily concerned with not being "tied down" to a single vendor's idea of "optimal user-interface" is capable of re-configuring KDE or Gnome to suit their tastes?

  81. Re:Insane by moonbender · · Score: 2
    Also do realize that 5% is about the same number of people who vote for the Greens, Communists and FDP (Liberals).
    Eh? Greens and Liberals get 7 to 8% each and the so-called Communists get another 5%. 20% != 5%. Oh and your observations on the rabid German computer users who install Linux out of principle are a bit peculiar, too.
    --
    Switch back to Slashdot's D1 system.
  82. Re:OT Re:Have your cake and eat it too? by Suppafly · · Score: 2

    It's "eat your cake and have it too." Having it and then eating it is no trick at all.

    That may be logically correct, but the phrase that people use is "have your cake and eat it too"

  83. Re:Unified Desktop by kin_korn_karn · · Score: 2

    Personally I'm to the point now where I'm so sick of Microsoft hegemony that I don't care if RedHat engages in similar predatory practices as long as MS goes down. I'll support RedHat even if they were a monopoly, because at least the technology inside is good and it's not MS snake oil.

  84. Engrish posting? Re:RH is doing the same ... by Rick_T · · Score: 2

    > Because they have done the wrong decision
    > adopting GNOME in first palce. KDE is
    > better, so chose a really KDE
    > distibutiong

    What you say !!

    Take off every 'zig'
    You know what you doing
    Move 'zig'
    For great justice

    --
    -- Rick
  85. If Linux is to gain mainstream acceptance.... by Newer+Guy · · Score: 2

    If Linux is to be accepted by the mainstream user, it must be easy to use. Two completely different looking and acting desktops simply does not accomplish this. Look, I realize that many of you here think this is a bad thing. It isn't. You are looking at this through the tainted eyes of a geek, not John Q. Public's eyes. Right now, Linux is a difficult (almost impossible?) OS for J.Q.P. to use. It's too technical. Windows isn't, and J.Q.P barely can use it! Redhat is trying to make the OS more user friendly. This is a good thing.

    I guess what it comes down to is this: Do you want Linux to become mainstream or not? If so, then you support it's homogenization. If not, then you don't.

    Of course, there's nothing from keeping you from coding your own version of Linux too you know, and please make it as geeky and user-unfriendly as YOU want it to be.

  86. Geez...relax people. by zerofoo · · Score: 2

    How many of you actually keep the default settings on your windows boxes? Linux, and open source software in general, is very flexible. If you don't like the defaults, just change them.

    -ted

  87. Two different issues by ericman31 · · Score: 2

    There are really two separate issues here, RedHat is addressing one, and everybody is screaming about the other. The issue that RedHat is tackling is ease of use and standards. In order for Linux to succeed in the corporate world, it has to have a set of standards for everything, including the user interface. Especially for corporate desktops. Corporate sys admins really don't have the time or the inclination to custom configure the Linux UI and then roll it out to all the users. What they will want is a UI that follows a reasonable standard. They can then tune/tweak the few things necessary for their environment.

    The issue everyone is howling about is choice in computing. It's still there. If you prefer not to use a distro built for the masses, go get Slackware or one of the other distros that is aimed at the niche, do it yourself, user community. If you don't like RedHat's implementation of KDE or Gnome, but you like the distro otherwise, then install RedHat without KDE and Gnome. Then download them and build them yourself.

    But don't confuse standards with choice. If we don't have standards then Linux will fail ultimately as anything but an edge server and hobbyist desktop. RedHat is trying to create a standard without eliminating choice.

    --
    In my universe I'm perfectly normal, it's not my fault you don't live in my universe.
  88. Re:Insane by einhverfr · · Score: 2

    So, basically their reaction to users having a choice is to try and negate that choice by making the options as similar as possible. How very MicroSoft!

    So, as long as we learn the right lessons from Microsoft, what's the big deal? Just so long as we don't learn the wrong ones...

    The whole point of having KDE/GNOME/WindoMaker/Et al is to allow people to pick the one that suits them.

    Right, but most end-users don't want customization. Don't get me wrong, customization is still very important, but it needs, I think, to be done by the OEM, business, or Linux distributor so that their end-users' needs are met.

    If RH don't like this then why don't they just drop the one(s) they don't want people to use?

    I always install both desktops because I use applications from both environments, and that way I have more apps available to me.

    --

    LedgerSMB: Open source Accounting/ERP
  89. Fair enough by 0x0d0a · · Score: 2

    You're right...I should have put the ellipsis. However, there was no ill will on my part -- the quotes are the same from a point of view of what I'm trying to argue. The point is, here is the way I read it:

    "I hope Red Hat successfully forces both GNOME and KDE to become compatible with one another. This would result in the creation of a single desktop."

    There are a couple of problems.

    First is that the user is implying by the use of the word "successfully" that Red Hat is actually trying to "force" KDE/GNOME to do something. I don't see any grounds whatsoever for saying that, and that has a tendancy to piss off people that see RH as becoming too overwhelming in the Linux world.

    Second is the claim that compatibility between GNOME and KDE -- often longed for by developers from both parties -- would result in the "creation of a single desktop". This is bogus, and the only reason for putting this in is to inflame die-hard GNOME or KDE supporters. KDE and GNOME working together doesn't destroy their existence as separate desktops any more than C and Common Lisp being able to interchange data makes them a single language.

    Finally, this whole string of stories has been incredibly aimed at blowing up what Red Hat has done -- choosing a similar *default theme* -- into an attack on Choice, GNOME and/or KDE, WindowMaker, or whatever.

  90. Gnome is supported by the companies by mrm677 · · Score: 2

    Because developers can create proprietary applications without buying a QT license. GTK is LGPL.

    This really is important. My university is developing applications using GTK even though the students preferred QT. However finding $3000 per developer is not easy in a bureaucratically run institution.

  91. Convergence is a dead end by nagora · · Score: 3, Insightful
    This sort of thing leads (and is intended to lead) to convergence: all Linux apps/desktops/installs look and act the same. This is the logical end point of the "Aunt Tilly" movement because Aunt Tilly won't understand the concept of "distros". The ordinary user all you "standard desktop" fans keep going on about will come to equate Linux with the system they learnt on (prob RH). Then, in the quest to protect them from ever having to think again, you'll have to make all Linux desktops look and feel like the one most people learn on (ie RH).

    Eventually, as with Windows and MacOS today, overhauling the system will become next to impossible (Apple pulled it off but it was a last gasp effort, like the Mac itself, before the company flatlined). If new ideas in desktop design come along they will be ignored not because they are not good but because they are different.

    That is not a future I'm interested in for Linux and if the cost of avoiding that was that Linux never made it to the big-time on the desktop then that would be a sacrifice I'd be happy to make.

    But, it doesn't even have to mean that. All this crap about KDE/GNOME is missing the truth:

    THE DESKTOP DOES NOT MATTER

    As many people here have said, the ordinary user just wants to get work done. Think about what that means (better yet, go and look at real users working in their offices). The normal user does not use the desktop. They use the Start menu but even that is because they have to. If they really had what they need it would be a screen with maybe six big buttons on it marked "Word Processor","Spread Sheet", "Email", "Web","Print Queue", and one custom button for whatever other app they use in their work (Quick Books, Photoshop, Quark, whatever).

    These buttons would be for restarting the given app if it crashes; in normal use a window for each app would be started up on boot.

    Give them a handy way to switch between them and that's all 90% of Windows users would ever want or need.

    I know this because I've done it. WindowMaker can set this up very easily and it takes about 3 minutes to turn a Windows User into a Linux User like this, for the simple reason that the desktop is not what people use all day, every day. If you have the apps (and OpenOffice has gone a long way on this) they don't give a toss what the desktop is doing.

    KDE and GNOME are not things normal users need! Power users like systems like KDE/Gnome because they are useful for handling large numbers of apps and file locations. Normal office users don't have lots of apps and keep all their files in "My Documents".

    The only thing convergence does is ossify the system and make life harder for power users who want to be able pick and choose their environments to suit their, minority, needs.

    So: package KDE, Gnome, WindowMaker, ICEbox, and as many other desktops with your distro that you can fit onto the CD, make them all options during install, and make the default choice one the simplest with a handfull of icons already set up to start the "usual" apps and leave Linux to celebrate diversity while Windows fades away as new ideas and innovations pass it by because they are "too radical" for users.

    TWW

    --
    "Encyclopedia" is to "Wikipedia" what "Library" is to "Some people at a bus stop"
  92. Re:Unified Desktop by krogoth · · Score: 2

    That doesn't make any sense at all. All red hat did is make the two desktops look more similar - they didn't make X configure itself. How can consumers "focus on making linux work for them, instead of making Linux work." just because KDE and GNOME look similar?

    --

    They that quote Benjamin Franklin on liberty and safety deserve neither.
  93. Yes, I was Joe Windows once... by dnoyeb · · Score: 3, Interesting

    I still get tempted to use KDE because so many people said KDE was better and I consider myself computer savvy so I thought I should use KDE.

    But I couldn't find the RedHat RPM tools on KDE. I didnt see RedHat network. I used KDE but had to switchdesk to GNome to do any administration.

    Next, can we get rid of the 100 word processors and text editors?? Its confusing as hell to have so many damn tools that do the same thing. Is this an OS or a program war???

    1. Re:Yes, I was Joe Windows once... by Metrol · · Score: 2

      From my experience in the *nix world, everything done GUI-ily can be done..not...gui-ly

      That's what I was thinking, coming from FreeBSD, until I got a hard look at the back end of Suse's config files. This is not a slam on Suse!! They have darn good reasons for some of the complexity that goes into their configs as it relates to the quite popular Yast2 app. The thing is, that complexity becomes really clever to figure out when just looking at the end result of the fancier tools. Had similar problems with Mandrake as well. Not really experienced enough with RedHat to say.

      Thing is, where on a non-gui administered system you may have one file that configures a specific function, the gui based apps tend to utilize several files that are intertwined. I'm certain there are pros and cons to this approach that I'm not aware of, but it does make console admin'ing a bit more challenging. At least for me anyway.

      --
      The line must be drawn here. This far. No further.
    2. Re:Yes, I was Joe Windows once... by mabinogi · · Score: 3, Insightful

      Here's an experiment....

      go to tucows. www.tucows.com and search for HTML editors for Windows.

      Or ftp clients

      Or pretty much anything...

      Now ask the authors of these programs if we can get rid of the 100 text editors, ftp clients, irc clients, etc....

      It's not a war of any sort, it's called choice, and it exists even in the windows world.

      The difference is that since Linux and Unix Free and Open Source software allow redistribution, that Linux distributions are allowed to bundle anything they consider worthy with their distribution, and this usualy means at least a couple of versions each utility, so as to please the greatest number of people.

      --
      Advanced users are users too!
  94. Gtk2 Theme by ghazban · · Score: 2

    Where can I find this gtk2 theme so I can try it out. I'm sure redhat are open enough for it to be downloaded, however I can't figure out which rpm it is in without downloading them all... (I also wouldn't mind some of 'them nifty icons').

    Thanks

  95. Re:Unified Desktop by neowintermute · · Score: 2, Insightful

    I wouldn't count on that if I were you.

    Consider this:

    1. internet explorer in crossover office runs well enough to use all day. internet explorer in the public GPL tree crashes after about 15 seconds of use.

    2. quicken doesn't install with the public GPL tree of wine. quicken under crossover office runs well enough to use for a long time.

    I know these things because I've tested them myself. I'm comparing crossover office 1.2 to wine 20020804.

    if you're looking to codeweavers to provide the community with a reliable wine while still trying to make a profit, you're not going to be happy.

  96. Re:Unified Desktop by rseuhs · · Score: 4, Insightful
    No, I don't think that we should all use the same distro from the same distributor. What I do think is that if Linux is going to succeed in the consumer market, then there must be a noticable face for the consumer to identify with. This is what Windows has done. Most users couldn't tell you the difference in the versions of Windows, other than the newer on is prettier.

    And I say again, that's nonsense.

    BeOS had a nice desktop. Where is it? It's gone because it doesn't has any apps.

    Windows succeeded because it was backwards-compatible. The PC was plagued by IRQ and DMA conflicts and still took away marketshare from Macs and Amiga.

    Linux needs to become backwards-compatible to Windows and needs to run Win32 applications.

    That's what is holding it back.

    In all areas where the apps are available, Linux is doing fine

    Examples? Webservers - Windows gets marginalized there. Professional 3D-animation: Just after the tools were ported, many movie studios moved right to Linux. Embedded systems: Except for PDA's which are ruled by Palm and WinCE (and now guess why? RIGHT! Because of the APPS!!!) Linux has become the standard.

    Software will be ported to Linux when the users are there. C++ and Delphi apps will be ported to KDE and C-apps will be ported to GNOME. Period. All apps work on all desktops, no problem in sight. End of story.

    People want applications.

    Nobody will give a shit wether an application runs on Qt, GTK or Wine. It doesn't matter as long as the functionality is there.

  97. Re:Unified Desktop by rseuhs · · Score: 2
    Answer this:

    Why should a "unified" desktop better than some default desktop?

    Both are new to the user. HOW DOES THE NEWBIE BENEFIT?

    Just look at KDE 3.l and Keramik and tell me RedHat should not install that as a default.

    If you think that newbies should not choose, just install KDE and include GNOME on the CDs for those who really want it - or do a recommendation.

    Actually I don't really mind distributors optimizing things, but in this case it's not an optimization, it's a "kill all innovation" approach. RedHat didn't try to make their default desktop better, they tried to align their default desktop to another desktop.

    RedHat newbies will never see Keramik, they will never see new cool features.

    All they will see is a bastardized desktop that just won't feel right and will be behind both KDE and GNOME.

    And for you "standardize"-fans: Now we have 2 major desktops (KDE, GNOME), how is going from 2 desktops to 3 desktops (KDE, GNOME, Redhat) a step towards standardization? Imagine every distributor would do that?

  98. Re:Unified Desktop by rseuhs · · Score: 2, Troll
    I would have done what every commercial Linux distribution except RedHat does:

    Install KDE by default but include Gnome in the distribution for those who want it.

    What's wrong with that?

    The reason RedHat pushes Gnome is just politics and stubbornness.

    But it's OK, it's their distribution, so why not install Gnome by default and include KDE in the distribution?

    Would still be better than such a half-assed desktop mixture.

    PS: You can't "take the best of both and integrate them into a single desktop" because KDE is written in C++/Qt and Gnome in C/GTK. Those don't mix. If they would mix, such a merger would have happened a long time ago.

  99. What reduction in choice? by Chas · · Score: 2

    All they did was create a uniform theme for KDE and Gnome.

    So the default install looks, more or less, identical, for both desktops.

    How does this remove your ability to change the theme?

    (Hint: No)

    How does this remove your ability to go in and turn features back on?

    (Hint: No)

    All it means is that, immediately after install, everything has a uniform look.

    B
    O
    O
    H
    O
    O
    !

    Now get over it already.

    --


    Chas - The one, the only.
    THANK GOD!!!
  100. Re:Unified Desktop by [amorphis] · · Score: 2

    Personally I'm to the point now where I'm so sick of Microsoft hegemony that I don't care if RedHat engages in similar predatory practices as long as MS goes down. I'll support RedHat even if they were a monopoly, because at least the technology inside is good and it's not MS snake oil.

    Roll your statement back 20 years:

    Personally I'm to the point now where I'm so sick of IBM hegemony that I don't care if Microsoft engages in similar predatory practices as long as IBM goes down. I'll support Microsoft even if they were a monopoly, because at least the technology inside is good and it's not IBM snake oil.

  101. a beautiful unified look? by Joe+Tie. · · Score: 2

    While I do like people having an option to more easily get a unified look throughout the programs, beautiful is the last thing I'd call the theme. In fact I used screenshots of it as an example to an artist I know, to make sure she knew that just because kerimik looks nice, artistic sensibility and Linux developers have been slow to mesh.

    And now the disclaimer. Yes, in any kind of art there's going to be different interpretations. Most seem to like this look, I happen to be one who strongly dosn't.

    --
    Everything will be taken away from you.
  102. Re:Unified Desktop by kin_korn_karn · · Score: 2

    stop being so freaking idealistic. The real world can't handle diversity. It's a matter of the lesser of two evils, in every part of life - for president, for which corporation you work for, and for software. If you have to have a monopoly -- and we do now that computers are a commodity -- wouldn't you rather have one that had some substance underneath all the flash??

  103. Re:Unified Desktop by metacosm · · Score: 2

    WINE and Windows Compatibility are a way to win the battle and loose the war, it is a short-sighted "Fix it now" solution that will cause more harm that good. All it will do is ensure that developers never develop for linux.

    WINE is a nice way to play catch-up forever. Think about it from a a developer point of view. If I know that my app will be developed for the massive market that is windows -- and get the linux market for free (since they are playing catch-up and compatibility) what possible motivation would I have for creating a native linux product. I would have ZERO motivation.

    This is what killed OS/2 -- they had a windows compatibility mode that was so good -- no one developed for OS/2, what possible motivation would there be to? Program to windows -- sell on windows and OS/2.

    Beyond all that -- the unified desktop (QT+GTK) will enhance the user experience. Widgets should look and act the same, you shouldn't have to train your eye to a new widget set for each application you use. You shouldn't select an application because it fits "with your desktop" -- you should select it because it is the best application -- the article makes the point very clearly and I whole-heartedly agree.

  104. Moderate parent up! by ChrisWong · · Score: 2

    I wish somebody would moderate your post up. This is solid information that nobody else here on /. seems to know. Perhaps the KDE project would consider offering a set of RPMs for Red Hat, particularly for upcoming versions of KDE that users would like to upgrade to anyway. The KDE project should not have to live with stability problems introduced by Red Hat.

  105. Re:Unified Desktop by fwr · · Score: 2

    Well, as someone who IS using the RedHat beta I find the lack of difference in the look and feel of the two desktops confusing. That may seem like an oxymoron, but it's not. I'm used to having KDE and GNOME look and feel differently, and now it just about looks the same whether I choose KDE or GNOME from the login screen. That lack of difference is now confusing, making me feel like they took something away...

  106. Re:Unified Desktop by Chasuk · · Score: 2

    So please stop telling me Microsoft's great secret of success.

    Microsoft's success is inarguable. Their "secret" may be arguable, but that shouldn't be the issue here. At issue is a unified desktop - the noticable face for the consumer to identify with - that the previous respondent vetted.

    You write:

    The only reason we have Windows now is because everybody else already had a GUI for years and Microsoft had to follow.

    Whether this is true or not is largely irrelevant; the Microsoft GUI is the only GUI that 90% of of current (consumer-Joe-and-Jane-public) computer users have ever known.

    When the first respondent wrote:

    Most users [can't] tell you the difference in the versions of Windows, he was entirely accurate. I've worked tech support for years, and the vast majority of our customers have no idea which version of Windows they are using. They frequently tell me they are using Windows '97, being unable to distinguish between the OS and a suite of applications.

    The point of this? If Linux is ever to succeed on the Desktop, with über-geeks AND consumer-Joe-and-Jane-public, a unified desktop is essential.

    As Linux exists now, customer support for Joe-and-Jane-public would be a nightmare.

    Me: "Do you use KDE or Gnome, Ma'am?"

    Them: "Hmm?"

    You also write:

    RedHat won't enable Linux on the masses' desktops. Codeweavers will.

    Bullshit. Most users - the non-MS haters, non-zealots - will see no reason to switch to another OS in the first place, and being able to run the same apps won't sway them. They will respond, logically: "If I'm going to be using the same programs, why not be using the same OS?"

    I see Wine as a hindrance to Linux, not as a help. I also find it puzzling. To me, it is a bit like going to a Chinese restaurant and ordering a cheeseburger.

  107. Is the Red Hat artwork covered by the GPL? by Animats · · Score: 2
    Or is it proprietary?

    It's a big issue, because the Red Hat "look" is likely to become standard if it's any good at all.

    As a business move, a unified look makes a lot of sense. It should have happened years ago. Maybe if VA Linux had done it, they'd still be a viable company.

  108. The issue is APIs, not looks by IamTheRealMike · · Score: 2
    Well, having said that, looks are indeed an issue, but clearly something is being done about that (thanks RedHat!). The real problem however is that both desktops provide their own APIs to do essentially the same thing. That's OK.... when those APIs are compatible, though it does use up more memory than strictly necessary.

    But all too often these APIs aren't compatible. Theming APIs are one good example as they are related to the problem that people either bitch about or get used to (depending on how long they use Linux for ;) Both GTK and Qt have different ways of writing pluggable theming engines. What RedHat have done is create several themes that look the same. OK. Good start. What we really need to do though is have a standard for plugin theming engines, so I can use the GTK ThinIce theme in KDE and vice-versa. Then if I run a program in KDE, it adopts the theme I chose for KDE, and if I run it in GNOME, it adopts the theme I chose for gnome.

    That's only one simple example. Sound servers are another pet hate. When I run Konqueror inside of GNOME2, it won't play sounds. Why? Because Konqueror uses aRts, and GNOME uses eSound. In about 6 months gnome is switching to GStreamer, and KDE is looking interested too, which will hopefully provide a unified API for Linux multimedia. The work Havoc Pennington is doing at freedesktop.org is great too.

    We're getting there, but it's a lot of effort. Which brings me on to my final point. There's a reason there are so few unified APIs - it's very, very hard to create code that is easily used by anybody. You often have to manually create bindings to umpteen different languages, and even different "feels" to make all the different programmers happy. Then you have to campaign for adoption. It's a lot of work.

    What's needed is a decent object model. Something as easy as KParts, as powerful as CORBA and as ubiqitous as COM. Something that lets me write an object in any language (including C), and then "export" it to the OS, so that it can be used in any other app. This would not only increase code sharing (so reducing memory usage), but would also lay the groundwork for many more technologies to be standardised. I wish I had time to do this, but it's far from easy.

  109. Re:Unified Desktop by rseuhs · · Score: 2
    WINE and Windows Compatibility are a way to win the battle and loose the war, it is a short-sighted "Fix it now" solution that will cause more harm that good. All it will do is ensure that developers never develop for linux.

    Wrong, Wine makes developing for Linux easier and faster. IBM has shown that you can make good and stable Wine-based apps (hpbuilder).

    WINE is a nice way to play catch-up forever.

    Also wrong. All Win-soft is Win98-compatible which is a fixed target for 4 years now. - And will be around for quite some time, too.

    This is what killed OS/2 -- they had a windows compatibility mode that was so good -- no one developed for OS/2, what possible motivation would there be to? Program to windows -- sell on windows and OS/2.

    Yeah, I saw that coming. But it's complete nonsense. OS/2 was killed because it was from IBM.

    From an OEM point of view:

    OS/2 = IBM = computer-maker = competitor = not a good idea.
    Windows = Microsoft = software-company = no competitor = OK

    Add in that OS/2 was too expensive, had really shitty marketing and wasn't really pushed by IBM itself (they sold DOS/Windows PCs at all times!) - but even the best price, the best marketing and IBM only selling OS/2 PC wouldn't have made OS/2 successful. OEMs would have been stupid to adopt it.

    Wine is a great way to attract users. If Wine becomes so good that Wine-apps run on Linux just like on Windows - well what's the problem?

    But we both know that developing for Win32 is a pain. Wine is a way to attract users. Once Linux gets a significant marketshare on the desktop (over 10%) developers will happily make native Linux-versions. Just like developers stopped made Win32-apps when Win95 was released. Also a native app will have better KDE-integration (and that's where RedHat's initiative fails - where it counts it doesn't work, it just puts a skin over it) than a Wine-version. Of course Linux-users have to be relevant, which is currently not the case on the desktop.

    We have to get the users *FIRST*. Whining about no native apps available won't change a thing. If Wine is a way to get users (and it is, IMO) it is the way to go.

    And another thing: Linux has a strong development community which puts out many great Linux-only apps. Wine won't change that. - If Linux manages to become the OS with the most apps (Qt, GTK, Win32 AND Motif) it will become the most popular OS.

    Beyond all that -- the unified desktop (QT+GTK) will enhance the user experience. Widgets should look and act the same, you shouldn't have to train your eye to a new widget set for each application you use. You shouldn't select an application because it fits "with your desktop" -- you should select it because it is the best application -- the article makes the point very clearly and I whole-heartedly agree.

    Well, where it counts, RedHat's approach fails. (Does Gnome's Palm-software get synch my notes with knotes? I don't think so. Does Gnome's PIM software know about my KDE-adressbook? Does Gnome's Windowmanager restore KDE-windows on relogin? on the correct desktop? I don't think so. Will Gnome apps use KDE's really fine printmanager? I don't think so.) RedHat made it *look* like it's integrated, but in reality it isn't.

    *IF* you think we need a really unified desktop you will have to choose.

  110. Re:Unified Desktop by Ed+Avis · · Score: 3, Insightful

    There are good political reasons to choose GNOME. (I don't know why when people say 'politics' it is assumed to be a synonym for 'bad'.) Namely, proprietary software vendors can produce GNOME versions of their apps without any trouble; but you have to pay Troll Tech if you want to produce proprietary software for KDE.

    Free software zealots won't care one way or the other - indeed they might even prefer the GPL'd Qt rather than Lesser-GPL'd GNOME libraries - but businesses are perhaps more likely to choose GNOME if they decide which desktop to develop for.

    --
    -- Ed Avis ed@membled.com
  111. Re:Unified Desktop by abe+ferlman · · Score: 3, Insightful

    RedHat having their great "unified" desktop won't make Photoshop run on it,

    Think about that for a minute. Part of the reason that software vendors are loath to enter the linux desktop market is because there is so little standardization and they don't want to have to support 50 different ways of launching a program. Standardization makes it easier to guarantee that the software you'd like to distribute will work. The LSB is moving towards making that possible at the developer level, but having the biggest commercial distro standardize on a desktop will help to make the user interface less of a moving target.

    --
    microsoftword.mp3 - it doesn't care that they're not words...
  112. Re:Unified Desktop by rseuhs · · Score: 2
    The point of this? If Linux is ever to succeed on the Desktop, with über-geeks AND consumer-Joe-and-Jane-public, a unified desktop is essential.

    First you say it is a problem that users can't distinguish Windows-versions then you say it's essential to make KDE and GTK indistinguisable? That doesn't make any sense.

    Me: "Do you use KDE or Gnome, Ma'am?"

    Aha, and "Do you use KDE, Gnome, RedHat's desktop, SuSE's desktop or Mandrake's desktop, Ma'am" would be better?

    *IF* we really need a unified desktop we have to choose from KDE and Gnome. Period.

    If RedHat would install KDE by default, we would have that unified desktop RIGHT NOW, because they are the only ones still holding out with GNOME. (The default is what counts)

    Creating a bastardized mixture of both will not solve this problem (if it really is a problem which I honestly doubt.)

    Bullshit. Most users - the non-MS haters, non-zealots - will see no reason to switch to another OS in the first place,

    Oh, Microsoft is doing their best to provide reasons: New licensing scheme, DRM, Palladium, spyware, requesting rights to control everything...

    Of course KDE offers so much, Windows can't do (more desktops, session manager, good MMB integration, etc.) but those are only discouvered after using it for some time.

    and being able to run the same apps won't sway them. They will respond, logically: "If I'm going to be using the same programs, why not be using the same OS?"

    By that theory, we would all still use DOS.

    Correct is: "Great that I can use better and more stable Linux-apps on a better desktop, but I still have to use this one important Win32-app or I can't switch."

    Or (more realistically for the average Joe): "Great that I can still listen to pirated music, but I still have to use these (also pirated) Win32 games"

    It's ridiculos to think that anybody will use Wine to use all their Win32apps on Linux. Wine is and will be used for those programs that don't have an equivalent in Linux and only for those, not for all.

  113. Re:Unified Desktop by rseuhs · · Score: 2
    There are good political reasons to choose GNOME. (I don't know why when people say 'politics' it is assumed to be a synonym for 'bad'.) Namely, proprietary software vendors can produce GNOME versions of their apps without any trouble; but you have to pay Troll Tech if you want to produce proprietary software for KDE.

    IIRC, Trolltech's license is about 1500$ - 3500$ per developer. That shouldn't be a roadblock for a commercial vendor. Microsoft's tools are also not free and people are obviously using them.

    Free software zealots won't care one way or the other - indeed they might even prefer the GPL'd Qt rather than Lesser-GPL'd GNOME libraries - but businesses are perhaps more likely to choose GNOME if they decide which desktop to develop for.

    Wrong, businesses will choose Qt if they use C++ and GTK if they still use C.

    And if they want to do multiplatform, they will choose Qt or Kylix (both KDE-based).

  114. Re:Sounds like they're trying to give KDE a fair s by infiniti99 · · Score: 2

    It's fairly clear the Red Hat's developers are more adept with Gtk+/Gnome than Qt/KDE, and there's nothing wrong with that - if they were better at Qt, we'd still be having this discussion.

    Actually, I wonder... Redhat is the only distribution I can name that has GNOME as a default desktop. Had Redhat chosen KDE as their default, then maybe they would not have even bothered with trying to theme with GNOME. So, no, I think if they were better with Qt then we wouldn't be having this discussion.

    The irony here is that Redhat, being the most popular Linux distribution, could probably end the desktop war by simply switching to KDE as a default.

    Anyway, just thinking out loud. I have nothing against GNOME.

  115. Re:cease and desist, Red Hat! by cant_get_a_good_nick · · Score: 2

    Maybe you could sue them and all UNIXen for having a /dev/null. If someone can sue all domain owners for using the generic term "easy" maybe you have a shot.

  116. Re:Unified Desktop by rseuhs · · Score: 2
    What I am saying is... A newbie NEEDS to see the EXACT same thing on each distro.

    Currently all distributions install KDE by default except one which installs GNOME.

    In 2 months, all distributions will install KDE by default except one which will install a bastardized mixture of KDE and GNOME.

    And you say that's great. What was your point again?

    The newbie benefits because (if this were in all distros)

    It is not in all distros. KDE is the default on all distros except one. If we really need standardization who should change?

    Also, I don't think anybody can expect all distros to put a redhat-logo in the bottom-left corner.

    And once again, you miss my point... this is NOT for you. This is for the person who has never run Linux before. This is for the person who can't set their microwave or VCR clock because it's too difficult. These are not stupid people, they are people who simply don't care. They just want to turn the machine on and get to work.

    Your point is completely irrelevant.

    Hell, KDE even offers a settings-manager which is launched at first log-in. Just choose "Windows" and *ALL* your settings will be set like Windows. It will look like Windows, it will feel like Windows. So the newbie thinks "I know Windows, so this is probably the best" clicks on it, clicks "next" twice and that's it.

    This is out-of-the-box KDE functionality.

    If RedHat thinks it's so damn important to keep Gnome, they could just write a similar application for Gnome and everything would be fine.

    Sorry, but creating a mixture won't solve *this* problem (which has nothing to do with uniformity) at all.

    And if RedHat is listening... this would be something that you DO install during a default installation, but can be de-selected during all installations if the admin chooses. If you want to elevate yourself among the masses, then you can call it the "Dummy Pack" for all I care, but either way, it has to be unifrom across all distros and it has to be a default that can be over-ridden by those who "know better".

    So you say that we need uniformity and think that RedHat is doing the right thing by being the ONLY ONE doing everything different.

    Sorry, I don't understand your point.

  117. Re:OT Re:Have your cake and eat it too? by spudnic · · Score: 2

    Maybe you can have your cake THEN it it, but you can't have your cake AND eat it. Once you've eaten it, you no longer have it.

    --
    load "linux",8,1
  118. Re:screens pls! by Speare · · Score: 2

    If the AC is still reading, I'm using gkrellm in those shots. A newer one made especially for gnome2/gtk2 is in the works, I hear, but the Null beta contains the gtk1 version.

    --
    [ .sig file not found ]
  119. Re:Unified Desktop by rseuhs · · Score: 2
    Windows XP offers multiple desktops.

    Yes, but only 4. And only since XP.

    Windows XP has session management

    No it has not. If you have 10 IE-windows on your desktop and you reboot, you start with an empty desktop.

    In KDE, all KDE-programs are restored just like they were before you left.

  120. Story really is bogus by 0x0d0a · · Score: 2

    These screenshots of null don't lack developers' names.

    The problem is one of themes, not modified about boxes.

    I don't know who started the rumor about altering about boxes -- happened sometime in the last submission about this.

    The problem is that there's been a lot of bullshit going around about this, and it's been trumped up a lot, and I hate to say it, but I honestly think that some of the people at companies that compete with RH might be stooping to somewhat dirty tactics.

    1. Re:Story really is bogus by 0x0d0a · · Score: 2

      And had I read my own link, I'd have found out.

      The authors names are still intact, but KDE programs only have an "about this program" menu entry, as GNOME programs do, not an "about this program" entry *and* an "about KDE" entry.

  121. Re:what bollocks by fault0 · · Score: 2

    Heh, what does this article have to do with GNOME?

    They modified GNOME almost as much as they modified KDE. They only thing I personally want changed is the ability to go back to a default KDE. Apparently there is a gconf key which you can use to revert some of the changes they made to GNOME. There should be an equivlent way of doing it in KDE.

  122. Its about sane defaults by Nailer · · Score: 3, Interesting

    I, for one, like the different options we have in terms of desktop environments. I don't want either KDE or GNOME to go away.

    People are continually misunderstanding this point. You can change the default look and feel and behaviour if you want t, but Red Hat have made the two desktops consistent. Which is a good thing, as users choose their desktop apps based on usefullness, rather than toolkit.

  123. Re:Unified Desktop by Nailer · · Score: 2

    Currently Joe installs Linux and either stays with it because he likes it better or drops it because doesn't run.

    How will that change?


    I thought that would be obvious. One of the reasons he might not like it is because his apps never look quite the same - QT, GTK2, GTK1, XMMS and Mozilla on every Linux desktop but Red Hat Nulls don't look consistent. This is annoying and unnecessary.

  124. Re:Unified Desktop by rseuhs · · Score: 2
    So unifying on one user environment and taking away choice with regards to environments is a good thing? I think THAT is a serious mistake.

    True, but nothing prevents them from including GNOME. But IF you think that standardization is important they should switch to KDE as the default. IMO, they should use KDE as a default, but not because of standardization...

    As far as RedHat being different is concerned, what does it matter for crying out loud!??

    Funny, it was *YOU* who said that everybody should have the same thing on every distro, not me.

    IMO, standardization is overrated, but that's me.

    What distro of Linux do you think newbies are going to buy in the US? They certainly aren't going to get Debian, SuSe or use Linux From Scratch. They are going to buy RedHat every time. When SuSE actually makes a dent in the US, maybe things will be different.

    Wow, you change your mind pretty fast. First you insist on cross-distribution conformity, now you say that RedHat is the only thing that matters.

    There is also Mandrake, BTW, which is not doing bad in the US either.

    Of course RedHat scare away so many users that there are fewer desktop Linux-users in the US than in Germany, despite being 3 times larger...

    Just check out newsgroups, you will see about 5 - 15% of Linux users in German newsgroups, but only 0-3% in US-newsgroups. (non-technical, OS-neutral of course.) I can send you a perl-script that analyzes with what people posted their messages if you want.

    But you seem to be fine with that, it seems.

    KDE isn't flexible enough,

    Do you have an example of KDE "unflexibility" or are you just trolling?

    At the same time, we don't need to limit a distro's choice of environment either. And that is exactly what you are proposing.

    Wrong. I was talking about defaults. Of course Gnome should be included for those who want it.

    Who cares if it's the environment that most distros use?

    You seem to.

    A theme is less of a limitation and has NO impact on advanced users.

    As I already pointed out, that's false. A theme just makes it "look" integrated, but the real cool features all don't work (and you don't know why some apps work while others don't because of your idiotic theme, which makes it even worse.)

    As I said, this standardization is overrated, however it's not completely pointless either. For example you might want to use the addressbook or the printing dialouge or want to dock to the menubar. These are things that really matter and those will not work better because of themes.

  125. Re:OT Re:Have your cake and eat it too? by KNicolson · · Score: 2
    I don't know how you managed to get a "Flamebait" on that message, but anyway, I googled for it and got this explanation:

    http://www.quinion.com/words/qa/qa-hav2.htm

  126. Legal does not mean SMART. by Moritz+Moeller+-+Her · · Score: 2

    Listen, troll.

    Just because a fork of KDE is legal, it does not mean it is smart to do a fork. Corel did this for their linux version and many changes were just lost , because noone ever ported them to KDE-2.

    Also many of the changes to KDE software are done by Gnome developers working for Redhat. These people call KDE "crapland" in public bug reports.

    At the moment the Redhat KDE changes the name of the KDE services, so that any program compiled for Redhat's KDE might not work with SuSE's KDE, Mandrake's KDE, Debian's KDE or any generic KDE.
    Noone needs this kind of crap.

    --
    Moritz
    1. Re:Legal does not mean SMART. by (void*) · · Score: 2

      Whoa, stand back and think. If RedHat wants to fork, then please let them support the fork. Imagine how simple it is for the KDE developers. Just issue a public notice, saying that RedHat KDE is not KDE, and cannnot be total supported. Then anytime anyone complains, point them to the notice. Problem solved.

  127. Re:Unified Desktop by nathanh · · Score: 2
    Oh, not another one explaining the success of Microsoft. Face it: Microsoft is successful because ...

    Oh, not another one explaining the success of Microsoft.

  128. Re:Unified Desktop by rseuhs · · Score: 2
    Fine, you like KDE. Why do you think it should be the exclusive default environment?

    Well, I didn't. I said that *IF* standardization is so damn important, you would have to standardize on an exclusive default environment.

    A theme will only make it look integrated but will fail where it will count.

    Answer this: why is standardization overrated? It's the only thing that allows something to gain mass acceptance. Look at cars. They are all pretty much the same in terms of the basic "user interface". You can soup up a car and make it look cool or give it some eninge modifications to get extra performance, but any joe off the street will be able to drive even the most modified car. This is becasue ALL cars have a "default theme", so to speak.

    A good example: All cockpits look very different (= **NO** "default" theme at all. not even near it) but the controls work similarily (like everybody has windows, menus, a mouse, etc.).

    So you provided an example that the average Joe does not freak out because some colors or looks are different. My point all the way.

    Your "steering knob" example is not appropriate. All common DEs work through the same principles.

    Regarding KDE: Yes, many themes support putting the buttons wherever you want, but some don't. On everything else you say it's "boring", whatever that means.

    I don't really care much about being "cool", I care about getting work done. KDE's printing manager lets me send a pdf as e-mail out of *every* KDE app. This is why I switched over to KWord for bills. Konqueror's "fish:" KIOslave lets me connect to *ANY* ssh-scp computer without any need to configure anything. (What a relief, before that you had to set up NFS, SMB or something like that - unnecessary for non-permanent connections. This is the first graphical ssh/scp client I am aware of).

    All it requires is a simple question: Are you new to Linux? If they answer yes, then BAM! install the low-grade user's default theme pack.

    Well, as I already pointed out, a settings-manager already exists in KDE and the "Windows-like"-settings will probably be fine for newbies coming from Windows.

    So what you request *EXISTS RIGHT NOW* and is used in SuSE, Mandrake, Caldera and all other distros that install KDE by default. But you seem to be in denial about that fact.

    You said that something like this is needed for mass-acceptance and you are right: Everywhere RedHat scares away new users, Linux is virtually non-existant on the desktop while everywhere a KDE-centric distribution is in the default installs, it is spreading. What a coicidence, eh?

    Stop denying the facts.

    Do you know the saying "A technology has not been invented until Microsoft incorporates it"? - We are discussing really long now and you beg for a solution that does not exist for you because RedHat does not incorporate it but everybody else is using for quite some time now.

    GNOME/KDE cooperation would solve that problem real fast. That's what I was saying earlier about how competition needs to go away since it is only a destructive force.

    Let's get some facts straight: GNOME was a reaction on KDE, if there were no KDE, there would neither be a GNOME. GNOME's only reason to exist is to kill KDE.

    Also if you look at GNOME, they seem to be eager to jump on every Microsoft-technology (MONO, a registry-like settings system(!)) but are not willing to use KDE-technology at all. It's not easy to work with people whose only goal is to kill you. But to be fair, it was getting better lately.

    Also, because of the nature of the two projects (C vs. C++) sharing code is hard or even impossible.

    You feel that KDE is the best environment for all users and should be the default.

    Wrong, I think (and I can support that with usage statistics) that KDE is the best environment for most (not all) users and should be the default.

  129. Re:Unified Desktop by rseuhs · · Score: 2
    Wrong, Micrsoft had hundreds of Asian companies providing cheap parts for razor-thin margins.

    The PC was the only open hardware platform at that time.

  130. What about GNOME/KDE on other platforms? by fwr · · Score: 2

    Another thing to think about is that some people like KDE to look the same on their Linux box as on their Solaris box or other platform. Same goes for GNOME. If RedHat wants to create a third unique desktop using aspects of both GNOME and KDE and meshing them together then that's great, but don't F-up the look and feel of the original desktops...

  131. Hooray! But include program names in the menus! by dwheeler · · Score: 2

    Actually, I think this is a GOOD thing, as long as other distributions can also pick up the defaults. Currently working with some programs is jarring - and thus painful to users. However, I think just having a generic function description in the menus is a mistake. It's important to modify the menus so that they show not just the function ("Web Browser"), but also the name of the program ("Mozilla"). Yes, it's longer, but it is MORE confusing to users when the programs change or when they update to a different program. When I see "Mozilla Web Browser" and "Galeon Web Browser", I can understand both (a) they do the same basic thing, but (b) will do it somewhat differently. You could swap the order if necessary "Web Browser (Mozilla)" if you'd prefer, as long as it was done consistently throughout the system. This is already a requirement in the GNOME User Interface Guidelines; you can see the whole document at: http://developer.gnome.org/projects/gup/hig/1.0/ And this specific guidance at: http://developer.gnome.org/projects/gup/hig/1.0/de sktop-integration.html#menu-item-names

    --
    - David A. Wheeler (see my Secure Programming HOWTO)
  132. Re:OT Re:Have your cake and eat it too? by jdcook · · Score: 2

    Thanks. That link was interesting.

    --
    Q:How many libertarians does it take to stop a Panzer division? A:None. Obviously market forces will take care of it.