49 | | * IMHO it is important to consider the different views which different users may want. If a user is a staff member for a Office/Warehouse/Hospital, then then might want to go directly to a dashboard for that Office/Warehouse/Hospital, instead of seeing summary information for all Office/Warehouse/HospitalS. |
50 | | * Do we need the pull-down level? Isn't this already a menu depth of 2? Wouldn't it be better to have all of the other "methods" (New, Search) accessible from the main list page for a resource, possibly revealed(or even loaded) using JS? |
51 | | * I think it is important to think about how the menus support the users to carry out their tasks, fitting Sahana to the work-flow of the user, rather than visa versa. |
| 49 | * IMHO it is important to consider the different views which different users may want. If a user is a staff member for a Office/Warehouse/Hospital, then might want to go directly to a dashboard for that Office/Warehouse/Hospital, instead of seeing summary information for all Office/Warehouse/Hospitals. |
| 50 | * Do we need the pull-down level? Isn't this already a menu depth of 2? Wouldn't it be better to have all of the other "methods" (New, Search) accessible from the main list page for a resource, possibly revealed (or even loaded) using JS? |
| 51 | * I think it is important to think about how the menus support the users to carry out their tasks, fitting Sahana to the work-flow of the user, rather than vice versa. |