An Open conversation about the future of Qt.
-
Just reading an article on the "BBC":http://www.bbc.com/news/technology-18527509 and it mentions Windows Phone 8 having native C/C++ API support. Does this mean a Qt port to WP8 is possible / allowed? If so, it might be an interesting option...
-
I vaguely recollect that this is more like "native" - but it's not full c++ support, just a subset that MS will allow. There was a separate thread for that on DevNet, you might want to look it up there, as I can't guarantee my memory to work well :)
-
it's not the thread I was talking about, but close: "link":http://qt-project.org/forums/viewthread/6751/P15.
-
-
bq. "I commissioned a deeper investigation into the scope of work required for Qt to work fully on Windows 8. I will receive the full review of this investigation early next week. I will make sure to share this detail with everyone as soon as I am able to."
"Chuck Piercey":http://lists.qt-project.org/pipermail/interest/2012-June/002751.html
Director Product Management & Key Accounts -
Well, for one, Qt is open-source so it is impossible to "kill" it. As far as I understand, Qt Project itself is also now not dependent upon Nokia per se for governance. I think the administrative costs and server costs etc. are paid by Nokia but those probably could be taken care of.
The question really is, where do the Qt contributors and maintainers employed by Nokia go now? How do we ensure that they can keep working on Qt full-time? I hope that divison of Nokia is sold to a home(s) where they can still keep working on Qt open-source.
As for mobile platforms, port to WP8 is a non-trivial endeavor. Android is a more likely destination, with some success already by Bogdan and others.
(About me: You have not seen me much around here, but I do love me some Qt and would love to contribute to Qt in my spare time, especially Android port.)
-
There is more to come.
Microsoft is "rumored":http://www.forbes.com/sites/ericsavitz/2012/06/21/microsoft-first-branded-tablets-next-their-own-cell-phone/ to be activly working on their own (non-Nokia) mobile devices; Research In Motion (BlackBerry) is "rumored":http://www.reuters.com/article/2012/06/24/us-rim-split-idUSBRE85N0D320120624?feedType=RSS&feedName=businessNews&utm_source=feedburner&utm_medium=feed&utm_campaign=Feed:+reuters/businessNews+(Business+News) to split or sell mobile devices division.
-
My two cents is this: I hope that in an ideal world the Trolls can be sponsored by a foundation like the FSF and also that Nokia would do the right thing and donate Qt to the same foundation and keep it free from commercial interests forever. Why Nokia has gone down the Windows 8 Phone route makes me shake my head in absolute disbelief.
-
OK. So this joint venture wasn't about using M$'s OS, but for Microsoft to put it's OS on Nokia devices. That makes more sense. I didn't even think of it that way.
-
My theory was MS actually wanted for Nokia to fail, so it can grab a nice chunk of Nokia's market share, which was pretty much dominating the mobile market a few years ago. Unfortunately for MS this plan didn't work out all that well, surely, Nokia lost its market, but it was immediately taken over by Apple, Samsung and a few other smaller Android platform players, MS is a big and slow to respond company...
-
I readed all the thread and nobody mentioned nothing about the "KDE Free Qt Foundation":http://www.kde.org/community/whatiskde/kdefreeqtfoundation.php, that means that in the worst, case the KDE proyect will aquire the ownership of Qt, and Qt will be controled by a real FOSS community.
The open source Qt is guaranted, there are no need to make a fork or to worry about the future. -
Sure, KDE Free Qt Foundation could end up with the rights on Qt. However, I doubt that would be a good thing for Qt. It is more like a last resort in case all else fails. With the transfer of the rights on Qt to the foundation, none of the infrastructure needed to run the project comes with it, let alone the resources needed to keep all those kick-ass developers working on Qt full time to make it the great toolkit we all love. So no, I'd much rather see a take-over by a company that actually can invest the resources to keep Qt running and keep it moving forward.
-
bq. With the transfer of the rights on Qt to the foundation, none of the infrastructure needed to run the project comes with it, let alone the resources needed to keep all those kick-ass developers working on Qt full time to make it the great toolkit we all love
You finally came to your senses, if KDE, a fairly big foundation and community cannot move Qt, what about the few volunteers you kept on repeating should stop "complaining" and write a complete modern GUI API...
On the other hand, the majority of effort, exerted by Nokia went in direction QML, the framework itself is fairly complete and most APIs are stable and done, KDE will have no problem maintaining what already exists, unfortunately, it won't have the capacity to innovate.
-
So no, I’d much rather see a take-over by a company that actually can invest the resources to keep Qt running and keep it moving forward.
It depends on which company, although nokia did sponsor Qt a lot, yet also in charge of
the road map of Qt.Could you imagine Qt taken by Oracle or MS? -
[quote author="utcenter" date="1343995985"]
You finally came to your senses, if KDE, a fairly big foundation and community cannot move Qt
[/quote]Moderator's note:
Watch your words, please. This forum is meant to be driven in a friendly manner. While we can "fight" with arguments, becoming personal, if not insulting, is not acceptable. We will delete further comments that do not fit into the "general rules":/forums/rules.Please not, that this is not to stop the actual discussion, but just to get everything back to a polite and unoffending track.
Thanks
Volker -
^^ Are you addressing me, as the act of quoting me infers? I fail to see anything impolite in my post, which merely noted he is finally agreeing with something I stated over and over again and he rejected. Overacting much perhaps? Having a bad day? Well, don't take it out on me ;)
