Re: Geolocation DataEngine broken?

2012-01-11 Thread Aaron J. Seigo
On Saturday, December 31, 2011 09:50:30 Luca Beltrame wrote:
 In data sabato 31 dicembre 2011 09:45:37, Aaron J. Seigo ha scritto:
  * fix the dataengine
 
 This poses the problem that the current service used by the dataengine now
 requires an API key to operate, and in turn requires a signup. Probably a
 different service is required.

often you can simply request and API key and they will give you one. if it 
requires paying for a key, often using the we're a f/oss non-profit works.

-- 
Aaron J. Seigo
humru othro a kohnu se
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43

KDE core developer sponsored by Qt Development Frameworks


signature.asc
Description: This is a digitally signed message part.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel


Re: Geolocation DataEngine broken?

2012-01-11 Thread Luca Beltrame
In data mercoledì 11 gennaio 2012 13:06:04, Aaron J. Seigo ha scritto:

 often you can simply request and API key and they will give you one. if it
 requires paying for a key, often using the we're a f/oss non-profit works.

I'll try to look into it this weekend, barring any problems...

signature.asc
Description: This is a digitally signed message part.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel


Re: Geolocation DataEngine broken?

2011-12-31 Thread Aaron J. Seigo
On Monday, December 26, 2011 15:51:33 Luca Beltrame wrote:
 What should be done? Disable the non-gpsd part of the geolocation
 dataengine, or find a different solution? As mgraesslin noted on IRC, this
 issue will also affect *all* released versions of plasma so far.

best solution:

* fix the dataengine

* make it use JS for interacting with the web service so we can easily update 
it via synchrotron, including older (in the future ;) releases.

-- 
Aaron J. Seigo
humru othro a kohnu se
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43

KDE core developer sponsored by Qt Development Frameworks


signature.asc
Description: This is a digitally signed message part.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel


Re: Re: Geolocation DataEngine broken?

2011-12-31 Thread Luca Beltrame
In data sabato 31 dicembre 2011 09:45:37, Aaron J. Seigo ha scritto:

 * fix the dataengine

This poses the problem that the current service used by the dataengine now 
requires an API key to operate, and in turn requires a signup. Probably a 
different service is required.

-- 
Luca Beltrame - KDE Forums team
KDE Science supporter
GPG key ID: 6E1A4E79


signature.asc
Description: This is a digitally signed message part.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel


Geolocation DataEngine broken?

2011-12-26 Thread Luca Beltrame
Hello,

today I was hacking around an existing plasmoid to add IP address information 
and I thought of using the geolocation DataEngine. Investigation with 
plasmaengineexplorer showed that it returned no results, only a location 
source with no information. As I don't have gpsd running, I remembered it 
relied on an external service to get IP address information, and so I checked 
the debug output.

Debug output showed that:

plasmaengineexplorer(2309)/plasma EngineExplorer::addSource: adding location
plasmaengineexplorer(2309)/plasma EngineExplorer::addSource: getting data for 
source  location
plasmaengineexplorer(2309)/plasma EngineExplorer::addSource: connecting up now
plasmaengineexplorer(2309)/plasma Geolocation::sourceRequestEvent: location
plasmaengineexplorer(2309)/kio (Scheduler) KIO::SchedulerPrivate::doJob: 
KIO::SimpleJob(0x22fb020)
plasmaengineexplorer(2309)/plasma Ip::update: Fetching 
http://iplocationtools.com/ip_query.php
plasmaengineexplorer(2309)/plasma EngineExplorer::addSource: adding location
plasmaengineexplorer(2309)/plasma EngineExplorer::addSource: er... already 
there?

Looking at that address show that it's no longer there, it only returns 
0.0.0.0 MOVED 0.0.0.0 and in fact iplocationtools now moved to an API key 
based query and a completely different syntax, hence it basically no longer 
works.

What should be done? Disable the non-gpsd part of the geolocation dataengine, 
or find a different solution? As mgraesslin noted on IRC, this issue will also 
affect *all* released versions of plasma so far.

-- 
Luca Beltrame - KDE Forums team
KDE Science supporter
GPG key ID: 6E1A4E79


signature.asc
Description: This is a digitally signed message part.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel