Hi, talking with David yersterday and thinking about it a little more today I came up with an idea of how to reorganise the main menu or the web2 module.
Drivers: - parts of the menu should be simply hidden if the user does not have the rights to use them. Secured components should be created in the spring context with a admin flag that allows us to limit the display. Rationale: we need to secure the pages, but moving the login boxes up in the header it does not make sense anymore to have a click thru login dialog - the menu should be extensible, so it would be better if it was completely driven by a plugin mechanism (as opposed of today's mix of plugin and hard coded) - the "content" elements of the configuration should be lumped togheter, and they may grow - we should think about items that we don't have in today's configuration and see where they could fit The menu I would like to see would look like: ------------------------------------------- Server -Information -Settings -(User and roles) -(Demos) Services -WCS -WFS -WMS Contents - data - namespaces - styles - (srs list) - (processes) Demo [Persist] [Revert] ------------------------------------------ Where Server,Services,Contents are categories, Demo is a stand alone line, [Persist][Revert] are buttons used to store the current configuration or reload it from storage. If you're wondering, server/demos is about configuring which demos are available for the user to see, whilst server/information would be a list of env information such as the ones we have in the admin page today. Configuration wise, I believe we should have the following classes: - Category(name,priority) which are the categories used in the menu, priority being a integer (std category should use 100,200,... to make sure there's room for custom extensions - MenuPageInfo(name,category,priority,...) that points to menu pages, eventually included in categories. If category is not specified, the link is top level (like demos). As a rule of thumb, a stand alone link is used when a category is believed to be likely and grow very much, thus filling the vertical screen estate too much (demos, or tools). What do you think? Cheers Andrea ------------------------------------------------------------------------- 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
