Summary: | [Chameleon] XMLThemeLegend-> Collapsible tree menu legend ability | ||
---|---|---|---|
Product: | Chameleon | Reporter: | Chris Thorne <cthorne@dmsolutions.ca> |
Component: | Widget | Assignee: | Fred Warnock <fwarnock@dmsolutions.ca> |
Status: | NEW | ||
Severity: | enhancement | CC: | chameleon-dev@lists.maptools.org |
Priority: | P4 | ||
Version: | 1.99 | ||
Target Milestone: | FUTURE | ||
Hardware: | PC | ||
OS: | Windows 2000 | ||
Whiteboard: |
I disagree with this. The structure of the widget is sufficiently flexible to enable the integration of a javascript-based menu system in the renderer file. Any attempt to provide a menuing system in the widget itself would likely only satisfy the requirements of one project, others would want it to be different in various ways that would require lots of changes. Instead, one of the sample applications should demonstrate how the XMLThemeLegend widget can be used to generate collapsible menus and then it is up to the application designer to provide their own solution. Assigning to Fred to incorporate an example in the sample templates, then to Jay to implement.
updated version to 1.99
So you are saying that it is unrealistic to have an XMLThemeLegend parameter to change the kind of XML Legend from non-collapsible to a Java script collapsible tree menu? I think think this would be a good enhancement.
Paul, I agree with you completely, but chris I see your point. We can produce many different kinds of javascript driven systems for navigating layers in a mapfile, but they are as unique as any legend template (or in this case renderer file) Creating a sample app(s) with a tree like (or tab like) legend interface is a cool idea. That way you'll have the basic javascript you need (or at least a really good start) to make really snazzy layer controls without bloating a streamlined and flexible widget.
changing target to "-", since "1.99 beta release" is no longer valid. Paul and Darren should decide at which point during the beta release cycle this should be resolved.
this has no target within my scope for releasing Chameleon, I do not believe that it is essential. If Fred has time, that's great, if not, it can come in some later version AFAIC.
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.)
Was this implemented? can you confirm?
unfortunately not yet.