Guidelines

• Reduce number of screens required for actions
• Reduce number of clicks (e.g. feedback should be in a div which appears instead of a popup that requires an OK).  Note: the div should have a close button not auto-close
• Have the UI be usable by keyboard without requiring the mouse
• Do not keep stuff in session, just cache globally, and use request.  The only things in session would be things that can be cached for the user but figured out if needed.  e.g. authentication information.  The app should be able to be used in a load balanced environment with session clustering.  No unserializable stuff in session

Security

• All methods should be POST, though if GET is required, have a whitelist
• Prevent CSRF by having a key (SESSIONID?) which is transmitted with each request in a form variable (will this work for dhtmlx GET requests?).  Have a switch that turns this off

Ideas

• Overall search screen should allow search for all grouper objects
• Comboboxes should have filters (e.g. for which source)
• Have recently used objects available
• Have a screen with each type of UI widget it in it for browser testing
• Hide dangerous operations (e.g. delete object) behind menus so they are less likely to be accidentally pressed

Help framework

• Investigate using this: http://embedded-help.net/
• Perhaps could use some youtube movies too...

Community suggestions

I'm not sure how many Grouper installers also use JA-SIG CAS, but we do, and I know that it would be helpful for us if the new Grouper UI used the same technologies as that of CAS, namely Spring MVC and Spring Web-Flow.  This would decrease the skill-sets necessary to customize and maintain an identity solution that includes both CAS and Grouper.

It would also be very convenient if the HTML structure was designed so it could be themed using CSS (along the lines of csszengarden) and if the JSP pages used customizable header and footer “includes” built in from the start.