Summary: | [Chameleon] XMLThemeLegend-> use ms generated leg_icons/symbol definition. | ||
---|---|---|---|
Product: | Chameleon | Reporter: | Chris Thorne <cthorne@dmsolutions.ca> |
Component: | Widget | Assignee: | chameleon-dev <chameleon-dev@lists.maptools.org> |
Status: | NEW | ||
Severity: | enhancement | ||
Priority: | P4 | ||
Version: | 1.99 | ||
Target Milestone: | FUTURE | ||
Hardware: | PC | ||
OS: | Windows 2000 | ||
Whiteboard: |
this is an interesting idea and probably quite useful but very hard to implement so that it will work consistently in all uses. The primary use of the XMLThemeLegend was originally to abstract layers into groups of layers for use with Context file (which have no sense of grouping), this makes it difficult to preserve the design of the widget and provide a one-to-one mapping from the interface to layers in the map file. A better solution would be to use the XMLThemeLegend to generate layer controls and the LegendTemplate to generate a real legend with icons.
updated version to 1.99
Since seeing how the XML Theme Legend widget and the HTML Legend can work together within an application (ie. gsc_worldminerals). I makes total sense to separate map layer/group interaction, from legend information. I guess the problem originated when we were trying to us the HTML Legend in an unrealistic manner. In the future I hope we will never use the HTML Legend as a layer/group controller.
Changed target to 2.1.
Changed Target Milestone to FUTURE. (Enhancements may be moved from this target to specific "versioned" targets after product design review cycles.)