The Qt Mobility 1.0.0 package has arrived!
After much hard work the team are very happy to announce delivery of our 1.0.0 package!
There is a party to celebrate, but only after I finish this blog post 
The 1.0.0 package is being made available both under our Commercial and also Open Source licensing agreements.
The release contains 9 APIs which are considered FINAL and 1 API which is marked BETA.
The list of APIs is as follows:
All the above are considered FINAL
The remaining API, Multimedia, is at a very good state of development but we are reserving the right to modify following some final review meetings. Given this, it has been appropriately marked as BETA for the time being.
Therefore, please be aware that our Multimedia API could well change before becoming FINAL and we would not be in a position to maintain the old Beta version
We just wanted to be explicit on that point, so you can manage your risks accordingly.
You can obtain these APIs in Qt Solutions and use as an add-on to Qt or you can find them in the Nokia Qt SDK Beta which was also just released today.
Some things to note:
The Qt Mobility 1.0.0 release for Maemo supports only Maemo PR 1.2 which is yet to be released.
There will be a patch release in the coming weeks to include bug fixes and backend updates for Symbian platforms. We also look forward to your contributions.
More APIs are being worked on in parallel so as soon as we have something drafted we will post early here for you to review .
These too will go through our software maturation process involving sharing through Qt Labs drafting ->Technology Preview -> Beta -> Final and eventually, where relevant, into Qt.
As always our focus will remain on the APIs themselves rather than applications development, so applications are always welcomed as contributions.
As a reminder our whitepaper is a good starting point for those as yet unfamiliar with the new Qt APIs for mobile development.
We hope you enjoy using the APIs and much as we enjoyed building them
Kind regards,
Gerard on behalf of the Qt Mobility team.
Possibly related posts:
17 comments
Well done, guys, Qt Mobility is promising!
Qt Mobility is so awesome! For our new mobile app this will speed up the development!
Does this mean Pop/Imap/mbox mail is supported on Windows?
I built the examples using Mingw, and qt 4.6.1 and the googplemaps and flicker demos don’t load images.
Great milestone, guys and gals! I’m really looking forward now for APIs that will specifically target “sensors”.
Hi, what is your next update, maybe 1.1 or 2.0, I’m eager to use telephony APIs, you know its very important.
Nice job, but hey.. where’s Camera?! Despite being just tech preview, the QCamera class worked well in beta package–at least in S60 5th ed… And it was thee best API for achieving the wow-effect quickly when introducing the APIs. I hope it comes back soon! Or what am I not seeing here?
@Tuukka: I think the Multimedia APIs cover that as well.
@scorp1us, mobility messaging exposes services of the local messaging stack on the machine/device, e.g. mapi on windows and windows mobile, and the native messaging stacks on symbian/maemo. imap/pop are internet mail protocols and mbox is a file format so I’m having difficultly understanding your question.
Perhaps you could clarify your question by specifying use cases you are aiming to satisfy.
I meant the beta left out windows mail support. Now it seems that 1.0 allows it but it needs MSCV not mingw, which is fine. Though I wonder if I could use the QMF support on Windows to test Linux support without having to have a linux box around… (And still use mingw) (Not for deployment, just development)
@detro: Multimedia module should cover Camera eventually, but now the whole set of code seems to miss, the oh-so-convenient classes QCamera and QStillImageCapture (both derived from QMediaObject in the beta version), so it seems they are really left out for this release.
Even though they would not have been considered final (I don’t really know their status–they worked well, though), it would have been really nice to have them still available.
Hi, thanks for this longly awaited API enrichments. However, the pdf you linked to share further information lacks serious punctuation errors and typos. I hope you strive for the best in proofreading as well
some of the typos:
“The layers restrict subscribers and notifications to a select set of value spaces.” select->selected.
” These functions are use to search by a defined filter” . use->used.
And there are a few cases where the lack of commas makes difficult to understand the long sentences, which I can’t find currently. I know these are trivial errors, but for non-native speakers they hinder the flow of the somewhat official documents.
Keep up the good work!
Yet another ambiguous sentence in that pdf, “However, because of the significant differences between a desktop system with operating system support for and a Symbian device.” Where is the verb or main clause?
Where is the maemo5 version of this release? I can only find beta1 related versions.
@Tuukka : Camera is not forgotten
We are still improving that API and it will be finialaised in our 1.1.0 release. It was ommitted from this release simply as we wanted to try keep this package to final versions. (We kinda missed there with leaving MultiMedia at Beta).
But to be transparent WRT our planning:
1.0.1 Should (if the plan.. er..goes to plan) include the finalisation of the Multimedia APIs currently marked in this release as Beta.
Then 1.1.0 will introduce several other APIs including your much missed Camera API
@comptrol: Thank you for your feedback. I agree with your comments and we will endeavour to improve our documentation.
@Pasi: The APIs only support PR 1.2 and when that is released you will be able to obtain access to the APIs via the Maemo Applications Repo. Given that the APIs are now mature we felt it was innapropriate to release via the extras-devel (due also to the potential BC issues once we would move to Apps repo), but of course we will again utilise the extras-devel channel for future Betas. I hope the wait is a short one for PR 1.2 but we saw this as the appropriate means to deploy considering end users.
Sorry for my broken English.
I want to ask, but perhaps not in the class QMediaRecorder recording capabilities in the buffer?
Sincerely, Alex
Does Qt Mobility for Maemo implement QRadioTunerControl?
In other words, is there an API to getting/setting frequency, etc.?
Comments on this entry are closed.