[mja]

Originally Posted by qgil

The MeeGo Handset UX announced by the TSG to go public this month basically consists of the MeeGo Touch Framework and a set of reference applications maintained by the MeeGo project.

The MeeGo based device announced by Nokia to go public on 2H2010 will have the software release codenamed Harmattan and a UX that basically consists of the MeeGo Touch Framework and a set of applications decided by Nokia.

Can someone remind me whether the UX is still Gtk or will it be Qt for Harmattan (or is it public knowledge)? Everything in the netbook and seen tablet UX are still Gtk I reckon..?

[bzhbok]

This UX layer is fully Qt-ified.

The MeeGo Touch framework is an extra layer on top of Qt, and basically all the classes start with a M instead of a Q in Qt:
MApplication
MApplicationPage
MApplicationWindow

Action extensions
MAction
MWidgetAction

Notifications
MNotification

Widgets
MButton
MComboBox
MContainer
MDialog
MMessageBox
MImageWidget
MInfoBanner
MLabel
MList
MContentItem
MCellCreator
MWidgetRecycler
MMashupCanvas
MPannableViewport
MProgressIndicator
MSlider
MSeekBar
MTextEdit

Layouting and grouping
MButtonGroup
MLayout
MLinearLayoutPolicy
MGridLayoutPolicy
MFlowLayoutPolicy
MFreestyleLayoutPolicy

Creating new widgets
MWidget
MStylableWidget
MWidgetController
MWidgetView
MSceneWindow
MTheme

[mja]

Originally Posted by bzhbok

This UX layer is fully Qt-ified.

The MeeGo Touch framework is an extra layer on top of Qt, and basically all the classes start with a M instead of a Q in Qt:
MApplication
MApplicationPage
MApplicationWindow

...

So if I were to write applications for handset-MeeGo in Qt should I use these classes instead of the corresponding Qt classes? Sorry if it's a dumb question, I'm relatively green when it comes to Qt. I know everything about Matlab and R though

[bzhbok]

Yes, it will be better to use those class, because it is better integrated with the platform and allow some extra methods, . Of course those classes inherits from Qt classes (like MApplication inherit from QApplication), so it shouldn't be too different.

[mja]

Originally Posted by bzhbok

Yes, it will be better to use those class, because it is better integrated with the platform and allow some extra methods, . Of course those classes inherits from Qt classes (like MApplication inherit from QApplication), so it shouldn't be too different.

I hope it doesn't break the write-once-use-everywhere principle though? Can the same code with M- instead of Q- be used in the Netbook UX then anymore?

[w00t]

You *should* have no problems in using regular Qt (write once run anywhere). That has been stated in the past on various discussions at maemo.org.

Doing so will end up being more portable (i.e. you won't have to port/install the MeeGo Touch library wherever else you want your application), which is something to keep in mind.

Personally, I'll be sticking to Qt itself where possible, because it has stability guarantees on API and ABI (and a track record to match) - but, at the end of the day, to each their own.

[w00t]

Originally Posted by bzhbok

Yes, it will be better to use those class, because it is better integrated with the platform and allow some extra methods, . Of course those classes inherits from Qt classes (like MApplication inherit from QApplication), so it shouldn't be too different.

Not completely correct. Qt can integrate itself in with platforms very well, without any help.

Take a look at:
- http://doc.qt.nokia.com/4.6/gallery.html
- http://doc.trolltech.com/qt-maemo-4....es-maemo5.html

[bzhbok]

Ok, perhaps I'm wrong. So perhaps it is:
-stick with pure Qt if you want maximum portability
-use MeeGo Touch framework if you target handset. Especially in MeeGo Touch the classes are extended to deal with the rotation of the screen, MeeGo notifications ...etc.

Hopefully we will have more official input soon.

[w00t]

Originally Posted by bzhbok

Ok, perhaps I'm wrong. So perhaps it is:
-stick with pure Qt if you want maximum portability
-use MeeGo Touch framework if you target handset. Especially in MeeGo Touch the classes are extended to deal with the rotation of the screen, MeeGo notifications ...etc.

Hopefully we will have more official input soon.

That's a better description, yes. I'm sure that Qt will work to adopt features from MeeGo Touch and other sources as necessary to make Qt a better development framework, I personally will be putting some effort into this.

(sidenote: what do you call 'official' in an open project, where anyone may contribute..? tricky question, and food for thought )

[bzhbok]

The thing is that at that point MeeGo Touch Framework is not part of MeeGo project : the source code is not in meego.gitorious.org ...

This will change soon, and we will get a message from the Technical steering group on meego.com front page, with some beatifull screenshots... it what I mean by official...

Anyway I agree that there is a tricky contradiction between 'developing with an open methodology' and 'mind blowing, breaking news release'...

I guess it is more for the 'initial release' (which is not really initial since it is already there under cover name)...