[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: libkgeomap
From:       Thomas_Lübking <thomas.luebking () gmail ! com>
Date:       2015-01-03 17:18:06
Message-ID: a4d59ff7-da22-4923-9b01-8685afb9d66a () gmail ! com
[Download RAW message or body]

On Samstag, 3. Januar 2015 15:09:58 CEST, Tobias Leupold wrote:
> > IMHO, the real question is, shouldn't that pointless wrapper be deprecated
> > in favor of just using Marble directly?
> 
> Can marble be used in an identical way as libkgeomap

Afaiu and would expect, libkgeomap wraps marble, openstreetmap and google maps for \
inclusion into your own GUI. The major difference i'd expect would be dependencies:
OSM & google should hardly require anything but an html renderer, in doubt QtWebKit, \
where the marble backend will require you to install marble (and maybe gain \
additional features like OGL etc.)

In this case, libkgeomap can obviously NOT reasonably be substituted by marble \
(introducing marble as new hard dependency)

And if the GG maps support comes otherwise for free (implementation like OSM, just \
slightly different API) and in case the google terms allow this usage, withdrawing \
the feature "to educate the user" seems like a pointless feature restriction.

To 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.

Cheers,
Thomas


[prev in list] [next in list] [prev in thread] [next in thread]