The introduction of the Nokia Qt SDK enables great ideas to become reality, in a cross platform way. "Code once, deploy everywhere" is not just a slogan for latest Qt releases, and the recent additions of API stacks like Mobility, QMF and sensors stretches what you can do by purely using the Qt framework. This allows great exploitation of the underlying platform while maintaining straight forward API usage and relatively relaxed learning curve.
This latest additions have been exemplified mostly on Nokian mobile Linux computer platforms. I would like to be able to offer Symbian developers the same great building blocks to build great software using pure Qt just as it is slowly being realized on the N900/Maemo/MeeGo.
I think this is very important in order to keep the Symbian offering live and up to date, and not fall behind the Mobile Linux computers application development offering. I feel this is important in order to revive the Symbian experience, as historically developing for the platform required specific lowlevel platform knowledge and usage of somewhat exotic development, signing and deployment paradigms that are even to date, considered by Symbian developers hard and unpleasant.
I would like to change this and make Symbian development fun, educational and rewarding through the latest Qt offerings, removing as much as possible the historic barriers. Nokia's latest changes to the signing and individual app publishing are great steps towards that, as an example.
To make the MeeGO-Symbian cross application development experience complete I would like to pursue:
both platforms. Posting vidoes.
That might look too ambitious at first glance, but it is planned for over a period of time, the more proximate stuff are the first action items naturally.
As some efforts and already ongoing for Qt across Symbian and MeeGo, it is useful to know who does what and the fields he can help with already, through the work he's done so far.
If you are interested in contributing to one of the items listed here, please contact the person coordinating it and start a discussion on the porting mailing list.
|Name||Hardware/OS||Affiliation||Working On||Can Help With|
|Sivan Greenberg||N900 (Maemo 10.2010.19-1, latest MeeGo arm)||sivan __AT__ omniqueue.com||Community Member||Starting coordination efforts, investigating current state of affairs, evaluating documentation, report porting bugs, develop porting examples and documentation (-in the future)||Testing ported works, listen to issue and try to find solutions or contact persons to help with porting requirements or issues.|
Thanks for Ville for pointing this status:
We have 2 Symbian - MeeGo portability stories
- QWidget - QML + Qt Components
(as far as the GUIs go - backend functionality is an open-ended problem, with a lot of it attacked by Qt Mobility).
Unfortunately QWidget stuff is not mature yet for MeeGo, so you can't do a useful analysis of the portability aspects.
As for Qt Components, Symbian backends don't exist yet. and for MeeGo it's a work very much in progress as well.
Please use this table to note any current issues you are facing trying to make your application cross platform (MeeGo <-> Symbian).
Please provide the git/svn/bzr/$YOUR VCS clone-able/branchable link so I can easily check out the code and see the build issues and try to run it on my devices to experience your pain. I am interested in creating "porting bugs" so of your issue triggers a bug in the underlying framework I will try best to report it as so.
If you already identified it as not your code's fault, and opened a bug about it, please include the links to the bug reports in the "VCS link" column as well.
If the issue was already solved, please include a link to a solution writeup you could do on the wiki for the benefit of others who face the same issue you did.
|Project Name||libs used||contact person email||link to issues page||VCS link||Solution|
|That Rabbit Game||Qt, QtMobility (M5+S^3) + dbus, opengl (M5 only)||thp||Blog entry||-||Workarounds (see blog post)|