maemo.org - Talk - Nokia rolls out Qt SDK for unified mobile developer experience

maemo.org - Talk (https://talk.maemo.org/index.php)

- Development (https://talk.maemo.org/forumdisplay.php?f=13)

- - Nokia rolls out Qt SDK for unified mobile developer experience (https://talk.maemo.org/showthread.php?t=51150)

Re: Nokia rolls out Qt SDK for unified mobile developer experience

I think emulator in QT SDK is not "full emulator" so you can't click and interact with Maemo OS or applications. It will just show your app.

Try those demos, they have buttons and whatnot, and are clickable.

F-Secure also reported something weird on QT SDK installation:
http://labs.dura.fi/p/tro/9671.png

p.s. I manage to crash my computer (cold boot from hardware) with Animated Tiles demo app. Fan goes for superfast and soon later cpu tops and hardware crashes.This happens a bit after I click something there and zoom Maemo emu up a bit. Anyone else having trouble?

Re: Nokia rolls out Qt SDK for unified mobile developer experience

Holy s**t!

The hd requirements is 4gb !??

OK so basically I do not need to install scratchbox anymore?
Is it still possible to port applications to maemo (PR1.2) and MeeGo (e.g. build abiword and deploy to n900)??

I know abiword is gtk-based but if the underlying platform has gtk installed cross-compiling software is still possible with this SDK?

Re: Nokia rolls out Qt SDK for unified mobile developer experience

Quote:

Originally Posted by kojacker (Post 631371)

The two languages supported are cpp and the Qt scripting language. Personally I would rather use neither, is it possible to make use of the device simulators but with other languages such as PyQt?

There has been already some talk about this, and apparently the answer is yes, but not with the current beta (or additional tweaking). I will try and see whether I can hack the madde/simulator part to cooperate with python (QtCreator people were not too enthusiastic about Python a while back, but that might have changed in the meantime). If QtCreator is not an option, we could still use the MADDE link for running stuff on-device and use the simulator + Maemo libs through plugins (=Eric, Eclipse, etc).

Re: Nokia rolls out Qt SDK for unified mobile developer experience

Quote:

Originally Posted by johnel (Post 631447)

Holy s**t!

The hd requirements is 4gb !??

You don't need to do a full install. If you don't want to develop for Symbian or don't need the Qt Sources, you can deselect those and save a lot of diskspace.

Re: Nokia rolls out Qt SDK for unified mobile developer experience

Quote:

Originally Posted by trotor (Post 631446)

I think emulator in QT SDK is not "full emulator" so you can't click and interact with Maemo OS or applications. It will just show your app.

You are right, the OS is not simulated.

Re: Nokia rolls out Qt SDK for unified mobile developer experience

Quote:

Originally Posted by nath (Post 631501)

You are right, the OS is not simulated.

That's a shame, as I guess it would mean we couldn't simulate status bar or Settings (control panel) applets.

Re: Nokia rolls out Qt SDK for unified mobile developer experience

Quote:

Originally Posted by pelago (Post 631509)

That's a shame, as I guess it would mean we couldn't simulate status bar or Settings (control panel) applets.

That's right. The Simulator is for testing Qt applications only. The reasoning is that only those are portable across devices (to the N8 for example).

Re: Nokia rolls out Qt SDK for unified mobile developer experience

Quote:

Originally Posted by nath (Post 631409)

It sounds as if you wrote an application that is showing nothing, so of course there would be nothing to interact with in the Simulator.

Or did I understand wrong what you are trying to do?

No, it's actually an application using QtMainWindow, so it should be visible (and it was, only no other widgets added to it yet).
But what I sort of had expected was that the simulator would be more responsive in that way that the window would be possible to minimize the app and see the system menu etc. Like the scratchbox.
Nah scratch that. I understand now, it doesn't simulate the OS.

But, another thing then, I don't get the hildon Qt style when running the app. in the simulator. How is that done?

Re: Nokia rolls out Qt SDK for unified mobile developer experience

nath, from your posts you sound like you worked on this SDK - is that right?

Re: Nokia rolls out Qt SDK for unified mobile developer experience

FINALLY!!!!!!

I'm so excited. I cannot wait to start developing with this. We'll also start seeing apps from major companies like Goggle, etc.. With the install base that Symbian has there is no way they'll pass it up.

I'm so proud of Nokia, lol.

Re: Nokia rolls out Qt SDK for unified mobile developer experience

Quote:

Originally Posted by pelago (Post 631763)

nath, from your posts you sound like you worked on this SDK - is that right?

Yes, that's right. :)

Re: Nokia rolls out Qt SDK for unified mobile developer experience

Quote:

Originally Posted by nath (Post 632642)

Yes, that's right. :)

In that case, I'm really glad to be able to ask some questions, because I have for quite a while been confused with some of the Maemo/N900 (fremantle) concepts. Here's what I've experienced so far:

1. Installing scratchbox under ubuntu, especially the 64 bit version was quite confusing and troublesome. Found out that it would probably be easier using the preinstalled vm images with the eclipse environment instead, I downloaded and launched one but I never got around using it because suddenly there was MADDE and I went for that instead.
2. So I installed MADDE (even though I realized it was a beta). I ran into trouble when I wanted to use Maemo specific things there, like Qt::WA_Maemo5StackedWindow and the QMaemo5InformationBox. They were not simply in the target SDK. It all felt somewhat useless, since most apps use those things and mine was no exception.
3. I saw a thread were some guy pointed me in the direction on how to install the Maemo5 SDK under MADDE, but quite experimental. As I tried this, it broke the QtCreator integration with MADDE and the packaging support, but I was able to compile, link and deploy the stuff to the device using MAD developer anyway.
4. It didn't run on the target, I got dependency problems with some QVectorData8 (C++ linker decorated) something. Trying a few things and commenting out some code that caused this it segfaulted instead when about to show the main window. I figured this was since the device didn't have the correct maemo5 runtimes. I found some place where someone said that when installing for example the 'Maesheep' game (that was dependent on these libraries) apt would install the libraries (I later realized I could have installed the libraries separately in apt).So I did that and my app. finally ran on the device even though I was somewhat confused over what versions of things I was using now. I don't even remember now what I did to get rid of that "QVectorData8" error message (maybe I linked with some additional library).
Now WHAT were people actually using when developing things for the N900 device without needing to deploy any extra libraries? Because clearly the stacked windows and the information box (Qt::WA_Maemo5... specific stuff???) was definitely there anyway in THEIR apps. Did they use scratchbox? And what version of Maemo (or should I say fremantle toolchain) would that be under scratchbox in such case? And why was then the MADDE beta delivered with some old version of Maemo that didn't even have the N900 specific stuff? Maybe I'm stupid and don't know where to look for stuff, but I just couldn't add things up.
5. Now the Qt SDK that unifies the development for several platforms was delivered this week and looks really promising indeed. So I installed it and realized a few things. The simulator target SDK can't be used to compile any Maemo5 or lets say N900 specific things like the Qt::WA_Maemo5StackedWindow or the yellow QMaemo5InformationBox. The headers are simply not there if I try to compile my code. What the hell am I missing there...isn't that supported?
6. So then trying instead to compile my code for the PR1.2 N900 target. Somehow I could compile but not link the application when using the yellow QMaemo5InformationBox. Commenting the use of that box out, I could compile, link and deploy, but on the device I'm back with the undefined reference to the "QVectorData8"... something error message when running the code. Even if I have the Maemo5 libraries installed. Ok, probably this is because the PR1.2 has not been released yet and that the device need the upgrade first.

But still, I'm very confused about the Maemo versioning, the N900 (fremantle toolchain) versioning and I do have trouble finding the one single place that documents clearly what to do, what to expect and what to install when developing for the N900 device.
I don't want to sound like I'm just complaining here, its not my intent. It's just that I find it difficult to find consistent information for the Qt developer targeting the N900. I'd be really happy if someone could straight things out for me once and for all.

Re: Nokia rolls out Qt SDK for unified mobile developer experience

Most of your problems stem from mixing two versions of Qt: 4.5 and 4.6. They are NOT binary NOR source compatible (unlike desktop versions of Qt).

Qt4.5 is the one you have on the device *now*, and the one the MADDE tech previews and betas supported

Qt4.6 is the one you have in PR1.2, and that is the one that is supported by the Qt SDK and also the one that has the Qt::WA_Maemo5StackedWindow, QMaemo5InformationBox, etc stuff.

The errors you see come from mostly compiling or running code for one by tools meant for the other.

Re: Nokia rolls out Qt SDK for unified mobile developer experience

Quote:

Originally Posted by attila77 (Post 632843)

Ok, thanks attila! I can for sure accept that I have done this mixing of sources and libraries that doesn't match the device binaries. And of course I am to blame for even trying such things.
But then, I'm not clear on why there are application's that do have the yellow information box, stacked windows (and more) that actually works under the current firmware. Are they NOT developed using Qt at all then, but instead the GTK toolkit?
If they ARE using Qt for such things, then how?

Re: Nokia rolls out Qt SDK for unified mobile developer experience

I guess, those applications simply aren't using Qt.
What attila said is correct.
With the release of PR 1.2, all will be easier. We also will improve the Nokia Qt SDK and the documentation.

Re: Nokia rolls out Qt SDK for unified mobile developer experience

Quote:

Originally Posted by Larswad (Post 632897)

But then, I'm not clear on why there are application's that do have the yellow information box, stacked windows (and more) that actually works under the current firmware. Are they NOT developed using Qt at all then, but instead the GTK toolkit?
If they ARE using Qt for such things, then how?

They mostly aren't using Qt. Those that ARE, are using a development snapshot version of Qt in extras-devel, and were developed in scratchbox (not with MADDE), or are Qt4.5 apps using a custom extra lib (deprecated with Qt4.6). That's really a hack, with known problems and drawbacks, so I'd very much recommend working with the Qt SDK and (duh) wait for PR1.2 to run those things on the actual devices.

Re: Nokia rolls out Qt SDK for unified mobile developer experience

Thanks, this actually helped and gives a better understanding of what I should expect. Then its just a matter of being patient. :cool:

So then I guess it's just a detail: As I mentioned when I compiled my app. using the "Qt for Fremantle PR1.2 Devices (Qt SDK Beta)" version and had a call to the static method QMaemo5InformationBox::information() I managed to compile, but not with linking for some reason. Is there a separate lib I have to add for that one with QT+=xxx, or something. Because I mean as you said that one should be supported for that Qt Version (to build at least).
If I look at the docs it looks like QtGui module...but isnt that by default? (Note I can compile because I include the #include <Qt/QtMaemo5> header). I have opened the file, and the method is declared.

EDIT: Ehm, never mind. This is funny, I just took a shot (didn't know it actually existed as a lib) and added 'QT+=maemo5' in the qmake additional args, and, what the hell it actually linked. Nice...but did I do the right thing?

Re: Nokia rolls out Qt SDK for unified mobile developer experience

You did the right thing. The documentation actually has a bug as it shows these classes as being part of QtGui, when in fact they are in a QtMaemo5 module (which is added with QT+=maemo5, just like you did it).

Re: Nokia rolls out Qt SDK for unified mobile developer experience

Just for closure - I mentioned this to friendly Qt folks on #qt-maemo and voila ! The documentation is fixed :)

Re: Nokia rolls out Qt SDK for unified mobile developer experience

I had a few problems when I first downloaded and installed this new SDK version and tried to follow the getting started PDF file. The examples were listed as "not installed" and I only had the option to build projects for a desktop target and not for the simulator or mobile targets.

It turned out that this was because I had previously had an older version of Qt installed (which I had uninstalled prior to this new version), so for anyone else that may have this issue it can be fixed by following the instructions here:

http://wiki.forum.nokia.com/index.ph..._SDK_v1.0_Beta

There are a few files that are left behind by older versions even after uninstalling that need to be manually removed.

Re: Nokia rolls out Qt SDK for unified mobile developer experience

This SDK is very good news... just downloaded now and have leaked pr 1.2 installed... all app examples and everything work fine... they have a lot of good coding examples even one for a torrent downloader...very interesting.
Should be better though as it will help more of the beginner developers like myself get up to speed with creating decent applications for the n900.

Re: Nokia rolls out Qt SDK for unified mobile developer experience

@postformac:
We're working on fixing those issues, especially for removing everything completely when you deinstall a component.

Re: Nokia rolls out Qt SDK for unified mobile developer experience

For those who were wondering about the Hildon style. The Qt Simulator does not have support for it due to the reason, that the style itself queries other libraries for stylehints etc. As we had needed to port all of those as well, this was considered to be too heavy then.

Re: Nokia rolls out Qt SDK for unified mobile developer experience

Quote:

Originally Posted by mauricek (Post 640914)

this was considered to be too heavy then.

Thanks. Does that mean the additional libs may be ported in a future version?

Re: Nokia rolls out Qt SDK for unified mobile developer experience

Quote:

Originally Posted by mauricek (Post 640908)

@postformac:
We're working on fixing those issues, especially for removing everything completely when you deinstall a component.

Yes I realise it is a known issue and there are instructions in the wiki to get round it as in the link I posted before. Following the instructions works fine so its not a problem, I was just mentioning it incase anyone else has the same issue and doesn't know how to solve it.

Re: Nokia rolls out Qt SDK for unified mobile developer experience

Truly applaudable work, it renders my previous attempts to seamlessly merge MADDE and Qt Creator obsolete.

However, I have a small issue to report - a full install from the offline package on Win7 takes bloody ages - I think it took almost an hour to install on my everything-but-weak computer. Given that I've installed it on quite snappy WD Caviar Black and there was no other process accessing that HD or using other resources, and that it only weights 4.55GB an hour to install is a bit too much even tho it had to write tons of files / folders. I can only hope that further versions will be able to upgrade the beta.

Re: Nokia rolls out Qt SDK for unified mobile developer experience

@pelago: As we have stated we are currently setting up the repositories, so that everybody has access to the code. We're looking forward to contributions as well ;)

@zwer: Actually we have provided the first updates today, though they are not that big. However, they do contain some fixes for the updater and the maintenance tool. This show, that you can keep your installation for some time and should be able to upgrade it then. However, we cannot guarantee that there will be no point in time, where we might require a full reinstallation as this is still in beta phasis.

Re: Nokia rolls out Qt SDK for unified mobile developer experience

This is really a great thing! :)

But am I to understand that Qt::Wa_Maemo5 stuff won't work in the Qt Simulator? I get the following error:

Quote:

WA_Maemo5PortraitOrientation is not a member of 'Qt'

Re: Nokia rolls out Qt SDK for unified mobile developer experience

@Sasler,

that is true. If you have a look at qnamespace.h you will see the following:

Code:

#if 0 // these values are reserved for Maemo5 - do not re-use them

        WA_Maemo5NonComposited = 126,

        WA_Maemo5StackedWindow = 127,

        WA_Maemo5PortraitOrientation = 128,

        WA_Maemo5LandscapeOrientation = 129,

        WA_Maemo5AutoOrientation = 130,

        WA_Maemo5ShowProgressIndicator = 131,

#endif

which means that they are only available, when you compile for the Maemo platform. Hence your source would need to like similar to

Code:

#if defined(Q_WS_MAEMO_5)

    w.setAttribute(Qt::WA_Maemo5PortraitOrientation, true);

#endif

Re: Nokia rolls out Qt SDK for unified mobile developer experience

Quote:

Originally Posted by mauricek (Post 640914)

Ok, fully understandable. But do you think maybe there'll be any efforts in making this work? I mean, for testing whether applications has the correct UI appearance, it would only make sense now to test those things on the actual target.