Hi Alex, thanks for the fair answer.
Just out of curiosity, what is going to happen to the rest of QtMobility APIs for the Qt5 time frame: will they also follow suit and migrate to Qt? ~ Akos. On Thu, Sep 22, 2011 at 00:52, <[email protected]> wrote: > Hi, > >>-----Original Message----- >>From: [email protected] >>[mailto:qt-mobility-feedback- > > First of all, thank you for the honest feedback. > >>I was really disappointed with reverse geocoding of qtmobility. >> >>I had done a application with qtmobility 1.0.1 at that time reverse >>geocoding was not available. So I used google web API and >>QNetworkAccessManager >>to do the job. Now when its available I tried it and results were not so good. >>First all I need is an address from a coordinate, and I get a list of >>places. Now I have to see how many places it returned? how close are >>they to the lat/lon >>that I provided for reverse coding. Even after doing that level of >>detail was very poor. Best address I got was: >>south bangalore, karnataka, india. >>while with google I was getting the sub-street also. and it was >>conveniently available as a string in returned json. It also has lot >>of other details nearby things. >>But at the top of the json there was the best possible resolved it >>could get (provide a similar api). > > I agree that the returned information is very marginal at best. I am equally > frustrated about the current situation as you are. > > We have recognised this and are working on improvements. Unfortunately this > will not happen in QtMobility anymore but Qt5. The beginnings of the new > places/search API can already be seen in the qt5 git repos. It will provide a > much better resolution and place search. The new API will utilize better > content providers as well. > >>And in general I have seen a lot of qtmobility like this: >>"if backend does this.... then this.... Backend may do that. Now where >>is this documentation what does a backend actually do, say symbian or >>maemo backend. >>And if you start coding keeping in mind all these "backend may do this >>and that", code will turn out to be a mess. > > In general there is no difference between Harmattan and Symbian. They use the > same REST server but that's of course only a small consolation given the > greater context. I'll make sure that this feedback is passed on to the > REST/content guys. On device search is always going to be limited as there is > simply not enough space on a device. > > -- > Alex > _______________________________________________ > Qt-mobility-feedback mailing list > [email protected] > http://lists.qt.nokia.com/mailman/listinfo/qt-mobility-feedback > _______________________________________________ Qt-mobility-feedback mailing list [email protected] http://lists.qt.nokia.com/mailman/listinfo/qt-mobility-feedback
