On Samstag, 3. Januar 2015 15:09:58 CEST, Tobias Leupold wrote:=0A>> IM=
HO, the real question is, shouldn't that pointless wrapper be deprecate=
d=0A>> in favor of just using Marble directly?=0A>=0A> Can marble be us=
ed in an identical way as libkgeomap=0A=0AAfaiu and would expect, libkg=
eomap wraps marble, openstreetmap and google maps for inclusion into yo=
ur own GUI.=0AThe major difference i'd expect would be dependencies:=0A=
OSM & google should hardly require anything but an html renderer, in do=
ubt QtWebKit, where the marble backend will require you to install marb=
le (and maybe gain additional features like OGL etc.)=0A=0AIn this case=
, libkgeomap can obviously NOT reasonably be substituted by marble (int=
roducing marble as new hard dependency)=0A=0AAnd if the GG maps support=
 comes otherwise for free (implementation like OSM, just slightly diffe=
rent API) and in case the google terms allow this usage, withdrawing th=
e feature "to educate the user" seems like a pointless feature restrict=
ion.=0A=0ATo educate the user, OSM could/should be the default, but if =
the user requires features from google maps (better/available satelite/=
road precision) for his partcular usecase and region, there's no point =
in punishing the USER, just because one may dislike GOOGLE.=0A=0ACheers=
,=0AThomas