[Viking-devel] License dialog (Was: Viking 1.5 Plan to Release by Sept 6th)

2013-09-13 Thread Guilhem Bonnefille
Hi,

2013/9/13 Robert Norris rw_nor...@hotmail.com

 Well, I'm nearing completion for 1.5 - which will now be after this coming
 weekend - to give anyone a chance to use the latest source.

 There is one last item I would appreciate feedback on (with this patch
 attached) - this hasn't be applied to the code repository yet...

 Originally I noticed I had spelt license 'wrong' - I had used
 licence''. So I was just going to align the spelling, but then it got me
 thinking:

 Why do we introduce the About this License dialog, every time one adds a
 map?

 No other software as far as I know generates such a warning with an
 interruption to one's work flow.

 So instead I just shifted it to be an 'About' menu action from the map
 layer.

 Thus this license information is always available, which it wasn't before.


I introduced this About this license dialog. Originally, I do so because
it seems really really important to ensure user is informed about the
license related to data he works with. I don't know how other similar tools
treat such topic. I just know that some other tools working with license
(like Eclipse when you install plugins) insert a dialog where the user must
accept or decline license, even open-source related licenses.

It is good to have such info in a About menu, but this cannot be the only
solution as it is less informative: a not skilled user won't open such
dialog to discover subtilities of map's license, IMHO.

Perhaps can we keep an in-the-flow dialog, but storing the choice on disk
in order to avoid answering the same question again and again.
-- 
Guilhem BONNEFILLE
-=- JID: gu...@im.apinc.org MSN: guilhem_bonnefi...@hotmail.com
-=- mailto:guilhem.bonnefi...@gmail.com
-=- http://nathguil.free.fr/
--
How ServiceNow helps IT people transform IT departments:
1. Consolidate legacy IT systems to a single system of record for IT
2. Standardize and globalize service processes across IT
3. Implement zero-touch automation to replace manual, redundant tasks
http://pubads.g.doubleclick.net/gampad/clk?id=5127iu=/4140/ostg.clktrk___
Viking-devel mailing list
Viking-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/viking-devel
Viking home page: http://viking.sf.net/

Re: [Viking-devel] License dialog (Was: Viking 1.5 Plan to Release by Sept 6th)

2013-09-13 Thread Nick Allen

Hi,

A couple of thoughts on this;

The OSM front page with the map merely has an attribution at the bottom 
right of the screen in exactly the same way as Viking does after the OSM 
Mapnik map has been loaded. You are not required to acknowlege the 
attribution before you zoom or search on the site.


OSM itself has data derived from other sources, and it acknowledges this 
by having a page on its wiki which you have to search for;  
http://wiki.openstreetmap.org/wiki/Contributors


My conclusion is, the suggestion of having something that does not 
interrupt the flow i.e. Perhaps can we keep an in-the-flow dialog, 
but storing the choice on disk in order to avoid answering the same 
question again and again. by Guilhem is an excellent one, as is an 
'about' page where you can click on the link if you wish to. As you can 
maps from alternative sources, I don't know if you need to consider this 
before making a decision? -  could get a little complicated! Perhaps a 
general statement somewhere to the affect that users should only use the 
maps in accord to the individual owner / suppliers licence.


I use OSM data on my Garmin  on my Android phone (Osmand for 
navigation, and NeonGeo or C:Geo for geocaching), and no other source 
reminds me every time that I load it that there is a licence which I 
have to acknowledge, so it may be time to move on. My Garmin satnav 
using Garmin mapping just loads  works.


Licence / License - I think it depends where in the world you are - From 
Wikipedia - The verb *license* or *grant license* means to give 
permission. The noun *license* (American English 
http://en.wikipedia.org/wiki/American_and_British_English_spelling_differences) 
or *licence* (British English 
http://en.wikipedia.org/wiki/American_and_British_English_spelling_differences,^[1] 
http://en.wikipedia.org/wiki/License#cite_note-1 Indian English 
http://en.wikipedia.org/wiki/Indian_English,^[2] 
http://en.wikipedia.org/wiki/License#cite_note-2 Canadian English 
http://en.wikipedia.org/wiki/Canadian_English,^[3] 
http://en.wikipedia.org/wiki/License#cite_note-3 Australian English 
http://en.wikipedia.org/wiki/Australian_English,^[4] 
http://en.wikipedia.org/wiki/License#cite_note-4 New Zealand English 
http://en.wikipedia.org/wiki/New_Zealand_English,^[5] 
http://en.wikipedia.org/wiki/License#cite_note-5 South African English 
http://en.wikipedia.org/wiki/South_African_English^[6] 
http://en.wikipedia.org/wiki/License#cite_note-6 ) refers to that 
permission as well as to the document recording that permission.
Personally I seem to have been spelling it both/either way for years  
didn't realise there was a difference until you mentioned it.


Regards

Nick (Tallguy)

On 13/09/13 11:30, Guilhem Bonnefille wrote:

Hi,

2013/9/13 Robert Norris rw_nor...@hotmail.com 
mailto:rw_nor...@hotmail.com


Well, I'm nearing completion for 1.5 - which will now be after
this coming weekend - to give anyone a chance to use the latest
source.

There is one last item I would appreciate feedback on (with this
patch attached) - this hasn't be applied to the code repository yet...

Originally I noticed I had spelt license 'wrong' - I had used
licence''. So I was just going to align the spelling, but then it
got me thinking:

Why do we introduce the About this License dialog, every time
one adds a map?

No other software as far as I know generates such a warning with
an interruption to one's work flow.

So instead I just shifted it to be an 'About' menu action from the
map layer.

Thus this license information is always available, which it wasn't
before.


I introduced this About this license dialog. Originally, I do so 
because it seems really really important to ensure user is informed 
about the license related to data he works with. I don't know how 
other similar tools treat such topic. I just know that some other 
tools working with license (like Eclipse when you install plugins) 
insert a dialog where the user must accept or decline license, even 
open-source related licenses.


It is good to have such info in a About menu, but this cannot be the 
only solution as it is less informative: a not skilled user won't open 
such dialog to discover subtilities of map's license, IMHO.


Perhaps can we keep an in-the-flow dialog, but storing the choice on 
disk in order to avoid answering the same question again and again.

--
Guilhem BONNEFILLE
-=- JID: gu...@im.apinc.org mailto:gu...@im.apinc.org MSN: 
guilhem_bonnefi...@hotmail.com mailto:guilhem_bonnefi...@hotmail.com
-=- mailto:guilhem.bonnefi...@gmail.com 
mailto:guilhem.bonnefi...@gmail.com

-=- http://nathguil.free.fr/


--
How ServiceNow helps IT people transform IT departments:
1. Consolidate legacy IT systems to a single system of record for IT
2. Standardize and globalize service processes across IT
3. Implement zero-touch