David Winslow wrote: > On Fri, 2009-03-20 at 11:53 +0100, Andrea Aime wrote: >> Chris Holmes ha scritto: >>> 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? >> Hmmm... if you're thinking to have a UI on top of this, then it makes >> not much sense, since a UI is there to hide the underlying storage >> anyways. >> >> CSS based styling idea is there to have web designers work on the >> CSS directly, and in that case, turning it into SLD to be >> posted on the server side does not look great, as we'd have to >> translate back and forth between the two ways of expressing a style, >> and possibly loose the CSS on the way along with comments that >> the web dev embedded in it. >> I mean, if you post the SLD to the server, where do you store the CSS? >> >> Cheers >> Andrea >> > > My 2 cents worth: it's valuable to expose the css source to web > designers; sometimes things are just easier in text mode (says the cli > junkie). It's probably possible to ensure a 1:1 mapping between CSS and > SLD, especially if that's taken into account throughout the design > process. >
Well, I was thinking they'd basically operate in a text mode type way, but in a panel in the Styler app, where their changes to the css would be applied instantly. I guess the one thing that wouldn't work well with the full javascript side would be capture the comments. But then again the only way to keep the comments if you're doing it in java is to actually store the css file in the data dir, which seems a bit nasty to me, to have two different persistence formats for styles. Or else you again lose the comments I imagine cascadenik probably loses comments. I don't think the idea behind this is really to make it a CSS thing used up and down in our system. I think it's to give designers a way in to styling maps that they're more comfortable with. The concepts are still going to be a bit different, our goal isn't to give them CSS, it's to give them a css like language and rules to explore these concepts, imho. C > Anyway, just wanted to comment that I have a couple of hundred lines of > javacc written toward CSS support in geotools, so I'd be happy to > (co?)mentor this one. > > -- > David Winslow > OpenGeo - http://opengeo.org/ > -- Chris Holmes OpenGeo - http://opengeo.org Expert service straight from the developers. ------------------------------------------------------------------------------ _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
