Changes between Version 3 and Version 4 of BluePrint/Menu
- Timestamp:
- 04/27/10 07:06:18 (15 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
BluePrint/Menu
v3 v4 1 1 Beginning to capture some ideas from improving the menu: 2 * Code for the menus should be segregated between the technical implementation and the layout - making it easy for non-technical users to customize the menu .2 * Code for the menus should be segregated between the technical implementation and the layout - making it easy for non-technical users to customize the menu and reducing the clutter in the code. 3 3 * Define the customization of the menu in CSV? 4 4 * Make Menu customization completely independent from the modules. 5 * How many levels? Configurable. 5 * How many levels? Configurable. Suggestion. 6 * Application - a deployments of Sahana may contain different applications, which may be used by different people and certainly at different times/workflows. This could be separate from the main menu - at the very top. 7 * Functional - what does someone want to do in the current application. 8 * Functional level 2 / Work Stage - this could represent work flow, or just reduce the clutter in one level of functional 9 * Avoid 3rd level - especially pop-ups! 6 10 * Breadcrumbs 7 11 * Allow modules to be turned on/off and also excluded from releases of code with simple switches. 12 * Allow the menu to indicate which option has been clicked (flag to set a class in the li - where set flag?). 8 13 9 14 Allow the user to define a custom home page, without editing core code.