Hmmm... The standards work would be good, but I was imagining that implementing the parser in javascript would be better. Parse from the language in to OL Style objects, which can then be persisted out as SLD objects for GeoServer. GS would still use SLD through and through. Doing things this way also gets us the ability to do real time previews on the client side, without GS having to do the rendering. Are there other advantages to a java parser that I'm missing?
Andrea Aime wrote: > Added this: > http://geoserver.org/display/GEOS/Styling+maps+with+CSS > > If anybody wants to comment or add details it would be > nice. > Mentor wise I could be the point person for the SLD > side of the fence, but a web designer is kind of > a required complement as I'm certainly no expert > at CSS. > > Cheers > Andrea > -- Chris Holmes OpenGeo - http://opengeo.org Expert service straight from the developers. ------------------------------------------------------------------------------ Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are powering Web 2.0 with engaging, cross-platform capabilities. Quickly and easily build your RIAs with Flex Builder, the Eclipse(TM)based development software that enables intelligent coding and step-through debugging. Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
