Slashdot Mirror
KDE SC 4.7 May Use OpenGL 3 For Compositing
An anonymous reader writes "KDE SC 4.5 is about to be released and KDE SC 4.6 is being discussed. However, Martin Graesslin has revealed some details about what they are planning for KDE 4.7. According to Martin's blog post, they are looking at OpenGL 3.0 to provide the compositing effects in KDE SC 4.7. OpenGL 3.0 provides support for frame buffer objects, hardware instancing, vertex array objects, and sRGB framebuffers."
or you just don't turn on the optional compositing in the first place? this is a new feature created and intended for newer machines.
Aerated plastic tubs and earthworms.
I don't know that we need any more eye candy in KDE 4. It already has a ridiculous amount of aesthetically pleasing features. How about we squash some existing bugs and add more usability features.
This is not the penguin you're looking for.
Oh for god sakes people. Kwin provides pluggable back ends for rendering engines for compositing. Currently we support xrender and OpenGL 1.1, soon we will support the next version of OpenGL. Big deal. You can turn compositing on or off, or choose which engine is best for your platform. We will not remove the old engines or force everyone to use compositing. So stop your trolling.
I can tell you that 4.5rc2 automagically loads up akonadi and all of its fluff/garbage/helpers if you have a clock plasmoid. Without option to turn it off.
Akonadi and Nepomuk are simply jokes. Enforcing them on the user, specially considering how useless both services are, is a really bad idea©.
Nepomuk can be disabled easily, not so much for Akonadi. You literally need to cheat it by giving empty path strings, or no clock.
I'm a major KDE advocate, but those two services get on my nerves way too much, specially because they are rather hefty for what they do (for me, nothing at all, for others, very limited usage).
Rant mode ON:
KDE seems exceedingly dependent on itself right now. And integration efforts (with popular apps out of KDE) are pretty much non-existent or unknown even among devs (I discovered after a friendly rant about the current "closed" state of things, that Krunner now does index Firefox bookmarks. The person who corrected me learned it by pure chance it seems, as no "user friendly media" (getting deeeeeeeeeeeep into mailing lists and all the bulk of svn commits is not user friendly, it costs more than mere minutes to check all that) reported on it at all).
I don't know who is to blame but whoever is responsible for this, is not helping the already damaged (by 4.0) reputation of KDE. Half-baked and/or mandatory apps are not helping. Neither does the silly "KDE SC" gimmick.
I can only think something in the management chain is broken, leading to absurd/rushed/experimental decisions pulled off. Either that or the exceeding majority of the 6-month release cycles is translation/bugfixing. As new features talked about during the release of "KDE 4.X" are implemented in "KDE 4.X+1" in the same state shown during the 4.X release (Look at tiled windows in the 4.5 branch. It's there, but...)
Rant mode OFF
Sorry, I really needed to put that up for discussion. Whenever Akonadi is mentioned I go berserk as I am reminded of stuff like it being a requisite for the standard clock.
The worst is that I am an enthusiastic KDE user and I follow development closely, trying betas and reporting bugs. I don't feel "betrayed" or anything like that, but some things are too annoying/habit breaking/RAM eating. Krunner, a Quicksilver/Kupfer-like launcher, can't be disabled and I was told by KDE people that it governs over logout functions (WHY THE LAUNCHER? why can't I just have my alternative of choice without option to take it out or disable it?).
Well, at least the project is dynamic and a good fix/decision changes for better can happen eventually.
I've been "trying" KDE 4 for maybe a year or so. I like some things, but I hate most of them. At 4.5 it still feels like someone's abandoned alpha. Every new release brings new UI candy, yet breaks long-standing functionality or fails to address real usability problems (like that stupid desktop peanut - whose idea was that?).
What particularly irritates me is that they seem to be reinventing non-desktop features. Not only is this very much against the "Unix way", but they're doing a terrible job of it and the whole mess is wholly unnecessary. I don't know if we as users are doing a poor job of informing the devs about desired functionality, but I would love to meet (and murder) the person who thought Akonadi would be a good idea.
Perhaps I'm a minimalist, but I like KDE for mostly one thing: KIO slaves. I love the fact that I can open up a file browser and treat remote files almost as though they were local. That makes my life as a developer and sysadmin so much easier. Everything else is fluff to me, as long as I can fire up Kate and edit my remote server's configs I'm happy. On the flip side, everything that gets in the way of that location-shifting goodness is EVIL! Akonadi is evil. Half-assed transitions to libssh2 are evil. Godawful "toaster" notifications and ambiguous error messages are evil. The plasma interface engine randomly crashing every few hours is evil. All those unfinished K apps that nobody uses are evil. I could go on...
It seems the KDE people have forgotten that, above all, we just want a GUI to make our lives easier. Streamline it, trim off the fat, we're Linux users for fuck's sake. People are flocking to minimalist interfaces like Fluxbox, just to get out of KDE hell.
-Billco, Fnarg.com