New GeoExt.ux.LayerTreeBuilder widget

[adube]

Add the GeoExt.ux.LayerTreeBuilder widget that is currently in Mapgears' sandbox as a GeoPrisma widget. It should deprecates the MapFishLayerTree widget.

When completed and fully operational, MapFish could be entirely removed from the external libraries and samples. All widgets using MapFish-client should then be deprecated. When ready, add this task in an other ticket.

Link to the widget in Mapgears sandbox :
​http://dev.geoext.org/sandbox/mapgears/geoext.ux/ux/LayerTreeBuilder/

[adube]

We should use the existing resource option "layertreepath" to define the "group" option for the created layers in the map widget (required by the widget). The rest should be automatically generated.

Don't forget to support i18n values along the way.

[adube]

r917, featuring :

• new 'geoextux_layertreebuilder" widget
• complete documentation
• new 'group' layer option ("layertreepath" not used yet. Should only be used by the PGSQLMapContextConfig driver)
• new 'map:addLayers' template in Map widget
• new 'addLayers' Map widget option
• a sample showing the use of the widget

Remaining things to do :

• i18n support inside 'group' option string
• remove mapfish from sample (#173 required)
• support in PGSQLMapContextConfig driver, (#172 required)

[yvesm]

You mention the GeoExt.ux.tree.LayerTreeBuilder does not yet support merged WMS layers. What kind of an impact is that going to have on performance for GeoPrisma and do you know when the LayerTree is to support layer bundling ?

[adube]

Performance : recent tests (outside GeoPrisma) proved that having many layers instead of one was fairly quick.

When : I don't know yet. I don't think I'll have some time remaining for this task, sorry.

[adube]

Here's an up-to-date list of the things remaining to do (replacing the one above):

• i18n support inside 'group' option string
• remove mapfish from sample (#173 required)
• support in PGSQLMapContextConfig driver, (#172 required)
• support layerParam nodes (WMS layers that were merged in a single OpenLayers.Layer object)
• don't add layers having the 'displayInLayerSwitcher' property set to false
• include the vector legend
• include an option to switch the legend off
• if the visibility of a layer is set to true, then the legend does not come up until you switch the layer visibility off then on again

[adube]

r919, among it features :

• support in PGSQLMapContextConfig driver

[adube]

r920, featuring :

• don't add layers having the 'displayInLayerSwitcher' property set to false

• widgets creating 'temp' layers to work with (for example 'marker' layer for the query widget, etc.) now have the 'displayInLayerSwitcher' option set to false in order to NOT add them to the layer tree.

[adube]

Here's the new features that were updated inside ​http://dev.geoext.org/sandbox/mapgears/geoext.ux/ux/LayerTreeBuilder/ :

• support vector legends
• turn the legends on and off options('wmsLegendNodes' and 'vectorLegendNodes'). Documented (r924)
• visible layers have their legend nodes correctly shown (fix)

Here's an up-to-date list of the things remaining to do (replacing the one above):

• i18n support inside 'group' option string
• remove mapfish from sample (#173 required)
• support in PGSQLMapContextConfig driver, (#172 required)
• support layerParam nodes (WMS layers that were merged in a single OpenLayers.Layer object)

[yvesm]

Thanx for your work Alexandre.

[adube]

That widget is completed and already used in production environments. From the remaining thing to do :

• i18n support inside 'group' option string : no one asked for this feature, so we'll simply forget it
• remove mapfish from sample : will be covered in an other ticket
• already supported by PGSQLMapContextConfig
• layerParam nodes : that's the only remaining feature required, so it was moved to #300.

Fixed.