Hello Andre,
I am familiar with the Mobility APIs. I may have missed something but I do not think there is anything relevant in the published APIs.
However, Nokia released the "Push Notification API":http://blogs.forum.nokia.com/blog/nokia-developer-news/2010/12/08/push-notifications-and-long-battery-life-with-notifications-api-beta which address the above scenario from a power perspective. Seems to me there is a need for a UI for it.
-jk
Hmm... Which version of Qt you are using to build the plugin ?
http://bugreports.qt.nokia.com/browse/QTBUG-9287 would cause Kern-Exec 3.
Also check that the buildkey doesn't contain compiler name and version. This issue was fixed at some point but didn't find the corresponding bug report. Symptom is that plugin fails to load.
What that is confusing for you is just some notes before starting with Qt. There's no different between platforms to use with QtCreator. Then you need to have a little knowledge about configuring Qt for different platforms. Although you can download compiled binaries from http://qt.nokia.com
then you can set the QtCreator environment to your desired SDK at Tools->Options->Qt4
to compile for WinMobile and WinCE you'll need to have their SDK installed. After configuring your Qt for required version, you'll have to use QtAddIn under VS2008 to compile and deploy to your device.
[quote author="SABROG" date="1294906845"]Why MeeGo using Clutter+Mx(widgets) instead Qt or QtQuick?[/quote]
Meego only uses Clutter + Mx libraries for Netbook UX, Handset UX uses MeegoTouch which is based on Qt. The reason for using Clutter + Mx on Netbook I think it's because they're native UX libraries on Moblin. Nokia may still want to keep something "Intellish" or new Netbook UX has not been developed or being developed, but things might change in the future, who knows?
Probably a link which you have checked yourself and is known to contain no malicious content. In this case the poster had posted an external link from other forum. The poster might have asked this because some forums restrict posting external links or using short url's.
Our support normally works via mail or IRC. I'd be the person to talk to
I'm dalaing on #qt, #qt-labs and #qt-mobility on freenode, ususally available from 0830 to 1630 AEST (GMT + 1000).
I asked about the licensing - since mapping is part of the 1.1 release it should be fine to use in a commercial product in general, although you probably need someone from your end to read and understand the terms and conditions associated with the Nokia mapping plugin if you're planning on using it in a commercial app, just in case.
I am using the VS console. here is the dump from the console command line:
C:\qtmobility>configure -prefix C:\qt\4.7.1
C:\qtmobility
Checking available Qt
4.7.1
Checking make
Cannot find 'nmake', 'mingw32-make' or 'make' in your PATH
Aborting.
i tried "configure -vc" with the same result.
I tried from a standard command line and set the path variable with the following command:
C:\qtmobility>set PATH=%PATH%;"C:\Program Files\Microsoft Visual Studio 9.0\VC\bin"
same result.
Well, the thread you read is correct. To display an & on a button, you have to double it to &&. The solution to your problem is therefore to un-double the && before you display it in a line edit. There are many ways to do this. One would be to simply do a string replace before pasting it on the line edit, where in replace a double && with a single &. Another would be not to use the caption of the button directly, but use another property instead. The latter would be a more flexible solution, I think.
qtrahul,
The device was updated to QT 4.7 using that of the Symbian^3 Developer Version and I installed the mobility 1.1 from file: qt-mobility-symbian-1.1.0-symbian3-nokia-signed.sis
I did that update becuse the N8 was hard reset and I reinstalled the qt using the Qt_4_7_for_Symbian_3_Developer_Version_v1_0_en.zip
My opinion is that there is no generic Best way of "layout-ing" the widgets.
In the end both methods are going to be C++ code (most likely very similar C++ code).
The only big difference is who is writing the C++ code you write it, or the UIC generate it (using the designer xml as a "pattern").
If you want to check this just open an ui_UIFILENAME.h and see the implementation of the setupUi(...) method.
So to choose one way or the other, you need to think of what is convenient for you: the time you need to write the code for Widgets/Layouts vs the time you need to achieve the same result using Designer.
Basically is the same for the application/code/compiler, it only depends on what is convenient for you: what are you most productive with, or what do you like, or maybe some simple dialogs (with simple layouts) are fast to code and some more complex layouts are easier to implement in the Designer.
[quote author="hasnain" date="1294405096"]then what should i do to make a call from a qt mobile app, any suggestion, any link or example or anything that might help. i am not asking for some sample code i am just asking for a direction. i can not bear with the idea that one can make call on from nokia device using J2ME application which run on JVM. but not using qt app which is intended for nokia devices. [/quote]
At this stage, you can make use of symbian native platform APIs for making call and other such telephony API requirements.
