View Single Post
Posts: 107 | Thanked: 74 times | Joined on Jan 2010
#29
Originally Posted by Helmuth View Post
From a technical point of view it is very reasonable to use the manpower to focus on the Harmattan Version. I bet, like the rest of the system UI, this version is then written in QT.

So, they have to port them from GTK to QT. The work has just began or finished. So it is not reasonable to develop the old GTK Version and the new QT Version when the end of GTK is scheduled.

We've got soon full QT 4.6 support for the N900.
Advertised here many times: "Develop as much as you can from now on in QT, not in GTK. So the Programms could run under Harmattan without rewriting the code. (or only small changes)"

So, when the Harmattan Version of OVI Maps is based on QT and it is a, from the system firmware, independent Software. Shouldn't it be so hard to port it for the N900 when the Harmattan Version is relased?
Well, as qt 4.6 will land on maemo5 it's not a toolkit problem, so we may restrict to:

* different wm standard, xatoms, etc. but should be trivial to fix
* different middleware to interact with gps, geodata, contacts etc.
* other things that does not come to my mind actually

I bet, qgil wont answer. I'm sure, he's hacked off by this topic... and I can understand this very good.
Oh I hope qgil will not abandone this thread, I imagine easily that he may be quite bored, but as he said let's try to collaborate.

Continuing on the technical aspect, and on the point that big part of nokia man power is dedicated to maemo6, do not understimate the man power of community.

I'll happy to collaborate in a community developer team to adapt ovi map 3 for maemo5, signing an NDA if necessary.
If that's not possible to be sure that code will remain private, we may develop a "middleware compatibility layer", using only the exposed API.

Wath do you think about that?
 

The Following 3 Users Say Thank You to nicola.mfb For This Useful Post: