kdereview? libkmap, libkface

John Layt johnlayt at googlemail.com
Mon Nov 29 21:07:38 GMT 2010

On Monday 29 November 2010 00:51:29 John Layt wrote:
> On Monday 29 November 2010 00:10:59 Albert Astals Cid wrote:
> > A Dilluns, 29 de novembre de 2010, Christoph Feck va escriure:
> > > Hi,
> > > 
> > > kdereview contains two new modules, but I did not see the announcement
> > > here. libkmap probably needs a changed/clarified name, I suggest kmap
> > > -> kgeomap. I first thought it was some replacement for QMap ;) Not
> > > sure about kface.
> > > 
> > > Christoph Feck (kdepepo)
> > 
> > Yep seems Gilles did not read my suggestions correctly and he only mailed
> > release-team and kdegraphics-devel when i said he had to mail k-c-d and
> > kdegraphics-devel.
> > 
> > You might want to search there for my and other people answers/comments
> > on the libraries.
> > 
> > Albert
> Definitely needs a better name than libkmap, and if it's a wrapper around
> Marble I have to wonder why it's not actually IN Marble, especially with
> marble planning a move of libmarble to kdesupport so people don't have to
> depend on kdeedu.  I need to dig a little deeper...
> John.

OK, had a very quick look, and libkmap is a phonon-like abstraction layer of 
mapping backends and some standard base classes and gui widgets which can use 
either libmarble as a backend or use its own code to access OSM or Google 
maps. (so why the hard dependency on Marble then?)  So pretty much the same 
purpose as QtMobility/QLocation then.  I'd guess Gilles wrote this to give his 
users a choice because Marble is not allowed to use Google Maps due to licence 
reasons, but an app like Digikam is allowed to (and also because he had his 
own Google/OSM code first).

I need to feed this into the evaluation I'm doing on geolocation/mapping 
backends that I hope to post later this week.


More information about the kde-core-devel mailing list