View Single Post
Posts: 103 | Thanked: 211 times | Joined on Sep 2011
#83
Originally Posted by qwazix View Post
I think it is still not clear what developers should do, if they want to target extras and ovi store. From what I gather:
If you want to apply for extras, your app MUST depend only of packages that could reach extras, ie: If you depends of Qt 4.7.4 you are sticked to CSSU users and what's more, your app shouldn't reach even extras devel (You need to cheat with runtime dependences). If you make use of qtm12 and qt-components-10, you satisfy that requirements.

qt-components is available without cssu, to target that we need to import org.maemo.fremantle and use qt 4.7.0, and depend on qt-components10. This should be ok with ovi
Ovi is a different beast. Ovi only allows you to depend of STOCK PR1.3 dependences, so if you want to push your app yo need to build a bundle with your app + qt-components-10 + libmaliit1 + qt-components-base-theme for QtComponents and qtm-12 and qtquickcompat for qtm12 (Or any other requirements for qtm12)

This problem also exists with Harmattan, but in that cases you already have QtComponents anf Qtm12


to target cssu users (extras) we should do the same as above but we can use com.nokia.meego and qt 4.7.4
If you target SSU, you are already targetting CSSU. You only need to package a com.nokia.meego based QML files for your app ONLY if you want to benefit of ActionKey functionality with Maliit VKB

should be a wiki page with instructions
http://wiki.maemo.org/Special:Search...mponents&go=Go
Wikis are editable by everyone. Feel free to contribute and add/update pages with your experiences.

As I said previously, Take a look to this:
https://qt.gitorious.org/~inean/qt-c...rld/autogen.sh
https://qt.gitorious.org/~inean/qt-c...World/main.cpp

That code generates Fremantle QML code from Meego couterpart and decided at runtime which system graphics and which QML set of files should use based on Qt version
 

The Following 6 Users Say Thank You to inean For This Useful Post: