Thread: What Will Make MeeGo Succeed
View Single Post
attila77 is offline attila77
2010-08-12 , 21:57
Posts: 3,319 | Thanked: 5,610 times | Joined on Aug 2008 @ Finland
#65
Originally Posted by dov View Post
I'm sure lots of other decisions that work just fine on the desktop, but don't scale to a mobile device with its different constraints. How does Qt take care of that? E.g. an Android application is supposed to automatically store its entire state on close. How does Qt/MeeGo do that, or doesn't it? Is it up to the application programmer to decide whether he wants to store the state, or popup a window asking whether to save the data?
That is not exactly what I was talking about The point is that, naturally, you will have to adapt to a mobile use-case. BUT. You will do that in Qt. You're not doing it 'in/for MeeGo'. The same stuff is applicable to Symbian, WinMo, UMPCs and even Android/webOS (should you want to use the unofficial ports). In those terms there is nothing specific in MeeGo (unlike when you develop for iOS or Android, where your tools and code are only good for THAT particular platform). Thus, the bottom line for a developer is "I'm making apps for Qt compatible platforms (of a given form factor)", and not "I'm making apps for MeeGo".
__________________
Blogging about mobile linux - The Penguin Moves!
Maintainer of PyQt (see introduction and docs), AppWatch, QuickBrownFox, etc
 

The Following 2 Users Say Thank You to attila77 For This Useful Post: