So whats in the box?
8 APIs at a Beta level of maturity, 3 new APIs at a Technology Preview level of maturity, some new demonstration applications and many more updates 
If you were the kind of kid who liked to rip the wrapping of your pressie and get straight to playing, then you will be interested to try the new demo applications first.
We have included:
Flickr demo , which displays a list of flickr images corresponding to the users current location, (or for demo purposes, a hard-coded location is used if there is no GPS source).
Weather Info demo
This displays the weather forecast at the users current location or again, for demo purposes, if no GPS is found then a default location is used. (As you can see its pretty hot these days in Brisbane).
“Lightmaps” demo which is an update to an older demo you may have seen, it shows a lookup of the local street map based on the users location, as determined by GPS.
If no GPS is detected a default location is selected.
The above all utilise the new Bearer Management and Location APIs.
In total there 27 examples. Although some are fairly sparse simple API feature examples, others are a little more interesting, like the above.
Also, for those who like to take their time and get a understand things before diving in, you may enjoy reading our new Whitepaper which covers all of the Beta level APIs.
What else?
Oh yeah, in addition to the source package with documentation updates we have sis and debian packages for you to try on your Maemo and Symbian devices.
Our webpage will direct you toward where you can obtain the downloads.
For those wondering how you can contribute:
The team are moving as fast as they can to offer new APIs, documentation and examples.
There is a lot of work ahead for us, and some great new APIs we hope to include in the future. The todo list is ever growing and our efforts, to be honest, are prioritizing first our Symbian and Maemo platforms. What we would benefit from is contributions toward other Qt platforms which are currently on a lower priority list for the team, but certainly would offer value to developers.
Note: Where we are introducing one of our APIs into Qt, we will first ensure appropriate platform support coverage is in place.
Next steps?
We will continue to mature the APIs and, for most, finalize in the next months.
Sensors and Camera APIs, which are currently at a Technology Preview level of maturity are likely to finalize a little later, as we hope to validate those, with your input, for a while longer.
Other APIs under development include: Document Gallery, Service Framework (out of process), Landmarks, Calendar and many more are on the list to be scheduled.
Have fun with the release and we welcome your feedback and contributions.
kind regards,
Gerard.
PS..
For those of you lucky enough to be attending MWC 2010 in Barcelona you will be able to see some of our demos at the Qt Booth. Its also a good opportunity to meet some of the Qt team face to face. The trolls are located in Hall 1 at stand #1E44.
Possibly related posts:
14 comments
Whitepaper file does not exist on the server.
Thanks Axel, you are fast! We are fixing now
Whitepaper file: http://qt.nokia.com/files/pdf/qt-mobility-whitepaper-1.0.0
It will helpful to include GCCE release builds in the binary package for Symbian in the next go around.
Another issue: After compiling and installing the GCCE libraries, I ran into linking problems with the following 2 methods:
QGeoPositionInfo::hasProperty
QGeoPositionInfo::property
The methods are in the headers, but not apparently in the libraries that the GCCE build generated.
@Chris – QGeoPositionInfo had an API change, from using “properties” to using “attributes”. I just checked the .tar.gz source package and the zip files that are meant to be extracted into the symbian SDKs and the change made it into the beta.
Did you have any of the previous versions of Mobility installed? There’s a possibility that an old version is hanging around in eopc32/include/mw (I’m not exactly sure about this, but it definitely sounds like an old header hanging around). I think that’s where the trouble is most likely to be coming from.
Spent yesterday having a look at the Location APIs and porting it to the platform I’m working on (Creative Zii Egg). 1 day later, this platform has full Location API support and all the samples compile run and work without modification… Impressive stuff!
You so need a web-service framework. Seems mobility would be the idea place to place it.
I’m working on a cross platform application that requires that I build the QTMessaging library on the Win32 platform, but I’m having absolutely no luck using either mingw32 or nmake. First issue is that the MAPI related headers aren’t present, so I’ve tried copying them from several different versions of the Windows platform SDK to the build directory, that only results in considerable compile errors with various structure definition redefines.
I would assume that at some point, Nokia clearly has been able to build the message library for a Windows platform, but if anyone has any specifics on which version of header files are required, or any other undocumented magic required, I think many of us would be extremely appreciative.
Pretty much, if I can’t resolve this shortly, we’ll have to give up on using QTMobility for our application and find an alternate solution. I’m a great advocate of Qt, it has served us extremely well for Windows and embedded Linux development, but have completely hit a wall trying to build this library.
I’m curious whether the video camera capture in Camera APIs in working in the technology preview stage. I was able to build, sign and install the CameraCapture example, but while it looked like it was recording, it didn’t record to the location specified in the source code. Please advise if there’s a better place for my inquiries.
@Michael Eskin
I answered the same question elsewhere. I’ll repost my answer here in case it’s helpful to others:
Please note windows is not an officially supported platform, but here are some instructions.
nmake can be used, but mingw32 can not.
QtMobility messaging has been tested with Outlook 2007 and Outlook 2003, I recommended Outlook 2007 service pack 1 for best results. Windows 7 is unsupported and untested. Don’t use Windows 7 with QtMobility messaging currently.
The QtMobility docs state, ‘On Microsoft Windows, MAPI header files are required to be installed, we recommend installing Visual Studio Express for this purpose.’ So it should be possible to install the MAPI header files when installing Visual Studio Express.
Personally I’ve installed the MAPI header files using Visual Studio 2008 Professional and Visual Studio 2008 Service pack 1
http://www.microsoft.com/visualstudio/en-us/downloads/microsoft-downloads.mspx
http://www.microsoft.com/downloads/details.aspx?familyid=FBEE1648-7106-44A7-9649-6D9F6D58056E&displaylang=en
Before installing qtmobility it is necessary to build qt for the win23-msvc2008 platform, and make sure the QTDIR and PATH environment variables are set/updated as per usual when working with Qt on windows.
To compile QtMobility on windows normally I create visual studio project file using
qmake -tp vc qtmobility.pro
then build using
nmake
I agree that the build instructions for Windows could be better, Windows Mobile also requires further instructions** but because Windows isn’t an officially supported platform yet this hasn’t been a priority. Recently one of the dev machines used for QtMobility messaging development was reimaged so I’ll have to go through the setup process again myself.
**Windows Mobile also requires ActiveSync 4.5, I’ve also installed Windows Mobile Standard and Professional SDK and DTK, but perhaps I didn’t need both.
Windows Mobile Standard SDK & Windows Mobile Professional SDK
http://www.microsoft.com/downloads/details.aspx?FamilyID=06111A3A-A651-4745-88EF-3D48091A390B&displaylang=en
Windows Mobile 6.5 Standard Developer Tool Kit (USA).msi & Windows Mobile 6.5 Professional Developer Tool Kit (USA).msi
http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=20686a1d-97a8-4f80-bc6a-ae010e085a6e
Regards,
Don.
I wonder if the QMessage type enumeration will/can be extended for more mobile message types, such as:
* CBS (Cellular broadcast service messages, see http://en.wikipedia.org/wiki/Cell_Broadcast)
* USSD (Unstructured Supplementary Service Data, see http://en.wikipedia.org/wiki/USSD)
Cell broadcast will be easy to include, as technically it is very much similar to SMS, it is just broadcast type to the recipient data is missing. So if SMS is there, in my opinion CBS should be there as well.
USSD is a bit different, as it could be understood more like “a protocol” than a “a message”. However there will be applications that have a need for USSD conversations (sending and receiving USSD messages) so eventually an API for that is required, whether it is included in Messaging API or not.
Hi to all.
sorry,
i work with Qt and have skil to developing applications by that but i’m newbie in qt mobility.
can any one help me and say how can i start developing mobility apps with Qt Step by Step?
i mean that what prerequisits and what ide is needed?
thank you already.
Hi,
I’m using qt-mobility to develop an application that uses the camera. I’m using the camera preview APIs provided in this last beta package. I created my application and it runs ok but now I’m needing some features that this preview doesnt provide and I now how to implement them. So I want to contribute but I dont know in what branch I should contribute. The camera preview is only in one “beta” branch. I’m guessing I have to add my changes to a clone of that branch and request a merge, am I right? I’m really not sure because the last commit in that branch dates from february. Also I havent found other proper place to put my doubts so I came here (let me know in case I’m wrong).
Thanks in advance,
Olympio Cipriano
Comments on this entry are closed.