View Single Post
Posts: 3,319 | Thanked: 5,610 times | Joined on Aug 2008 @ Finland
#83
Originally Posted by jnwi View Post
Of course it does. If MeeGo wouldn't be closer to a full desktop operating system, there would be no point to it, since Symbian is much lighter. Some functionality will be easy to implement on MeeGo and very hard on Symbian. Qt can't abstract away the things that a lighter operating system will inevitably be missing, and in many cases people will want and need to use other libraries than Qt.
Care to share some examples of such functionality (except the dbus thingy, which is already being tried to get rid of) ? The whole point of QtMobility is to abstract away those gritty details, and while being able to use other libs is a huge boon, (for better or worse) it's a sideeffect, not something encouraged.

Anyone who thinks MeeGo is a 'whatsthat' will most likely understand Qt even less. If the objective is to work around the Symbian brand, the best solution might be to start pushing Orbit and DirectUI branding, not Qt.
I would agree with that, but I also think making it clear that the actual platform is Qt, not MeeGo or Symbian, brings more benefit on the long run, exactly because it spans the whole Nokia smartphone ecosystem (=can provide synergy). And then, within that, those who care enough to know what Unix means can go for MeeGo. On a similar note - take the Bada thing - do you know how the constituent OS-es (one Linux, one some proprietary RTOS) are called ? Does anyone ? Does it matter ?
__________________
Blogging about mobile linux - The Penguin Moves!
Maintainer of PyQt (see introduction and docs), AppWatch, QuickBrownFox, etc