Originally posted by GreatEmerald
View Post
Announcement
Collapse
No announcement yet.
Nokia's Actions Already Harm Qt 5.0 Release
Collapse
X
-
Originally posted by funkSTAR View Post
Comment
-
Originally posted by n3wu53r View PostNot to mention the widgets Digia sells are similar to Qwt which is LGPL only.
So digia hasn't done any foul here at all.
Completely different looks and target market.
As for the foul, this is indicative of an "open core" future. While it may not be bad _yet_, what it's pointing to is.
Comment
-
Originally posted by funkSTAR View PostThey(Nokia) want proven customer cases to show the paying crowd.
I know that when I go to work, I'm not working for free. You?
So if a portion of Qt doesn't bring in the bucks, then it makes logical sense that it wouldn't be a top priority, or outright cut.(which is the case here) I'm all in favor of these removed Qt libraries integrated directly into KDE, or as Lars suggested. At least they won't be totally killed off, if there's functionality that's necessary.
Nobody has unlimited resources. Nobody. So priority has to come into play.
And KDE is a nice puppet who follows Qt. So you will se (an attempt) to port to Qt5 even before Qt5 is ready and KDE is ready. Sad but true.
Comment
-
Originally posted by n3wu53r View PostThe only concerns I have with Qt 5.0 are moving a way from C++ to Javascript (IMO bad) and less features (the point of the article).
On Nokia's website there's quite a lot written with regards to interaction between C++ and QML.
Comment
-
Originally posted by curaga View PostIf you take a look at the screenshots of both, you'll see they aren't the same at all. Qwt = scientific, ugly, mostly dots, lines, charting = pretty charts, pies, effects.
Completely different looks and target market.
As for the foul, this is indicative of an "open core" future. While it may not be bad _yet_, what it's pointing to is.
So if a portion of Qt doesn't bring in the bucks, then it makes logical sense that it wouldn't be a top priority, or outright cut.(which is the case here) I'm all in favor of these removed Qt libraries integrated directly into KDE, or as Lars suggested. At least they won't be totally killed off, if there's functionality that's necessary.
Isn't QML more advanced than Javascript? Perhaps it could even be said that it's(QML) a mix between the two?(the two, C++ and Javascript)
On Nokia's website there's quite a lot written with regards to interaction between C++ and QML.
Below is what they want from developers when they write a new Qt 5.0 application (not porting existing ones, new apps from scratch in 5.x).
1) do all the UI in QML, logic in C++
2) or do it all in QML
However QML only uses non native widgets. It doesn't use the native ones of the platform until at least Qt 5.1
See: http://labs.qt.nokia.com/2011/03/10/...s-for-desktop/
Also QML was really intended for mobile.
Comment
-
Originally posted by n3wu53r View PostThe KDE QT agreement kicks in and Qt goes BSD licensed?
It is quite easy to avoid this happening. Just keep making yearly bugfix releases to Qt and deliver all new features in commercial addons. And to keep it proper, make partners do it. Just like Digia is doing these days. Nokia has all they need to avoid this. KDE ev.s agreement with this commercial and evil entity is not worth more than the used to sig the Munich agreement.
Comment
-
Originally posted by funkSTAR View PostYeah right. A white knight will appear and save Qt and the lords virgin daughter.
It is quite easy to avoid this happening. Just keep making yearly bugfix releases to Qt and deliver all new features in commercial addons. And to keep it proper, make partners do it. Just like Digia is doing these days. Nokia has all they need to avoid this. KDE ev.s agreement with this commercial and evil entity is not worth more than the used to sig the Munich agreement.
THERE ARE NO COMMERCIAL ADDONS.
They haven't touched the API.
They haven't added any classes.
It's just a few widgets to help you make pretty looking charts. The most of the same functionality is in Qwt, except Qwt is lacking in the looks department and is LGPL only. With these commercial widgets Digia's customers don't have to be obligated to the LGPL and get support (the purpose of commerical verison in the first place). There are a few things not in Qwt like Pie charts, because well this is targeted at business.
Guess what, Digia isn't alone ICS and KDAB also sell pre made widgets. Hell, ICS even has charting widgets like Digia: http://www.ics.com/products/qt/kdchart/
If they ever touched the API and fragment Qt I'll eat my hat. Digia isn't stupid, they run a business. They know it wall _harm_ their business to fragment and open core Qt, it will piss off every single Qt developer.
Besides, what does Qt need saving from, right now it is certainly not Digia. It needs saving from Nokia because they no longer care/want Qt. Let me explain what a company does when they no longer want/need an asset. Do they kill it off? No because companies like money and they would make $0 off killing it, and would only do that if there is no buyer. They sell it.
Also Qt is backed with many massive corporations invested in it, Nokia couldn't kill it no matter how bad they wanted to. You know when companies as big as Google, Samsung, HP, Seimens, Philips, Panasonic, Volvo, ect. are invested in Qt, they have legal clauses and other measures to ensure Qt is still around.
All the facts seem to point to a sale of Qt, there is nothing to worry about.
We only have to really worry if a horrible company is announced as the buyer.
So please stop spreading FUD. End your trolling. You are obivously a Gnome fanboy looking at the last thread: http://phoronix.com/forums/showthrea...3-6#post278982
Whenever someone says things that prove your points wrong, you pretend nothing happend and ignore whatever was said. Your probably going to ignore half the stuff in this post too.
Comment
Comment