Camera Problem on Symbain^3

kamalakshantv

Yes and better develop the complete app in Symbian than Qt as you need to put it on Ovi. You will have to develop the engine in native Symbian and if you develop the ui part also in Symbian instead of Qt - probably your app will support wider range of devices.

kamalakshantv

[quote author="tamhanna" date="1291440958"]The Qt has the most benefits if you later want to port to Maemo or desktop at some point in the future...[/quote]

But then again you Qt mobility is mainly for mobile devices and these API's won't be supported on Desktop right. And N900 being the only maemo device with Qt updates the target audience is very few. Maybe once meego comes in the scenario might change.

xsacha

[quote author="QtK" date="1291441234"]
But then again you Qt mobility is mainly for mobile devices and these API's won't be supported on Desktop right. [/quote]

Read the first post from here: https://developer.qt.nokia.com/forums/viewthread/1732/
It says "but also provide useful application functionality across desktop platforms."

xsacha

It's quite useful and a time saver. I don't see the problem. SmartInstaller will install the latest on the users system.

xsacha

It wouldn't update your app if you didn't use SI either. What's the point?

If you mean your app will be built on an older Qt, that's fine. Qt will be backwards compatible with your app anyway. You can update it in your own time.

xsacha

Well Qt Mobility obviously has a very useful API set and is very quick to code with. Better to use the wheel than reinvent it. And it does link in well with Qt. SmartInstaller means that you don't need to worry about whether the user has it on their system or not. So, it's win/win.
What would you use instead?

The only problem (with regards to topic) is that the QtMobility the user wants isn't allowed to be deployed in Ovi, yet.

xsacha

No, we've been over this. Write once, it will always work. You don't need to update your code because new Qt versions come out.

xsacha

Oh I guess Nokia weren't talking about QtMobility. I got it confused when Nokia mentioned that all Qt4.6.3 apps will work in future.

Well just keep updating your apps if they ever break ;) I'm sure Nokia won't break it intentionally.

kamalakshantv

[quote author="xsacha" date="1291446040"]Oh I guess Nokia weren't talking about QtMobility. I got it confused when Nokia mentioned that all Qt4.6.3 apps will work in future.

Well just keep updating your apps if they ever break ;) I'm sure Nokia won't break it intentionally.[/quote]

But these days decisions made by Nokia confuses developers a lot. You cannot say if they will stick to one plan. Especially, the way the roadmap is being changed.

xsacha

I will still use it especially for camera, regardless. I prefer coding a little a lot rather than a lot a little.

xsacha

You don't get Qt apps signed. Nokia signs it for you. It's completely free. (Exception being when it requires too much capability).

I submit unsigned app on Ovi Publish, mark it as 'unsigned' and Nokia does the rest. Hopefully this is what you meant.

[quote author="tamhanna" date="1291449010"] This is a question of taste.[/quote]
Only if they break compatibility. If they didn't, it would be a no-brainer. Code a little, little.

kamalakshantv

Well both of you are right. Just to add the app which nokia signs cannot be distributed via any other channel. It can be distributed only via Ovi. Thats the catch for free ovi signing.

xsacha

I didn't say you can't sign it yourself. I'm saying that's the way you're meant to submit apps on Ovi and that's the way I do it. It fits in with QtCreator, it's the easiest and of course free.
If your app needs more than basic capabilities, then you'll need to pay to sign of course.

Nokia gives you free UID3's by the way. In allotments of five unless you require more.

My route is 0 euros a pop.

xsacha

How about just use that UID3 in the first place?
I don't understand. You have to stick with an old UID3 so you have to pay to sign it?

xsacha

This is for Qt apps.
This is the first time Qt apps have been allowed on the Ovi Store.

So no apps from 2008, no old UIDs.

I fail to see your point.

xsacha

Not 2008 :P Time between SmartInstaller existance and free signing is a very short time window.
Unlucky if you missed out, but it's a one-off break from UID. And it affects only a handful of apps.
It also saves 20 euro (per pop as you say) for each future update.

Anyway you can create a topic about it if you want. Going off-topic.

xsacha

Well I think you're in the minority, so I stand by my free signing of Qt apps with Nokia UIDs.

Going back on-topic:
So, for you, updating your projects for each QtMobility update may prove expensive but it doesn't really affect the rest of us. Especially considering these are new apps we are talking about.
So I'll happily go with QtMobility to use such APIs as Camera and update when it is required.

kkrzewniak

Please correct me if I'm wrong but all the APIs in QtMobility 1.1 are stated to be final (API Maturity Level -FINAL). So any app using QtMobility 1.1 should run with future mobility packages, as the API is final. "Mobility Doc":http://doc.qt.nokia.com/qtmobility-1.1/

xsacha

Well that is true kkrzewniak.

But there's a lot of important functionality in QtMobility 1.1 that resides in the 'labs' -- this of course is not final and will change soon.

Examples:

Gestures (pinch-zoom, swipe and so on) Plugin
Folder List Plugin
Particles Plugin

Fortunately for the OP, Camera shouldn't change much.
The APIs defined as 'FINAL' may still be extended (but still backwards compatible).

kkrzewniak

Yes and that is my point exactly! Stop whining that QtMobility so bad, just stick to the parts You know to be final.