KDE Developers Discuss Merging Libraries With Qt
An anonymous reader writes "A proposal has been brought up with KDE developers by Cornelius Schumacher to merge the KDE libraries with the upstream Qt project. This could potentially lead to KDE5 coming about sooner than anticipated, but there's very mixed views on whether merging kdelibs with Qt would actually be beneficial to the KDE project, which has already led to two lengthy mailing list talks (the first and second threads). What do you think?"
Keep the specifications as they are. Fix all the current issues and make a SOLID product. It's good, but could be a LOT more stable and tight. When that's done, then go for the big merge and add new features.
Tamran
Why don't we finish some unfinished projects (Quanta) that many people are waiting for before changing things again.
"Enjoy what you're doing! If it becomes drudgery, you're doing it wrong!" - Jim Butterfield
It's a cute idea, but how much does QT benefit from it? QT has grown a lot over the past few years and feels rather bloated already.
I think Linux is for faggots. Mod me down if you agree.
If you find this post offensive, don't read it! THINK ABOUT YOUR BREATHING! I am what I am because of how apes behave.
I'm sure it would be convenient for the KDE folks, but wouldn't this be a little superfluous for everyone using Qt on non-KDE platforms? Qt is a pretty massive runtime as-is...piling in the KDE libraries seems to me like it would be adding a lot of weight for relatively little benefit to anyone other than KDE. I don't use KDE myself, but I have been developing for Qt for a while...anyone who knows more about the KDE libs feel free to correct me if there's actually some great benefit I'd yield from having the KDE libs included in Qt...
Everything else is trivial by comparison.
I think I don't want to read anything posted on Phoronix.
No! No! No! I enjoy having Qt free from other stuff! It's big enough already! If you want, just make a system better of find a way to communicate better, but DO NOT FUCK MY PRECIOUS Qt!
I'll fork it if I have too!
Have you heard about SoylentNews?
I don’t really see how they should be able to merge as long as Nokia requires copyright assignment.
KDE is GPL. Qt is unfree OR LGPL OR GPLv3, as the developer wishes. Qt with KDE could only be GPL.
And I don’t see a reason to deprive free software developers of the advantage which KDE offers them over developers of unfree software.
Being unpolitical
means being political
without realizing it.
... maybe the mystery of why both payloads continue to bloat /opt can finally be resolved.
Hint: Hey, fellas! There are these fancy, new fangled dirs called /usr , /lib , and /bin ! Try 'em out!
After seeing the last attempt at cooperation over Phonon - which was half-implemented in Qt, then Nokia went with Qt Multimedia while KDE continued evolving Phonon but all the new things aren't in Qt I wouldn't want them to try. Some of the functionality that exists on the KDE layer should be pushed down into Qt, but most should stay out otherwise there will be far too much platform in the toolkit.
Live today, because you never know what tomorrow brings
Like we've seen time and time again throughout history, the best innovation always comes when there's a lot of competition. Open source desktop environments are no different.
KDE needs some real competition. A decade ago GNOME was that competition, but these days the GNOME project is basically dead. GNOME 3 has been delayed for so long that most people have given up hope of it ever being released. The September 2010 release date has now become March 2011, and I doubt that's even a reasonable date. Even if it is released, it will be significantly behind the times in terms of features and functionality.
There are other open source desktop systems, but they're very marginal. There are very few XFCE and GNUstep users, for instance. This is because those desktops strive to fit a very small and specific niche. None of them can provide any sort of competition for KDE.
KDE considers yet another massive reorganization and new version! Certainly this won't affect usability or the long term future of the project at all, just like the transition from KDE3 to KDE4 didn't!
STOP . AMERICA . NOW
Currently Qt requires copyright assignment (as I understand it) for code to become part of Qt proper. This is going to be a non-starter for a lot of open source folk. As I understand it,this was one of the biggest issues with the OpenOffice.org project in terms of community health, and one of the main drivers for LibreOffice. Qt has gotten away with it better because most of the things people want to do with Qt USE the toolkit instead of CHANGING the toolkit, but it remains a concern. As long as that restriction is in place Qt remains extremely dependent on Nokia continuing development. To date they've done an awesome job - Qt is arguably the best option for cross platform open source graphical application development out there - but longevity for open source is measured (at a minimum) in decades. Corporate good will is thin ice on those time scales - what if Oracle bought Nokia? Could "LibreQt" succeed as a community project without the considerable resources being funneled in by Nokia, if it ever came to that pass? (OK, the other side of this coin is that Qt is ALREADY essential to open source - that concern exists regardless, but it's something to think about in a move like this. Would putting the relevant kdelibs functionality in Qt result in less community familiarity with the code over time?)
Anyway, the KDE devs who wrote the code in question would have to sign on, and to me that sounds like a long shot. The other option - Qt devs implementing Qt versions of features currently in KDE and then KDE moving to the new stuff - sounds slightly more practical but would require a serious manpower commitment.
"I object to doing things that computers can do." -- Olin Shivers, lispers.org
I think it's pretty irrelevant since it seems that the effective goal of the KDE developers is to mimic Windows Vista and 7. Besides the window manager, just look what they did to Amarock between 3.5 and 4.0 as a prime example for what they have done with the apps. It's like Winamp3.
It seems like the KDE folks are desperate.
Nokia loves Qt, but they don't like KDE. If you look at the Meego platform, it has plenty of parts from the Gnome world (GStreamer, GLib, GConf, Tracker, GUPnP, GeoClue etc), but nothing, zero, nada from KDE. The only KDE related thing they use is Qt (because they own it).
The reason for that is simple, the KDE folks are not so good as building infrastructure. Look at Phonon, it's so bad that the Nokians are forced to write QtMobility Multimedia and now finally they're doing QtGStreamer (so you can just use GStreamer directly with a Qt-ish API).
It's also interesting to note that Meego IVI and Netbook as still Clutter based, not Qt..
It depends on which functionality they really want to move to QT. If I understand it correctly they want to move the plasma stuff, which is GUI code, to QT. That makes sense. Just like moving GUI stuff from GNOME to GTK and GDK. However, it makes no sense if they want to move other parts of the application model to QT. It would not hurt, but there would be no benefit.
Basically, there's three phases of software:
1. Software that's in development. Sure, there's bad decisions made, but at least things are changing. After a decade of neglect, Windows seems to be back in development mode. KDE is definitely in development mode. Developers love this, because nothing has to be "finished" or "bug free." Everything can be a quickly hacked-together proof of concept.
2. Software that's in support mode. Almost nothing happens, except for a few patches. Mac OS X seems to be in support mode these days, same with Gnome. Support mode is actually a good thing for users who are used to the product, but developers will get bored.
3. Software that's dead. No patches, the developers abandoned the project. Eventually the users will disappear as well.
There's no -1 for "I don't get it."
Qt (Nokia) doesn't care about KDE. However, KDE cares about Qt.
So they shouldn't merge kdelibs into Qt. They should merge Qt into kdelibs.
The one positive thing about Qt is that there's at least a remote chance of it becoming genuinely free software... someday... If this merger means more code falling under this condition - good.
Will this mean Debian will break less due to KDE updates? If so, I'm all for it. If not, I probably won't care either way.
Ask me about repetitive DNA
It's not just the copyright assignment: it's also the fact that Qt is now controlled by a huge organization (much like OO.o is). Nokias goals for Qt may already be quite different to KDEs goals for kdelibs, and if something is certain it's that corporate interests change. We cannot tell what Nokia wants to do with Qt next year, or in in five years.
I don't know about you, but I had a REALLY hard time getting used to running tshark instead of tethereal.
Can you imagine the havok if we suddenly have KQtDE, KQtonqueror, KQtXSLDbg, KQtBibTeX, KQtSVN, KQtDiff3, KQt9Copy, KQtb3, and so on?
Madness! Re-tooling this many brains is NOT worth it!!
Do daemons dream of electric sleep()?
Nokia no longer requires copyright assignment for Qt.
Whatever they do regarding this issue, I just want to implore the KDE devs to please focus on stability and performance improvements for the next few point releases, rather than adding any more new features.
KDE4 has the potential to be an awesome IDE; the improvement from 4.0 -> 4.5 has been excellent. The problem at the moment is that it's a resource hog and the apps (e.g. Okular) still crash from time to time. The file manager Dolphin is particularly slow. Despite this, I still prefer KDE4 to the competition, but it could be so much better if the issues I (and many others) have outlined are addressed.
It's not just the copyright assignment: it's also the fact that Qt is now controlled by a huge organization (much like OO.o is). Nokias goals for Qt may already be quite different to KDEs goals for kdelibs, and if something is certain it's that corporate interests change. We cannot tell what Nokia wants to do with Qt next year, or in in five years.
Everybody is in agreement on where Nokia is. Mobile is tier one, everything else is tier two, the question is really if KDE should keep making thin convenience classes like KIcon on top of Qt's QIcon or just hand that stuff to Nokia. By being in kdelibs it should already be LGPL, so really the question is can Nokia do something useful with a little desktop-oriented code they could put in a fully proprietary app instead of a proprietary app using LGPL libraries. I suppose it's possible, but I think it's more principles than practice that is the problem here.
P.S. Technically it's not a copyright assignment, but they demand full relicensing rights so in practice they can do whatever they want.
Live today, because you never know what tomorrow brings
Quote from the parent comment: '... that can legally only happen if Nokia moves away from the currently mandatory "right to relicense..." '
."
Could you explain the "right to relicense" and provide a link? I don't see a reference to that on the Qt web site.
This paragraph illustrates two issues with Qt: 1) a possibly impossible licensing provision, and 2) managerial sloppiness. Quoting exactly:
"You must purchase a Qt Commercial Developer License from us or from one of our authorized resellers before you start developing commercial software as you are not permitted to begin your development with an open source licensed Qt version and convert to the commercially license version at a later
License provision: If someone develops some code using a free version of Qt at home, and re-implements that at work, an entire commercial project can be corrupted, apparently. It seems that license provision is impossible for Nokia to enforce, and also impossible for a company to defend against, if Nokia brings a case against a particular project. It's common that commercial programmers consider programming issues at home. How would a company show that there was no contribution to a commercial product from the free version of Qt?
Why should open-source developers care about close-source licensing provisions? Because, historically, technological development moves away from undesirable conditions. That makes the long-term prospects uncertain.
Sloppiness: At present, 2010-10-31, 16:34 PDT, the last word of the quoted paragraph is missing. What will happen now that Nokia bought Qt? Will there be internal politics at Nokia that prevents sensible management? There is a lot of sloppiness; that's only one example.
Don't Nokia managers look at their own web site? My company does that kind of work, and we've found that, perhaps surprisingly, sloppiness in communication generally indicates serious problems with management.
How about they fix the steaming bloat-fest that is KDE4 before thinking about KDE5?
LK
"Hi. This is my friend, Jack Shit, and you don't know him." - Lord Kano
You can also determine whether the tenant is a sex offender. Rental background check also protects the tenants you already have in your rental business. nhl jerseys , in an initial day of meetings with China's leadership nfl jerseys, stressed cooperation on pressing economic nba jerseys, security and environmental challenges mlb jerseys, rather than focusing on issues like human rights and soccer jerseys religious freedom that have historically divided the U.S. and MBT shoes China .Mrs. Clinton announced Saturday that her Chinese counterpart cheap mbt shoes, Minister of Foreign Affairs Yang Jiechi wholesale ugg boots, will visit Washington in early March to help coordinate a U.S.-China response wholesale Christian Louboutin shoes to the global economic crisis ahead of the Group supply cheap Christian Louboutin shoes of 20 summit in April in London.Hillary Clinton attends sell discount Christian Louboutin shoesOf course, you may never want to have a tenant who is hot-tempered, has served jail time for a criminal act.
http://www.mbt-shoes.com
Qt is on LGPL for some time now. What you wrote was true few years backwards.
http://qt.nokia.com/about/licensing/
Qt is on LGPL for some time now. What you wrote was true few years backwards.
http://qt.nokia.com/about/licensing/
It's still true today. You can probably do anything you need to do under the LGPL, but in the event you find some need to have a commercial license, then you still have exactly the same old impossible model. Whoops, we have to rewrite all the code from scratch, since we didn't begin development with a commercial license. Or we can just pretend we started over from scratch, since there's no way to prove anything.
Their commercial licenses are a completely stupid model.
Maybe merging KDE with QT libraries will stop the finger-pointing when there is a problem between them...which occurs after every KDE release and sometimes with QT updates.
At the risk of trolling, KDE is already in enough trouble and they really shouldnt be worrying about this kind of thing. They should be fixing bugs, removing Dolphin and dumping that stupid pulse audio support. KDE3 is forking and Trinity exists for a reason. Don't be GNOME people, Don't be GNOME. Bugger the features, bugger futureproofing where you don't know whats going to happen, bugger contaminating other libraries, JUST FIX THE BUGS AND MAKE IT PERFECT. Otherwise you are going to wake up and find XFCE has won the war (and it IS winning it).
You have a valid point - the most probable scenario is that NOKIA and Microsoft would merge (or in other words that NOKIA would be assimilated) at some point in the future. Look at all the signs - the writing is on the wall.
That would put KDE in a far worse position than anything SUN created, as Oracle is dependent on the success of Java.
I use Windows, like 95% of planet earth, and the other 5% uses Mac. Who cares about what developers of a desktop used by 12 or 13 people think ?
Not really, Qt is LGPL licensed and you can switch from GPL to LGPL licensing (according to the FAQs) so the worst case is that you have to follow the LGPL as far as the Qt libraries do.
As Qt is licensed per developer, they would presumably be covered when working from home as well.
...because I use wxWidgets / wxPython and I believe it's far better than QT.
This is a quote from the Qt licensing FAQ:
"Can I switch from using Qt under the LGPL to commercial afterwards?
"No. Users of the LGPL versions of Qt need to comply with the LGPL licensing terms and conditions. Qt's commercial license agreement contains a restriction that prohibits customers from initially beginning development with the LGPL-licensed version of Qt and then transitioning to a commercial version of Qt."
Four sections earlier, the FAQ says this, in part:
"... If you are uncertain as to whether or not you will be able to comply with the LGPL requirements at the time you begin your development, our recommendation is that you purchase a commercial license as it gives you the flexibility to decide licensing (commercial or LGPL) at the time of distribution."
It seems to me that it would be easy for a company to create a legal mess for itself. What a company will do in the future cannot be foreseen.
What would happen if a developer at a company who did not have a commercial license, but was using a free license, contributed to a commercial project? Often there are discussions about architecture, and someone may contribute ideas for an architecture that are later adopted. The sociology of programming is not as clean as Qt licensing apparently considers it to be.
Note that this problem was not created by Nokia. It existed when Qt was owned by Trolltech.
Instead of a huge change like Gnome Shell, they should (also) be fixing just a few basic usability issues:
-when you select a file in Nautilus and do Ctrl+c or Ctrl+v, they icons should indicated that they've been copied or cut.
-the "Recently Used" in the File Open dialog saves you from a lot of needless folder hopping. But it should also include recently used folders as well (the folder of a file you just saved, plus folders you created recently). "Recently used" should also be present in Nautilus.
-if you choose "single-click" behavior in Nautilus, the File Open dialog should also be single click. OK, so the latter is from GTK-- just add single click to GTK, then have Nautilus set the option for it.
I'm not a lawyer, but I play one on the Internet. Blog
>For example kio_slaves or gnome's vfs which are great features (for sftp, ftp, etc...)
This.
For those that don't know what he's talking about: Open up Nautilus. Do File: Connect to Server. You get a dialog asking your for your (S)FTP login info. Connect.
Now you can open up remote files in gedit or whatever. Copy/paste/drag, etc.
Works for WebDAV and Windows shares, too.
I'm not a lawyer, but I play one on the Internet. Blog
There's a bug going around the OSS community that causes some to see corporate monsters where there are none.
Not only that, but it also causes them to brainstorm or take pro-active action against corporate sponsors because their Palantirs say they "might" stop support at some unspecified future date. See LibreOffice. Does nothing other than annoy the corporate sponsor, divide the community, and thus possibly bring up that exact scenario in a self-fulfilling geek-martyrdom prophecy.
I'm not a lawyer, but I play one on the Internet. Blog
The thing about Opera is it takes too much resources, and it's too slow. You can watch it redo a page, whereas Chrome is instantaneous with Ctrl+Page'ing through pages. That was Opera latest on Karmic.
I'm not a lawyer, but I play one on the Internet. Blog
(nice offtopic trolling but) Opera works rather fine for me (i.e. instantaneous). I'm using Debian though.
Quick way to get 30% Funny 70% Troll: defend Opera browser on
"He makes a lump-sum statement withaout backing anything up and gets an "Insightful" rating. I merely ask what exactly he means and get "Troll"??? WTF??"
Agreed - but this is /.
Me? I love KDE 4.2 and later. KDE 4.0 was a bit thin, but still stunning. KDE 4.1 a bit better.
As for bloat, KDE 4.x runs well even on an ATI Radeon 9200 SE, which was low-end when it came out, in 2003! KDE is a charm!
For what possible reason do they require a true RDBMS rather than something like bdb or even sqlite if you want to get crazy? But frankly, why wouldn't you simply use xml (bottom of the list), flat files, csvs, or some such thing behind a configuration server?
Once the configuration server has abstracted concurrent access to your machine's and user account's settings from multiple applications running in multiple sessions, it might as well be using an RDBMS such as SQLite as its storage backend. If I were writing a registry replacement for a desktop OS, I'd probably use SQLite too.
Keep the specifications as they are. Fix all the current issues and make a SOLID product. It's good, but could be a LOT more stable and tight. When that's done, then go for the big merge and add new features.
one of the reasons KDE apps go down in flames with segfaults is KDElibs' memory management. Qt can remove the memory cleanup work with it's garbage collection. However, it's still possible to manually destroy things, so it's not mandatory. Make it work and then make it efficient.
the root of evil code is premature optimization.
"That clause was a clear shot at people trying to get away from paying for Qt."
I have a good impression of Qt, Trolltech, and of Nokia. However, the license arrangement seems to cause potential problems.