Hi Gerd, I think it's quite similar to my idea. Just I was thinking to have one option to summarise the option file, you were suggesting. As option file is more easy to implement, I think its better to go your way first. The only advantage of my approach is that we later on can change the options if best practice is changed and user don't need to update any option file Henning On 11 Feb 2019, 17:50, at 17:50, Gerd Petermann <gpetermann_muenchen@hotmail.com> wrote:
I think we can create a file in examples called maybe good-options.cfg which contains options like route index housenumbers gmapi gmapsupp nsis ... (to be defined)
Do we really need more?
________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Henning Scholland <osm@hscholland.de> Gesendet: Montag, 11. Februar 2019 10:10 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] documentation improvement patch
Hi, Maybe it is a good idea to introduce some switch like 'just create a simple map'='for Garmin device and BaseCamp' , where mkgmap is always doing, what is currently best practice and new people get easily a map eg. for copying to their Garmin device or Basecamp or MapSource. So he don't need to worry an index is missing...
All the existing users still can keep their scripts with their specific settings.
Henning On 11 Feb 2019, at 02:12, Mike Baggaley <mike@tvage.co.uk<mailto:mike@tvage.co.uk>> wrote:
Hi Gerd, I have attached a patch to improve the documentation of the command line. I did it some time ago and had forgotten about it, but the discussion on whether to change default options prompted me to come back to it. The change is purely to the documentation, no code changes.
Please review and if it meets with your approval, commit.
Thanks, Mike
________________________________
mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev