<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">It's a great goal, and I'd be very up for getting OSP into shape to accept 0.2 spec MapCSS.<div><br></div><div>I agree on pretty much all your points about what should be cut with one exception – shields. OSP doesn't actually support them, but I think they're valuable to have, and simple to implement, I suspect most people who haven't implemented them (myself included) will have not done so out of laziness, rather than an issue with them.</div><div><br></div><div>One other tweak I'd like to propose is the dropping of a syntactic leniency which has some nasty consequences. Namely, that the last declaration in a specifier list does not need a semicolon after it in the current spec. This (surprisingly) is sufficient to stop the grammar being LALR(1)! More so, I don't really see what it gives the language, beyond the ability to easily generate syntax errors while adding declarations. I realise my reasons for requesting this are a bit selfish – they have a lot to do with the style of implementation I have chosen for my MapCSS parser, but I do think there are compelling reasons for it too.</div><div><br></div><div>Thanks</div><div><br></div><div>Tom Davie</div><div><div>
<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div><span class="Apple-style-span" style="font-family: Arial; "><pre>if (*ra4 != 0xffc78948) { return false; }</pre></span></div></span>
</div>
<br><div><div>On 28 Apr 2012, at 09:59, Komяpa wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>Hello everyone,<br><br>We all know everyone is willing to make their renderer the best one.<br>Everyone has own purpuose - some are targeting on speed, some are<br>willing to provide good editing experience, some want to just show<br>something to the user...<br><br>So, what do I propose:<br><br>1. Count and list active renderer developers. Those who really have<br>time to fix minor things and want to have a badge "Supports MapCSS 0.2<br>final".<br><br>2. Set up a deadline. Something real, like 1st of June (or July),<br>2012, when a spec will be marked "final", and all things post this<br>date will go to further versions/extensions/discussions.<br><br>3. Chop the current draft to really really basic things. As we see,<br>almost noone supports extrude, not everyone has support for eval(),<br>.pseudoclasses aren't widely used, shields aren't implemented in most<br>software, set and exit; ...<br>So, we make a list of core features that everyone supports or will be<br>able to support in the nearest time.<br><br>4. Split all the stuff that's chopped from 0.2 spec into some separate<br>features for further discussion.<br><br>5. Draw beautiful badges "Powered by MapCSS" for sites and renderers.<br><br>Are there any supporters for this initiative? :3<br><br>Why:<br><br>Lately, I've tried to make a stylesheet that will look the same in<br>kothic, komap, potlatch and josm, and wasn't able to do it, because<br>even basic things like casing-width are handled differently in all of<br>these.<br><br>I just want to have a strict subset of MapCSS that will work<br>everywhere for sure. :3<br><br><br>-- <br>Darafei "Komяpa" Praliaskouski<br>OSM BY Team - <a href="http://openstreetmap.by/">http://openstreetmap.by/</a><br><a href="xmpp:me@komzpa.net">xmpp:me@komzpa.net</a> <a href="mailto:me@komzpa.net">mailto:me@komzpa.net</a><br><br>_______________________________________________<br>Mapcss mailing list<br><a href="mailto:Mapcss@openstreetmap.org">Mapcss@openstreetmap.org</a><br>http://lists.openstreetmap.org/listinfo/mapcss<br></div></blockquote></div><br></div></body></html>