Hey everybody-

My name's Chris Patterson, and I've been working recently on the  
GeoServer 2 interface.

Thought it might be good to check in and send along my $.02 on where  
we stand regarding UI stuff right now:

==Sidebar
* needs reorganization
* needs a listing (with at-a-glance status bars) for all the currently  
active services
* there was some conversation in IRC about bringing the [Persist]  
[Revert] buttons back into the sidebar, so they'd be always accessible  
(rather than on the server admin screen, where they are now).

==Data Manager
* Needs a lot of attention. Individual pages need to be converted to  
use the same markup conventions as the rest of the UI, and may need to  
be reordered / reorganized to be easier to use.
* We're using a tree view on the main data manager page (and have a  
fair amount of work invested in it). I'm not convinced this is the  
best approach for displaying this data, as I don't think we'll ever be  
nested more than two layers deep. This may be a moot point, given the  
amount of time invested in the tree view and our time constraints -  
but I'd love to get a better solution if we end up with time to do it.

==Demo pages
* Needs some attention to avoid the link-overload effect of listing  
every single format for every item.

==Avoiding overwrite collisions
* David and I have chatted about various ways to help users avoid  
overwriting each other's changes. The last time we'd talked, the  
options (in descending order of preference) were:
** Since wicket keeps track of what page each user is on, display  
messaging to the effect of "Hey! So-and-so is already on this page"  
when accessing a page that's already in use.
** Store the configuration time with the session data, and display  
messaging if the configuration is updated by another user
** Display the relevant configuration update time on pages which need it

==Errata
* Pagination will probably be needed on all pages which may display  
sufficiently-long result sets
* All result sets should be sorted by a sensible column. Time pending,  
adding client-side sorting by other columns might be nice (although it  
could be confusing in conjunction with pagination [users could think  
that they were looking at a different set of results])
* Adding animation and more AJAX-y effects as appropriate are all time- 
permitting at this point

Chris

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Reply via email to