[Qt-qml] QML if Nokia goes WinPhone7?

[Jason H]

Qt-interest has had a thread on this, and engadget has several posts. 


However on your points:
"Specifically, through this deal, Microsoft effectively has primary control of 
the Qt product line."
is absolutely false. The git repos are open, and will remain that way. Someone 
in qt-interest said keep with the main branch until they stop accepting 
contributions, then fork away.

Qt and MeeGo are still essential to the tablet line. WP7 won't ever be on a 
tablet because MS wants a full Win7 license for it. So MeeGo is it.

We'll still have what we want, but my bet is that the enhancements will come 
slower.

QML is absolutely awesome and is likely immensely important to the tablet 
endeavor. So I think its here to stay.






________________________________
From: Charley Bay <charleyb123 at gmail.com>
To: Mark S. Townsley <mstownsley at gmail.com>
Cc: qt-qml at trolltech.com
Sent: Fri, February 11, 2011 5:08:24 PM
Subject: Re: [Qt-qml] QML if Nokia goes WinPhone7?

Mark spaketh:

>
>While it may be obvious, I do not believe it is confirmed.

Good point:  It is not confirmed exactly what this future means.  However, IMHO, 
there's maybe 72 hours  to hurry-and-reverse-course, and IMHO, that is quite 
unlikely.

Specifically, through this deal, Microsoft effectively has primary control of 
the Qt product line.
  

Is Nokia going to abandon QML and the rest of Qt toolchain?
> 

Yes.  Qt will be used for Meego, which effectively is also killed.  In short, Qt 
is no longer part of the Nokia value proposition, as I read it (and I wasted 
five hours of my life today reading threads and analysis).

In its place, the Microsoft toolchain and .NET will explicitly be used.
 

Remember that Qt toolchain is not just for phone.  It is used by many other 
things and has been around for a while as a cross-platform C++ toolkit.
>
>

Agreed -- most of my work is "heavy desktop" (commercial), including my use of 
QML.  However, I can no longer justify commercial development using Qt nor QML.  
Quite literally, in every sense, they have no place in the forward-looking Nokia 
business plan (so "real" developers have no way to appraise the Qt product 
offering).

It is possible Qt is sold off.  However, IMHO, Microsoft will exercise as much 
power as it is able to disallow that (to kill Qt).  Of course, an LGPL-fork is 
always possible.

IMHO, an LGPL-fork will be imminent.  We can re-assess possible Qt and/or QML 
use after that spin-off and/or fork.  But yes, in the mean time, BRICK WALL.

This was an absolutely disastrous decision in the short-term, in terms of 
developers using Qt.  In the long term, it may be positive, specifically because 
the net result *may* be Qt/QML/Quick managed independent of the Nokia parent 
company, which has irreversibly alienated its current developer community.

Bummer, since I still think Qt/QML is best-of-breed for state-of-the-art today 
(by a lot).


 
____________________________________________________________________________________
It's here! Your new message!  
Get new email alerts with the free Yahoo! Toolbar.
http://tools.search.yahoo.com/toolbar/features/mail/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.qt.nokia.com/pipermail/qt-qml/attachments/20110211/a67f122a/attachment.html