Hi!

For something to start with, I made a checklist based on
http://wiki.openstreetmap.org/wiki/MapCSS/0.2

https://docs.google.com/spreadsheet/pub?key=0AqNs4tRpFzJGdG5nUDFZdUFkTl8xaGRwU0Z4dnlWTFE&output=html

"*" means feature supported, "-" means it won't be supported for some
reason (platform, performance, design, personal).
Empty one means noone checked / no reasons not to support, but not
supported currently.

Ping me privately for edit link. Feel free to add rows and add more
details about different renderers/engines.


2012/4/28 Richard Fairhurst <[email protected]>:
> On 28/04/2012 12:49, Paul Hartmann wrote:
>>
>> The openness of the MapCSS language is great, because it invites people
>> to take an active part in the development. But one downside is the
>> fragmentation of the language. I think we are at point where we should
>> fix at least a subset of the specification.
> And a +1 from me too. In a bit of a rush today but some great ideas here.

>
> _______________________________________________
> Mapcss mailing list
> [email protected]
> http://lists.openstreetmap.org/listinfo/mapcss



-- 
Darafei "Komяpa" Praliaskouski
OSM BY Team - http://openstreetmap.by/
xmpp:[email protected] mailto:[email protected]

_______________________________________________
Mapcss mailing list
[email protected]
http://lists.openstreetmap.org/listinfo/mapcss

Reply via email to