logo separator

[mkgmap-dev] Style include files

From aighes osm at aighes.de on Wed Sep 5 15:16:49 BST 2012

Hi
I think about something like include "default_address_search" and other 
basic elements.

To include parts of other styles could be pretty hard, because some 
parts aren't really stand alone because of requirements. Eg. copying 
name from route-relation to a normal way. One style copy name-Tag to 
bicycle_name another style to xyz and so on. So there is no really 
difference between change existing code to your needs and include code 
from someone else or just changing the code an copying the code directly 
to your style.

Henning

Am 05.09.2012 16:06, schrieb Steve Ratcliffe:
> Hi
>
>> Last year, I wanted to divide the default style into modules. It would
>> be easier to continue this with the style-include branch. Perhaps there
>> could be a 'standard library' of files that all styles (including
>> user-defined styles) could include?
> A library is a good idea.
>
> I don't think that including from other styles is a bad idea,
> the question is just how do we do it.
>
> If you are developing your own style then you can divide it
> up into as many different files that you like and place them
> all somewhere inside the style.
>
> You might want to include a file from one of the built in styles but
> then you would be relying on it not changing too much in an
> incompatible way.  Having a library of style fragments as a built in
> style might go a long way to make that more manageable.
>
> So I'll ask another question: if there was a syntax
>
>    include some-file from some-style
>
> should the some-style be restricted to a library or any built in
> style?  I am worried that --style-file and --style arguments already
> cause some confusion.
>
> ..Steve
> _______________________________________________
> mkgmap-dev mailing list
> mkgmap-dev at lists.mkgmap.org.uk
> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
>




More information about the mkgmap-dev mailing list