On Thu, Mar 31, 2011 at 10:16, Sousou, Imad <[email protected]> wrote:
>
[snip]
>
> take a look at the MeeGo UX Components
> (source - http://meego.gitorious.org/meego-ux/meego-ux-components,
> wiki - http://wiki.meego.com/MeeGo_UX_Components).
There's been some confusion, and I hope to get this clarified before
everyone's scratching their head:
* What is the relationship between MeeGo UX Components and
Qt Components[1]?
I can undestand that something is necessary to present the right UX,
but is it API compatible? *Please* don't say that the developer story
for Qt & MeeGo has now changed again, and that Qt Components should be
used for Symbian & MeeGo Handset, and MeeGo UX Components for Tablet
UX.
Up until recently the developer story was good:
* Use Qt
* Use Qt SDK
* Use Qt Quick
* Use Qt Components which is coming along and being developed in
the open (ish)
Now there's the MeeGo SDK, a different SDK for the Tablet UX, a new
set of UI controls. WTF is going on? This constant shifting on "how to
write a portable Qt application targetting MeeGo primarily and Maemo
and Symbian secondarily" is confusing and frustrating.
Thanks in advance,
Andrew
[1] http://qt.gitorious.org/qt-components
--
Andrew Flegg -- mailto:[email protected] | http://www.bleb.org/
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev
http://wiki.meego.com/Mailing_list_guidelines
