[ANNOUNCE] Qt Mobility 1.1 for Fremantle

[attila77]

... and a happy new year !

We have kickstarted a community 'compatibility program' with a little Forum Nokia help which will focus on bringing the latest Qt and related tech tools/fixes/updates to developers, without having to worry about Nokia release schedules and support status. The first component that is released as part of this effort is QtMobility 1.1 (as 1.0.2 is getting long in the tooth), currently available as libqtm-11-* in extras-devel. If/when a SSU is released with 1.1 as the official, these libraries will be replaced with placeholders that point to those 1.1 libs. The bleeding edge can always be attained with libqtm-experimental which will permanently remain in extras-devel (after we test 1.1 this will switch to 1.2, etc)

Install howto: http://wiki.forum.nokia.com/index.ph...ation_on_Maemo

Enjoy (and provide feedback/patches !)

EDIT: To use these packages you need do to CONFIG += mobility11 in your .pro file instead of just 'mobility' (as mobility will reference always the official one from the firmware).

[dbrodie]

Thats great, thanks alot!
What other packages of Qt are you working on? can we expect an updated qml or pyside?

[attila77]

Originally Posted by dbrodie

Thats great, thanks alot!
What other packages of Qt are you working on? can we expect an updated qml or pyside?

mairas and his team is working on PySide and I do expect them to have their own releases in the future just as they did in the past. We will integrate packages like the bearer hotfix or the qtquick compatibility one (these will probably, along with mobility, form the base of the first edition of the community service pack), and likely Qt4.8 when it accumulates enough features/stability to be interesting to people.

[hqh]

Nice job, it's good to know that someone is working on bringing the latest Qt fixes and features to Maemo

I guess something like

maemo5 {
        CONFIG += mobility11
} else {
        CONFIG += mobility
}

has to be used with these in the project file?

[attila77]

Originally Posted by hqh

Nice job, it's good to know that someone is working on bringing the latest Qt fixes and features to Maemo

I guess something like

maemo5 {
        CONFIG += mobility11
} else {
        CONFIG += mobility
}

has to be used with these in the project file?

Oops, yes, forgot to mention that - one of the key aspects of this is to make it non-destructive with regard to the original firmware and packages that might be upgraded via the SSU, so yes, you need to use the proper CONFIG keyword - mobility11 as you said.

[dbrodie]

Wow that was quick, new version of pyside is in!

[Venemo]

Originally Posted by attila77

Oops, yes, forgot to mention that - one of the key aspects of this is to make it non-destructive with regard to the original firmware and packages that might be upgraded via the SSU, so yes, you need to use the proper CONFIG keyword - mobility11 as you said.

This sounds annoying, seriously.

[attila77]

Originally Posted by Venemo

This sounds annoying, seriously.

I think one line in your .pro file is a small price to pay for being able to develop for two versions (=future-proof SSU-wise and Extras/Ovi compatible). If someone has a better solution that keeps those goals and requires no .pro changes - I'm all ears

[hqh]

What still seems to be missing are the mobility QML plugins (which are packaged in libdeclarative-* in the "original" version).
They seem to be there after all, maybe my problem is somewhere else...

Update: Qt seems to load some mobility stuff from the old libraries if both are installed. Will report more information next week if required

Excellent! This just made my day. My thanks to everyone who made this happen.