Slashdot Mirror


KDE Celebrates 10 Years of Existence

Rob Kaper wrote in to tell us about KDE's 10th anniversary. From the article: "Yesterday at 10:00 AM the president of the KDE e.V. Eva Brucherseifer welcomed the audience of the presentation track at the KDE anniversary event at the Technische Akademie Esslingen (TAE) in Ostfildern near Stuttgart, Germany. Keynote speakers were Matthias Ettrich, founder of the KDE project, as well as Klaus Knopper of Knoppix fame. During their presentations they looked back at KDE's successful past 10 years and they offered their thoughts about the future of KDE and Free Software." Rob adds this thought: "We've come a long way in ten years, but where must we still improve?"

270 comments

  1. And I thought the Christian Fundies were nuts by Anonymous Coward · · Score: 0, Funny

    As someone who graduated high school in 1982, I can assure you the universe is older than 10 years.

    1. Re:And I thought the Christian Fundies were nuts by Anonymous Coward · · Score: 4, Funny

      Yet another sickening blow has struck what's left of the Linux community, as a soon-to-be-released report by the independent Commision for Technology Management (CTM) after a year-long study has concluded: Linux is already dead. Here are some of the commission's findings:

      Fact: Linux has balkanized yet again. There are now no less than 140 separate, competing Linux distros, each of which has introduced fundamental incompatibilities with the other distros, and frequently with Unix standards. Average number of developers in each project (except for Redhat and Novell/Suse): fewer than five. Average number of users per project: there are no definitive numbers, but reports show that all projects are on the decline.

      Fact: The trivial issue os what to call Linux continues to hound Linux. At a recent Linux conference in San Francisco, a fight broke out between RMS (Richard M. Stallman) who says Linux should be called GNU/Linux and Linus Torvalds who created Linux and says that Linux should be called Linux. This led to a massive barroom style brawl involving at least 150 Linux geeks. The SFPD was called out to break up the melee, and arrested 150 people. It was estimated that at least 2 to 3 times that many were involved in the brawl, but there wasn't enough police on hand to arrest or count all of them. Sixty one people were hospitalized as a result of this brawl, and one person is still in a coma. Another three people had to get their jaws wired shut.

      Fact: Linux is plagued by a lack of professionalism. The stereotype of Linux users being fat unwashed dateless geeks who still live in their parents' basements and refuse to shower more than once a month is all too true. The best example of this is RMS who claims to have a "water phobia" and thus rarely bathes. RMS also looks like he has been living in a cave for the last 5 years. In fact, RMS has been arrested twice because he has been mistaken for Osama Bin Laden. While RMS has always been found to not be Osama Bin Laden, it has created a perception of that Linux is the "terrorist operating system". Linus Torvalds has been forced to spend a great deal of time correcting this perception instead of working on the Linux kernel. Alan Cox quit Linux kernel development since he got tired of everyone saying that he was a terrorist.

      Fact: There are almost no Connectiva developers left, and its use, according to Netcraft, is down to a sadly crippled .005% of internet servers. This led to Mandrakesoft, makers of another troubled distro, to purchase Connectiva and become Mandriva. However, industry anaylists say that this will not help since Mandriva is already a shell of its former self.

      Fact: X.org will not include support for Redhat's Fedora project. The newly formed group believes that Fedora has strayed too far from Unix standards and have become too difficult to support along with other Linux distros and Solaris x86. "It's too much trouble," said one anonymous developer. "If they want to make their own standards, let them doing the porting for us."

      Fact: Ubuntu Linux, yet another offshoot of the beleaguered Debian "distro", is already collapsing under the weight of internal power struggles and in-fighting. "They haven't done a single decent release," notes Mark Baron, an industry watcher and columnist. "Their mailing lists read like an online version of a Jerry Springer episode, complete with food fights, swearing, name-calling, and chair-throwing. It also doesn't help that most people think the word, "Ubuntu", is an obscure term for a homosexual orgy." Netcraft reports that Ubuntu Linux is run on exactly 0% of internet servers. An attempt to save Ubuntu by creating a derivative distro called Kubuntu has also failed.

      Fact: Debian Linux, which claims to focus on "being free" (whatever that is supposed to mean), is slow, and cannot take advantage of multiple CPUs. "That about drove the last nail in the coffin for Linux use here," said Michael Curry, CTO of Amazon.com. "We took our Debian boxes out to the backyard and sh

    2. Re:And I thought the Christian Fundies were nuts by Anonymous Coward · · Score: 0

      So, was it ancient Egyptians or ancient Chinese who had high schools back then?

    3. Re:And I thought the Christian Fundies were nuts by h2g2bob · · Score: 1

      In the words of Zim: "Lies! Filthy earth-boy lies!!"

  2. Where can you improve ? by Anonymous Coward · · Score: 4, Insightful


    how about memory usage ? be nice to run KDE on older hardware to replace those soon-to-be-defunct Win98 boxes

    1. Re:Where can you improve ? by Anonymous Coward · · Score: 5, Funny

      Frankly I'd love to see them pick better application names. I kan't stand the ones they have now.

    2. Re:Where can you improve ? by FudRucker · · Score: 1

      gnome_is gnome_just gnome_as gnome_bad, sometimes worse...

      if you have gnome installed just look at all the files in /usr/bin with gnome in front of the name...

      --
      Politics is Treachery, Religion is Brainwashing
    3. Re:Where can you improve ? by Anonymous Coward · · Score: 2, Insightful

      > be nice to run KDE on older hardware.

      I read that at the end of the Akademy they made the kde window manager OpenGL aware (without needing GLX). That would mean that the each window can be cached on the graphics card and switching between windows will be very fast in KDE 4 even on a slow cpu, the cpu will have more time to spend on other tasks, making KDE faster and feeling significantly faster.

    4. Re:Where can you improve ? by Anonymous Coward · · Score: 1, Funny

      Better names? I just kunt do it kaptain! The nameology is in place. It'll take me half an hour to change the programming. Kaptain, you just don't know what your are asking.

      But Kaptain, I'll try!

    5. Re:Where can you improve ? by Anonymous Coward · · Score: 0

      I'd love NOT to see any more K related "jokes". They may have been funny ten years ago, but please, move on.

    6. Re:Where can you improve ? by scotch · · Score: 1

      Maybe there is some way you can pin the KDE naming problem on the Democrats?

      --
      XML causes global warming.
    7. Re:Where can you improve ? by Anonymous Coward · · Score: 0

      Well, it they renamed all the 'k' apps, then the jokes will stop.

      Seriously, it is pretty annoying and amateurish

    8. Re:Where can you improve ? by temcat · · Score: 1

      Have you used Gnome recently? Because of all apps that are present in my Applications menu on Ubuntu Edgy, only Gnometris and gtranslator somehow demonstrate the pattern meant by you. And my set of apps includes much more than just those installed by default.

      Meanwhile, on KDE you are overwhelmed by KThis and KThat. Last time I tried KDE was in the early stages of Edgy development cycle.

    9. Re:Where can you improve ? by hobo+sapiens · · Score: 1

      um...what? I guess maybe some apps are named that way, but you aren't beat over the head with gnome this and gnome that, like on the menus and so forth. Ok, so a theme is cute and all, but KDE takes it waaaaaay too far.

      --
      blah blah blah
    10. Re:Where can you improve ? by pizzach · · Score: 1

      KDE definitely goes a lot farther than gnome with the k vs g thing. I also think k is a more annoying letter to hear over and over again for some reason.

      --
      Once you start despising the jerks, you become one.
    11. Re:Where can you improve ? by ZakuSage · · Score: 1

      Still better then Apple's application names. iCant stand their names.

    12. Re:Where can you improve ? by Anonymous Coward · · Score: 0

      Nah, Democrats are too busy throwing Oreo cookies at black Republicans, censoring critical YouTube videos, and making more inane comparisons to Hitler and Nazis. You know, stuff that really shows their liberal tolerance at work.

    13. Re:Where can you improve ? by IdleTime · · Score: 1

      K!

      --
      If you mod me down, I *will* introduce you to my sister!
    14. Re:Where can you improve ? by cheater512 · · Score: 1

      I can run KDE and Mozilla (not Firefox) on a old Pentium laptop with 32mb of ram just fine.
      Admittedly its slightly slower than my desktop (mainly hdd speed) but its very usable.

      Its nice to brag that I can use the latest version of Linux with KDE and Mozilla on this laptop when XP and Vista wont even think about installing on it. :)

    15. Re:Where can you improve ? by Neil+Hodges · · Score: 1
      how about memory usage ? be nice to run KDE on older hardware to replace those soon-to-be-defunct Win98 boxes

      I did that, and even with Gentoo's compilation ways, KDE ended up being faster than GNOME on a PII 233 MHz with 512 MB of RAM. I could even enable the X Composite extension for the Voodoo3 video card and there was no significant performance hit.

    16. Re:Where can you improve ? by Anonymous Coward · · Score: 0

      I gno!

    17. Re:Where can you improve ? by Anonymous Coward · · Score: 0

      Dang, that is just nasty. Is this the current line of talking points the traitorous right-wing talking heads are spewing? Holy crap that is nasty talk. Talk about having to be brainwashed already to actually agree with foul speech like that. NASTY. Dang, you people talk about LIBERALISM being a mental disorder, while having no clue just how fucked in the head you fucking jackasses are yourself. Takes one to know one I guess. Oh ya, I guess it's ok for male Republican congressmen to sexually exploit teenage pages now, isn't it. Just go to Rush Limbugh's web site it's all the fucking liberals fault that a mother fucking Republican lapdog did the things he did. FUCK ALL YOU FUCKING DIPSHIT FUCKING "CONSERVATIVE" FUCKING JACKASS SPEWING SHIT ALL OVER OUR COUNTRY FUCK YOU ALL I HOPE YOU ENJOY LOOKING BACK AND MISSING OUR ONCE GREAT COUNTRY THANKS FOR THE RIDE.

    18. Re:Where can you improve ? by Anonymous Coward · · Score: 0

      You mean like the entire gnome interface? Where every time I want to do a simple thing I have to jump through hoops because of some "programming ideal" that sleek, beautiful, and non-functional is best? Talk about annoying and amateurish!!!

    19. Re:Where can you improve ? by CronoCloud · · Score: 1

      I've run Mozilla/Firefox under KDE1/2 on a PS2 Linux kit, (294MHz CPU 32MB RAM)as you said, slow but usable. Though Dillo is probably a better choice for basic browsing, especially if you want to do anything else. The RAM is the problem not the CPU speed. I wish I could try out KDE3 on it but QT3 won't compile.

      I normally use fluxbox as my window manager of choice on it.

    20. Re:Where can you improve ? by cheater512 · · Score: 1

      I used KDE 3.5. It runs Gentoo so it just runs the newest version in Portage.

      I needed Mozilla to read my email when I was away from my main computer for 2 months.
      I still have the twitch from using the laptop for 2 months straight nearly a year ago. ;)

    21. Re:Where can you improve ? by LiquidFire_HK · · Score: 1

      KDE 4 is based on Qt 4, which is significantly faster and lighter than 3. Additionally, KDE is so customizable, that you can strip it down to only what you need as far as eye-candy goes.

    22. Re:Where can you improve ? by NumerusSpy · · Score: 0

      You're right. Those dumb democrats. There is no comparison between Hitler and Dubya as Hitler had the balls to at least serve in uniform.

      --
      There they are a conga line of suck holes. On the conservative side of Australian politics. - Mark Latham
    23. Re:Where can you improve ? by vhogemann · · Score: 1

      Well,

      I used to run KDE 3.5.4 on a PIII 700MHz laptop, with only 128MB of RAM. And while I was using only K apps, everything went quite smooth... I could even let several konqueror windows open! Also, KOffice worked like a charm.

      The real problem was Firefox and OpenOffice... these are real memory hogs. I couldn't belive how many memory Firefox eat, open a few tabs and it will use more memory than X and KDE combined! OpenOffice is also a mammoth, compare it to KOffice or Abiword + Gnumeric and you'll see what I'm talking about.

      KDE is pretty lightweight, and it will run nicelly on a old machine. Firefox and OpenOffice won't.

      --
      ---- You know how some doctors have the Messiah complex - they need to save the world? You've got the "Rubik's" complex
    24. Re:Where can you improve ? by jb.hl.com · · Score: 1

      Correction: ball.

      (Pedantry in action ;)

      --
      By summer it was all gone...now shesmovedon. --
    25. Re:Where can you improve ? by jZnat · · Score: 1

      *Demokrats

      --
      'Yes, firefox is indeed greater than women. Can women block pops up for you? No. Can Firefox show you naked women? Yes.'
    26. Re:Where can you improve ? by sanguinemoon · · Score: 1

      I use KDE 3.5.4 in a laptop with a 366 PII and 256 megs ram without problems. I did have it working in only 128 megs on the same ancient machine, it was just a bit on the slow side.

    27. Re:Where can you improve ? by Anonymous Coward · · Score: 0

      Filenames are not the same thing as application names, genius. It's the application names themselves that are so annoying. You don't see gnome- in front of everything you run in the graphical environment, but you do see the horrid Ks. It's like a fourth grader's idea of a catchy naming scheme.

      Personally I just can't feel professional managing my files using "Konqueror" and writing my papers using "KOffice". I mean, for fuck sakes, at least GNOME has the decency to call nautilus "File Manager". I'm a KDE fanboy myself, but I'm not going to pretend like the K naming scheme is a good thing.

    28. Re:Where can you improve ? by Anonymous Coward · · Score: 0

      Still KDE is the leaner of the 2 full desktop enviroments around there:

      http://ktown.kde.org/~seli/memory/

    29. Re:Where can you improve ? by niskel · · Score: 1

      My old hardware doesn't have any OpenGL support.
      If it tried to use OpenGL it would end up using the software implementation thus hosing the CPU.

    30. Re:Where can you improve ? by NumerusSpy · · Score: 0

      I always thought that was just one of those propaganda stories just like babies on bayonets, babies thrown out of incubators, babies as bulletproof vests, etc, etc.

      --
      There they are a conga line of suck holes. On the conservative side of Australian politics. - Mark Latham
  3. Where to improve? by Travoltus · · Score: 4, Interesting

    That's easily said and not so easily done.

    How about this one...

    All "official" KDE apps get restructured to be command line interface (CLI) and graphical user interface (GUI) front ends to shared object libraries. In every KDE app you can find an entry in the "about" function that shows you how the CLI would do various tasks, including the last task you did. You can even make it optional as a compile-time option in source code. (Power users would rather not have that function bloat up their code, no doubt.)

    In a flash, any GUI using novice with a hunger to know more about Linux, can look right there and see how it's done.

    In no time you'll have tons of people speeding up their KDE by doing everything on the command line and perhaps even using less memory (as far as CLI vs GUI memory usage is concerned).

    --
    --- Grow a pair, liberals... stop letting the Republicans bully you!
    1. Re:Where to improve? by eille-la · · Score: 1

      DCOP already does something like this, but it is not present in all kde apps and not all functions are supported.
      http://developer.kde.org/documentation/other/dcop. html

    2. Re:Where to improve? by Ford+Prefect · · Score: 1

      DCOP?

      It's not the 1970s any more...

      --
      Tedious Bloggy Stuff - hooray?
    3. Re:Where to improve? by Ant+P. · · Score: 1

      KDE sort of already has that using DCOP/DBus commands. You still need the GUI app running for them to work, but it's a start...

      The one thing I like about K* stuff is that it's sort of like Perl, in that it doesn't force users to do things "This way, or else".

    4. Re:Where to improve? by eclectro · · Score: 3, Funny

      In no time you'll have tons of people speeding up their KDE by doing everything on the command line

      Your post gives me a hankering to boot up DOS 3.3, the last true great OS if you ask me.

      --
      Take the cheese to sickbay, the doctor should see it as soon as possible - B'Elanna Torres, "Learning Curve"
    5. Re:Where to improve? by Nutria · · Score: 1
      Your post gives me a hankering to boot up DOS 3.3, the last true great OS if you ask me.

      Obviously you've never used OpenVMS.

      --
      "I don't know, therefore Aliens" Wafflebox1
    6. Re:Where to improve? by B3ryllium · · Score: 1

      I like your suggestion. If there's one thing I hate more than bad GUIs, it's GUIs that wrap CLI executables, rather than shared object libraries. The CLI wrappers tend to do a crappy job, and they don't generally handle failure conditions well - but with an SOL, the user won't be SOL. :)

    7. Re:Where to improve? by also-rr · · Score: 1

      In no time you'll have tons of people speeding up their KDE by doing everything on the command line and perhaps even using less memory (as far as CLI vs GUI memory usage is concerned).

      Since most of the GUI libraries used by KDE are shared if you have one KDE app open then you have 90% of the memory use required to display an interface for *all* of them (discounting the actual functional code, which is required if you are using the UI or CLI).

    8. Re:Where to improve? by temcat · · Score: 1

      I think the wrapper/frontend mentality is bad as such, it's not actually about CLI vs shared libraries. IMHO a good GUI app should be first designed from the user's point view of the user, and during the further iterations a suitable backend should be chosen (with possible modifications) or written from scratch.

    9. Re:Where to improve? by temcat · · Score: 1

      user's point view of the user

      That's what one gets for not hitting Preview.

    10. Re:Where to improve? by heinousjay · · Score: 1

      It's not the code that eats up the memory, it's the data. There's a sigificant memory overhead to managing the widgets that would be freed if the GUI were never started. I'm kinda guessing here, but that may be what the OP meant.

      --
      Slashdot - where whining about luck is the new way to make the world you want.
    11. Re:Where to improve? by andersa · · Score: 2, Insightful

      I. Don't. Wan't. To. Use. A. CLI. That's why I use KDE.

    12. Re:Where to improve? by Bogtha · · Score: 1

      A lot of what you want is already there. Use the 'dcop' command, and it lists the applications running that are available to manipulate. Use an application name that is already running and it lists the operations you can perform with it. Use the 'kdcop' command and you have a graphical application to explore what is possible.

      --
      Bogtha Bogtha Bogtha
    13. Re:Where to improve? by Reziac · · Score: 1

      That sounds kindof like a configuration utility I've been begging for (not being a coder, I can't do it myself) -- give us the GUI so we can see the options right there in plain sight, but in a second panel, SHOW us exactly what is being done to the actual config file's text -- so we can learn by watching it happen in realtime. That way even beginners can learn config file syntax without having to plow through manuals that to non-geeks, make NO sense out of context.

      This can't be rocket science to accomplish -- even some fairly primitive HTML editors can do simultaneous WYSIWYG and raw mode editing, which is functionally the same process as the above-described config utility.

      --
      ~REZ~ #43301. Who'd fake being me anyway?
  4. A song... by Mateo_LeFou · · Score: 3, Funny

    Kappy Kirthday to you,
    Kappy Kirthday to you,
    Kappy Kirthday Kister Kresident,
    Kappy Kirthday Ko Kou

    --
    My turnips listen for the soft cry of your love
    1. Re:A song... by honkycat · · Score: 1

      Shouldn't it be "Kappy Kirthday toK youK" ?

    2. Re:A song... by Anonymous Coward · · Score: 0

      I kwn the kopyright on that partikular sonk, you insensitive klod! Kive me my royalties or I'll ksue!

  5. Let me be the first to say... by Anonymous Coward · · Score: 1, Funny

    Keep up Khe Kood Kork

  6. Congratulations! by reldruH · · Score: 2, Insightful

    I'd just like to say congratulations and thank you for making such a great desktop. Keep up the good work for KDE 4. Just in case anyone is interested in getting involved, here's the link to the Support KDE page. There's info there on how to donate money, time, code, etc.

    --
    I've always pictured the color of OS zealotry as a sort of bright flamingo pinkish hue
    1. Re:Congratulations! by JamesGecko · · Score: 1

      I believe you mean "Kongratulations".

  7. A few thoughts by Anonymous Coward · · Score: 1, Interesting
    "We've come a long way in ten years, but where must we still improve?"


    • Speed. KDE (and Gnome) need better speed optimizations. It feels very sluggish compared to either Windows or even Windows apps under Wine.
    • Memory usage. The memory requirements of KDE and and Gnome are ridiculous. They make Windows seem memory efficient, which is not good. Just try running Blackbox or even XFCE for a few days and notice the massive decrease in memory.
    • Clutter. The KDE dialogs and windows make Windows apps seem organized and lean. As of Gnome 2.12, they finally got it right. Previous Gnome releases where, IMHO, too crippled to be useful which is why I stuck with KDE for so long (8 years). KDE needs to make serious progress in this area.
    • Consistency. This really needs to become a focus. It makes Vista seem consistent.

    1. Re:A few thoughts by Anonymous Coward · · Score: 0

      And this is why I run XFCE or fluxbox.

      The folk using KDE and Gnome think the items you are unhappy with are 'features'.

    2. Re:A few thoughts by zlogic · · Score: 1

      KDE is fast compared to Gnome (at least in my opinion).
      Most Linux DEs run slower than Windows because anti-aliasing is turned on. I turned on Cleartype in Windows and simple scrolling of a source code file became significantly slower than without it. And the PC was a Celeron-1300 with 256 megs of RAM and a Radeon 9200, which perfectly runs Quake 3, UT2004 and other games, which need much more power than simple window drawing.
      As for memory usage, you haven't seen Vista yet. 300 megs right after boot (if you're lucky!). KDE has vector-based icons, an advanced GUI toolkit (much better than MFC) etc.

    3. Re:A few thoughts by Anonymous Coward · · Score: 0

      You're kidding? I have the complete opposite experience. Windows drags its feet on everything. I can't believe you actually think this is true.

    4. Re:A few thoughts by sparksinspace · · Score: 1

      nevermind memory footprint and speed JOE USER DOESNT CARE! He does however care about consistency and clutter. AND..... how about getting rid of the stupid "K" everywhere. the K was a good joke while it lasted, and for gods sake just keep it in the name of the executables, but why does the stupid UI have this stupid K everywhere? Have you ever heard something about accessibility and how its a good idea to make your UI easy to understand, i.e. READ??

    5. Re:A few thoughts by pherthyl · · Score: 4, Informative

      Speed. KDE (and Gnome) need better speed optimizations.

      This is most likely your video card drivers. KDE is plenty fast, but if you dont have acceleration working in X, then everything will seem sluggish. My card is poorly supported (ATI Xpress 200m) and it makes everything seem slow.

      Memory usage. The memory requirements of KDE and and Gnome are ridiculous.

      Yes, if you mean ridiculously low. Fresh boot, Debian with KDE 3.5.4 on my old box, 32MB of ram used. Start up konversation (irc client) and it's about 45MB. Every subsequent application uses less extra ram, because the libraries are already loaded. Fresh boot on windows xp is at least 100MB, on my laptop more like 150. Most likely you have no idea on how to measure memory usage on linux. Have a look here: http://ktown.kde.org/~seli/memory/

      Clutter.

      You've got a point there, it's getting better with every release though. And no, sacrificing features for simplicity like Gnome did is not a good strategy.

      Consistency.

      That's one of the strengths of KDE actually. Everything works the same across the KDE apps. Keyboard shortcuts, look, general menu structure, colours, style, etc etc. And then we get into the even more important consistency, which is functional consistency. Just about every app that needs a text editor uses the same one, so they all behave the same. The same spell checking engine is used almost everywhere, and the password manager saves passwords for every application that has a need to store them. No other operating system is anywhere close to that consistent. Not OS X, not Windows, nothing.

    6. Re:A few thoughts by Homology · · Score: 2, Informative

      I would like to add that KDE 3.5 starts faster and loads applications quicker than earlier versions, in contrast to some other desktop environment I shall not name. Kudos to the KDE developers to work on this.

    7. Re:A few thoughts by pembo13 · · Score: 1

      Something is definitely wrong with your machine if things run faster under Windows than KDE on the same box.

      --
      "Thanks for all the money you paid to us. We've used it to buy off ISO among other things" -Microsoft
    8. Re:A few thoughts by oohshiny · · Score: 2, Informative

      You know, I don't particularly like KDE (see my other comment). But compared to Mac and Windows, KDE is a lot faster and more consistent. I think it also has significantly lower memory usage than a Mac. I'll give you that it is more cluttered than the Mac.

    9. Re:A few thoughts by RAMMS+EIN · · Score: 1

      ``Speed. KDE (and Gnome) need better speed optimizations.''

      As an interesting note, the other day I installed Ubuntu Dapper on a machine with a Pentium II 266 MHz and 256 MB RAM inside. I expected it to be slow to the point of being unusable, but, to my surprise, it actually worked really smoothly. I recall getting similar results using KDE 3.2 when that was current.

      In conclusion, while speed improvements are obviously always welcome, neither GNOME nor KDE seems to be doing too bad these days.

      --
      Please correct me if I got my facts wrong.
    10. Re:A few thoughts by Bwian_of_Nazareth · · Score: 1

      Can you quote some sources for your claims? I find KDE desktop faster than WinXP on my computer. Obviously, both are blindingly fast, so it is more about the perceived speed rather than actual numbers. Also, in my experience, KDE was less memory hungry than Windows98 (back then). I am not saying KDE does not need optimising. I just thing that performace of KDE is more than sufficient. Also, you can't really compare Blackbox to KDE - KDE is a desktop environment and application suite, Blackbox is a window manager. Ale you comparing KWin+Kicker+kdesktop to Blackbox? As for the dialog boxes - I find Windows "seven levels of dialogs" much worse than KDE dialogs. And a lot of work is being done on usability in KDE. The bottom line is - without arguments, your post is just trolling.

    11. Re:A few thoughts by abradsn · · Score: 1

      Memory usage does vary from machine to machine. Mostly I see a lot of memory leaks every I run Linux in any kind of GUI mode. It seems like the Swap doesn't work well either. Though, if I have more than a gig of memory in the box everything seems great.

      Also, I see speed vary from machine to machine too. I've found that recompiling the kernel has a tremendous impact on speed every time. It usually increases responsiveness by about double.

      I think Windows gets around this particual problem by having a kernel that can adapt very well to the various different processors it is installed on. Linux distros could improve on this during installation, and I think that a lot of people would say that the performance is much better. Basically compile several kernels, and poll the hardware for which one is best to install.

      I've found that the whole system is much faster if some of the plugin modules are just directly compiled in. It doesn't typically bloat my kernel very much, because there is a lot of unused features in there that I just unselect.

      Another helpful thing that I've found when that slow down problem occurs -- turn off swap... swap is terrible under Linux. Swap is at least mediocre on windows. Turning off swap in Linux makes it so that if I leak too much memory it doesn't get swapped to disk, and when it is needed again at least it is pulling from a faster memory store.

      And instead of a command line interface, I would like to see a unified way of handling dependencies in libaries, and also a unified way of searching through api of the libraries available on the system. (Directly from the libraries themselves, ala the .Net Framework object browser)

      A well integrated GUI development environment would be nice too. One that you can drop a button, or a text box on a form, and the double click on the button or textbox to add an event to it. Like Kylix except supported through version upgrades of Linux. Kdevelop isn't there yet.

      Just my two cents.

    12. Re:A few thoughts by abradsn · · Score: 1

      Do you have some stats to show XP is slower than a KDE Linux distro? Mostly I'm conncerned with application startup times, which are typically double on Linux as opposed to Windows for the same app. Get a stopwatch and time opening up notepad in XP as opposed to your favorite note editor in Linux (gedit in gnome, kate in kde) Do the same thing for FireFox. Do the same thing for Open Office. Linux is slower. I don't like to wait. I'll use Linux when it is faster, or when there is only a negligable difference in speed due to the increasing speed of hardware. And what is the "seven levels of dialogs" that you are complaining about? Is that something that is Windows only? I'd really like to know, so I can keep it from happening when I write programs.

    13. Re:A few thoughts by Anonymous Coward · · Score: 0

      Just try running Blackbox or even XFCE for a few days and notice the massive decrease in memory.

      Well, yes, but why would you want to? Blackbox really isn't useful for anything beyond running a little dock applet that shows off how little RAM your machine is using...

    14. Re:A few thoughts by Knuckles · · Score: 1

      time opening up notepad in XP as opposed to your favorite note editor in Linux (gedit in gnome, kate in kde)

      That's just stupid. Since when can Notepad do syntax highlighting and all the other stuff kate/gedit can do? Comparing applications with completely different feature sets is not valid.

      Do the same thing for FireFox. Do the same thing for Open Office.

      Approx the same for me on Win and Ubuntu.

      --
      "When I first heard Daydream Nation it quite frankly scared the living shit out of me." -- Matthew Stearns
    15. Re:A few thoughts by Ash-Fox · · Score: 1
      Just try running Blackbox or even XFCE for a few days and notice the massive decrease in memory.
      Strange as it maybe, GTK applications felt slower under XFCE, and in the end, the system seemed to take approximately 120-150MB more memory with the KDE applications I use.
      The KDE dialogs and windows make Windows apps seem organized and lean.
      I really have no idea what you're talking about here. Could you give some examples?
      Consistency. This really needs to become a focus. It makes Vista seem consistent.
      Again, no idea what you're talking about -- Examples?
      --
      Change is certain; progress is not obligatory.
    16. Re:A few thoughts by bazald · · Score: 1

      Am I missing something? Why has the parent been modded funny? Informative is more like it. Mod it troll if that is what you mean (you troll you). It is times like these that I wish I had mod points to correct stuff like this.

      --
      Insert self-referential sig here.
    17. Re:A few thoughts by .com+b4+.storm · · Score: 2, Insightful

      Keyboard shortcuts, look, general menu structure, colours, style, etc etc. And then we get into the even more important consistency, which is functional consistency. Just about every app that needs a text editor uses the same one, so they all behave the same. The same spell checking engine is used almost everywhere, and the password manager saves passwords for every application that has a need to store them. No other operating system is anywhere close to that consistent. Not OS X, not Windows, nothing.

      I'd like to offer a rebuttal to that. Mac OS has always been about the general interface and styling being consistent across apps, and this is still true with OS X. Some rogue apps (looking at you, Microsoft) sometimes use retarded, non-standard shortcuts, but even in Microsoft's case this is not as bad as the majority of Windows or Linux apps I've encountered. Toolbars, buttons, dialogs, menus, and the majority of keyboard shortcuts work the same across all OS X apps. The only common exceptions are poorly-written little utilities, which I'm sure even KDE is susceptible to.

      As for the spell check engine, password management, etc. your assertion that OS X does not do that is just downright false. The standard text widgets support the system-wide spell checker, and any app can easily take advantage of the system Address Book, Keychain database for passwords, Spotlight for searching, etc. Any app worth using will support all of these things if they are at all applicable to the program.

      So, yes, I resent the "not anywhere close" remark. Windows is a lost cause, but I would say that OS X is at least on par, if not far beyond in some areas (e.g. the ability to AppleScript any virtually application, even if it was not coded with that in mind... or the combination of Expose with drag-and-drop wizardry to make it easy to move chunks of data around).

      --
      "Wow, you're like some kind of superhero able to ward off happiness and success at every turn."
      -- Ryan Stiles
    18. Re:A few thoughts by ToAllPointsWest · · Score: 1

      Yeah, I agree - I don't know who is complaining about speed, but whoever they are has to have something wrong with their system. I'm running KDE 3.5.4 (Kubuntu) through an NX session on a 1.3GHz Duron with 1.5GB of ram and KDE is far more responsive than Gnome on the same box.

      --
      They came for the Communists, and I didn't object - For I wasn't a Communist; They came for the Socialists, and I didn'
    19. Re:A few thoughts by molnarcs · · Score: 1
      Debian with KDE 3.5.4 on my old box, 32MB of ram used. That's almost umbelievable - I mean, that's only possible with a stripped down KDE installation, with not a single service running. But actually, I wanted to support your argument, and I agree that KDE's memory usage is ridiculously low. I have a load saved session setting, and after startup, it consumes 130 Mb ram. That includes
      • Two panels, transparent, with: ktaskbar, ksystray, a clock, kmixapplet, kpager, lots of icons
      • 1280*1024 wallpaper, four desktopts.
      • 4 instances of konqueror preloads
      • one fullscreen konsole (also with background wallpaper)
      • kopete
      • kgpg
      • kget
      • ktorrent
      • korganizer reminder daemon
      • amarok (uses a lot, but there is a huge difference between SIZE and RES in top: 73828K and 26288K - I use RES values here)
      • kmail
      • kmixapplet
      • keyboard switcher
      • kcpuload
      • klipper
      • oh, and almost forgot: 130Mb includes xorg as well (didn't bother substracting it after startx)
      Considering all this, KDE memory usage is indeed, ridiculously low. Usually those complaining work either from memory (they used KDE 5 years ago, and assume its still the same and has the same problems) or have something misconfigured.
    20. Re:A few thoughts by Anonymous Coward · · Score: 1, Informative
      This is most likely your video card drivers. KDE is plenty fast, but if you dont have acceleration working in X, then everything will seem sluggish. My card is poorly supported (ATI Xpress 200m) and it makes everything seem slow.


      nVidia with 128mb RAM. Official drivers. Windows feels more responsive.

      Yes, if you mean ridiculously low. Fresh boot, Debian with KDE 3.5.4 on my old box, 32MB of ram used. Start up konversation (irc client) and it's about 45MB. Every subsequent application uses less extra ram, because the libraries are already loaded. Fresh boot on windows xp is at least 100MB, on my laptop more like 150. Most likely you have no idea on how to measure memory usage on linux. Have a look here: http://ktown.kde.org/~seli/memory/


      I am no fan of Windows. However, run KDE or Gnome on a PII 400MHz machine with 128mb RAM. They crawl, especially when actually trying to do something like run Firefox or OpenOffice (don't even bother). Windows XP, however, will run adequately. Firefox works and feels responsive. So does OpenOffice. To get KDE or Gnome to run adequately, you need to bump up the ram to at least 384mb, though it still feels less responsive.

      If you still don't believe me that KDE and Gnome use ridiculous amounts of RAM, download VMWare Server (make sure your machine has at least a gig of memory). Create several VMs with 128mb of ram. Try several Linux distros, both with KDE and Gnome. Feel how unusable they are. Bump it up to 256. See the improvement. Bump it up to 384 and notice more of an improvement. Now try Windows XP with 128. Doesn't work great, but it does work better than KDE or Gnome with that amount.
    21. Re:A few thoughts by Dadoo · · Score: 1

      Most Linux DEs run slower than Windows because anti-aliasing is turned on.

      Wait, what? Haven't we had thread after thread here, where one of the main complaints the Windows people had was the fonts on Linux, and how bad they looked, because Linux didn't have anti-aliasing support? Are you telling us that, all this time, Windows didn't have it, either?

      --
      Sit, Ubuntu, sit. Good dog.
    22. Re:A few thoughts by Bwian_of_Nazareth · · Score: 1

      KMail starts faster than MS Outlook (in my experience). My Gentoo boots faster than XP (to usable desktop, not to login prompt). Linux does not take 30 seconds to return from screen-saver. :)

      Your claim that Linux is slower is wildly inaccurate - start-up times of some applications are greater than that of other applications. Agreed - but this is very loosely linked to Linux/Windows split.

      As to the seven level of dialogs... try changing something in email preferences in MS Outlook... or network settings, or modem settings.

    23. Re:A few thoughts by zlogic · · Score: 1

      Most windows installations have Cleartype turned off. And Tahoma is a font designed to look good even without smoothing. By default, Windows does anti-aliasing only on really big font sizes.

    24. Re:A few thoughts by Anonymous Coward · · Score: 0

      Grow up. These kind of comparisons are lame, old and irrelevant. How about comparing Windows XP with KDE 1.4.x running on XFree86 3.3.x?
       
      And how about actually trying to at least imitate having some kind of brains? You don't run firefox on top of kde in a limited-ram scenario, konqueror will do just fine in like 99% of the time, and prevents a lot of swapping, but I guess that wouldn't fit with your agenda.
       
      Also, you don't run every fucking background service you can think of, like beagle etc, and you don't turn on every piece of eyecandy you can find. But then again, I guess that wouldn't fit your agenda.

    25. Re:A few thoughts by mickwd · · Score: 1

      Surprisingly, even within 3.5, KDE 3.5.5 seems noticeably faster than 3.5.0 was, presumably due to continuing performance optimisation work.

    26. Re:A few thoughts by pherthyl · · Score: 1

      Debian with KDE 3.5.4 on my old box, 32MB of ram used. That's almost umbelievable - I mean, that's only possible with a stripped down KDE installation, with not a single service running.

      Yeah, I was amazed myself. I think it also had something to do with a recent XOrg upgrade, as before that, memory usage was around 45MB on fresh boot. The KDE itself is not overly stripped. Although this is running on my second box, which is a PII 266 w/ 196 mb of ram, so I disabled the background image, disabled all UI effects, and turned off antialiasing. Also, things like klipper (which I have no use for anyway) are disabled. Other than that, it's fairly standard KDE.
      Keep in mind that this is running on Debian, which by default has nothing running (I think before starting X, it uses about 10MB of RAM). A similar setup on a more desktop oriented distribution like Kubuntu will be using around 100MB, mostly due to little applets running, and more system services.

    27. Re:A few thoughts by molnarcs · · Score: 1

      That's more like it :) My current background image is 344K plus I have large icons, background tiles in conqueror (paper), UI effects almost at max. I hate this myth that KDE is resource hungry when you can run it on a PII 266 with 196Mb ram. With UI effects turned down, smaller wallpapers and resolution, I had a smooth desktop experience on a machine similar to yours (PII 233, same amount of ram). Usually it is the distro shipping misconfigured KDE, or running uneccessary services (like kubuntu the HP printer stuff whether you have a printer or not) in the background. My low-end box was freebsd, and unless I started up firefox or similar resource hungry progs, swap space was barely touched, even in actual use like browsing, editing in koffice - except krita perhaps, but that's understandable -, listening to music on xmms or watching something in mplayer. You can configure KDE to run as fast as XFCE while providing the same - if not more - services. Amazing indeed, especially contrasted to the "KDE is bloated, resource hungry, etc." meme that gets repeated here on ./

    28. Re:A few thoughts by Reziac · · Score: 1

      In my experience, linux with a normal desktop is always slower than a concurrent Windows version on the exact same hardware, generally by a factor of 2 or 3. That's why I use the fastest machine I have for trying out linux disties -- I also hate to wait, and couldn't stand it on the same hardware that's fine for Windows, even for XP.

      I was surprised and disappointed by this, having heard over and over how linux was great for older hardware.

      Naked commandline linux is not a fair comparison to a Windows desktop, and for performance, should be compared to DOS instead.

      (Note: I have a very good internal clock. I can spot performance diffs as small as 3%.)

      As to layers of dialogs, in my observation linux tends to group/layer them according to the thought processes of the developer, rather than of the user, occasionally leading to "all at once" or "delve into the depths", depending on who wrote it. In Windows, dialog depth tends to be consistent for a given *type* of task -- with the exception of network config type things, which are often well-buried in strange places. Either way, so long as the process is logical enough and doesn't force needless backtracking, I don't think it's something to get all wired about.

      --
      ~REZ~ #43301. Who'd fake being me anyway?
    29. Re:A few thoughts by abradsn · · Score: 1

      The cached startup time is nearly the same on both. Maybe that is what you are noticing?

      But, the uncached startup time is significantly different. So much so, that you can use a stopwatch to measure seconds of difference.

    30. Re:A few thoughts by abradsn · · Score: 1

      I don't care about syntax highlighting when I just want to open up an editor to view a file quickly, or take a note quickly.

      I like syntax highlighting however, and I use VS.Net for that. It takes about 2 seconds to load (the way I've got it setup) and does way more than Kate.

      The point here is that if Syntax highlighting or folding slow it down, then let me optionally turn them off (without recompling) so that it loads faster. Besides that, the thing ought to just load in an instant, no matter what. Things that load slowly should put off their time consuming operations until after the window pops up. I might be done with it before it gets to those instructions anyways.

      Even MS Word (the overweight beast of lore) loads as fast as Kate.

    31. Re:A few thoughts by abradsn · · Score: 1

      I've noticed that login times vary wildly based on hardware and OS. I've seen Linux boxes boot immediately and I've seen them take 7 minutes. I've seen Windows boxes boot immediately, and I've seen them take 5 minutes.

      I don't really mind either way, since I just leave the computer on most of the time.
      Honestly, it is good for me as long as it boots up somewhere less than the time it takes me to take off my coat, and shoes, and throw something in the Microwave.
      That's probably 3 minutes and is usually about right.

  8. Improve? by shadow42 · · Score: 2, Insightful

    Not that KDE's a bad window manager, but it seems too... childish. Brightly colored icons that bounce up and down whenever I click something don't generally appeal to me. Let's kill the bouncing.

    1. Re:Improve? by midkay · · Score: 3, Informative

      "Let's kill the bouncing."

      Or disable it in the configuration options. In fact, the several times I've used KDE in the not-too-distant past, it was off by default.

    2. Re:Improve? by abigor · · Score: 1

      Control Center -> Appearances and Themes -> Launch Feedback

      Use your brain next time, kid.

    3. Re:Improve? by FluffyArmada · · Score: 1

      Umm... KDE is not a window manager. KDE is a desktop environment. There is a BIG difference. If I recall correctly, the window manger is called kwin.

      --
      If con is the opposite of pro. Then isn't congress the opposite of progress?
    4. Re:Improve? by segedunum · · Score: 1

      Defaults?

    5. Re:Improve? by Dadoo · · Score: 1

      Thanks!

      The bouncing cursor always annoyed me a little, though not enough to go to the effort to find out how to turn it off. Now I know.

      --
      Sit, Ubuntu, sit. Good dog.
    6. Re:Improve? by cheater512 · · Score: 1

      I like the bouncing mainly just for teasing Windows users.

      "Lets see your OS do something like this without requiring a quad core SLI beast."

    7. Re:Improve? by udippel · · Score: 1

      Seconded.
      Have been pointing out for years that I'd prefer KDE despite of the klutter on the menu.
      But I can't stand the strain-inducing childish colours and ugly icons. Is there no arts akademia in Germany to provide non-Kindergarten icons ?

      Technically KDE pleases me. But 'usability' seems to b a word missing in the German language.

      (... and there goes the karma ... )

    8. Re:Improve? by Anonymous Coward · · Score: 0

      If the GTK open dialog is what the Gnomies think 'usability' means, I'd stick with the KDE concept every day. Anyway, colors and icons can be changed, and the Oxigen icon set for KDE4 looks very promising.

    9. Re:Improve? by udippel · · Score: 1

      Why so AC ?
      I'm no troll and I'd be too pleased with a desktop better than the competition.
      WTF is a 'Gnomie' ? I don't know what the GTK open dialog looks like.

      I only know that over the years I receive the same answers:
      1. You can change it
      2. Have a look at the upcoming version

      And my answer is consistent:
      1. The default should be convincing
      2. The alternative settings don't do much different
      3. The current one should be convincing

      You might think you need to defend your preferred one. I don't. I want FOSS to succeed. If it needs a jab of useability research and some grown-up artistry, give it some ! Over.

    10. Re:Improve? by Anonymous Coward · · Score: 0

      No default is ever going to please everyone. The default that might please you might look awful to the eyes of others. That's why you can actually change icons, fonts, and themes. If the defaults were universally good enough for everyone then developers wouldn't bother coding those settings dialogs and move on to less tedious tasks instead. But hey, if the only complaint you've got (you and many others, from what I've read here) is about colors and icons KDE must be doing pretty well.

  9. Where to improve - VOIP by arivanov · · Score: 1

    Finally improve kphone to the point where it is stable enough to live through 2+ phone calls and make it use arts instead of using the sound hardware directly.

    Even better, throw it out and start something from scratch that aims to be a good SIP phone while being modular so you can expand it with plugins to a useable Asterisk switchboard console or add codecs that cannot be GPLed (or both).

    This is possibly the only KDE app that I feel like missing when using KDE.

    Disclaimer - I have not looked at kphone for a few months now so I may be barking up the wrong tree ;-)

    --
    Baker's Law: Misery no longer loves company. Nowadays it insists on it
    http://www.sigsegv.cx/
    1. Re:Where to improve - VOIP by arivanov · · Score: 1

      One more: Software defined audio mixers.

      Currently NAS and ESD in a network environment are rather useless because there is no way to control the volume and mix correctly into NAS or ESD input on the server. Having the mixer done in software and mapping it onto hardware only if hardware is present will definitely help here. It will also allow to emulate some capabilities not present on some of the less supported hardware.

      --
      Baker's Law: Misery no longer loves company. Nowadays it insists on it
      http://www.sigsegv.cx/
    2. Re:Where to improve - VOIP by quintesse · · Score: 1

      You might want to take a look at Twinkle (www.twinklephone.com). I can't exactly say that it is a thing of beauty, but it sure works for me.

    3. Re:Where to improve - VOIP by superfebs · · Score: 1

      there's wengophone, that is QT-based and GPL. www.wengophone.org www.wengophone.com Ciao

    4. Re:Where to improve - VOIP by Rumagent · · Score: 1

      You might want to take a look at http://ihu.sourceforge.net/ It has been getting pretty decent reviews...

    5. Re:Where to improve - VOIP by andersa · · Score: 1

      arts is dead tech. Nobody in their right mind should use arts.

    6. Re:Where to improve - VOIP by caluml · · Score: 1

      Make it use SRV records too. It's annoying if your domain name A record points at a hosted box, but you want to receive SIP calls for it on another box. SRV records are supposed to do it, but KPhone doesn't use them. Gah.

    7. Re:Where to improve - VOIP by jZnat · · Score: 1

      Exactly. ALSA for the win nowadays.

      --
      'Yes, firefox is indeed greater than women. Can women block pops up for you? No. Can Firefox show you naked women? Yes.'
  10. No flame please by bookstack · · Score: 2, Insightful

    It would be annoyed to see another flame between KDE, GNOME, XFCE, *box, FVWM, E17, WM, ... Shall we just focus on KDE, buddies ?

    1. Re:No flame please by Anonymous Coward · · Score: 1, Funny
      Shall we just focus on KDE, buddies ?

      Sure thing buddy; it sucks major ass which is why we all use XFCE instead.

      HTH

  11. KDE Possible Improvements by linguae · · Score: 5, Informative

    I was a KDE user on FreeBSD before I bought a Mac a few months ago. I was generally very happy with my KDE experience, and they seemed to have done a great job with their desktop. There are a few complaints that I've had:

    1. All of the themes look too "plasticky" and fake to me. You may find this very strange coming from a OS X user, but compared to OS X's Aqua or the Windows Classic theme (or even GNOME's themes), the KDE themes just don't feel right to me. I want something either a bit more serious (like Windows Classic) or something that does a great job with fanciness (like Aqua or even Vista's Aero). The KDE themes aren't terrible, but they can use some more work. I am also somebody who spend hours on web sites finding alternate themes, either; I call that a waste of time that can be better spent actually doing work.
    2. Now that I've been using OS X for an extended period of time, I can't live without Expose and Spotlight now. Expose is easily doable; I've seen GNOME and KDE clones of that feature. A clone of Spotlight is much harder; the closest thing that I've seen to it is Beagle. I'll like to see an effort to introduce something like Spotlight or even the long-delayed WinFS to the Linux world. Heck, I may strongly consider contributing to such a project.
    3. This page describes a few more complaints that I have about KDE. As an ex-Windows user (I dual-booted between FreeBSD and Windows XP), I like toolbars (I was upset with the Office 2007 ribbons because operations that used to require just one click on the toolbar may require two or three clicks, and there is no customizability). However, there is a such thing as too many default toolbars and too many options on the screen, which I notice in KDE applications. Many OS X applications handle access to features with Inspectors, which are dialog boxes that contain all of the main functionality of a program stored in tabs. The toolbar is only used for very commonly-used operations. Whenever I get to work, I just want a good-sized window to work with, along with a toolbar that contains some commonly-used operations. I don't want my workspace to be hidden by gobs of menus, toolbars, and other options. However, I don't want my functionality compromized either. Inspectors are a nice way of handling this. KDE can improve in this regard.

    Those are my only complaints about KDE. KDE is a very nice desktop environment. These improvements will make it the perfect desktop environment for me, and a serious contender to GNOME, Windows, and OS X for most other users. Keep up the good work.

    1. Re:KDE Possible Improvements by oever · · Score: 1

      Heck, I may strongly consider contributing to such a project.

      Why don't you check out Strigi? It's written in C++, runs as a background daemon, can index files recursively and is light on your RAM.

      Here's an ODP presentation (pdf) about it.

      --
      DNA is the ultimate spaghetti code.
    2. Re:KDE Possible Improvements by Anonymous Coward · · Score: 0

      > All of the themes look too "plasticky" and fake to me.

      KDE is like the guy from that kids program starring the girl with the pink hair. I know this show is prime viewing material for all slashdotters, so nobody needs to pretend they haven't seen it. KDE artwork and 'feel' reminds me of the irritating, blue lycra wearing, sporty super hero prick. The cool in that program is the villain who wants everyone to relax with some comfort food before they all drop dead from over-exertion. That's what KDE needs, less of the uptight and klean-kut and more of the self-depreciating, mischievous sloth. Basically they should recruit some of the more inventive slashdot trolls. caveat emptor.

    3. Re:KDE Possible Improvements by Anonymous Coward · · Score: 0
    4. Re:KDE Possible Improvements by lakeland · · Score: 1

      I've got something called 'Kerry' in my KDE desktop. I haven't looked at the source so I don't know exactly what it is doing, but I know it is based on Beagle and from a user's perspective appears to do much the same as spotlight does on a mac. It is a fair bit slower than I remember spotlight being - takes roughly 5s for a search of a few gigs of data (all fully indexed). It correctly indexes quite a number of document types including HTML and PDF. It claims to do "Office Documents, Conversations, Images and Media" too...

      Also, it's interface is not as good as spotlight's - it tries to be its own application rather than a little widget in the background.

      Still, I would say it is a decent enough clone - certainly not a missing feature.

    5. Re:KDE Possible Improvements by bcmm · · Score: 1

      So, basically you want KDE to be more like MacOS X? You could try using the Baghira theme and running KDE in XGL.

      --
      # cat /dev/mem | strings | grep -i llama
      Damn, my RAM is full of llamas.
    6. Re:KDE Possible Improvements by jsebrech · · Score: 1

      You can't solve usability issues by changing to a different theme. it's a common mistake in open source crowds to think you can. Usability relates to the fundamental structure of a gui, not to it's style. Trying to solve usability issues in kde by using a mac theme is like trying to solve the acceleration issues in a yugo by painting it neon blue and sticking a "turbo" sticker on the back.

    7. Re:KDE Possible Improvements by jZnat · · Score: 1

      Kerry is a Beagle front-end.

      --
      'Yes, firefox is indeed greater than women. Can women block pops up for you? No. Can Firefox show you naked women? Yes.'
    8. Re:KDE Possible Improvements by Spliffster · · Score: 1

      i have been a kde user since ~97 (can't remember exactly, however pre 1.0 versions). All your complaints are really solved/fixed in gnome, this is where i have settleded. it offers the stuff i really need on a daily basis right in front of my eyes, all the more complex tasks are eighter reachable trough menues/keyboard-shortcuts.

      As a OS X user, you'd be surprised that former apple employees designed and started gnome to bring a "mac" experience to the *nix desktop.

      Cheers,
      -S

    9. Re:KDE Possible Improvements by bcmm · · Score: 1

      I wasn't addressing the usability issues. I was offering an answer to "All of the themes look too "plasticky" and fake" and the need for a good "expose" type feature.

      --
      # cat /dev/mem | strings | grep -i llama
      Damn, my RAM is full of llamas.
  12. MOD PARENT FUNNY by Geoffreyerffoeg · · Score: 2, Funny

    Come on, guys. Troll? RMS has been arrested twice because he has been mistaken for Osama Bin Laden ... RMS has always been found to not be Osama Bin Laden .... is just one of the gems in this mess of meta-troll.

    1. Re:MOD PARENT FUNNY by goarilla · · Score: 1

      i must agree this was very very funny

    2. Re:MOD PARENT FUNNY by Anonymous Coward · · Score: 0

      Yep, I've got to agree with your agreement. I just read it. Maybe the "-1" was from someone who forgot the Ritalin today? Zing Zoom, bad Linux == Troll, Zort!!

      I'd try to mod it myself but I've been reading Slashdot since long before the whole login / mod system came into existence and I'm not about to change.

  13. s/Congratulations/Kongratulations/ by Mateo_LeFou · · Score: 1

    (OB)

    --
    My turnips listen for the soft cry of your love
  14. Presents? by nutshell42 · · Score: 5, Insightful

    Couldn't /. celebrate the birthday by finally replacing the old (as in 10 years old) logo with the new (as in 5 years old) one?

    --
    Don't think of it as a flame---it's more like an argument that does 3d6 fire damage
    1. Re:Presents? by MarkRose · · Score: 2, Insightful

      I propose a new tag. If everyone were to tag this article and others with 'oldicon' as needed, perhaps the editors will get around to updating old icons.

      --
      Be relentless!
    2. Re:Presents? by Anonymous Coward · · Score: 1, Insightful

      I propose a tag: "tagssuck". Honestly, they've done basically nothing with them, and I'm so sick of seeing every story tagged "yes,no,maybe,fud,notfud"

      You still can't search stories for a tag. This is not hard to do. It just requires some motivation, someone in the paid slashdot staff to actually care about slashdot.

  15. I just tried Kubuntu for the first time... by realmolo · · Score: 1

    I had installed plain-old Ubuntu a few months back, and was fairly impressed.

    But Kubuntu....well, it sucks. The interface is cluttered as hell. I actually had a couple of apps FREEZE, which I've never seen before. It's slower than Gnome on my machine. File management is goofy. The themes are ugly. And, honestly, it seems to me that most of the cooler applications are written for Gnome/GTK, and don't fit in very well under KDE.

    I was suprised at how bad it was, actually. I used KDE way back when, because it was better than Gnome. But I think the tide has turned.

    Now if the Gnome guys (and KDE guys, too) could just figure out a way to have decent fonts installed by default, with the correct anti-aliasing and hinting. I *hate* all the screwing around you have to do to get fonts to look good on Linux. It's retarded. Everything else is a few clicks away, but to get fonts looking good you have to hand edit multiple config files.

    1. Re:I just tried Kubuntu for the first time... by osi79 · · Score: 1

      > Now if the Gnome guys (and KDE guys, too) could just
      > figure out a way to have decent fonts installed by
      > default

      Well, KDE nor Gnome create or package fonts, so this is up to the distros. The only thing KDE and Gnome can do (or their respective UI toolkits) is ot render the fonts nicely. And even that is mostly business of freetype (who can't implement all the good algorithms due to patents).

    2. Re:I just tried Kubuntu for the first time... by Chaffar · · Score: 1

      I had the same problem with Kubuntu, and promptly uninstalled it in favour of Vanilla Ubuntu... However, when I had to get a new PC I thought to myself "let's give Kubuntu another look, maybe it just needs some getting used to"... and I've learned to enjoy it ^^, and now prefer it to Ubuntu ^^ But I must also admit that it probably isn't the best implementation of KDE you will find...

    3. Re:I just tried Kubuntu for the first time... by kcsmith · · Score: 0, Flamebait

      You are just as bad as most windows users trying out linux for the first time. Just because things don't work the way they are used too they throw a fit. I find this rather annoying, and your comments make it seem like you tried out KDE for at most 5 minutes.

      I know a few hardcore gnome users, that have recently converted too using konqueror as a filebrowser and Amarok as there audio app, so your comment about the filebrowsing and 'cool' apps seems like flamebait too me.

      BTW you are probably used too the gnome way of handling things (ie reducing functionality), because installing new fonts was simple for me. I just went into Control Centre (kcontrol) and went too the fonts section. From there I browsed too my windows partitions fonts and installed all of the fonts. No hassles, worked straight away.

    4. Re:I just tried Kubuntu for the first time... by Keichann · · Score: 1

      All I ever had to do to get Ubuntu looking right (particularly firefox):

      ln -s /etc/fonts/conf.d/autohint.conf /etc/fonts/conf.d/40-autohint.conf
      ln -s /etc/fonts/conf.d/sub-pixel.conf /etc/fonts/conf.d/41-sub-pixel.conf

      Yes, this should be done by default.

    5. Re:I just tried Kubuntu for the first time... by hobo+sapiens · · Score: 1

      I recently made the mistake of installing kubuntu in addition to my ubuntu DE. Of course, I could use ubuntu instead, but I could not get rid of the stoopid K(r)apps.

      The worst thing, though, are all of the stinkin settings. Yes, settings are nice and all, but must we go overboard? Do I really need a context menu on EVERYTHING? I mean, I just move my mouse around the screen and menus and popups just mushroom from everywhere. Come on, now.

      I opened the sound controls, and I got a window three times as wide as my screen with volumn sliders for all kind of stuff I never even knew existed. Yeah, ok, so it was interesting seeing all of the channels/devices, but am I ever going to use those? Or are they just clutter preventing me from getting to what I really need? I'd say the latter.

      It's kind of like the difference between Microsoft and Apple. Think iTunes vs Media player. iTunes has fewer options, but the ones that are there are the ones I normally want. Media Player has settings on top of settings on top of settings (like Media player's Options dialogue box), most of which I will never need and many of which could allow me to make conflicting settings. I get that same feel from KDE. A well intentioned attempt to provide lots of functionality comes off as extremely cluttered.

      I guess what I am saying is this...KDE looks pretty nice (subjective, I know). It would be awesome if they would just make better choices on what is configurable, which settings are available via dialogue boxes. If I really want to enable something wierd, I can do that via the CLI. Don't pollute the things I look at 99% of the time with things I only want to see 1% of the time.

      --
      blah blah blah
    6. Re:I just tried Kubuntu for the first time... by Anonymous Coward · · Score: 0

      Try Suse, a desktop distribution that gets KDE right. I love KDE, but Kubuntu seriously sucks. I don't know how they manage to screw KDE as they do, I think De Icaza himself must be behind its development.

    7. Re:I just tried Kubuntu for the first time... by Stimpack · · Score: 1

      Some of us like and use these options all the time, that is why we use and love KDE. I think you would be better off with Gnome.

    8. Re:I just tried Kubuntu for the first time... by Anonymous Coward · · Score: 0

      Kubuntu has serious stability issues. I don't know what the heck they did to it, but every other distro I've seen does KDE better.

    9. Re:I just tried Kubuntu for the first time... by Anonymous Coward · · Score: 0

      You obviously have not tried Redhat/Fedora recently. There is no possible way to fuck up KDE more than they manage to.

    10. Re:I just tried Kubuntu for the first time... by Brandybuck · · Score: 1

      But I must also admit that it probably isn't the best implementation of KDE you will find...

      That's for sure. I'm a huge fan of KDE, but my one Kubuntu install left me cold. I dumped it off my laptop and put on FreeBSD. I can't understand why so many Linux distros seem obsessed with mucking up KDE. Just use the plain vanilla KDE sources, add a wallpaper with the distro's logo, then LEAVE IT ALONE!

      --
      Don't blame me, I didn't vote for either of them!
    11. Re:I just tried Kubuntu for the first time... by Anonymous Coward · · Score: 0

      and I've learned to enjoy it ^^, and now prefer it to Ubuntu ^^

      That ^^ is ^^ really ^^ nice ^^

    12. Re:I just tried Kubuntu for the first time... by Polly_Morf · · Score: 0

      Kubuntus default theme is horrible. Not even close to ubuntus Gnome. The thing with KDE is that you can make it behave like you want to. The thing with gnome (i found) is to be forced using a way that works quite well. Even though it is more work to get KDE to do as you want, the final result is (at least for me) superior.

    13. Re:I just tried Kubuntu for the first time... by jZnat · · Score: 1

      Subpixel renderring is only for LCDs, so that would have to be worked around.

      --
      'Yes, firefox is indeed greater than women. Can women block pops up for you? No. Can Firefox show you naked women? Yes.'
  16. Misc GUI improvements by VanessaE · · Score: 3, Interesting
    I've been a KDE user for a while (now using 3.5.4), and have run into a few things here and there that I think really *do* need an improvement. Off the top of my head:

    • One of our machines has a TV for it's second head, but the TV is almost always turned off or displaying a movie from our DVD player. Since the TV is never used for anything but movies, KDE should be able to ignore the presence of it entirely when a new window is opened, but still let me drag an already-open window over to it if I want to.
    • From the point of view of an advanced user, there doesn't seem to be any logical reason for the Dock-Apps panel to exist. Why can't I just dock my WM/AS apps into a regular panel instead?
    • As one other user pointed out, there are a few sluggish spots here and there that shouldn't happen on a fast box like mine (AMD64x2 3800+ with 1GB RAM and Nvidia 6600). These seem to concentrate on Konqueror when it's used for file management.
    • When the Control Center can't load a settings module, it should display a warning message and tell me what to do to fix the problem, instead of just saying "Loading..." and then returning to the 'main' start screen after a couple of seconds.
    Other than these, KDE seems to do pretty well for my husband and I. I've tried several other environments (Gnome, E, Windowmaker, Afterstep, FVWM, XFCE) and KDE just had the best round-up of features for my needs and preferences.
  17. Welcome to the past by diegocgteleline.es · · Score: 5, Informative

    DCOP can already do amazing things, like opening and writing a koffice document (including commands to do things like ie: activate bold fonts and many other things)

    Do you want to send the oputput of ls -l to your IM contact via Kopete? Just do "dcop kopete KopeteIface messageContact jabber.com "`ls -l `"

    Those are the kind of things that make many people use KDE instead of Gnome BTW

    1. Re:Welcome to the past by Anonymous Coward · · Score: 5, Funny

      Do you want to send the oputput of ls -l to your IM contact via Kopete? Just do "dcop kopete KopeteIface messageContact jabber.com "`ls -l `"

      Wow. Here I'm sitting, thinking "Hmm, a suitable task for my friends Copy and Paste." And then you bring your simple and intuitive solution. Just WOW! Thank you.

    2. Re:Welcome to the past by settrans · · Score: 1

      Citing DCOP as an advantage of GNOME only takes you as far as KDE 3, since KDE 4 will use dbus just as GNOME does.

      --
      "When I wake up in the morning I piss cryptographic excellence." - Bruce Schneier
    3. Re:Welcome to the past by Anonymous Coward · · Score: 1, Informative

      How about trolling somewhere else? Gnome does NOT use dbus to any greater extent atm, in fact a recent kde3 installation probably makes more extensive use of it.. and what is dbus except dcop on steorids? tsk,tsk.

    4. Re:Welcome to the past by hauer · · Score: 1
      "Hmm, a suitable task for my friends Copy and Paste."

      Please, remind me how you select text in a terminal window without a mouse
      thanks
    5. Re:Welcome to the past by Neil+Hodges · · Score: 1
      Do you want to send the oputput of ls -l to your IM contact via Kopete? Just do "dcop kopete KopeteIface messageContact jabber.com "`ls -l `"

      This oddly reminds me of AppleScript. One more thing non-Windows OSes have over it.

    6. Re:Welcome to the past by WilliamSChips · · Score: 2, Funny

      not using KDE, that's for sure.

      --
      Please, for the good of Humanity, vote Obama.
    7. Re:Welcome to the past by Anonymous Coward · · Score: 0

      Hit Alt+Shift+Numlock and use the numberpad.

    8. Re:Welcome to the past by diegocgteleline.es · · Score: 2, Informative

      Naturally, this work was done mostly by GNOME hackers...

      Well. It was Gnome who was lacking a IPC system, not KDE. So yes, it find it sensible that the ones who didn't have it are who implemented it. In the same way, since they've lacked it for years it's reasonable that they have built a comparable competitor.

      and it was built in such a way that there are no desktop dependencies. Had it been done by KDE hackers, it would have been tied to Qt

      Bullshit. Dbus does depend on glib.

      DBUS is heavily used in recent GNOMEs

      Bullshit. Dbus usage in gnome is very light - which I find reasonable, since gnome hasn't had a IPC mechanism for most of its life. There're programs with thousand of lines of code that need to be DBUS-ified

      KDE 4 in the other hand inherits apps which all of them used DCOP for years, so the DBUS usage in KDE 4 is actually much wider than in gnome. it does have sense: KDE has had a IPC mechanism for years, so the apps were ready for the idea, gnome apps wasn't so it will take some time until they catch up.

    9. Re:Welcome to the past by Anonymous Coward · · Score: 0

      Well. It was Gnome who was lacking a IPC system, not KDE.

      GNOME has an IPC system that is a hell of a lot more capable than KDE... Bonobo. The problem was that it was *TOO* featureful and complicated... using it was a ball-ache and people did it relutantly (but they did it).

      Bullshit. Dbus does depend on glib.

      glib is not a desktop dependency. glib is a *tiny* little C library with that is LGPLed. Qt is a massive blob with a GPL license. glib/gtk/pango/atk were properly designed, with good software enginering practises in mind. Qt was designed to force people into buying licenses. Hence the reason everything in KDE is closely tied to QT.

      Bullshit. Dbus usage in gnome is very light - which I find reasonable, since gnome hasn't had a IPC mechanism for most of its life. There're programs with thousand of lines of code that need to be DBUS-ified

      You haven't got a fucking clue. See above for this "no IPC" bollocks.

    10. Re:Welcome to the past by Anonymous Coward · · Score: 0

      An IPC system that no one uses. In my book, that is equivalent to saying it doesn't have any. Sure... now you will tell me Gnome has something like KDE's KParts (Corba), and KDE's IOSlaves, that no one in the Gnome camp uses either. Oh well, now at last Gedit uses GnomeVFS.

      Oh, and the reason KDE is heavily tied into Qt is because is very good and provides them with everything they need and there's no need to reinvent the damn wheel. It was not designed to sell licenses, though I can tell you that no one in their right mind would ever pay a dime to suffer developing using the "well enginereed" GTK :-)

    11. Re:Welcome to the past by Black.Shuck · · Score: 1

      Why not just: "ls -l > filelist"

    12. Re:Welcome to the past by Anonymous Coward · · Score: 0

      An IPC system that no one uses. In my book, that is equivalent to saying it doesn't have any.

      Read the post. It was used... but people didn't like it... hence it was replaced.

      Oh, and the reason KDE is heavily tied into Qt is because is very good and provides them with everything they need and there's no need to reinvent the damn wheel.

      The reason KDE is so heavily tied to QT (not just for widgets), is that the core developers work for Trolltech. It's that simple. For years stuff has been pushed down into Qt (hence becoming Trolltech IP)... which rightfully belongs outside it. It is a bloated mess that has much in common with the bad points of Java, but without the VM advantages.

      It was not designed to sell licenses, though I can tell you that no one in their right mind would ever pay a dime to suffer developing using the "well enginereed" GTK :-)

      Clueless zealotry. There are plenty of things to hate about GTK, but the work done has all been about modularisation and good software engineering by ensuring that programs only get what they want. Qt is about selling licenses and land-grabbing IP... it's that simple.

    13. Re:Welcome to the past by a.d.trick · · Score: 1
      Those are the kind of things that make many people use KDE instead of Gnome BTW

      There is this thing used in Gnome, we call it dbus. It is replacing dcop in KDE (although a dcop style interface will be available because I've heard dbus' interface is anoying sometimes). So yeah, it's not like you can do special stuff we can't.

      P.S. I don't mean to flame KDE at all. It's a great project and it does have many nice things I wish were in Gnome, but this is not it.

    14. Re:Welcome to the past by Anonymous Coward · · Score: 0

      Except it's barely used in Gnome, if at all. DCOP has been used thought KDE for ages, since KDE 2.0

    15. Re:Welcome to the past by Anonymous Coward · · Score: 0
      Read the post. It was used... but people didn't like it... hence it was replaced.


      No, that's not true. It was not used because nobody got it, basically. It has been replaced now by DBus, which is fairly recent and of course is not being used much either, but let's be fair and give them time. The thing is, all this time Gnome hasn't been using an IPC system. Make up as many excuses as you'd like but those are facts.

      Clueless zealotry. There are plenty of things to hate about GTK, but the work done has all been about modularisation and good software engineering by ensuring that programs only get what they want. Qt is about selling licenses and land-grabbing IP... it's that simple.


      Sure... whatever. Call Qt bloated all you want, everyone's favorite buzzword that does not mean a thing. All I know is that just looking at the documentation for Qt and GTK anyone can tell which one is professional quality and which one is amateur work :-)
  18. Spotlight clone exists by rmm4pi8 · · Score: 2, Informative

    First there was Kat, which seems to be dead for unknown (personal to the lead developer?) reasons, but is still packaged by eg Mandriva, and is very useful, see its Wikipedia entry. Now its successor is Strigi which acts as KPart and KIO-slave. I don't think anyone's currently packaging it because it's pretty new, but there's no real cost to switching something like a search engine, so use Kat for now if you want it, and switch to Strigi when it becomes available for your distribution. I love the Plastik theme and the customizability of the KDE toolbars, so to each his own on that front. I think you will find that with KDE-look, you hardly have to spend hours looking for themes if you do want something different, however.

    --
    U.S. War Crimes blog. Email for free Mandriva support.
    1. Re:Spotlight clone exists by ajdlinux · · Score: 2, Informative

      Debian is packaging Strigi, I assume Ubuntu and co will follow.

  19. This is my take on KDE by bogaboga · · Score: 3, Interesting
    "We've come a long way in ten years, but where must we still improve?"

    For me, it's the two major sub-items covered under one big one: Beauty.

    • The fonts are ugly. What does it take to make KDE display beautiful fonts. I am particularily impressed by this Kdevelop image. http://kdevelop.org/graphics/screenshots/3.0/full_ ide.png. If a product is touted as significantly better technologically, it should also be a pleasure to look at.

    • They (KDE) should look at hiring a beautification expert. Xandros and Linspire should provide a hint. The point here is that KDE should be a pleasure to look at by default. Thank you.
    1. Re:This is my take on KDE by christurkel · · Score: 1

      I'll add to this: less Klutter (get it, ha! I'll be here all week, thank you). The volumes of apps included in a standard KDE desktop is just staggering plus all the eye candy turned on by default. KDE needs to be toned down and more modular.

      --

      CDE open sourced! https://sourceforge.net/projects/cdesktopenv/
    2. Re:This is my take on KDE by Cal+Paterson · · Score: 1

      If a product is touted as significantly better technologically, it should also be a pleasure to look at.

      No, no, no. This is most certainly not a requirement.

    3. Re:This is my take on KDE by Anonymous Coward · · Score: 0
      KDE is extremely modular - in fact, "KDE" itself consists of just kdebase and kdelibs, which is basically the kicker, the desktop, and a handful of apps (including, of course, Konqueror). Unfortunately, distro packagers tend to bundle everything up in to a small number of packages, leading to the "klutter" that many people complain about. It's pretty much out of their hands, unfortunately.

      Defaults are also up to the distro makers.

    4. Re:This is my take on KDE by bogaboga · · Score: 1
      No, no, no. This is most certainly not a requirement.

      Where is it mentioned that a pleaseure to look at *is* a requirement? I simply, as the subject noted, had my take on KDE.

    5. Re:This is my take on KDE by Anonymous Coward · · Score: 0

      I think the solution for your first problem is 'kerning'.

      Here is the link which will teach you how-to kern your fonts ;)

      http://alkalay.net/linux/docs/font-howto/Font.html

  20. Improvements... by Senjutsu · · Score: 1

    I stopped using KDE years ago, but does Konqueror still do that ridiculous thing where it asks you what you mean when you drag and drop a file, every single time you do so, with no option to set a default?

    As ridiculously poor user-interface decisions go, introducing extra clicks to achieve a common goal rather than defaulting to the almost universal standard of assuming a drag-and-drop means "move" ranks right up there as one of the worst I've seen.

    1. Re:Improvements... by Askadar · · Score: 1

      Funny, that is exactly one of the things I like about KDE. I get constantly annoyed by Gnome and Windows because they guess what I want to do and get it wrong most of the time. I don't want to predict how the system will behave, I want the system to ask me when in doubt!

      I guess it shows that you can never please all of the users at the same time...

    2. Re:Improvements... by caluml · · Score: 1

      I always thought that it was "move, if it's the same device, copy, if it's not". When you drag a file to a network share, do you want it to disappear locally?

    3. Re:Improvements... by Anonymous Coward · · Score: 0

      Really... it's one the KDE features I miss most when I use other environments, and I always wonder what the hell the desktop has done with my files after DnD them. With KDE's method there's no confusion. Maybe there should be an option to set a default, but then people would moan and cry "KDE is full of options! Too many features!". You can't make everyone happy.

    4. Re:Improvements... by kimvette · · Score: 1

      Yep. Depending on where you are dragging from/to, Windows assumes one of these:

      Copy
      Create shortcuts
      Move

      Unless you know the nature of the source and destination filesystems, you may not get the action you expect. With windows you can right-click, drag, then select from the context menu to force the action you desire.

      --
      The Christian Right is Neither (Christian nor right). See: Matthew 23, Matthew 25, Ezekiel 16:48-50
    5. Re:Improvements... by Polly_Morf · · Score: 0

      Now i can't really remember the exact keys, but when you drag and drop things to another folder and hold shift, it does not ask what to do. I think shift means "move", and alt means "copy", but now it was a couple of months since I used my home computer. I find this system much more appealing than the gnome one. Since nautilus is severely brain-damaged I always end up using konqueror in gnome...

    6. Re:Improvements... by Anonymous Coward · · Score: 0

      I always thought that it was "move, if it's the same device, copy, if it's not".

      On Windows boxes, that's true. It's only intuitive because Windows is very in-your-face about the underlying devices.

      On a *nix box, the Windows style would be a recipe for utter confusion. The *nix filesystem is abstracted to a single device, no matter how many drives it's really spread across. How is the user to know whether they're copying to the same device or not? If I drag something, say, from /tmp to my home directory, should the default behavior be different depending on whether /home/~ is on the same drive as /tmp or not? How would a user know which is the case?

      When you drag a file to a network share, do you want it to disappear locally?

      As above, if the network share is mounted as part of the file system, the user wouldn't know that it was a network share. It would just look like another directory. This isn't Windows; it's entirely possible that / is local, /usr is a network share, and /usr/local is local again, but a different local drive than /. The user doesn't know where the storage is, just *that* it is. See why the Windows way won't work?

      Then there's the matter of symlinks. If I drag a file from one place to another, I could copy it, move it, or create a symlink to it. Windows is confusing enough since its behavior is to copy between different devices, but move if you're dragging between folders on the same device - unless you're dragging an executable, in which case it creates a shortcut if it's on the same device. When organizing self-extracting archives, you end up having to right-drag to get the menu anyway, so you can tell it you want to move the thing, not create one of those broken .lnk shortcuts that doesn't work in file/open dialogs. After a while, I just learned to always right-drag so I'd get the menu. Why not just have the default be that the system asks what you want to do, since you end up having to ask for that menu anyway most of the time?

  21. Re:Amazing but true... by Anonymous Coward · · Score: 0

    Your mom is your neighbor?

  22. A few things by Rumagent · · Score: 1

    First of all. Congratulations. Kde has come a long way.

    Now as for things that I would like to see:

    - better integration with sites like kde-look. Why is there a "Get New Wallpapers" button and not a "Get new icons", "Get new themes" and so on. Everyone likes eyecandy (even those who claim they don't:) ).

    - Mac Spotlight 'nuff said

    - And when we are stealing from apple: why not read http://developer.apple.com/documentation/UserExper ience/. These people are know for the usabilty of their os and applications. Why not learn from them? There is ample room for improvement.

    - Some way to easily steal extensions from firefox and import them into konq. (I like kde, but no way in hell I'm giving up ff).

    - Enough with the K crap, please

    - One toolbar per application. Kile (a nice app none the less) is a scary example of not getting the idea of a toolbar.

    - XGL + KDE. Is it at all possible?

    - KDM shutdown picture (the lightning thing) is horrible.

    Thats it. I am really looking forward to kde4.

    1. Re:A few things by bcmm · · Score: 1

      I use KDE on XGL, with only a few problems. For the moment, you can't use kwin, but you can theme cgwd to look a lot like various kwin themes. For some reason, the taskbar applet for switching virtual desktops doesn't work properly. A few keyboard shortcuts are broken, mostly because compiz uses them for something else. Other than these problems, it works fine for me. The Gentoo Wiki has some good instructions, some of which will apply to other OSs too.

      --
      # cat /dev/mem | strings | grep -i llama
      Damn, my RAM is full of llamas.
    2. Re:A few things by Rumagent · · Score: 1

      Ok, I'll give it a try. Can I mail you if I get stuck?

    3. Re:A few things by bcmm · · Score: 1

      Am I expected to put my email address on Slashdot, of all places? ;-)

      Use your journal. Or something.

      --
      # cat /dev/mem | strings | grep -i llama
      Damn, my RAM is full of llamas.
  23. Rookies by BeeBeard · · Score: 1

    CP/M-80 with ZCPR for the win.

    And yes, I still have my Kaypro II.

    1. Re:Rookies by Nutria · · Score: 1
      And yes, I still have my Kaypro II.

      I'd have never graduaded University without WordStar, the KayPro II and it's beautifully clear green screen.

      Still, that's comparing a hopped-up Datsun B210 to a Mercedes 300D.

      The Datsun is certainly nice and functional, but can't beat the MB.

      --
      "I don't know, therefore Aliens" Wafflebox1
  24. KDE -- you are the best! by Kesha · · Score: 1

    Happy Birthday KDE! I love you!

    Where I would like to see you improve -- Please, Please Please implement support for OSX style application bundles -- it would make it so much easier for me easier to make easily distributable packages for you if you would support them.

    Don't pay attention to the clueless dorks who are suggesting that you should switch everything from C++ to something else, use GTK libs or reimplement everything to be a GUI front end to CLI commands -- those are incredibly bad ideas. You are pretty much perfect the way you are (especially on openSUSE). Next steps should be to make yourself more accessible for non-core Qt/KDE developers. Adding support for a flexible packaging scheme like the bundles used on OSX would go a long way towards that.

    Paul.

    1. Re:KDE -- you are the best! by jmt(tm) · · Score: 1
      Please, Please Please implement support for OSX style application bundles

      Like, uhm, klik?

    2. Re:KDE -- you are the best! by Anonymous Coward · · Score: 0

      "Don't pay attention to the clueless dorks who are suggesting that you should switch everything from C++ to something else, use GTK libs or reimplement everything to be a GUI front end to CLI commands -- those are incredibly bad ideas. "

      Don't worry... I don't think they are so stupid to throw away the best Free Software development platform that exists, after all they've worked to build it, and replace it with that ... that... thing known as GTK ;)

    3. Re:KDE -- you are the best! by Pseudonym · · Score: 1
      Don't pay attention to the clueless dorks who are suggesting that you should switch everything from C++ to something else, [...]

      On the contrary, it would be enough if KDE did switch to C++.

      At the moment, it uses a bastardised dialect of C++ which doesn't support exceptions. This makes combining KDE with just about any other ISO C++-compliant library (Boost being but the most obvious) in the same application impossible.

      From this C++ developer's point of view, it's the most important fix, and it won't be easy. It means that when I write an application, I have to choose between writing it in C++ or writing it for KDE, and I have to check all of the third-party libraries I want to use to use to make sure they're obsolete enough to work with KDE.

      --
      sub f{($f)=@_;print"$f(q{$f});";}f(q{sub f{($f)=@_;print"$f(q{$f});";}f});
    4. Re:KDE -- you are the best! by Kesha · · Score: 1

      It's strange to hear you say that KDE doesn't use exceptions -- that's the first time I hear of it. Do they disable exception handling at compile time in their libraries? I uses exceptions all the time in my multi-threaded Qt based code -- works great. Are you sure this isn't a distribution/packaging/build-time issue?

              Paul.

    5. Re:KDE -- you are the best! by Pseudonym · · Score: 1

      I know that KDE libraries, as packaged on every distro I've seen, have exceptions disabled. This means you can't link to them with exception-throwing code. (The GNU linker knows it's a disaster waiting to happen.)

      I'm surprised to hear you say that you use exceptions in your Qt code. You must be using a fairly recent version. The Qt source itself, last time I checked, is full of such leaky code as:

      QThing* thing = new QThing();

      Most of the KDE source looks like that too. It doesn't help that Qt's exception safety is poorly documented and is not obvious from the interface. (Ten years ago it made sense, but today, no method should take ownership of a raw pointer unless that method is a managed pointer constructor.)

      The problem may simply be that KDE was designed for a previous incarnation of Qt, Qt has improved but KDE hasn't gotten with the programme yet. I get the impression that a lot of KDE developers think that way; I was informed not too long ago that Qt is "an alternative to the standard library", the implication being that you probably shouldn't use the STL in Qt code.

      --
      sub f{($f)=@_;print"$f(q{$f});";}f(q{sub f{($f)=@_;print"$f(q{$f});";}f});
  25. Look at Vista for inspiration? by Futil3 · · Score: 2, Insightful

    As I tried out Vista a couple of months ago I became rather fond of some of the (for windows) new features. I would love to see some of them implemented in Gnome/KDE/Ubuntu/linux in general;

    Instant searches and dynamic stacking of files. A constantly indexed system *cough*spotlight*cough* that lets you create dynamic stacks. Stacks behave like folders - you can browse a stack for instance - but have no physical location on your drive. This combined with instant searches from anywhere in the OS, gives you the ability to generate "directories" sorted on basically any kind of index. If you create a stack of every file in the system created since a given date it would stay updated in real time!

    Searches that include the entire system. Search for "resolution" and you'll not only get files, but also info on how to set the desktop resolution, and links to the settings page.

    Per-network settings. The system remembers networks you connect to, and lets you define custom settings for each network. You want your firewall disabled when connecting at home, but back on when you connect from school? No probs.

    Quick swapping of pre-defined (configurable) power settings will let you avoid your laptop going to sleep in the middle of a presentation. I would like a built-in application for power control that allows me to set not only the standard options of HDD spindown and screensaver - but also a detailed control over advanced settings like core and memory voltages, CPU clocks, WLAN output effect and so on.

    1. Re:Look at Vista for inspiration? by Ash-Fox · · Score: 1
      Instant searches and dynamic stacking of files.
      Beagle, Kilo, that instant search thing on Konqueror. Seem fine to me.
      Searches that include the entire system.
      I think Beagle is capable of doing that.
      Per-network settings.
      Problem is, many distributions have their own network management tools, some of which support which you ask.
      Quick swapping of pre-defined (configurable) power settings
      I've seen such a taskbar program in Mandriva that replaces klaptop, but I can't remember the name of it.
      --
      Change is certain; progress is not obligatory.
    2. Re:Look at Vista for inspiration? by Ash-Fox · · Score: 1

      Sorry, Kilo should be Kerry.

      --
      Change is certain; progress is not obligatory.
    3. Re:Look at Vista for inspiration? by Overly+Critical+Guy · · Score: 2, Informative

      Every one of those features is originally from Mac OS X, not Vista.

      --
      "Sufferin' succotash."
    4. Re:Look at Vista for inspiration? by BlueLightning · · Score: 1

      A lot of the things you mention are coming in KDE 4. In particular the system-wide searching (Kerry/Beagle, Strigi, etc.) and hardware / system integration through Solid, such as not doing silly stuff like power saving in the middle of a presentation, and network profiles.

  26. Dock by RAMMS+EIN · · Score: 1

    One of my pet peeves is the taskbar. Having long textual descriptions on the buttons for open windows is fine when you have only a few windows open, but gets problematic rather quickly. Putting two layers of buttons over one another is not a good solution, as the top layer takes a lot longer to reach (Fitt's law). Moving the taskbar to the side of the screen helps somewhat, but results in the window buttons being rather too small.

    The right way to solve this, IMO, is to use icons, just like NEXTSTEP and its descendants (WindowMaker, OS X, etc.). I know there is kxdocker, but last time I tried to use it is was unstable like nothing I've ever seen before, and it doesn't play together with the KDE dock very well (as in, not at all).

    For the rest, I find KDE a very nice desktop environment (and have since 3.1), although I must admit that desktop environment aren't really my thing; I prefer ratpoison, uxterm, and screen.

    Special kudos go to Konqueror; it's my favorite browser, because it's both fast and featureful. I can't comment on its qualities as a file manager; I never use it as such, and, frankly, I'd probably sleep easier if that functionality were moved into a separate program. Still, it works great as it is.

    --
    Please correct me if I got my facts wrong.
    1. Re:Dock by ErikZ · · Score: 1

      Actually, the best way to solve this is to put the start bar on the right or left side of the screen. The buttons only change width, not height. And you can stack many more open tasks/windows/programs that way.

      Works great in Windows. KDE and Gnome? Functional but could use some work. OSX? Heh. For reasons of backwards compatibility they have to keep that awful bar on top.

      --
      Democrats or Republicans. They are both taking us to the same place and they are not afraid of us anymore.
    2. Re:Dock by Anonymous Coward · · Score: 0

      KDE has a panel called Kasbar, which is a clone of the NeXTstep icon thing you describe. Right click the panel, choose Add New Panel - Kasbar, and you can kiss that gargantuan Windows-style taskbar goodbye.

  27. KDE problems, fixed by BeeBeard · · Score: 2, Informative

    It's funny how most of KDE's critics just have no idea what they're talking about, and haven't even used KDE long enough to know how to fix any of the "problems" they have with it. All of your issues with KDE are easily fixed. Watch:

    The fonts are ugly.

    Font anti-aliasing isn't even enabled in the screenshot you linked to. That's a very easy fix. Control Center --> Appearance & Themes --> Fonts --> Tick "Use anti-aliasing for fonts". The difference will be dramatic. Everything will look beautiful after that. In fact on my main box, the fonts in KDE with anti-aliasing turned on look much better than the fonts in Windows XP with font smoothing/Cleartype turned on. I kid you not.

    The interface by default, is full of huge buttons wasting screen real estate.

    Again, I can tell you haven't actually used KDE. Otherwise, you might know that the little perforated area on the left of the toolbars in that screenshot let's you easily drag the toolbars to where you want them. If that's not good enough, you can right click on the buttons and customize the toolbars that way. In fact, in my own setup, I have those two toolbars combined into one.

    They (KDE) should look at hiring a beautification expert. Xandros and Linspire should provide a hint.

    This gave me a little chuckle. You see, both of those distros ship their own KDE theme on top of ordinary, run-of-the-mill KDE. So what you've basically just said is that you like the default KDE themes for those distributions. That's why KDE is themeable in the first place, just like Windows, Gnome, and pretty much everything else--there is this understanding that all users might not like the same color schemes and graphical changes. KDE allows for plenty of different ways of customizing what you see. In fact, I daresay you can change pretty much everything you see. My own desktop looks very OS X-y because I spent about 5 minutes making it look like that. If you're not willing to invest the same amount of time into making KDE look better, than why do you have all this free time to complain about how it looks?

    1. Re:KDE problems, fixed by bogaboga · · Score: 2, Insightful

      I think a I mentioned that KDE should be a pleasure to look at by default. I wonder whether its default look satisfies anyone. Do you know?

    2. Re:KDE problems, fixed by Overly+Critical+Guy · · Score: 3, Insightful

      Users shouldn't have to fix someone else's broken interface. Telling someone to go to "Control Center --> Appearance & Themes --> Fonts --> Tick 'Use anti-aliasing for fonts'" or tear off all the toolbars to get them out of the way is just stupid.

      --
      "Sufferin' succotash."
    3. Re:KDE problems, fixed by Anonymous Coward · · Score: 0

      The interface by default, is full of huge buttons wasting screen real estate.

      Again, I can tell you haven't actually used KDE. Otherwise, you might know that the little perforated area on the left of the toolbars in that screenshot let's you easily drag the toolbars to where you want them. If that's not good enough, you can right click on the buttons and customize the toolbars that way. In fact, in my own setup, I have those two toolbars combined into one.


      Just yesterday I was trying to tweak Konqueror so I could begin using it instead of Mozilla. First thing I wanted was the "Location" bar in the "Main toolbar". Guess what? That's not quite so trivial to manage. I did it, but only after searching and finding out that "Location" can only be in one toolbar, so I had to remove it from the Location toolbar and add it to the Main toolbar. Then I wanted the icons on the right side removed, and I had to edit the "khtmlpart" toolbar to fix those, even though it is the Main toolbar that is in the Toolbars menu.

      Then came fonts: Select a higher minimum font size (from 7 to 10), and fill in fonts for Serif, Sans Serif, Fantasy, Cursive, etc., and only then did it look useable.

      So yeah, I agree with GP: KDE is slick and can be made what I want, but the defaults aren't quite right and should be fixed.

    4. Re:KDE problems, fixed by zsau · · Score: 2, Interesting
      It's funny how most of KDE's critics just have no idea what they're talking about, and haven't even used KDE long enough to know how to fix any of the "problems" they have with it.

      That basically is my problem with KDE. There's so many ways to fix just about every problem with it that to work it out, you have to spend ages searching. But some problems which I haven't yet worked out the solution to:
      1. OK/Apply/Cancel. Having used GTK and OS X based apps for so long, I forget to do this. I won't ever use a desktop environment that doesn't automatically apply preference changes. Can I do that in KDE?
      2. Open folder in new/same window. I like to browse the filesystem with new folders opened in new windows most of the time, but occasionally I want them opened in the same window. Just about every other file manager I've used lets you do this by Button-1 for new window and Button-2 for same/replace window. But KDE uses Button-2 for a new tab.
      3. Too many menus! Like the problem with preferences, there's just too many menus. My view is that if you have so many menu items you can't fit them all comfortably on a right-click menu, you've probably got too many. One program should do one thing, well.
      4. Customising shortcut keys. It's possible to customise shortcut keys from some central control panel, but with GTK+ you can customise them just by hovering over the relevant menu option in the window and press the key you want. This is an incredibly useful feature, and I'm sure KDE has it, I just don't know how to enable it.
      5. The open & save dialogs. Big and ugly. At least they don't try to be a file manager like Windows ones, but they're missing important features from the ones I like. Like existing at all (my favorite ones just let me use drag-and-drop and that's about it), or letting me drag a file into the Save As/Open dialog box and then switching to the containing folder so that if I can quickly save a file into a folder I'm already looking in--why should I have to browse to the same place twice? (or frequently more, if you're regularly using a save as dialog that keeps defaulting to the wrong place). Actually, if it had this feature, then the fact that they're 'big and ugly' wouldn't bother me at all, it'd just provide a bigger drop target :)
      6. Complexity. You have to spend 'long enough to know how to fix any of the "problems" they have with it'

      I have other issues I think, but aside from Konqueror, I haven't used KDE recently.

      In any case, I'm really happy with my current DE and I'm not really thinking of using KDE. But considering your comments to your PP, I thought I'd see what your opinion was on some of my problems.
      --
      Look out!
    5. Re:KDE problems, fixed by BlueLightning · · Score: 1

      The default look satisfies me, so that's at least one. I'm sure it could be improved but it's not that bad at the moment.

    6. Re:KDE problems, fixed by BlueLightning · · Score: 1

      I'll answer the ones I can answer:

      1. Just click OK. It's not that difficult. If you close the dialog or click Cancel you're telling the application you aren't sure of your changes.

      4. Most (if not all) KDE applications have Settings -> Customise Shortcuts. This will let you customise all of the shortcuts for the application. I admit, being able to do it from the context menu on a toolbar button would be nice though.

      5. Well, for me the open/save dialogs are a hell of a lot better than those you find in GTK+ applications, because they're far more flexible.

      6. For me, KDE's integration and consistency far outweigh any minor "problems". In all honesty though it sounds like the Gnome style of sparse options is more suited to your tastes, so you should probably stick with it (I'm assuming that's what your current DE is).

    7. Re:KDE problems, fixed by Blakey+Rat · · Score: 2, Insightful

      I guess you missed the part where he said "by default."

      The offense is even worse if KDE is technically capable of better, and yet is set to look crummy by default. What are the developers thinking?

    8. Re:KDE problems, fixed by DandyRandy · · Score: 1

      IMHO, default KDE is just plain ugly.

    9. Re:KDE problems, fixed by zsau · · Score: 1

      1. Just click OK. It's not that difficult. If you close the dialog or click Cancel you're telling the application you aren't sure of your changes.

      Doesn't solve the problem. Doesn't provide an easy way to test and revert a group of changes. The KDE Control Centre requires that you apply changes to individual sections, rather than everything at once, and this only makes it worse. (If you have to put in a nasty reminder like 'you haven't applied your settings yet. do you want to?', you've probably designed the interface wrong.)

      5. Well, for me the open/save dialogs are a hell of a lot better than those you find in GTK+ applications, because they're far more flexible.

      I don't want a flexible open/save dialog; I don't want to have to browse the filesystem a million times. I should be able to easily switch to a directory I already have open somewhere else. GTK+ gives me this. KDE doesn't, but should. This is an unsolved problem. (Being a big huge flexible dialog is not a cost in any way, so long as it's not fullscreen so I can use DnD on it properly, so the KDE dialog could be made perfect for me without any cost to you. I like the GTK+ because it has some functionality the KDE one doesn't have, not because it's simple and hides everything.)

      6. For me, KDE's integration and consistency far outweigh any minor "problems". In all honesty though it sounds like the Gnome style of sparse options is more suited to your tastes, so you should probably stick with it (I'm assuming that's what your current DE is).

      I don't use and don't much like Gnome; and almost every Gnome application I use I've gone into gconf-editor to modify. But KDE otoh has way too many poorly organised options, so it's hard to find what I want. Every time I've tried KDE, I've found something I couldn't work out how to do last time can be done, usually quite easily. Maybe it even makes perfect sense to put the option there—once you know where it goes. But it still takes way too much time to find the first time. (Finding the right setting to tweak is usually easier in gconf-editor than KDE programs in my experience, because in gconf you've only got two dimensions to search through, and good applications put in detailed descriptions.)

      I've heard many great things about KDE's architecture, integration etc. and I've wanted to try it, but it makes the things I can already do harder. Every time I have, sooner or later I've reverted to my preferred environment, because there's things I can't do (either because I can't work out how to, or because it doesn't work that way).

      --
      Look out!
    10. Re:KDE problems, fixed by Reziac · · Score: 1

      "I won't ever use a desktop environment that doesn't automatically apply preference changes."

      Conversely, I won't use one that DOES automatically apply preference changes -- because it is FAR too easy to make a mistake you can't readily recover from (like setting text and background to the same colour). I want some sort of "Hey stupid, did you really mean Do THIS?" query *before* changes are applied, just in case That Wasn't What I Meant.

      Right-click menus that are too long can be helped with grouped submenus. I don't recall seeing this as an issue with KDE, but it's been a while since I looked.

      IMO "Open Folder in Same Window" should be the default, not something you have to set. Most people simply want to navigate the dirtree, not wind up with 50 open windows.

      Speaking of view settings, I don't know if this has been fixed since my now-ancient MDK7 setup, but many settings simply don't STICK. I got really tired of having to select View As Details EVERY time I used Konq.

      Re the Save As reverting to the origin location, I'm frequently annoyed by that too. I think "switch to New Default Save directory" (like WordPerfect 5.0 could do in 1988!) would be a good context menu item.

      Better yet, let me add Save Location on the fly, and pick the desired one from the context menu. I often open an image from a CD, save a basic edit in one location, and save a further edit in some other location, and it'd be nice to just pick the Save directory on the fly, and not have to navigate back and forth each time.

      --
      ~REZ~ #43301. Who'd fake being me anyway?
    11. Re:KDE problems, fixed by zsau · · Score: 1

      Conversely, I won't use one that DOES automatically apply preference changes -- because it is FAR too easy to make a mistake you can't readily recover from (like setting text and background to the same colour). I want some sort of "Hey stupid, did you really mean Do THIS?" query *before* changes are applied, just in case That Wasn't What I Meant.

      A good user interface will make it hard do something stupid. Not impossible, not getting-in-your-way hard and not hard-to-find. More like riding-your-bike-uphill-against-the-wind hard than where've-I-left-my-keys hard. It'll also make it easy to recover from a stupid change (instant apply dialogs have a 'revert' button (and the thing you changed is probably right under your mouse, too!), but manual apply ones don't. so if you don't realise you've done something stupid, you choose 'apply' (or worse 'OK'), and goodbye to any hope of easily recovering). And instant apply isn't incompatible with warning the user they're about to do something stupid.

      And lastly, isn't KDE meant to be the world of infinite configurability =)

      Right-click menus that are too long can be helped with grouped submenus. I don't recall seeing this as an issue with KDE, but it's been a while since I looked.

      Not what I meant. I was meaning that the maximum number of menu items in a program in total (i.e. including the main menu bar) should be what you can comfortably fit on a right-click menu (with submenus if necessary, but obviously fewer because it becomes harder to navigate). This implies, with good reason, that programs should be small and do one thing well. Not having a filemanager and a web browser in the same program (I never worked that one out, meself.)

      IMO "Open Folder in Same Window" should be the default, not something you have to set. Most people simply want to navigate the dirtree, not wind up with 50 open windows.

      I don't mean to be negative, but not what I meant. I want to be able to do both, with my mouse, without right-clicking and choosing a special option. I have never wanted to use a tabbed file manager. I would like Button-1 to open in a new window, and Button-2 to open in the same window. I would settle just as easily for the reverse. But KDE can give me Button-1 in a new window or the same one; but Button-2 always opens in a new tab.

      Re the Save As reverting to the origin location, I'm frequently annoyed by that too. I think "switch to New Default Save directory" (like WordPerfect 5.0 could do in 1988!) would be a good context menu item.

      Probably my fault, but not what I meant either. Save As dialogs will almost always pick the wrong folder unless you store everything in "c:\documents and settings\zsau\my documents", which I don't. But I probably have the write folder open in my file manager--I want a way to quickly make the save as dialog point to where my file manager is, without having to browse the filesystem.

      Your suggestion of a context menu would get very unattractive in my circumstance. I'd have ~/Projects/{foo,bar,baz,splat}, ~/UNI/{splodge,quux,quuux,quinx}, ~/{aargh,chicken,antelope,cantaloup} and so on. It could save number-of-clicks, but increase search time (bizarrely, search time in humans seems to be O(n)—even if we're looking for what happens to be the third item in a list, it takes us longer to respond if the list is one hundred items than if it's five).

      --
      Look out!
  28. continuous session saving by darkwhite · · Score: 1

    "We've come a long way in ten years, but where must we still improve?"

    Continuous session saving. KDE already saves session state on logout. Now the API for doing this should be changed so that each application saves its state not only on logout, but on every change (with several seconds' delay so as not to overload I/O).

    --

    [an error occurred while processing this directive]
  29. pithier by wonkobeeblebrox · · Score: 1

    "KDE Celebrates 10 Years of Existence"
     
    ...don't we call that sort of event a birthday? Original wording seems, kinda... well... wordy....

    ...we could be pithier and simply state:
    "KDE turns 10"

  30. proper mouse button support would be nice by Blymie · · Score: 1

    As per this 5 year old bug, proper mouse button support would be nice. Hacks are not very user friendly, as the whole POINT of KDE is that an end user isn't going to have to monkey with something like imwheel. Heck, 7 button support has been in Window Managers like Sawfish for 7+ _YEARS_. I'm not quite sure why this isn't implemented, but it sure as hell isn't because of QT.

    http://bugs.kde.org/show_bug.cgi?id=34362

    I wonder about a recent bug I found.. about three months ago, about applications not showing on iconification when also shaded, in the tasklist. The bug report I found was about three years old.

    My point? Usability means that perhaps you should deal with usability bugs. I have KDE set up for my parents. Trust me, when they iconify an app that happened to be shaded, they don't know to use ps to find it and kill it. They don't know about alt-tab. They just think it crashed.

    1. Re:proper mouse button support would be nice by BlueLightning · · Score: 1

      applications not showing on iconification when also shaded

      Interesting, I had never noticed that - but to be honest, shading is a feature that I have never thought was particularly useful. In your parents' case I would suggest changing the double-click behaviour so that they never use the shading by accident (which is the only way I ever used to activate it) and then they'll never run into the problem.

      To be fair, KDE has a much greater usability focus now than ever, and usability bugs do get fixed. Perhaps the particular ones you mention have just been forgotten - if nobody else has, perhaps you could add a comment mentioning that the bug is still present in which ever version you are using.

    2. Re:proper mouse button support would be nice by s2jcpete · · Score: 1

      I'm using 3.5.1 level "a" in opensuse 10.1, and didn't have a problem with shade / iconify making my window disappear. I would have lost this post otherwise :)

  31. Happy birthday by xming · · Score: 2, Funny

    Kongrats

  32. Learn from MacOS. by Inoshiro · · Score: 1

    I think the best thing you can get from MacOS is the SDI vs. MDI issue.

    In MacOS, Apple+Tab = switch Application. Apple+~ = switch window. This means I can easily go between application windows without futzing accidently into other applications.
    In KDE and Windows, this is not enforced, so I run into the situation of EVERYTHING being hidden in alt+tab.

    Consider: are subdirectories a good thing? Would you rather everything was in one root directory, each time having to search it for a file you want? No.

    Here's another one I'd like: hiding applications. If I'm not working with an application, but I'd like it to retain its state, I just Apple+H it (it'd be even better if all applications were stateful, but that's a bit harder to enforce). I can Apple+Tab back to it when I want it (and have its state restored as it's unhidden). No analog to this behaviour exists under other systems. The closest would be virtual desktops, but those bring their own set of problems (do you switch to a desktop when you switch to that application? Is it bound to that desktop? etc).

    MacOS is very consistent in its keyboard shortcuts. Apple+Q, Apple+W, Apple+H -- they all have the same meaning (unless you use bad applications, like Microsoft Office or Photoshop, which are greedy and appropriate every shortcut they can). No such consistency exists in UNIX land.

    Current attempts to clone Quicksilver and Expose are terrible, and not ready for prime time. The 3D features of my video card are not used to accelerate anything. Why not?

    In MacOS, if I go into the system Applications directory, there are maybe 20 programs. I can live with that (do full development, documentation, office work, etc). /usr/bin$ ls -l k* |wc -l
    334

    I know that not all of these programs are KDE applications, but there must be a better way. MacOS is nice in that it keeps the GUI world and the CLI world connected, but not intermingled. the KDE team could learn from this.

    In MacOS, applications and their support files and libraries are bundled into .app files I can easily drag into my ~/Applications directory (to install), and delete (to uninstall). Have fun doing that on Linux!

    KDE is great if you are used to Windows, which is a bad paradigm to begin with, but it's trash if you've used a real GUI system.

    --
    --
    Internet Explorer (n): Another bug -- that is, a feature that can't be turned off -- in Windows.
    1. Re:Learn from MacOS. by Anonymous Coward · · Score: 0

      In Windows, Alt+Tab = switch Application. Ctrl+Tab = switch window. This means I can easily go between application windows without futzing accidently into other applications.

    2. Re:Learn from MacOS. by Anonymous Coward · · Score: 0
      In MacOS, applications and their support files and libraries are bundled into .app files I can easily drag into my ~/Applications directory (to install), and delete (to uninstall). Have fun doing that on Linux!
      I tried to do that in MacOS, after installing all the 6 applications available for MacOS I got bored - and depressed.
    3. Re:Learn from MacOS. by Trinn · · Score: 1

      As for (mostly good) exposé clones, and using the GPU, check out:

      forum.beryl-project.org
      #beryl on freenode

      beryl is the community-driven fork of compiz, an OpenGL based compositing and window manager.

    4. Re:Learn from MacOS. by drsmithy · · Score: 1

      In KDE and Windows, this is not enforced, so I run into the situation of EVERYTHING being hidden in alt+tab.

      This is a *good* thing, as it lets you quickly and easily move between *arbitrary windows*, rather than making moving from one arbitrary window to another often a multi-step, multi-key affair.

      I have never seen any benefit to OS X's method. If you want to switch between windows within an application (Apple+~), Ctrl+Tab in Windows achieves tihs. If you don't and want to switch between windows in different apps, Alt+Tab does this on Windows, but has no equivalent on OS X. I have never seen any point or benefit in switching to an "entire application" and then raising all its windows to the top of the stack.

      Ironically (at least in terms of your attitude), the whole point of Expose is to make Windows-like task switching (between arbitrary windows) easier.

      Consider: are subdirectories a good thing? Would you rather everything was in one root directory, each time having to search it for a file you want? No.

      Alt+Tab is designed for quickly switching between 2 - 3 windows, as the Z-order is stored in a Most-Recently-Used stack. This was done because that's the typical usage pattern.

      Hiding applications is another thing I've never seen the point in, although I can see its usefulness due to how much the Dock sucks at pretty much everything it's supposed to do.

      In MacOS, if I go into the system Applications directory, there are maybe 20 programs. I can live with that (do full development, documentation, office work, etc).

      Your comparison is broken. Have a look in /usr/bin on your Mac.

      In MacOS, applications and their support files and libraries are bundled into .app files I can easily drag into my ~/Applications directory (to install), and delete (to uninstall). Have fun doing that on Linux!

      I agree this is an excellent feature, although it must be remembered that Trashed apps can leave files hanging around the system (primarily in the user's home directory), which is one argument for proper uninstallers/package managers.

      KDE is great if you are used to Windows, which is a bad paradigm to begin with, but it's trash if you've used a real GUI system.

      Please. OS X is as far from GUI nirvana as Windows is. The Dock is a great place to start (a UI train wreck in nearly every respect, albeit becoming more and more irrelevant with every OS X update), closely followed by Finder (horrible for file management in deep and complex directory structures, almost as bad as the old Chooser was for accessing networked resources, but fortunately similarly becoming less and less relevant - it seems Apple's plan is not to fix the things that are broken, but work around them), the poor level of keyboard-accessibility (something Windows has _always_ excelled at), the way some apps quit when their window is closed and others don't and the largely random application of different themes to different applications. I'll mention the overall sluggishness of the UI as well, but that's really an implementation, rather than conceptual or design, problem.

      MacOS Classic was a better GUI in nearly every respect to OS X. Relatively minor updates (including making it "lickable") - some of which *are* actually in OS X - would have been the best thing Apple could have done. Instead, it got Steved and has subsequently taken four major releases to work around most of the brokenness.

    5. Re:Learn from MacOS. by Reziac · · Score: 1

      Normally in Windows CTRL+TAB switches between windows within a given application, whereas ALT+TAB switches between application windows. So, Windows' CTRL+TAB is the same as the Mac ALT+~ (maybe that exists because CTRL isn't quite the same thing on a Mac, and isn't available for such a purpose?? I dunno.)

      This works even with oddballs like tabbed applications, which didn't exist when the CTRL+TAB thing was invented. Generally with those, CTRL+TAB moves between tabs, which is essentially the same as moving between windows within a single app.

      I thought CTRL+TAB worked on KDE too, tho it's been a while since I had the MDK box up, so I may be imagining things. :)

      --
      ~REZ~ #43301. Who'd fake being me anyway?
  33. KDE Performance Tips by IYagami · · Score: 1

    You can find them at:

    http://wiki.kde.org/tiki-index.php?page=Performanc e%20Tips

    And, according to http://terra.es/personal/diegocg/kde/#DCOP

    KDE 4 will use Qt 4.0 which is a big improvement in that field. When Qt designer was ported to Qt 4.0 - only the neccesary changes to make it compile - the "libqt size decreased by 5%, Designer num relocs went down by 30%, mallocs use by 51%, and memory use by 15%. The measured Designer startup time went down by 18%".

  34. Overly Critical Gay by Anonymous Coward · · Score: 0

    The known troll and bullshit story submitter chimes in. Seems like grandparent's point was that the interface isn't broken at all and you can change what you don't like. That makes KDE no worse than every other fucking thing out there. Hey asshole, now tell us how Windows is broken for no other reason than because you have to right click on the desktop and go to properties and effects to turn on cleartype. Laff.

    1. Re:Overly Critical Gay by Overly+Critical+Guy · · Score: 1
      Seems like grandparent's point was that the interface isn't broken at all and you can change what you don't like.


      Forcing the user to change to sensible defaults IS a broken interface.

      Hey asshole, now tell us how Windows is broken for no other reason than because you have to right click on the desktop and go to properties and effects to turn on cleartype. Laff.


      Now you're getting it! That's a broken interface, though that's hardly the only reason the laughable Windows interface is so shoddy (don't get me started on the Start menu).

      Next.
      --
      "Sufferin' succotash."
  35. Not true. by Inoshiro · · Score: 1

    Open FireFix in Win32. Hit Ctrl+N. Now, does Ctrl+TAB move between the two firefox windows, or does Alt+Tab move between the two Firefox windows? How many entries for Firefox are there in the Windows taskbar?

    I thought so.

    --
    --
    Internet Explorer (n): Another bug -- that is, a feature that can't be turned off -- in Windows.
    1. Re:Not true. by Vexorian · · Score: 1

      Ctrl+tab switches between tabs in firefox. If you actually have 2 firefox windows for no reason then you can use the taskbar (you know, they do have the webpage's title as caption so you can recognize which one is it) Or I could keep alt+tab pressed so instead of instantly switching to next window I see the app switch window and find a firefox icon with the title of the web page I want. Also if you created a new window it is reasonable that it has a 2nd button in the task bar, or if you change the task bar's option to group buttons it will only have one, Whatever the user likes.

      --

      Copyright infringement is "piracy" in the same way DRM is "consumer rape"
  36. My humble suggestions by brentl · · Score: 1

    1. Split the packages
    Yeah it's more of a distro maintainers problem, but it reflects badly on KDE. It's so annoying to have to big packages of stuff i mostly don't use. E.g. I like the dirfilter konqueror extension, but it's part of kdeaddons which depends on kdegames and kdepim (which i don't want)

    2. Better file association management
    If you can't split the packages the least you can do is provide better file association management. It should be easier to edit a group of file types. E.g. I want everything in the image group to open with gwenview with krita second and nothing else. I had to go through every one and edit it.

    3. Separate Konqueror and kfmclient
    Konqueror the Web Browser and Konqueror the File Manager should be separate. Completely separate toolbars, menus, settings and file associations (konqueror the web browser's file associations should be much simpler, something like Firefox's). At the moment i can't get konq web browser to work the way i want it without messing up konq file manager.

    For the most part I like KDE :)

    1. Re:My humble suggestions by 404Brain-not-found · · Score: 1

      I find the Konqueror File manager and Web Browser rolled into one quite useful..The right amount of tweaking should remove your annoyances..I mean, how many times I have switched between tabs containing my home folder and websites. Information lookup from the harddrive and using the same with some websites is a snap..This ironically was one of the reasons for my switch to kde from gnome. I couldnt use nautilus for quick web sessions. Of course konqueror does need some touch ups..

  37. yay KDE! by minus_273 · · Score: 1

    10 years of the Kool Desktop Environment. really Kool!

    --
    The war with islam is a war on the beast
    The war on terror is a war for peace
  38. Use xfce by jdbartlett · · Score: 2, Informative

    That's what xfce is for. It has a KDE compatibility layer, and now even comes in handy Xubuntu live CD form.

    http://xubuntu.com/

  39. Improved startup time, please by massysett · · Score: 1

    I love KDE, but my biggest complaint is the time to start KDE. It's fast enough when it's running, but man, you have to get it started up first...add KDE startup on top of a live CD (like KNOPPIX) and then you're talking intolerably slow. Startup time alone keeps me using GNOME on my laptop, though I use the K on my desktop.

  40. KDE...sucks. by swordgeek · · Score: 1

    Now before you flame too hard, keep in mind:
    Gnome...sucks.
    Vista...sucks.
    MacOS...sucks.
    CDE...still sucks.

    User interface design is retarded. We need to get some complete computer neophytes to look at our interfaces, and point out the obvious blind spots we've created for ourselves.

    Put another way: Computer user interfaces SUCK! The current set of 'innovations' are only innovative and progressive within the context of users (such as ourselves) who have rigorously trained ourselves to think like computers.

    Nothing about computers is intelligent, elegant, or intuitive. Ironically enough, the command line interface is probably still the best thing we've got, beyond a certain level of complexity.

    No computer interface--not a single one--deserves a celebration. Not until they figure out people think when they're not trying to think like computers.

    --

    "People who do stupid things with hazardous materials often die." -- Jim Davidson on alt.folklore.urban
    1. Re:KDE...sucks. by smash · · Score: 1
      We need to get some complete computer neophytes to look at our interfaces, and point out the obvious blind spots we've created for ourselves.

      This is a mistake. You get neophytes to design an interface, you'll get something only useful to neophytes who have no idea what they're doing.

      People need to accept that using a computer is a *learned* skill, much like driving a car or riding a bike or cooking. There's only so much you can do to simply the tasks involved.

      User interfaces should be designed to make common power-user type tasks easier to accomplish for everyone. Not cater to idiots who don't really use it to accomplish anything productive...

      --
      I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
    2. Re:KDE...sucks. by ardor · · Score: 1

      A learned skill? Yes. But the real problem we are talking about is accessibility.

      An example: the command line has awesome usability. The things I can do with this tool are numerous. Also, it matches the way people think: in verbs.

      But the command line has TERRIBLE accessibility. awk, sed, etc. are very useful command-line tools, but as a beginner, it is extremely hard to get a clue how they work. "find ../foo -name 'c1.t*' -exec rm {} \;" is quite logical once you grasp how find works. But until then - what?

      This is where typical GUIs shine. I can try things in Photoshop, they are VISIBLE, they are THERE (try to find this-one-obscure-command in /usr/bin). "I want to find something to turn my pic into a pointilism-like image, lets see... ah, in Filters there is something called Boxify, lets try this..." Try this with the command line.

      The PS UI can be used as a sandbox environment for experimenting with the features, because it has two things the command-line interface lacks: much better accessibility, and an undo feature. As a golden rule, EVERYTHING should be reversible unless it is physically impossible, and irreversible actions should pop up a big fat WARNING (this is where popups actually belong).

      Generally, I propose two improvements for the command line:
      - Undo functionality.
      - Quick online help of fundamentals. The joe editor is a very good example. In the upper right corner, there is written "Ctrl-K H for help". After pressing this, a quick help appears in the upper portion of the screen, describing all basic keystrokes. This reflects the PS UI; now, the commands are VISIBLE, they are THERE.

      Also, WIMP interfaces do have their place. WIMP and command line are not mutually exclusive. Graphics-intensive apps like 3D modelers absolutely NEED the mouse, and there a WIMP interface makes sense. Since the mouse pointer is in motion anyway, the buttons are easy and quick to access. But with an editor, things are different. In an editor, the keyboard dominates, and having to move the hand to the mouse and the mouse pointer to the "save" button is an unnecessary delay. Just like everything else, WIMP is the right tool for the right job - not for everything. Same applies to the command line.

      --
      This sig does not contain any SCO code.
    3. Re:KDE...sucks. by swordgeek · · Score: 1

      Ah now be careful. I didn't say we need neophytes to design our interfaces, but to audit them. Agreed, a neophyte-designed interface is likely to be horrible. However, put a neophyte in front of a product, and let them muck with it, with minimal instructions. After a while, they'll come up against a stumbling block, and ask for help. When you explain the solution to them, do they say, "oh that makes sense--I should have realised it;" or is their response, "What the hell kind of heroin addict came up with that idea?!" This can be very useful data, as long as its realised that it won't be perfect either.

      Fundamentally, computer interfacees are completely abstract compared to the tasks you're trying to accomplish, and this isn't good. When you learn to ride a bike, you learn to balance. When you learn to cook, you learn to mix flavours and add heat. Driving is a bit more abstract, but the interface is pretty logical--turn the wheel left to go left, etc. In computers, if you want to (for example) add a filter to a picture, you click here, drag down to the menu, pull the slider over, and click 'apply.' None of that has anything to do with the basic premise of putting a filter on a picture.

      Only one example, I know, but it's pretty much true through almost all computing.

      --

      "People who do stupid things with hazardous materials often die." -- Jim Davidson on alt.folklore.urban
  41. Finally, some decent complaints by BeeBeard · · Score: 1

    Those are way better complaints than the typical ones, which are usually something like "KDE isn't the way I like it by default and I don't understand why a desktop environment is not exactly the way I like it by default! Forget navigating one menu and clicking one option, What about my needs!"

    1. OK/Apply/Cancel - Yes, this was stolen from Windows and I can't say I like it myself. In the Control Panel, if you forget to apply your settings before moving on, you will get a notice asking you if you want to apply them. That kinda helps the problem, but not really.

    2. Open folder in new/same window. - I thought for sure this was the default setting anyway. If not, in Konqueror go to Settings --> Configure Konqueror --> and it's the very first checkbox you see, right on the Behavior tab. That's a really, really easy fix. I was beginning to doubt you until you said...

    3. Too many menus! - This is a very good point--I would mod you up for it if I could. A lot of software has novice/intermmediate/advanced user settings that hide or show certain options based on the user's sophistication level. With KDE it's just WHAM: "How about these 500 different settings, do you like those?" If you don't know where to go to change a setting, then be prepared to look for it. And I agree, that's not something a user should have to do. (note: There may already be a way of doing this, but if there is, I'm not aware of it and it's buried in the menus somewhere. How's that for irony? ;)

    4. Customising shortcut keys. Yes, shortcut configuration is more intuitive in GTK apps. With KDE, you usually have to navigate a few menus in the DE and/or in most KDE apps to change them.

    5. The open & save dialogs. I'm not sure I completely understand your problem, but I will say that the GTK dialogs, in my opinion, are even worse. They're blocky and borderline non-functional and love to ignore old save points as well. My own issue with the KDE dialogs is that getting file listings for large directories just chokes. It doesn't matter if I'm trying to get listings for FAT or ext3 partitions, too. I've got lightning fast drives, but for some reason giving me the graphical equivalent of an "ls" under KDE takes forever. So yeah, you've got another legit complaint--the dialogs need some optimization work or something.

    6. Complexity. This is just the same problem as #3. There needs to be a way to pare down the options so that just the ones that most people will want to change are obvious, while advanced users still retain access to the more minute settings.

    You raise some great points. You know, I was once a huge critic of KDE. On my old box, it was slow, unresponsive and bloated. I don't know exactly when the KDE people fixed those problems--version 3.x maybe? But anyway, when I tried it again after another few years of development I was very pleased with it. Now it's less a question of optimizing the code and more about tweaking the design. The good news is they're listening to their userbase and they're willing to make changes to whatever we don't like. That's about the best we could hope for from the people behind such a huge open source project.

    1. Re:Finally, some decent complaints by zsau · · Score: 1

      Regarding the open folders in new windows thing... The way Konqueror is configured on my computer, is that if I press Button-1, it opens in a new window; and if I press Button-2, it opens it in a new tab. But I want Button-2 to open in the same window. Maybe there's some preference I've overlooked (because of the Complexity issue, that's way too likely!), I'll have another look when I'm at home.

      Regarding the open & save dialog boxes, you can't do anything in GTK ones, true; but thing is, all I use an open/save dialog box for is to find the right place to open/save a file. Probably I'm already doing something in that folder, so I have the folder open elsewhere. With GTK dialog boxes, I can drag another file in and the dialog box switches—this is the killer feature for me. With KDE dialog boxes, I can do all sorts of things, but to find the right place, I have to browse to the right place again. And again. And again.

      I've heard all sorts of great things about the architecture of KDE. I've tried it every significant upgrade. But it's basically this list of things that's pissed me off each time.

      --
      Look out!
  42. Arrogance is not my default setting by BeeBeard · · Score: 1

    No, I read the word "default" just fine. I guess I just don't share the arrogance associated with believing that I'm some kind of Everyman and that all software I use should be exactly the way I like it the first time I use it--especially when making it that way requires the most trivial of changes.

    Bizarre megalomania aside, if the default settings are too spartan and ugly for you, then perhaps you've forgotten that every time something is made "prettier" it uses more RAM, burns more CPU cycles, or both. The idea is to make software that will run capably on most anything without tweaking, from a lowly Pentium I all the way up to the latest and greatest hardware. Complaining that you own the latest and greatest gear and have to change a handful of settings to take advantage of it tends to resonate as so much empty bleating. Are you sure you wouldn't just be happier running Vista?

    1. Re:Arrogance is not my default setting by Blakey+Rat · · Score: 1

      I can guarantee I'd be happier running Vista. I'm running OS X right now. Last time I tried KDE, I took one look at the preferences window and ran away screaming. There's no way every single one of those 40,000 different options are all actually used by people, and it's impossible to QA a product with that many different combinations of settings. (Not that the open source community usually gives a crap about quality, but either way.)

    2. Re:Arrogance is not my default setting by BeeBeard · · Score: 1

      Fair enough. At least you don't presume to demand that KDE should be the way you like it the moment you use it, the way some of these other people have. That's about as empty and selfish as complaints go. But if you're sitting there trying to use the software, and you have an idea to change something, look at the menus and go "Eh..." then that's a sure sign that there's a problem. The KDE "Control Center" is easily the best and worst thing about it. Best because hey, the options to change almost everything are there and worst because the way they're presented is so unintuitive. It would be so much better if you could just toggle your user setting to "beginner" or "intermediate" so you didn't have to see the other 500 options you don't ever have to worry about.

    3. Re:Arrogance is not my default setting by Blakey+Rat · · Score: 1

      I disagree. I've never seen an application with a "beginner" mode that was even half-decent. Remember Apple's terrible "Simple Finder" option in OS 9? Did *anybody* on Earth end up using it? The "Easy" mode in Azureus is so horribly-implemented, I almost thought it was some kind of terrible joke. Or what about "Personalized Menus" in Office 2000? Another horrible implementation of that idea.

      What KDE needs to do is to collect data on which of those options are actually *used* (I'm guessing that the vast majority of those options have been touched by less than 100 people), and remove all the others. Then when they have the number of options down to a reasonable level, they can actually start applying some QA to the environment and hunt down pesky bugs.

      There are two rules of interface design that KDE really needs to figure out:

      1) The vast majority of people never change the defaults. Why do you think people here on Slashdot always complain about Auto-Format in Word, even though you can turn it off easily in the Options dialog? Because they don't change the defaults, even when they annoy them.

      2) The more options there are, the more intimidated the user will be. It's never a good idea for the computer to make a user feel dumb, but when you see an option entitled, "Treat ctrl as alt if Mouse 3 is held down for over 14 seconds", that's exactly what you do.

      (Once again, Slashdot treats a click of the Submit button in Safari as a click of the Preview button. FIX THIS BUG PLEASE!)

    4. Re:Arrogance is not my default setting by BeeBeard · · Score: 1

      Under Windows (which, like it or not, is what many of KDE's UI concepts were *cough* borrowed *cough* from) there's regedit for some of the more obscure settings. I would suggest that that's at the very extreme end of the unusability spectrum. And sure, a Control Center that offers to change regedit-like settings but with checkboxes is not much of an improvement. But just getting rid of the options altogether could alienate the more hardcore crowd. The "different user levels" idea could be a sound solution to the problem, but yeah, it's been badly implemented in the past. I don't know if a notorious history of bad implementation derails it as a potential solution or not.

      As an aside, partial blame for the (in some cases poor) default DE settings should fall on the distributions as well. They have just as much ability to change the settings to suit their intended userbase as the KDE people do.

      One final thing to consider is that most people don't configure their desktop environment any more than once, (or as you pointed out) if at all. I can't remember the last time I've tinkered with my KDE settings--it's probably been about 18 months since I have. So in that sense, I am perhaps not the best judge about the importance of this because I don't see an argument about the difficult of configuring as having the same weight as arguments against day-to-day usability. But hey, that won't stop me from opining on the subject! Woo woo, Slashdot!

    5. Re:Arrogance is not my default setting by Blakey+Rat · · Score: 1

      One final thing to consider is that most people don't configure their desktop environment any more than once, (or as you pointed out) if at all.

      Thus going back to the ORIGINAL point of this debate, that since most people don't do any kind of configuration, the defaults need to be as sane/beautiful as possible. The very small minority who care about CPU/memory usage will tweak it to be more efficient (just like they do in Windows now with RegEdit, as you noted), and the large majority will be happy with KDE by default.

  43. Exactly by BeeBeard · · Score: 1
    In all honesty though it sounds like the Gnome style of sparse options is more suited to your tastes, so you should probably stick with it (I'm assuming that's what your current DE is).


    Hit the nail on the head. The good news for people who have unsurmountable problems with KDE is that there are literally dozens of other options out there. With enough energy and curiosity they'll find something they like. KDE, one of the few DE's that at least tries to be a shoe that fits every foot is taking heat for its lack of customization and default options, which I find highly ironic. I can tell by the way this thread has been moderated that I'm alone in noticing this.

    But keep in mind that these people are not KDE users--they're people who are logging onto Slashdot using Firefox on their Windows machines to complain about how ass-hurt they are that KDE didn't have the exact settings they wanted enabled by default. They're typically not people who even use KDE/Linux/whatever else enough to have anything but the stupidest of complaints. A legitimate complaint about KDE would be something like "Help! There are all these menus and I can't figure out how to change this stuff!" That's a good sign that something's wrong. Not, "I'm such a pompous ass that I believe this should already be the way I want it by default. I represent all KDE users, everywhere."

    Oh well, at least another person gets it.
  44. Change...sucks. by Anonymous Coward · · Score: 0

    "Nothing about computers is intelligent, elegant, or intuitive. Ironically enough, the command line interface is probably still the best thing we've got, beyond a certain level of complexity."

    In general I agree. However the CLI is just another variation of people thinking like computers. The thing to keep in mind about your "think different" is that most people wouldn't use such a thing unless it was head and shoulders above what they're using. And even then it would be slow going. Just look at how non-C (and derivitives) languages are treated by those most capable of understanding them if they tried.

    I should also point out that hardware would have to change to make such a revolution possible. We're getting bits and pieces, but no one has put them into a cohesive whole.

  45. Geeks...sucks. by Anonymous Coward · · Score: 0

    "User interfaces should be designed to make common power-user type tasks easier to accomplish for everyone. Not cater to idiots who don't really use it to accomplish anything productive..."

    And once again the "priesthood" image is reenforced. Curse all those "idiots" who bought Visicalc so they couldn't "accomplish anything productive". Same with those business "idiots" that bought the original IBMs, so they too could accomplish nothing "productive". As long as geeks are happy, who gives a fisk about those who really pay the bills so their toys can be cheap.

    1. Re:Geeks...sucks. by smash · · Score: 1
      And once again the "priesthood" image is reenforced. Curse all those "idiots" who bought Visicalc so they couldn't "accomplish anything productive". Same with those business "idiots" that bought the original IBMs, so they too could accomplish nothing "productive". As long as geeks are happy, who gives a fisk about those who really pay the bills so their toys can be cheap.

      You misunderstand, either that or have a predetermined agenda...

      A neophyte is a neophyte until they learn better, than then from then on until the day they die, they know how to use whatever technology it is we're discussing.

      Why cater only to neophytes when people who are actually interested in learning how to use the tools will not be neophytes for the vast majority of the time they spend using it?

      I mean (random example), there are excel wizards in my company who can do stuff i can only dream about in excel. Should excel be dumbed down at their expense so I can more easily use the program to add up a couple of rows of numbers? Another example... autocad is hard to use. Should it be turned into something like paint so that any dumbass can use it, but using it for professional level tasks is made more of a pain in the ass?

      No.

      I'm not sure why you bring up the original IBMs in your argument, as they were much harder to use than modern machines, and the people who decided to learn how to use them had to put in the effort...

      --
      I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
  46. KDE's Killer Apps?? by Aquila+Deus · · Score: 0
    I have always wanted to switch to KDE from gnome/xfce, but it'd be pointless if I still have to run gtk apps...
    • konqueror (browser) - screw up with a lot of firefox-compatible websites. Anyone makes kde UI for gecko??
    • kopete - definitely superior to gaim, but lacks cute trillian animations!
    • amarok - the playlist tree makes me mad, why can't it just be simple and show me genre/artist/album?? (PS: like itunes or wxmusik)
    • krita - the UI simply sucks, especially when you have to open 5+ small images (ex: theme decorations).
    • koffice - openoffice is bad enough but koffice is just unusable for my word documents, a lot of pictures/diagrams missing and chinese doesn't work.
    • (vmware-server alternative??)
    well, that's all of my complaints over the 10 years. :)
    --
    hmmm... dumb...
    1. Re:KDE's Killer Apps?? by KayosIII · · Score: 1

      Amarok - I believe the collection Tab is what you are looking for. Rather than the Playlist tab... (Look at the left side of Amarok there should be a bunch of vertical tabs running down the side of the screen... These are pretty central to running amarok...

    2. Re:KDE's Killer Apps?? by arevos · · Score: 1

      Plastikfox is a theme for Firefox that mimics the default Plastik theme. Openoffice also has a Qt interface that blends into KDE fairly flawlessly.

  47. predictable moderation by oohshiny · · Score: 1

    The moderation on the parent message is predictable KDE groupthink and just reinforces my point.

    All other major desktop environments (Gnome, Mac, Windows) allow no-cost commercial development and distribution, and all other major desktop environments are moving to languages other than C/C++ (namely, C# and Objective-C). You can make KDE as wonderful as you like from a user's point of view, and it may maintain a significant market share for another few years, but this is as good as it's ever going to get for KDE.

    1. Re:predictable moderation by Mr.+Hankey · · Score: 1

      The idea behind KDE is to engineer a solid application environment. They felt the best way was to use an object oriented language. Based on the development environments I've seen, I happen to think they're on to something. C does have a more stable ABI under GCC at this point, which is nice, and gcc's C++ optimization still isn't what it could be. Once these issues are resolved though, C++ is simply a richer, more functional environment on which to build a graphical application.

      I'd still like to see some work done on KDE/Qt though. I personally think Qt and GDK/GTK should be stripped down such that one can write against either API and connect to a more universal GUI layer, one which is themable and efficient. It should handle all the drawing regardless of the backend, which would reduce the number of portability issues. While we're at it, how about a consistent object-oriented clipboard which handles non-textual data types using a generic interface that can pass them back and forth between all apps (not just GNOME or KDE) which register to receive them? Now THAT'S something I'd be willing to contribute to.

      --
      GPL: Free as in will
    2. Re:predictable moderation by Anonymous Coward · · Score: 0

      This is a reasonably interesting read on Klipper.

    3. Re:predictable moderation by Mr.+Hankey · · Score: 1

      Nice application, but at the wrong level IMO. Ideally, this functionality would be implemented at a lower level than the GUI.

      --
      GPL: Free as in will
    4. Re:predictable moderation by oohshiny · · Score: 1

      Once these issues are resolved though, C++ is simply a richer, more functional environment on which to build a graphical application.

      You're barking up the wrong tree. I'm not arguing C vs. C++. I think both C and C++ are lousy languages to write GUIs and desktop apps in. The only C-based language that is even close to being object oriented is Objective-C, and it has a lot of other problems. (I leave Java and C# out of the discussion because, despite their syntax, they are not really C-based.)

      I personally think Qt and GDK/GTK should be stripped down such that one can write against either API and connect to a more universal GUI layer, one which is themable and efficient. It should handle all the drawing regardless of the backend, which would reduce the number of portability issues.

      You're still assuming that Qt and Gtk+ APIs are APIs people will want to write against in the future; I think neither of them are. C++ has turned out to be a failure as an object-oriented programming language (it has turned out to be good a other things, however).

      I think the real migration strategy is from something like Gtk+ to Gtk#, followed by a pure C# implementation of Gtk# based on Cairo. Gnome has taken big steps in that direction. Microsoft has done something similar. Apple has ditched C++ and has moved everything to Objective-C (now with garbage collection). Only KDE still clings to C++.

      While we're at it, how about a consistent object-oriented clipboard which handles non-textual data types using a generic interface that can pass them back and forth between all apps (not just GNOME or KDE) which register to receive them? Now THAT'S something I'd be willing to contribute to.

      The "graphics layer" and the "clipboard layer" you speak of is what X11 was supposed to be. It has all the provisions and facilities for providing that functionality in a toolkit-independent way. Unfortunately, both Qt and Gtk+ ignore most of that stuff and instead do their own thing.

    5. Re:predictable moderation by Mr.+Hankey · · Score: 1

      You're barking up the wrong tree. I'm not arguing C vs. C++. I think both C and C++ are lousy languages to write GUIs and desktop apps in. The only C-based language that is even close to being object oriented is Objective-C, and it has a lot of other problems. (I leave Java and C# out of the discussion because, despite their syntax, they are not really C-based.)

      You're misunderstanding my point. Objective-C is not widespread enough for serious discussion in the real world, OS X/NeXTStep/OpenStep notwithstanding. C++ is widely available, almost certainly installed on a Linux distro with development tools, and not as bad as you make it out to be. There are problems with every language, but C++ has the virtues of being widespread and familiar to a large number of programmers who are skilled in its use - especially those coming from Windows. It presents an object oriented API to the programmer if they choose to use it, whatever your opinion of its virtues. The standard Java and C# implementations both use different virtual machines as their native targets, and I'd rather not even get into that mess just yet.

      You're still assuming that Qt and Gtk+ APIs are APIs people will want to write against in the future

      IMO there's nothing wrong with the Qt API, although I will admit that most of the GTK+ code I've seen/had to work with looks like spaghetti. Probably due to Glade's code generation more than the API itself, but even that makes me not want to use it.

      I think the real migration strategy is from something like Gtk+ to Gtk#, followed by a pure C# implementation of Gtk# based on Cairo. Gnome has taken big steps in that direction. Microsoft has done something similar. Apple has ditched C++ and has moved everything to Objective-C (now with garbage collection). Only KDE still clings to C++.

      You're only going to end up with further fragmentation in this direction, and limit the languages in which people are able to write their applications. I'm not talking about a specific language, I'm talking about a more powerful low level X11 layer on which the various toolkits can build upon. This would give application developers the flexibility to choose their own language/toolkit and still have better consistency in the resulting applications. It would also help when someone had to port existing code into the environment.

      The "graphics layer" and the "clipboard layer" you speak of is what X11 was supposed to be. It has all the provisions and facilities for providing that functionality in a toolkit-independent way. Unfortunately, both Qt and Gtk+ ignore most of that stuff and instead do their own thing.

      The "clipboard layer" in X11 is a piece of garbage, and needs to be replaced. There it is, stated clearly and for the record. I'd like to see an object oriented replacement for X11 which is toolkit independent. The graphics layer and native GUI toolkit (if Xt and the Athena widgets are what you'd consider native) also need serious reworking for modern GUI application development, which is why most people tend to use a separate toolkit like Qt or GTK+. There are reasons why people have done their own thing for such a long time. The network transparent layer and ubiquity are nice, but services which a generic application can depend on are severely lacking.

      --
      GPL: Free as in will
    6. Re:predictable moderation by oohshiny · · Score: 1

      C++ is widely available, almost certainly installed on a Linux distro with development tools, and not as bad as you make it out to be.

      That's where you're wrong: C++ is an absolute disaster and has held back desktop and application enormously.

      You're only going to end up with further fragmentation in this direction, and limit the languages in which people are able to write their applications.

      If it "limits" people away from writing code in C and C++, I'm all for it. In any case, it's not a question of what "I" do, it's already happening: Microsoft and Gnome have made C# a full-fledged application development language, and Apple has moved to Objective-C. In the Microsoft/Gnome case, you can still write C/C++-based applications, but increasingly, you're going to see more and more fancy widgets written in C# only (and even then, you can call them from C/C++ compiled to a CLR backend). It's a good migration strategy. The Apple strategy is similar. Only KDE still clings to the notion that people should write everything in C++.

      The network transparent layer and ubiquity are nice, but services which a generic application can depend on are severely lacking.

      They are "lacking" because KDE, Qt, Gnome, and Gtk+ have largely chosen to ignore what was there before they started, instead of participating in improving it. The end result? We have two Linux desktops that look really nice but whose underlying technologies are less capable than what Motif could do nearly 20 years ago. I mean, neither Qt nor Gtk+ applications even work correctly remotely.

    7. Re:predictable moderation by bensch128 · · Score: 1

      That's where you're wrong: C++ is an absolute disaster and has held back desktop and application enormously.

      Tell that M$, Apple, Trolltech and every other professional desktop development company in the world. Currently, it's the only language that is capable of supporting highpowered applications like 3D Modellers, multimedia processing programs, and others.

      Just because it's not as flexible or forgiving as C#/Java/Ruby/Python doesn't mean that you can't build amazing software with it. Besides, if the developers use a consitant coding format like TT does, you can build very powerful language bindings on top of C++. Just look at SIP and SMOKE and here. I gurrentee that for KDE 4.x, there will be an extremely powerful scripting layer (JS/Ruby/Python) for developing kde applications in. It'll be so powerful that it'll cause major security holes but that's a good thing in my opinion.

      Cheers,
      Ben

    8. Re:predictable moderation by Mr.+Hankey · · Score: 1

      That's where you're wrong: C++ is an absolute disaster and has held back desktop and application enormously.

      That's an opinion. You're welcome to it, but C++ has more developer mindshare and code written than Objective C. This is a fact.

      If it "limits" people away from writing code in C and C++, I'm all for it.

      And I'm all against it. Flexibility should be a requirement for X11, since it works across so many platforms. We're talking about completely different issues in any case; I'm advocating further development of the underlying architecture of X11, whereas you're talking about a particular API for a single toolkit sitting on top of X11 which will NOT interoperate with other toolkits. All toolkits could benefit from improvements in the basic X11 architecture.

      In any case, it's not a question of what "I" do, it's already happening: Microsoft and Gnome have made C# a full-fledged application development language, and Apple has moved to Objective-C. In the Microsoft/Gnome case, you can still write C/C++-based applications, but increasingly, you're going to see more and more fancy widgets written in C# only (and even then, you can call them from C/C++ compiled to a CLR backend). It's a good migration strategy. The Apple strategy is similar. Only KDE still clings to the notion that people should write everything in C++.

      It's a migration strategy, but to do it in just GTK would mean doing it at too high of a level to do any good. X11 has been and should continue to be platform agnostic. That doesn't mean it shouldn't have any features, but rather that these features should not be tied to a particular type of system and definitely not something vendor specific. Developers should be able to write their code in any language and have the application look alike, which should be the job of a separate UI drawing layer as it's done in OS X (Quartz) and Windows (GDI/GDI+/etc). The API and language choice should be left to the programmer.

      They are "lacking" because KDE, Qt, Gnome, and Gtk+ have largely chosen to ignore what was there before they started, instead of participating in improving it. The end result? We have two Linux desktops that look really nice but whose underlying technologies are less capable than what Motif could do nearly 20 years ago. I mean, neither Qt nor Gtk+ applications even work correctly remotely.

      Bollocks. The "Open" Software Foundation/Open Group can only blame themselves for what happened with Motif. They kept it closed for so long that it became irrelevent. This is why GTK and Qt are now eating Motif's lunch, note that GIMP was originally a Motif app before they developed GTK (Gimp Toolkit) to replace it. Motif apps have been and are still just as limited in how they can interact with non-Motif applications as Qt and GTK+ applications are. Qt apps tend to like other Qt apps, and the same can be said about GTK+ apps. There is some integration, XDND and the very limited X clipboard, but this functionality should be augmented at the X11 layer to allow for e.g. copying and pasting data objects of any type using whatever method an application can accept it in.

      BTW, do you have an generalized example I can apply to any Qt or GTK+ application which shows that they do not work correctly remotely unless they're using XSHM, XV (YUV overlay extension) or another extension which requires local hardware access? I use X11 extensively without these supposed local vs. remote issues, and have for over 10 years including Openlook on Solaris and Linux, Motif and the Motif-based CDE on several platforms, the current crop of desktop environments from KDE to XFCE, and dozens of WMs. That's not to say that there are no issues, but rather that these are issues with X11 R6 itself.

      --
      GPL: Free as in will
  48. 10 years eh? by Anonymous Coward · · Score: 0

    So, where are all the posts claiming:"8 more years before its legit!"?

  49. Re:Welcome to the past - copy and paste from term by Anonymous Coward · · Score: 0

    Um, I use the application 'screen'.
    See: http://www.gnu.org/software/screen/

  50. QT Licensing! by Anonymous Coward · · Score: 0

    Cant believe no-one raised this: QT Licensing! - cmon guys Open Source it!!! Until you do I wont touch KDE, sorry.

    1. Re:QT Licensing! by bhalo05 · · Score: 1
      Cant believe no-one raised this: QT Licensing! - cmon guys Open Source it!!! Until you do I wont touch KDE, sorry.


      Yeah. I'll do the same and not touch Linux until is GPL! Oops, wait...

  51. Filter by Anonymous Coward · · Score: 0

    "We've come a long way in ten years, but where must we still improve?"

    I wish Konqueror had a filter that filtered out the kvery kboring kjokes.

  52. What a non-sequiter. by Inoshiro · · Score: 1

    "I have never seen any benefit to OS X's method. "

    Great, you haven't, I have. I believe the question was, "what can we do to improve KDE" -- and adding this behaviour would improve my experience with KDE.

    Feel free to turn it off on your install, and I'll feel free to turn it on, on mine. There's no such thing as a "right" interface.

    --
    --
    Internet Explorer (n): Another bug -- that is, a feature that can't be turned off -- in Windows.
  53. Unconfigurable key trapping by 5pp000 · · Score: 1

    I have used KDE for years, and have been pretty fond of it. (I have not liked Gnome when I tried it, but the last time was a while ago.) There's only one complaint I have. Every so often someone on the KDE team gets the bright idea that the way to implement some feature is to trap some key combination in the window manager or X server or some low-level place where the behavior is unconfigurable. In one release, a couple of years ago, the Windows key brought up the K menu, and there was no way to change this, not even using xmodmap. And now I find that in the new KDE used in SLED 10, Alt-Space brings up the Kerry Beagle Search dialog, and there's absolutely nothing I can do to change this -- it's not a configurable shortcut. In fact, it's clearly implemented at some low level, because it has a bug: not only does the dialog pop up, but somehow the Alt key's key-release event is lost, so Alt stays on unless I press and release it again.

    Dear KDE team: please make it a part of your culture that you never ever ever do this. All special key combinations must be trapped in such a way that they are configurable, period. (In fairness, these things do seem to get fixed in subsequent releases... but I have to live with them in the meantime.)

    Since I'm sure you're wondering why I care -- well, you must have no Emacs users on your team; Alt-Space (or Meta-Space in Emacs-speak) and Control-Meta-Space are both important Emacs commands which I use frequently. Interestingly, both of them are now bringing up the Kerry Beagle dialog, which is additional evidence that the key combination is being trapped incorrectly.

    Except for that -- keep up the good work!

    --
    Your god may be dead, but mine aren't!
  54. OSX may not be "better" but I'm sticking with it.. by Anonymous Coward · · Score: 0
    .. as my desktop of choice until another one comes along that is. This may seem funny given that about the only applications I run are:
    • Terminal, ssh, emacs
    • Firefox, Opera, Safari - Yes I use all 3: Firefox for work, Opera for research and Safari for recreation. This way I can manage javascript, cookies, etc easily. Having the ability to wipe the Safari cache in an instant has proven useful on various occasions.
    • Yahoo Instant Messenger
    • Preview
    • World of Warcraft
    All the other stuff to me is junk and if I could find a way to turn off spotlight, expose and all that I would.

    When KDE does a substancially better job of running those applications, I'll take a serious look at it.