[Users] Tree Layer question...

[Alexandre Dube]

Hi,

Andreas Hocevar wrote:
> Hey Paul,
>
> sorry for the delayed reply. The difference between the layer tree 
> approach in Mapfish and GeoExt is that the former uses a model on the 
> tree level for custom trees, and the latter lets you use the a plain Ext 
> configuration for the tree, because you have a choice of different node 
> types for representing layers.
>
> The layer tree that you see in 
> http://demo.mapfish.org/mapfishsample/1.1/examples/tree/tree_automatic.html 
> will be possible in GeoExt, with this configuration:
>
> var tree = new Ext.tree.TreePanel({
>     root: new GeoExt.tree.LayerContainer({
>         defaults: {
>             loader: new GeoExt.tree.LayerParamsLoader({
>                 param: "LAYERS"
>             })
>         }
>     }),
>     ...
> });
>
> This does not work yet, but as Eric said, there is work going on to make 
> it happen. We are currently switching to loaders, like 
> Ext.tree.TreeLoader, for populating LayerContainers (ticket #122). The 
> next steps will be:
>
> * Resurrect the LayerParamsNode (known from a previous patch for #22). 
> This can do more than just change the layers param on WMS layers. It can 
> also be used e.g. to use CQL_FILTER and any arbitrary params that 
> OpenLayers layers take in the params object.
>
> * Create a loader that looks up a params name (e.g. LAYERS) as argument 
> and will create one subnode for every param it finds. To make this even 
> smarter, the loader could process additional information from the 
> LayerStore, e.g. titles for the node texts.
>
>   

I'm really interested in this kind of enhancement. If you open a ticket 
for this, could you please announce it on the list ? I would 'cc' myself 
to the ticket to follow it development.

Many thanks,

Alexandre

> Please give feedback if this makes sense for your use case.
>
> Regards,
> Andreas.
>   
>
>   


-- 
Alexandre Dubé
Mapgears
www.mapgears.com