Hi Gerd I don't think having: BRANCH: default-typ makes sense because I don't think there will ever be a single, ideal file. So better to accept now that it will be a collection of files, and, as nothing exists at the moment, they might as well go in 'trunk'. In trunk, they will be visible sooner to all mkgmap users. Then any in the dist/examples/typ-files directory could be selected to be used as -is or a starting point for modification. I don't know what the best visual effect should be either, but, having tried a complex example I found somewhere, the raw Garmin device rendering (with just a _drawOrder section in the TYP file) looked much, much better. I'm hoping others will submit examples, then we just need some reference in the documentation to point people to the examples, along with good comments in the files themselves. Ticker On Tue, 2018-11-27 at 10:59 +0000, Gerd Petermann wrote:
Hi Ticker,
well, we have it because I wrote that I'd like to have a typ file for the default style. My problem is that I cannot help with that because I feel helpless when it comes to questions reg. "what looks better?" or "what should be rendered and how?" Do you think we need another branch or do you think that the exising one makes no sense?
Gerd
________________________________________ Von: Ticker Berkin <rwb-mkgmap@jagit.co.uk> Gesendet: Dienstag, 27. November 2018 11:37 An: Gerd Petermann; Development list for mkgmap Betreff: Re: AW: [mkgmap-dev] New branch for default typ file
Hi Gerd
Is it worth having a branch for typ-files development?
Ticker
On Tue, 2018-11-27 at 09:25 +0000, Gerd Petermann wrote:
Hi Ticker,
okay, see http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=425 8
Gerd
________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Ticker Berkin <rwb-mkgmap@jagit.co.uk> Gesendet: Dienstag, 27. November 2018 09:56 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] New branch for default typ file
Hi Gerd
Happy with either, but slightly prefer typ-files.
I don't think it's worth me doing another patch, it was really just a 1 line change to build.xml and inserting the attached file
Ticker
On Tue, 2018-11-27 at 06:27 +0000, Gerd Petermann wrote:
Hi Ticker,
I don't like the directory name TYPs. One reason is that the directory doesn't contain *.TYP files, the other is that one might want to write TYPes instead. I'd prefer typ-files or maybe typ-sources.
Gerd
________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Ticker Berkin <rwb-mkgmap@jagit.co.uk> Gesendet: Montag, 19. November 2018 13:07 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] New branch for default typ file
Hi
I suspect there will be a few TYP files for different usages.
I propose that they should be handled like the styles, where they are gathered in a directory resources/TYPs and the build process copies then to dist/examples/TYPs
I don't think a new branch is necessary, as there is nothing in the system at the moment.
I'd like to submit my most basic TYPfile and attach the file and patch. This, along with option --order-by-decreasing-area, has been adequate for me for a few years (but I have problems with my new Etrex 30x not showing some line types)
Ticker _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev