Since it seems like most every developer is refusing to add new capabilities to the web admin tool (which I do understand), could we at least file JIRA bugs for all the config options that are blocking on a new UI? Most of them are pretty minor, and I feel like they're easy to commit. Maybe make a 'UI' release in jira that we can file them against?
Brent Owens wrote:
The WMS path option is just for the get capabilities request; it will format your layers in a tree hierarchy based on the wms path. It won't actually effect what layers are rendered in a map. I will add this to the FAQ.
The layer grouping, at least through the web UI, only allows for one group. But the rest of the code allows for as many groups as you want. We just haven't changed the UI to allow for many groups, not until we change what technology we use.
Brent Owens
(The Open Planning Project)
Ross Elliott wrote:
You understand exactly what I want it to do. I did look at both of these
options before but they don't quite deliver what a WMS client or user
would expect, whilst a user would like a nested layer tree returned they
would also expect (as would the WMS client) to be able to select a
parent layer and display all the child layers and Geoserver doesn't
quite do this yet from what I can see (especially as under 1.4 the WMS
path stuff seems to be broken) and from what I understand the layer
grouping looks like you can only have one layer group. It's not a big
deal and I'm sure things will change over time.
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
!DSPAM:1003,45c0c954196651365099012!
--
Chris Holmes
The Open Planning Project
http://topp.openplans.org
Yep we need to get that started so we can keep track.
Here is the task: http://jira.codehaus.org/browse/GEOS-881
Brent Owens
(The Open Planning Project)
Chris Holmes wrote:
Since it seems like most every developer is refusing to add new capabilities to the web admin tool (which I do understand), could we at least file JIRA bugs for all the config options that are blocking on a new UI? Most of them are pretty minor, and I feel like they're easy to commit. Maybe make a 'UI' release in jira that we can file them against?
Brent Owens wrote:
The WMS path option is just for the get capabilities request; it will format your layers in a tree hierarchy based on the wms path. It won't actually effect what layers are rendered in a map. I will add this to the FAQ.
The layer grouping, at least through the web UI, only allows for one group. But the rest of the code allows for as many groups as you want. We just haven't changed the UI to allow for many groups, not until we change what technology we use.
Brent Owens
(The Open Planning Project)
Ross Elliott wrote:
You understand exactly what I want it to do. I did look at both of these
options before but they don't quite deliver what a WMS client or user
would expect, whilst a user would like a nested layer tree returned they
would also expect (as would the WMS client) to be able to select a
parent layer and display all the child layers and Geoserver doesn't
quite do this yet from what I can see (especially as under 1.4 the WMS
path stuff seems to be broken) and from what I understand the layer
grouping looks like you can only have one layer group. It's not a big
deal and I'm sure things will change over time.
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
!DSPAM:1003,45c0c954196651365099012!