Good point Andrea, I wonder if it is worth making seperate pages for the different kinds of layer group? Some of these options only make sense when the layer group is named (and thus drawable) for example.
-- Jody Garnett On 27 October 2015 at 10:44, Andrea Aime <andrea.a...@geo-solutions.it> wrote: > On Tue, Oct 27, 2015 at 5:32 PM, Niels Charlier <ni...@scitus.be> wrote: > >> Hi, >> >> I want to propose some minor API changes for the catalog, will make a >> proper proposal but just wanted to check already if I can expect this to >> be an issue or not. >> >> 1. Move property [AttributionInfo attribution] from LayerInfo to >> PublishedInfo, so that Layergroups can have this as well. >> >> 2. Add [List<MetadataLinkInfo> metadataLinks] to LayerGroupInfo so that >> a LayerGroupInfo can have its own metadatalink (for layer, this is >> actually in ResourceInfo). >> > > No particular objections, but a couple of observations: > * What if the group is published as tree or named mode, are these going to > make > sense regardless? I guess so... but by spec they will be inhrerited by > all sub-layers. > I guess it will be up to the admin to decide if this makes sense or not > * The layer group UI is starting to become pretty crowded, breaking it up > in tabs > like the layer one would probably be good > > Cheers > Andrea > > -- > == > GeoServer Professional Services from the experts! Visit > http://goo.gl/it488V for more information. > == > > Ing. Andrea Aime > @geowolf > Technical Lead > > GeoSolutions S.A.S. > Via Poggio alle Viti 1187 > 55054 Massarosa (LU) > Italy > phone: +39 0584 962313 > fax: +39 0584 1660272 > mob: +39 339 8844549 > > http://www.geo-solutions.it > http://twitter.com/geosolutions_it > > *AVVERTENZE AI SENSI DEL D.Lgs. 196/2003* > > Le informazioni contenute in questo messaggio di posta elettronica e/o > nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il > loro utilizzo è consentito esclusivamente al destinatario del messaggio, > per le finalità indicate nel messaggio stesso. Qualora riceviate questo > messaggio senza esserne il destinatario, Vi preghiamo cortesemente di > darcene notizia via e-mail e di procedere alla distruzione del messaggio > stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, > divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od > utilizzarlo per finalità diverse, costituisce comportamento contrario ai > principi dettati dal D.Lgs. 196/2003. > > > > The information in this message and/or attachments, is intended solely for > the attention and use of the named addressee(s) and may be confidential or > proprietary in nature or covered by the provisions of privacy act > (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection > Code).Any use not in accord with its purpose, any disclosure, reproduction, > copying, distribution, or either dissemination, either whole or partial, is > strictly forbidden except previous formal approval of the named > addressee(s). If you are not the intended recipient, please contact > immediately the sender by telephone, fax or e-mail and delete the > information in this message that has been received in error. The sender > does not give any warranty or accept liability as the content, accuracy or > completeness of sent messages and accepts no responsibility for changes > made after they were sent or for other risks which arise as a result of > e-mail transmission, viruses, etc. > > ------------------------------------------------------- > > > ------------------------------------------------------------------------------ > > _______________________________________________ > Geoserver-devel mailing list > Geoserver-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/geoserver-devel > >
------------------------------------------------------------------------------
_______________________________________________ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
