Komяpa wrote:
So, I propose to add the following things:
collision-sort-by: (tag/eval()) - a value used for sorting items
within z-index and layer when rendering;
collision-sort-order: asc/desc, by default desc;
Good idea.
I'd suggest renaming to collision-index and collision-index-sort. This
is analogous with z-index and therefore more CSS-like.
Also, we should probably have 'ascending' and 'descending' rather than
'asc' and 'desc' (CSS doesn't generally use abbreviations).
font-size should be allowed not only an exact value, but also a list
of different sizes, tried to be used from start to the end. If a
renderer doesn't want to support that, it should just stick to the
first value
That's analogous to the way font-family works, so yes, I like that. :)
text-placement, with default value "exact". pssible:
- "any" - whatever renderer decides;
- "exact" or just "X" - the one that was chosen otherwise (centered,
offsetted down by text-offset);
- N, E, S, W, NE, SE, NW, SW, X - values, that can be separated by
commas. show where a label can be shifted instead of "down" by
"text-offset" amount of pixels.
Sounds good, but again, I think CSS doesn't do abbreviations. So
'north', 'east', 'south' etc. etc. It's not much more to type and it's
much more readable. :)
cheers
Richard
_______________________________________________
Mapcss mailing list
[email protected]
http://lists.openstreetmap.org/listinfo/mapcss
