Active Topics
-
Firefox with Leste (10)
to Maemo 7 / Leste by teroyk - 3 days, 6 hrs ago - more...
| The Following 35 Users Say Thank You to attila77 For This Useful Post: | ||
|
2010-12-29
, 11:03
|
|
Posts: 3,319 |
Thanked: 5,610 times |
Joined on Aug 2008
@ Finland
|
#3
|
Originally Posted by dbrodie
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.
Thats great, thanks alot!
What other packages of Qt are you working on? can we expect an updated qml or pyside?
__________________
Blogging about mobile linux - The Penguin Moves!
Maintainer of PyQt (see introduction and docs), AppWatch, QuickBrownFox, etc
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: | ||
|
|
2010-12-29
, 11:19
|
|
Posts: 388 |
Thanked: 842 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
has to be used with these in the project file?
I guess something like
Code:
maemo5 {
CONFIG += mobility11
} else {
CONFIG += mobility
}
| The Following 4 Users Say Thank You to hqh For This Useful Post: | ||
|
|
2010-12-29
, 11:27
|
|
Posts: 3,319 |
Thanked: 5,610 times |
Joined on Aug 2008
@ Finland
|
#5
|
Originally Posted by hqh
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.
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
has to be used with these in the project file?Code:maemo5 { CONFIG += mobility11 } else { CONFIG += mobility }
__________________
Blogging about mobile linux - The Penguin Moves!
Maintainer of PyQt (see introduction and docs), AppWatch, QuickBrownFox, etc
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: | ||
 |
|
2010-12-30
, 00:27
|
|
Posts: 1,296 |
Thanked: 1,773 times |
Joined on Aug 2009
@ Budapest, Hungary
|
#7
|
Originally Posted by attila77
This sounds annoying, seriously.
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.
__________________
You should follow me on Twitter!
Apps: Puzzle Master, IRC Chatter for Harmattan, IRC for Sailfish
You should follow me on Twitter!
Apps: Puzzle Master, IRC Chatter for Harmattan, IRC for Sailfish
| The Following User Says Thank You to Venemo For This Useful Post: | ||
|
|
2010-12-30
, 08:20
|
|
Posts: 3,319 |
Thanked: 5,610 times |
Joined on Aug 2008
@ Finland
|
#8
|
Originally Posted by Venemo
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
This sounds annoying, seriously.
__________________
Blogging about mobile linux - The Penguin Moves!
Maintainer of PyQt (see introduction and docs), AppWatch, QuickBrownFox, etc
Blogging about mobile linux - The Penguin Moves!
Maintainer of PyQt (see introduction and docs), AppWatch, QuickBrownFox, etc
|
|
2010-12-30
, 09:38
|
|
Posts: 388 |
Thanked: 842 times |
Joined on Sep 2009
@ Finland
|
#9
|
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: | ||
|
|
2011-01-02
, 23:06
|
|
Guest |
Posts: n/a |
Thanked: 0 times |
Joined on
|
#10
|
Excellent! This just made my day. My thanks to everyone who made this happen.
 |
| Tags |
| extras-devel, qtmobility |
«
Previous Thread
|
Next Thread
»
|
All times are GMT. The time now is 18:53.
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.