JAMISON CONLEY wrote: > > If the dead-ware CustomGlyphRenderer is a mystery, it was initially > written to support some functionality in GeoVISTA Studio that was > designed to allow editing of arbitrary glyphs, but did not go so far > as SVG. It so happens that I am in the process of resurrecting > Studio, or at least that part of Studio, to work with the most recent > stable version of GeoTools (2.4.2). I have no objection to the > deprecation of CustomGlyphRenderer--a library of various glyph > renderers, including the CustomGlyphRenderer, within the Studio code > base is more appropriate than in the GeoTools code base--but would > appreciate support for the GlyphRenderer interface, in its current or > another location. > > Of course, if the PMC or those who are less tangential to the GeoTools > project than I am decide to deprecate the GlyphRenderer interface, I > respect that decision. Jamison does the new proposal work for your needs? As Andrea says it is more complete...
You will also find that Eclesia has been looking at some of the Symbology Encoding functions that are set to replace the range of classification and multidimensional classification functions that were for me the real magic for GeoVista. Cheers, Jody ------------------------------------------------------------------------- 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 Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
