On Tue, Oct 2, 2012 at 3:40 PM, David Winslow <[email protected]> wrote:

> LegendInfo could be embedded in the StyleInfo, and in fact this would
> happen automatically if you simply make a LegendInfo class and add one as a
> property of StyleInfo objects.  Justin might disagree but I don't see any
> potential drawbacks with this approach (unless it's useful to share legends
> between styles - but it shouldn't be, right?)
>
>
Doing this would make sense if you want to offer a style wide legend (as
opposed to a per rule symbol),
it would require an API change in catalog (which is possible only on trunk,
not in the stable series)
and then modifications in the GUI so that the SLD editor also provides a
way to choose a style legend.

While both this approach and the per rule one are based on the idea of
providing pre-build images, they
serve different purposes: the rules can have scale dependencies and legend
graphics generation should
take that into consideration,
if you have the per rule symbols it's easy to build a legend for a certain
scale, with the style wide one not,
we'd need something like a list of legends, one per possible scale range

Cheers
Andrea

-- 
==
Our support, Your Success! Visit http://opensdi.geo-solutions.it for more
information.
==

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054  Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39  339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

-------------------------------------------------------
------------------------------------------------------------------------------
Don't let slow site performance ruin your business. Deploy New Relic APM
Deploy New Relic app performance management and know exactly
what is happening inside your Ruby, Python, PHP, Java, and .NET app
Try New Relic at no cost today and get our sweet Data Nerd shirt too!
http://p.sf.net/sfu/newrelic-dev2dev
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Reply via email to