Reply
Thread Tools
Posts: 3,319 | Thanked: 5,603 times | Joined on Aug 2008 @ Finland
#1
... 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).
__________________
Blogging about mobile linux - The Penguin Moves!
Maintainer of PyQt (see introduction and docs), AppWatch, QuickBrownFox, etc

Last edited by attila77; 2011-01-21 at 23:21.
 

The Following 35 Users Say Thank You to attila77 For This Useful Post:
Posts: 163 | Thanked: 95 times | Joined on Feb 2010 @ Israel
#2
Thats great, thanks alot!
What other packages of Qt are you working on? can we expect an updated qml or pyside?
 

The Following User Says Thank You to dbrodie For This Useful Post:
Posts: 3,319 | Thanked: 5,603 times | Joined on Aug 2008 @ Finland
#3
Originally Posted by dbrodie View Post
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.
__________________
Blogging about mobile linux - The Penguin Moves!
Maintainer of PyQt (see introduction and docs), AppWatch, QuickBrownFox, etc
 

The Following 3 Users Say Thank You to attila77 For This Useful Post:
Posts: 388 | Thanked: 838 times | Joined on Sep 2009 @ Finland
#4
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
Code:
maemo5 {
        CONFIG += mobility11
} else {
        CONFIG += mobility
}
has to be used with these in the project file?
 

The Following 4 Users Say Thank You to hqh For This Useful Post:
Posts: 3,319 | Thanked: 5,603 times | Joined on Aug 2008 @ Finland
#5
Originally Posted by hqh View Post
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
Code:
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.
__________________
Blogging about mobile linux - The Penguin Moves!
Maintainer of PyQt (see introduction and docs), AppWatch, QuickBrownFox, etc
 

The Following 2 Users Say Thank You to attila77 For This Useful Post:
Posts: 163 | Thanked: 95 times | Joined on Feb 2010 @ Israel
#6
Wow that was quick, new version of pyside is in!
 

The Following User Says Thank You to dbrodie For This Useful Post:
Venemo's Avatar
Posts: 1,192 | Thanked: 1,224 times | Joined on Aug 2009 @ Budapest, Hungary
#7
Originally Posted by attila77 View Post
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.
 

The Following User Says Thank You to Venemo For This Useful Post:
Posts: 3,319 | Thanked: 5,603 times | Joined on Aug 2008 @ Finland
#8
Originally Posted by Venemo View Post
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
__________________
Blogging about mobile linux - The Penguin Moves!
Maintainer of PyQt (see introduction and docs), AppWatch, QuickBrownFox, etc
 

The Following 2 Users Say Thank You to attila77 For This Useful Post:
Posts: 388 | Thanked: 838 times | Joined on Sep 2009 @ Finland
#9
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

Last edited by hqh; 2010-12-31 at 13:13.
 

The Following 4 Users Say Thank You to hqh For This Useful Post:
Posts: 531 | Thanked: 310 times | Joined on Oct 2008 @ Burnaby, BC, Canada
#10
Excellent! This just made my day. My thanks to everyone who made this happen.
__________________
-Jeffery
Computer Engineering student // Open Source Enthusiast // All-around Geek
Weapons of choice: N810 // N900
Blog: http://ffejery.creativemisconfiguration.com
New users look here if the volume settings are confusing you.
"Ssh! I'm in a terminal."
 
Reply

Tags
extras-devel, qtmobility

Thread Tools

 
Forum Jump


All times are GMT. The time now is 12:30.