The lightmaps example was an existing Qt demo that was modified to show off the Bearer Management API and the positioning part of the Location API. It will probably be removed from Qt Mobility eventually - we were just unsure about how polished the new example was going to be by release time. We have already removed the Fetch Google Maps example for a similar reason.
We've got an unofficial OSM plugin in a branch in the public gitorious (which does maps and geocoding) but it really shouldn't be used for anything other than testing since we really don't want to hammer the OSM servers more than necessary. Because of this it probably won't end up as an officially blessed plugin - in fact it probably won't receive much more development. I believe there is already some work happening in this area that will avoid the server-hammering issue - I'll ask the people involved to see if/when they want to announce anything on this front. Hopefully that will happen sooner rather than later and avoid any unnecessary duplication of effort. Cheers, Dave > -----Original Message----- > From: [email protected] [mailto:qt-mobility- > [email protected]] On Behalf Of ext Cornelius Hald > Sent: Monday, 4 October 2010 6:06 AM > To: Till Harbaum / Lists > Cc: [email protected] > Subject: Re: [Qt-mobility-feedback] GPSD support? > > Hi Till, > > nice to meet you here :) I can't comment on the position stuff, but I > know a bit about the maps widget. > > On Sun, 2010-10-03 at 17:39 +0200, Till Harbaum / Lists wrote: > > Also the maps seem to face the same issue. There are two map > demos/examples, one being openstreetmap based and one being nokia maps > based. It seems the osm example is handling osm completely in the > application and not by qtmobility. Does this make sense? What's the > point having a powerful framework when it's up to the application to do > the most complex parts itself? Will this change? My expectations were > that the map widget reports to the application what map source plagins > it has and then uses one of these. What's the point of moving low level > map stuff out of the framework into the application? > > The QGraphicsGeoMap is based on a plug-in system, but currently only > the > Ovi Maps plug-in is included by default. The application can query > available service providers and select one. Yesterday I wrote a plug-in > that displays OSM tiles instead of Ovi tiles. Basically I took the Ovi > plug-in code and changed the tile URL. It's far from finished, but > looks > quite straight forward. > > If I'll continue with that I'll publish the code somewhere, but first > I'm curious how to integrate that with QML. Anyways, another thread > exists about that already... > > Cheers! > Conny > > > _______________________________________________ > Qt-mobility-feedback mailing list > [email protected] > http://lists.trolltech.com/mailman/listinfo/qt-mobility-feedback _______________________________________________ Qt-mobility-feedback mailing list [email protected] http://lists.trolltech.com/mailman/listinfo/qt-mobility-feedback
