Thread: What Will Make MeeGo Succeed
View Single Post
fatalsaint is offline fatalsaint
2010-08-11 , 14:31
Posts: 3,428 | Thanked: 2,856 times | Joined on Jul 2008
#57
Originally Posted by dov View Post
I have seen this argument several times, but I still don't get it technically. If you write for Qt for the desktop, you may e.g. make clever use of the third mouse button. You may make interesting applications based on hovering. You may save and load your data in application specific places. You can popup lots of sub windows (e.g. like gimp does). You can make heavy use of read/write cycles to the hard disk. And 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?
Yes, it's up to the developer to decide how their app works.. I don't see a problem with that?

If a Developer designs something with Desktop, AND Mobile devices as their target.. then as they are designing it they will avoid such things as the third mouse button. If the developer designs it for Desktops only then they might add things that would be non-optimal for mobile devices.

This is not a bad thing.. Developers decide for themselves how their app works. Besides, it's not like most desktop UI's are very efficient on small touchscreens. So when a Developer designs their application they take all this into account.

As far as saving state, all MeeGo is, is Linux. There is no "saving state" like in android, Maemo doesn't have it, so what's the question? If a Dev wants their app to save state, they make it, otherwise they make it work like every other application for Linux and Windows. Android is a separate beast because it thinks for you. It decides which apps you want running when and it decides which apps gets backgrounded/sleeped/or saved out. So therefore the applications on Android have to maintain a state or people will soon realize how annoying it is to go to an app you were just using only to find out it restarted itself.

On Maemo/MeeGo, you have to manually close the application, if you don't it'll sit there running constantly until you do - therefore no need for "save states".

Again, the power here resides with the Developer to decide their target audience, design their application accordingly, and code it.
__________________
If I've helped you or you use any of my packages feel free to help me out.
-----------------------------------------------------------------------------------
Maintaining:
pyRadio - Pandora Radio on your N900, N810 or N800!
 

The Following User Says Thank You to fatalsaint For This Useful Post: