Are you a heavy duty styler? If so, read on:

  I notice that quite a lot of postings on the list are from people who
  are having problems with complex style files. This little patch won't
  (directly) solve those problems but it does provide a useful capability
  that could be part of a solution for those people who have complex
  styling requirements and are willing to do some coding.

  What the patch does is allow elements (nodes, ways) to specify their
  garmin type (and a few other things) explicitly using these tags:

  mkgmap:gtype  the element's type (integer constant)

  [snip]

Do you think the problem is that the style rules are too hard to figure
out, that there are bugs, or that they aren't expressive enough?

I wonder about adding extension language support so that people could
write a program that takes an element and figures out what to do with
it.  We sort of have this, but not a real language.  I suppose that is
one possible read/crunch/write external program and your patch enables
such experimentation.

Attachment: pgpOr0Grrhikj.pgp
Description: PGP signature

_______________________________________________
mkgmap-dev mailing list
[email protected]
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Reply via email to