The Road To KDE Frameworks 5 and Plasma 2 89
jrepin wrote in with a link to an article about the steps being taken toward a Qt5 based KDE 5 and Plasma Workspaces 2. From the article: "KDE's Next Generation user interfaces will run on top of Qt5. On Linux, they will run atop Wayland or Xorg as display server. The user interfaces move away from widget-based X11 rendering to OpenGL. Monolithic libraries are being split up, inter-dependencies removed, and portability and dependencies cut by stronger modularization. For users, this means higher quality graphics, more organic user interfaces and availability of applications on a wider range of devices. Developers will find an extensive archive of high-quality, libraries and solutions on top of Qt."
Re: Frameworks (Score:1)
Re: (Score:2)
...K-K-KEEP IT!
two comments posted... (Score:1)
Remote desktop? (Score:4, Insightful)
NX is already pretty much unusable with compositing DMs, do they have a solution for remote desktop connections?
Re: (Score:2)
I know it would be potentially a lot more work, but it would be easier if KDE and GNOME and Ubuntu Unity had a fallback 2D mode that was friendly for remote viewers.
Re:Remote desktop? (Score:4, Informative)
KDE compositing can be turned on/off with a single key.
Re:Remote desktop? (Score:5, Funny)
LIES!
It takes three keys: alt, shift and f12, and NOT ONLY THAT BUT YOU HAVE TO PRESS THEM AT THE SAME TIME! This is clearly far too complex a process, and this bug should be given highest priority.
Re: (Score:3, Funny)
Re: (Score:3, Informative)
The shortcut is assignable...
Who down modded this? Obviously a joke.
Re: (Score:2)
Re:Remote desktop? (Score:5, Funny)
...it would be easier if KDE and GNOME and Ubuntu Unity had a fallback 2D mode that was friendly for remote viewers...
A fallback text mode for remote access would be really sweet. How hard could that be? <runs away>
Re: (Score:3)
Re: (Score:2)
I tried to sell them on Linux without X as a superior replacement, but I couldn't get any interest from the rest of the team. I set up a Linux server with XFCE and XRDP, the program menu in the bottom left, the clock in the bottom right, a taskbar, icons on the d
Re: (Score:2)
Re: (Score:2)
At a big company with lots of resources, we could just take the Windows team and send them to training with the edict "adapt to the changes or be replaced". But this is a very small company, and just as importantly these people are pleasant to work with and intelligent. Even if I had the resources and authority to steamroll changes in plac
Re: (Score:1)
Re: (Score:2)
Why don't you use X instead of VNC?
VNC sends small bitmaps over the connection. X sends draw commands.
RTFA? (Score:5, Funny)
Re: (Score:2)
Oh no, not again... (Score:2, Funny)
KDE moving to a new version of Qt? Abandon hope, all ye who dare to upgrade in its first three years of life...
Re:Oh no, not again... (Score:5, Insightful)
KDE 4.0 was missing a lot of expected 3.5 features, but a lot of the bad reputation it received were from terrible Kubuntu packages. The Kubuntu maintainers admitted they didn't understand the new build process or what they were doing. Canonical pushed it way too early and pushed crappy packages, but KDE took the blame. Early KDE builds on openSUSE, Arch, Fedora, etc. didn't have the same problems.
And honestly, I think only a year later (KDE 4.2) they had a great desktop for everyone.
The shift from KDE 3 to 4 (and Qt 3 to 4) meant a massive rewrite, and having to reinvent most of their core features.
KDE 5 sounds more like an evolution than revolution, so it should be smoother this time around.
Re: (Score:1)
This is pretty much on the mark, though it wasn't just the Kubuntu/Ubuntu camp that screwed up their KDE migration. KDE 4.0 and 4.1 were clearly alpha releases, neither stable nor feature complete. They weren't mean to be, they were developer previews. Yet many distributions migrated overnight without any thought to how that would affect the users. Kubuntu certainly made the mistake, Fedora did too. I think the SUSE developers were among the few to offer both the 3.5 and 4.x desktops side by side during the
Re: (Score:2)
KDE 4 is still missing the much loved KDE 3 feature of being able to slide the task bar off to the side.
Re: (Score:1)
Not really, panels can be configured to auto-hide. Sure, a button is not left anywhere but do you really care?
Re: (Score:1)
I care that it is much harder to configure. I care that the taskbar didn't work as well as 3.5 until I finally gave up and went back to Windows. Remember Kaskbar? Square Icons with a preview of the window. Exactly like Windows 7 before Windows 7. I'm positive that MS stole it from KDE. Could I figure out how to replicate it in KDE for the first couple of years? Nope. Finally give up? Yup. And have you ever looked at the bug reports on the auto-hide panels? Ugh, especially with dual monitor.
So yeah, I still
Re: (Score:2)
There were several plasmoids that allowed you to replicate Windows 7 taskbar functionality in KDE, and they've been available for years. I used this one back in 2009.
http://kde-look.org/content/show.php/STasks?content=99739 [kde-look.org]
I think the current version is here.
http://kde-apps.org/content/show.php/?content=148813 [kde-apps.org]
Re: (Score:1)
So should I use the one that isn't stable or the one that isn't found (404)?
I am more than leery or using extensions as part of my core _anything_. Gnome Tweak means you don't have it. KDE plasmoids on kde-look means you don't have it. And this is an example of why, the software you gave a link to no longer exists.
Re:Oh no, not again... (Score:4, Interesting)
I love that people are arguing that KDE 4 is missing a "core feature" that was actually a third-party add-on for KDE 3, but at the same time argue that installing a plasmoid means the feature doesn't really exist.
KDE 4 was designed to be extendable, and supports multiple methods of easily installing plasmoids. Installing content from the internet into KDE 4 was a core underlying technology since 2008.
http://userbase.kde.org/Plasma/Installing_Plasmoids [kde.org]
http://newstuff.kde.org/ [kde.org]
Re: (Score:1)
Kasbar was part of the BASE PACKAGE in KDE 3.5. It was included in at least three different distributions that I tried back in the day.
And now I'm suppose to install plasmoids that don't exist.
It does not exist. Honest. 404 (Score:1)
Re: (Score:2)
Most people don't install packages directly from the KDE Looks website I imagine.
My distro has a package for it in their main repository. I assume most do.
http://software.opensuse.org/package/plasmoid-smooth-tasks2 [opensuse.org]
And KDE allows you to browse for an install plasmoids right from your desktop.
Re: (Score:1)
Re: (Score:2)
Not really, panels can be configured to auto-hide. Sure, a button is not left anywhere but do you really care?
Bzzzt. No cigar. Autohiding is not the same as "sliding off to the side".
Re: (Score:1)
With auto-hide the computer decides when the panel is visible. With the button I decide when the panel is visible. I prefer the latter and hate the former.
Re: (Score:2, Insightful)
KDE 4.0 was missing a lot of expected 3.5 features, but a lot of the bad reputation it received were from terrible Kubuntu packages.
KDE 4.10 is still missing a lot of expected 3.5 features. I'm sure it's much closer to feature parity now (I'm assuming you can finally manage your system-level wireless connections in KDE, maybe fonts in KOffice even use decent kerning), but go back to KDE 3.5 and just look at the printing system. Seriously, just look at all of the things you can do to a printed document. Now look at the KDE4 one. Maybe KDE5 will fix this...
Re: (Score:1)
And where is my Kaskbar?
Re: (Score:2)
Kasbar was a third-party app, not officially part of KDE3. And it wasn't maintained.
But Smooth Tasks is pretty nice today.
Re: (Score:1)
"Kasbar is included in the kdebase package" - http://xmelegance.org/kasbar/index.html
If it is in the official release I'm counting it. And no official or semi-official replacement.
Re:Oh no, not again... (Score:4, Informative)
You're talking crap. KDE4 has managed wireless well for quite a long time. Not knowing this suggests you haven't used KDE4 in a long time and are just spouting some crap you once heard.
Re: (Score:2)
I ran KDE from 4.0 on, running openSUSE and didn't have crashes. I had no problems with Phonon until they started integrating PulseAudio.
Konqueror still existed. Some people were butt-hurt that Dolphin was simpler and the default, but that didn't mean you didn't have the option of running Konqueror.
How was Konsole bad?
KDE 4.2 == Awful Desktop (Score:1)
I made it until at least 4.3 and probably 4.4 before I gave up and went back to Windows. And this is from someone who hadn't used Windows in 4 years. KDE 4.2 was didn't hold a candle to KDE 3.5 for me.
Re: (Score:2)
I made it until at least 4.3 and probably 4.4 before I gave up and went back to Windows. And this is from someone who hadn't used Windows in 4 years. KDE 4.2 was didn't hold a candle to KDE 3.5 for me.
I stuck with 3.5.10 until 4.4 on some systems and 4.5 on others. But I haven't looked back.
Honestly, I looked at 4.0 through 4.3 from time to time but kept seeing that they were not production ready, and KDE themselves didn't call them production ready either - especially 4.0 and 4.1.
Re: (Score:2)
I was using Mandriva at the time and I can assure the early KDE 4 releases were just as unusable. I can't see how it was the fault of the Kubuntu maintiners, KDE 4.0-4.2 was half-baked, alpha quality software, full stop.
Luckily it's improved out of sight since then, but it's a worry that the KDE developers still don't acknowledge their mistake in releasing those early versions as releases, and not alphas or betas. I really hope they don't make the same mistake with KDE5.
Where are the screenshots? (Score:4, Insightful)
The summary essentially says "KDE is going to look better". Where are the screenshots?
Re: (Score:2)
I think it says "If you like KDE today, better watch out and don't upgrade until at least 5.2."
Re: (Score:2)
The summary essentially says "KDE is going to look better". Where are the screenshots?
They're improving the graphics pipeline - no matter what the eye candy looks like, it's going to render to the screen better.
Organic user interfaces? (Score:3)
What does "more organic user interfaces" mean?
If that means that developers are more free to break with conventional UI's and come up with their own "innovative" controls and other UI interfaces, I don't want that - that sounds like when Flash designers started going wild on the web and each Flash web site had its own UI elements and the users had to figure out that flipping a virtual switch on one website was implemented as shooting an arrow into a target on another website and on another website you had to click the virtual LED light that was actually a button (but you don't know it's an active UI element until you discover that it's clickable).
Re: (Score:1)
What does "more organic user interfaces" mean?
Fewer pesticides.
Re: (Score:2)
What does "more organic user interfaces" mean?
Fewer pesticides.
Now that's a UI I can support - I had to stop using Windows because their pesticide laden UI was giving me a rash.
Re: (Score:1)
What does "more organic user interfaces" mean?
Fewer pesticides.
But then you get more bugs.
Re: (Score:2)
Free range electrons and photons.
Re: (Score:2)
it's supposed to mean that the interfaces spring up from genuine need for functionality at a certain place, not from some UI nazi deciding that all file dialogs shall be purple and have ability for previewing web pages.
Re: (Score:1)
An organic user interface means that the mouse is furry and the keyboard moans when you hit the "right" key, and when X is booted you'll be presented with the "operating system host" which is a Blender rendered ent that only take entish spoken commands (like Unity); the system will turn itself off at 8pm to sleep untilsunrise, and often not be responsive when there are other virtual events requiring system resources, like floods and firestorms.
Please don't screw up Kmail (Score:5, Insightful)
KDE devs: Please do not screw up Kmail more than it already is. In fact, please put serious thought into restoring the good old filesystem-based folder database and just do away with that horrible Akonadi mistake that is dog slow, when it works at all. Running critical apps on top of a full blown database may look like a good idea on a Presenter slide, but in reality it is just cruel and unusual punishment.
I know this isn't strticly related to Qt5, but just try to keep it in mind ok? Thxbai.
Re: (Score:3)
Man, I totally agree with you. I've used Kmail since KDE2 and despite its flaws, I generally liked it better than the alternatives (and I've tried many). It's always annoyed me that while there are several GTK email clients, the KDE desktop really only has kmail, and they royally screwed the pooch with all this akonadi crap.
I just discovered an alternative. It's like watching a star form in the distance out of clouds and ether. It's Trojita (http://trojita.flaska.net/screenshots.html [flaska.net]) and it's written b
Re: (Score:3)
I don't think that the database is the problem. The problem is that Akonadi is about as decent, code- and design-wise, as aRts was. Long on promise, short on delivery -- designed and implemented by people who demonstrably don't have enough software engineering experience. College kids may be bright and hard working, but that's no substitute for a certain amount of experience and understanding of the engineering side of things. Just look at this software engineering "recommendation" [kde.org] to give the idea what's w
Re: (Score:3)
I don't think that the database is the problem.
It's certainly part of the problem. The database may be fast, but it isn't anywhere near as fast as the underlying filesystem. And you are right, the basic design flaws are compounded by very obvious inexperience at designing and developing multitasking applications.
Re: (Score:2)
Huh? The database isn't there just to store data. It offers indexing, structured queries, etc. Usually, when people implement that functionality on top of a filesystem, it ends up as a yet another me-too half baked "database". It's like with any sufficiently large software project having half-baked LISP functionality in it :)
Re: (Score:2)
Huh? The database isn't there just to store data. It offers indexing, structured queries, etc. Usually, when people implement that functionality on top of a filesystem, it ends up as a yet another me-too half baked "database"...
You sum up perfectly why this idea looks so good on a Presenter slide. Never mind that the reality sucks. Because in real life, the database is a whole lot slower than the filesystem and introduces a lot of new boundary conditions that tend to completely overshadow the shiny new functionality introduced. Sorry, but there's a big gap between the way you imagine the the universe, and how it actually is. You'd have done well on Bill Gate's Vista design team. Entirely designed on Powerpoint slides I understand.
Re: (Score:2)
You're crazy if you think MySql is somehow underpowered for Akonadi. It's not the problem. The problem is with how Akonadi's details were engineered, and how it was executed. If you seriously think a mainstream database is too slow to do relatively simple indexed queries on a *personal* email/contact database, you're crazy. The database is not a problem. That's about the only design decision I agree with. The filesystem does not offer the data indexing and querying functionality that you need in an email ap
Re: (Score:1)
Re: (Score:2)
I'll second this. That said, I'd settle for the ability to reply to HTML emails without totalling the formatting, given that it's pretty much the only reason that I have to use an alternative these days.
(Not sure if this is fixed in a later version - I'm on Debian, so I'm still using 4.4 because of the feature freeze.)
Meet me half way (Score:1)
Deduplication (is that a word?) (Score:5, Insightful)
A lot of classes were rewritten way back in the day when the licensing of Qt was under fire. Once those issues went away there really wasn't much point in continuing the duplication of effort. Bringing the two back together is long overdue. In the long run it could bring greater stability to KDE applications since more developers will be working on improving the same framework instead of two independent but close frameworks. This is good for both Qt and KDE.
Re: (Score:1)
Ummm... this isn't correct. KDE developers never had a problem with the licensing of any of Qt classes. What this is referring to here is that either 1) something was written in KDE that wasn't available in Qt and Qt has since added support for it - might as well use the Qt version, or 2) a Qt class was extended with a KDE version to add extra functionality and Qt has added the functionality or the functionality is deemed not important enough for an extension.
Re: (Score:3)
Ummm... this isn't correct. KDE developers never had a problem with the licensing of any of Qt classes.
Not the Qt licensing per se, but a lot of KDE developers have problems with the Qt contribution agreement. In order to support Qt Commercial etc. you essentially have to sign away all rights to the code, here's perhaps the most relevant part:
Subject to the terms and conditions of this Agreement, Licensor hereby grants, in exchange for good and valuable consideration, the receipt and sufficiency of which is hereby acknowledged, to Digia a sublicensable, irrevocable, perpetual, worldwide, non-exclusive, royalty-free and fully paid-up copyright and trade secret license to reproduce, adapt, translate, modify, and prepare derivative works of, publicly display, publicly perform, sublicense, make available and distribute Licensor Contribution(s) and any derivative works thereof under license terms of Digiaâ(TM)s choosing including any Open Source Software license.
As a result, a lot of code in the KDE libraries that could ideally could have been enhancements to Qt instead (both being LGPL) have remained outside Qt and will most likely remain so. Reducing the duplication has been a stated goal for ages but in reality not much happ
Re: (Score:2)
You've missed the non-exclusive part, for one. You're not signing away all rights to the code. Just the rights enumerated above. You can do with your code as you please, and they can do with their copy as they please as well, within the limits of non-exclusivity! You're not losing any rights to your own code! You can, for example, publish it under a license of your choice -- if the code is not a Qt-derived work in the meaning of copyright law. So, if it's not a derived work, you can publish it under BSD, or
Re: (Score:2)
True, you keep a slither of positive control in that you can still release it under the licenses you want, but you can't stop your code being used anywhere under any circumstances in any form since the license grant is pretty much limitless. Not exclusively so, but limitless all the same. I'll give you one Hermes Conrad point for being technically correct, though.
Re: (Score:2)
We're doomed, doooooomed.... (Score:1)
" means higher quality graphics, more organic user interfaces "
How awesome! When I'm working with a spreadsheet I always wish it was more organic instead of just a boring old grid. I think I would be way more productive if it were organic.
And yeah, I'm sure we've all been there - you go to click a button or type into a form and notice how the graphics quality is so low - it's like they don't know that I have BluRay on my computer or something, even though VLC is installed and can do 1080p.