Microsoft want’s to push and sell their own tools. I do not see any valid reason for them to support a product that is clearly in competition with theirs.

This is not a technical problem – I’m quite it would be possible relatively easy. Qt is already working (at least kind-of) on iOS, but I doubt there will be any official version.

So, maybe some community project may port it to WP7, but I don’t see any effort on this from Microsoft nor from Nokia. Remember, we’re talking about business here, not community or what “would be good”.

Also for online app-stores to work best and on all devices there must be some tools/framework/run-time environment uniformity.

The official answer is here [conversations.nokia.com]

“Also for online app-stores to work best and on all devices…”

Honestly, that’s just an excuse, not a reason. ovi was supposed to work the same for all platforms. It (ovi or msappstore) could work just as well with WP7.

I guess that there will be an unofficial port like the ones that are currently brewing for Android and iOS. We’ll see.

Yes it’s only an excuse, but it’s a good one, for Ovi Nokia was the author of: software(OS and Qt) and hardware and website so Nokia was the only “dictator” there, now with WP7 there are many producers and Microsoft is the one in charge ;)

Anyway Nokia phones “primary” OS will be Windows Phone 7, this is achieved by:
1) launching another 150 millions “burningSymbian” devices
2) launching one device with MeeGo (this means Nokia still works on MeeGo with Intel) and
3) we will see if MeeGo gets more market share than Nokia WP7…

marsupial wrote:

Hi,

the question in the title is something I’ve been wondering about a lot. I haven’t worked with WP7 and do not plan on doing so, but out of curiosity this question is in my mind.

Are there technical reasons?
Would it be possible to see a community-port on windows phone 7? (like the android-lighthouse project)
Wouldn’t Microsoft profit from a bigger developer community as well?

Please lets try not to use this thread to discuss our opinions about the Nokia-Microsoft-Deal, but let’s stay on topic.

I’m eager to read your answers!

Are you joking? Qt will be on MS devices. http://www.msqt.org/

What a … I haven’t heard anything official about any msQT …. It’s joke ….

peppe, please use sarcasm tag or at least smileys :)

Quote from the site:
“This is a satire, for the real Qt website go to qt.nokia.com.”

Ivan, first time I opened this website (even before I found link here) I didn’t noticed this text. And I have found it only after your comment :)

Well, most of those www.ms*** sites are like that :)

http://www.mslinux.org/
http://www.msfirefox.com/ (seems to be dead now :( )

microsoft wont allow windows phone porting with qt, because he want to grab the market with its own product.

The fact that Windows Phone 7 only runs managed code, not native code, is a technical problem, isn’t it? Of course, Microsoft could decide to support native code if they wanted to, maybe they will one day, but as long as they don’t, I cannot see how Qt could be ported to Windows Phone 7.

WP7 runs unmanaged code as well, although its execution is forbidden on non-jailbroken devices. There will be a (community driven) WP7 port of Qt sooner or later; just see the iOS port, which suffers from the same “political” artificial restriction.

Using Qt you will be able to write applications for all major desktop platforms including Windows, Linux and MacOS and all major mobile and tablet platforms including Android, Meego / Maemo / WeTabOS, (iOS) and Symbian except non-jailbroken WP7 phones, the declared flagship platform of the same company responsible for the development of Qt.

I’m looking forward to see if Nokia / Microsoft will sustain the “WP7 exclusive” attitude. Keep in mind that the WP7 ecosystem is almost non-existent right now.

There will be Qt applications on WP7. Officially or jailbroken – we will se.

Qt on Windows would divide the developer community from a Microsoft perspective.
Qt on Windows would unify the developer community from a Nokia perspective.
Stephen Elop said there will be no Qt on WP7 because it would divide the developer community. WTF?

I’m fine with keeping Windows lovers out of the equation for the future of Qt;) Does anyone know what exactly is behind the marketing term “Windows Phone 7”? Is it just another reiteration of the Windows CE or NT legacy? Or is it something more substantial? For instance does it support full multiprocessing? (fork(2) etc…)