I agree that Francesco's suggestion looks to be much more supportable for the kinds of large layer sets we're targeting in the new interface.
Specific feedback on the screenshot he's posted:
* There are two columns ('Public' and 'Access') which may be redundant
* The column immediately to the right of the 'Public' column is unlabeled, and it's unclear what that references
* Are the workspace / datastore / access / rule filter dropdowns modifiers for whatever users enter in the "filter" text field, or predetermined collections of filters against those critera?
+1 on this direction from me
Chris
On Jan 16, 2009, at 6:18 AM, Francesco Izzi wrote:
Hi all,
speaking with Andrea about geoserver 2.0 resources ui and per layers security ui, we realized that wicket treetable ui in not suitable for large numbers of layers (1000+)
This is a proposal for a new interface, with filters, paging ...
http://imagebin.ca/view/w8o3Se.html
it is important to take a decision on this
--
Francesco Izzi
CNR - IMAA
geoSDI - NSDI
Responsabile Sviluppo Software
C.da Loja
85050 Tito Scalo - POTENZA (PZ)
Italia
phone: +39 0971427305
fax: +39 0971 427271
mob: +39 3402640314
mail: francesco.izzi@anonymised.com
skype: neofx8080
web: http://geosdi.nsdi.it
------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel