I like it. Have you thought of a name for the common super class? I have
thought about this before but always came up short. LayerableInfo? WWWInfo,
etc...  Could never find anything that fit.

But with that in mind it might be a cleaner chance to rename
LayerGroupInfo.getLayers() to something else like
LayerGroupInfo.getLayerables(), and possibly just deprecate
LayerGroupInfo.getLayers(), and have it implemented as a derived property
that either strips out the layer groups, or throws an exception when layer
groups are present.


On Thu, Jan 3, 2013 at 12:53 AM, Davide <[email protected]> wrote:

> Hi,
>
> I'd like to propose a change to layer groups: I'd like to add nested
> layer groups support, allowing a layer group to be a child of another
> layer group.
>
> A layer group could contain layers and layer groups in the same children
> list.
> To have an homogeneous list we could extract a common interface from
> LayerInfo and LayerGroupInfo:
> they both extend the CatalogInfo interface, but they share other
> properties so we could create a new super interface.
>
> These are the properties that LayerInfo and LayerGroupInfo share and
> that can be included in the new super interface:
> - name
> - prefixedName
> - workspace
> - title
> - abstract
> - metadata
> - authorityURLs
> - identifiers
>
> LayerGroupInfo method getLayers() will return a list of layers and layer
> groups.
> Method getStyles() will contain null entries for layer groups.
>
> The work will be based on changes already made for GSIP 84 where
> LayerGroupInfo has
> two new methods renderingLayers() and renderingStyles().
> These methods are used by the WMS service to retrieve layers and styles.
>
> renderingLayers() will continue to return a list of LayerInfo, so the
> LayerGroup will expand
> nested LayerGroups to expose only a list of Layers.
>
> renderingStyles() will continue to return a list of StyleInfo with a
> 1-1 correspondence to renderingLayers(),
> so the LayerGroup will expand nested LayerGroups styles.
>
> Nested layer groups could replace usage of layers WMS Path property.
>
> Opinions? :)
>
> --
> ==
> Our support, Your Success! Visit http://opensdi.geo-solutions.it for
> more information.
> ==
>
> Davide Savazzi
> @svzdvd
> Senior Software Engineer
>
> GeoSolutions S.A.S.
> Via Poggio alle Viti 1187
> 55054  Massarosa (LU)
> Italy
> phone: +39 0584 962313
> fax:      +39 0584 1660272
>
> http://www.geo-solutions.it
> http://twitter.com/geosolutions_it
>
>
> ------------------------------------------------------------------------------
> Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
> MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
> with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
> MVPs and experts. ON SALE this month only -- learn more at:
> http://p.sf.net/sfu/learnmore_122712
> _______________________________________________
> Geoserver-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>



-- 
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
------------------------------------------------------------------------------
Master HTML5, CSS3, ASP.NET, MVC, AJAX, Knockout.js, Web API and
much more. Get web development skills now with LearnDevNow -
350+ hours of step-by-step video tutorials by Microsoft MVPs and experts.
SALE $99.99 this month only -- learn more at:
http://p.sf.net/sfu/learnmore_122812
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Reply via email to