On Sat, Jul 14, 2012 at 3:11 AM, Jonathan Bennett <[email protected]> wrote: > There's a lot in common with some features that have been suggested > and/or implemented in MapCSS (eval, nested rules, pseudo-classes) and > what Less provides for web CSS. What does everyone think (in general > terms) of incorporating Less into MapCSS instead of recreating most of > its features independently?
Ok, from my quick perusal (http://lesscss.org), it's a javascript script which converts enhanced CSS into normal CSS. You can run it either client-side or server-side (with NodeJS). Questions: - how many MapCSS implementations don't have access to a JavaScript interpreter? - can Less cope with MapCSS, or would it need to be modified? - if you're talking about simply using (then modifying) the code (Apache 2.0 licence), will this cause licence issues for anyone? - are there alternative libraries to consider? - if there is a Less feature duplicated by an existing, implemented MapCSS feature, are you proposing deprecating/removing the existing feature? My instinctive reaction is to be cautious - this could add a lot of extra expressive complexity, especially when Less features are similar to existing ones. Steve _______________________________________________ Mapcss mailing list [email protected] http://lists.openstreetmap.org/listinfo/mapcss
