Re: KDE Geolocation Services

2010-11-04 Thread John Layt
On Thursday 04 November 2010 07:23:38 Cyrille Berger Skott wrote: > On Wednesday 03 November 2010, John Layt wrote: > > * Comes packaged with lots of other services that we don't need, such as > > Solid, Phonon and kdepim equivalents. > > It is worth to note that QtMobility is very modular, so you

Re: [Marble-devel] KDE Geolocation Services

2010-11-04 Thread Ariya Hidayat
> From looking at the current state of the Terms and Conditions of the Ovi Maps > API I'm not sure whether we can legally make use of it: IANAL but it seems as long as you don't initialize/start using the Ovi Maps provider plugin, you should be good. We do not need to remove the plugin code comple

Re: KDE Geolocation Services

2010-11-04 Thread Sebastian Kügler
On Thursday, November 04, 2010 16:56:54 Kevin Krammer wrote: > On Thursday, 2010-11-04, Sebastian Kügler wrote: > > On Thursday, November 04, 2010 16:04:33 John Layt wrote: > > > Which kind-of makes the whole GConf usage moot? > > > > No, it doesn't. If that stuff is still needed for actually usi

Re: KDE Geolocation Services

2010-11-04 Thread Kevin Krammer
On Thursday, 2010-11-04, Sebastian Kügler wrote: > On Thursday, November 04, 2010 16:04:33 John Layt wrote: > > Which kind-of makes the whole GConf usage moot? > > No, it doesn't. If that stuff is still needed for actually using it, we're > still effectively depending on whateverlibgconfisin, and

Re: KDE Geolocation Services

2010-11-04 Thread Sebastian Kügler
On Thursday, November 04, 2010 16:04:33 John Layt wrote: > Which kind-of makes the whole GConf usage moot? No, it doesn't. If that stuff is still needed for actually using it, we're still effectively depending on whateverlibgconfisin, and that, as Aaron points out would be rather unfortunate. B

Re: KDE Geolocation Services

2010-11-04 Thread John Layt
On Thursday 04 November 2010 14:43:19 Kevin Krammer wrote: > Ah, you meant using the D-Bus API directly in apps. I interpreted it as in > not using their C library, i.e. using D-Bus indirectly (through their C > wrapper). Phew! Yes, just to be clear, our api would only call their DBus interfac

Re: KDE Geolocation Services

2010-11-04 Thread Kevin Krammer
On Thursday, 2010-11-04, John Layt wrote: > We'd then have only one place where we generate the QDbus adaptor instead > of 50, only one copy of the template set-up/tear-down code instead of 50, > and only one place that needs maintenance if/when Geoclue changes. [I do > need to read more on how

Re: KDE Geolocation Services

2010-11-04 Thread John Layt
On Thursday 04 November 2010 09:01:12 Kevin Krammer wrote: > On Wednesday, 2010-11-03, Aaron J. Seigo wrote: > > a) annoyance of using DBus directly > > It's a single line in the CMakeLists.txt, isn't it? > > > b) changes in the DBus API are out of our control. > > Sure, but upstream API changes

Re: KDE Geolocation Services

2010-11-04 Thread Kevin Krammer
On Wednesday, 2010-11-03, Aaron J. Seigo wrote: > On Wednesday, November 3, 2010, Kevin Krammer wrote: > > On Wednesday, 2010-11-03, John Layt wrote: > > > The obvious backend solution is Geoclue, a freedesktop.org project > > > which is available on almost all distro's now, is used by Gnome, and >

Re: [Marble-devel] KDE Geolocation Services

2010-11-03 Thread Torsten Rahn
Hi, I agree that this will be likely one of the important topics at the Marble Sprint indeed. Am Mittwoch, 3. November 2010 21:42:22 schrieb John Layt: > part of the Meego platform. The problem comes in the api to access > Geoclue, which is a DBus based service with C bindings, as we would > o

Re: KDE Geolocation Services

2010-11-03 Thread Kevin Krammer
On Wednesday, 2010-11-03, John Layt wrote: > [Apologies for the cross-post, but I'd like feedback from app developers on > their requirements too, not just core] > > Hi, > > This weekend the Marble devs are meeting for a sprint, and I'm tagging > along to discuss a few different issues that I'd l

KDE Geolocation Services

2010-11-03 Thread John Layt
[Apologies for the cross-post, but I'd like feedback from app developers on their requirements too, not just core] Hi, This weekend the Marble devs are meeting for a sprint, and I'm tagging along to discuss a few different issues that I'd like peoples feedback and opinions on. The big one is