Jody Garnett ha scritto: > Andrea Aime wrote: >> As an alternative, I can try to make a full fledged >> proposal with a general idea of what extra stuff >> I'm going to add to TextSymbolizer. >> > If the change was just limited to the rendering module we should be > okay; similar work is happening in CQL with out a proposal. Do you plan > to change the xml parser / generation code to support your extra arguments?
Renderer is not involved at all, only the geoserver kml and rss generator will be (the extension is about adding stuff that's relevant to KML). So I will need to touch at least text symbolizer implementation and the xml parser (but not the encoder). Both changes should be pretty transparent. I guess I'll have to roll a KMLTextSymbolizer interface as well with three extra properties, title, abstract and List<OtherText> where OtherText is made of (label, xpath) (it can be used to create stuff located at a certain xpath in the output, for example you can use it to specify extrusion or time in a kml output). Ah, another thing we want to experiment is a cross between SLD and FreeMarker, in particular, the ability to make a Label be defined by a FreeMarker template. Since this will be done by adding a FilterFunction, I can start by adding it on the GeoServer side and eventually bring it back into its own module when done if anyone is interested in _very_ fancy labelling (the mixed content label support we added from a user patch already allows quite a bit of latitude) Cheers Andrea ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
