Hi Andrea, Andrea Aime wrote: > Hi, > I'm trying to setup a new preview page and I'm getting > some nastiness trying to stick the two things, layers > and layers groups, in the same table. > > Generally speaking it would be nice if Layer and LayerInfo > shared some superclass. I would prefer to favor composition over inheritance at least it _is_ a layer info and not just a group of layer infos? not the best timing for me to look deeper into it though, sorry
> Failing that, it would be still nice if LayerGroupInfo > had at least: > - a workspace that contains it sure > - a isEnabled that just states whether all the layers in > the group are enabled or not (e.g., will the layer > group display or not^?) > What about LayerGroupInfo.isEnabled() == true as long as at least one of its aggregated layerinfos is enabled? will this way allow for a layerGroupInfo to still be visualized while hiding the non enabled layers? > Opinions? In the meantime I'm working around the above > limitations by creating a wrapping class only for the > map preview purposes I think that's cool if you have to deviate a little bit from the model for presentation purposes. Cheers, Gabriel > > Cheers > Andrea > ------------------------------------------------------------------------------ _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
