Hi Bernd,
> that commit is a hack - one api key for all debian users would clearly
> not work. viking needs a way to configure api keys at runtime.
I'm not sure what the content provider wants from their API keys: are they for
individuals or applications? The first sentence of the documentation about
them implies to me they are application-level, in which case one API key baked
into viking is OK.
http://www.thunderforest.com/docs/apikeys/
It actually is already possible to set the API key at runtime via a config
file. The following ~/.viking/maps.xml works fine in stretch:
https://sourceforge.net/p/viking/feature-requests/146/
(yes, it needs a simple GUI to set that value if the the API key is to be
obtained by the individual)
cheers
Stuart
--
Stuart Prescott http://www.nanonanonano.net/ stu...@nanonanonano.net
Debian Developer http://www.debian.org/ stu...@debian.org
GPG fingerprint 90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7
