[MeeGo-dev] Qt for all UX? (was: Re: Qt/Quick Netbook UI)
kamikazow at web.de
Fri May 28 14:26:21 PDT 2010
On Freitag 28 Mai 2010 21:06:19 JD Zheng wrote:
> seems I am unable to get consistent answer.
I only subscribed today to this list and one thing is clear:
The MeeGo developer "community" is a total mess. In no way coordinated as if
they are working towards making it fail.
When MeeGo was announced, it was very clear: Qt is the main toolkit, GTK is
just "community" supported.
Nokia is obviously keen to push Qt-based frameworks and applications out of
Intel seems to only officially support Qt while in reality they are working
against it. Instead of moving the former Moblin UX towards Qt, they even
introduce an entirely new toolkit that competes with Qt:
According to http://gitorious.org/mx-toolkit the project was created just two
months ago -- certainly not some legacy technology that's just there.
Then Novell's ex-Ximian team joins the game to push Mono into MeeGo (probably
with the agenda to release MonoTouch later for MeeGo Handset). Contrary to the
"replacing stuff that already works is a waste of time" argument, Novell
pushes newly written specialised ports of Banshee (Mono app) and Evolution
This, again, is obviously in no way coordinated with founder Nokia.
For example: Nokia chose to extend KDE's KCal library for calendaring
Evolution uses the Evolution Data Server for that.
I bet it'll be easier to sync a Windows Mobile phone with Mac OS X than a
MeeGo phone with a MeeGo netbook....
On one hand it's a "waste of time" to migrate everything in MeeGo to a common
base, on the other hand it's supposedly no waste of time and resources to
develop everything twice...
Are you secretly all Android supporters or what? Instead of acting as if
Moblin and Maemo were still completely independent products, look how KDE
works: They are currently developing a desktop PC GUI, a netbook GUI, a
smartphone GUI, and a media center GUI from a single base (Plasma) in a
More information about the MeeGo-dev