| Version 54 (modified by , 14 years ago) ( diff ) |
|---|
BluePrint for CSS
We have moved to a full page design to allow maximal screen real estate to be available for list views & data entry. Ours is based on:
- http://matthewjamestaylor.com/blog/perfect-full-page.htm
- This was inspired by the work done on Sahana PHP: http://demo.respere.com/dnn/
- Link on doing something similar with the default web2py menu: http://groups.google.com/group/web2py/browse_thread/thread/ecffcd0427af0fec
The logo font is Brush Script.
Q: Should we migrate to BlueTrip?
A: Probably not as their value isn't proven.
The CSS could still do with some cleaning up to remove unused styles.
CSS can be previewed in different browsers, however no interaction is possible:
Original Sahana CSS documented here: DeveloperGuidelinesCSS
Maximal usability ideas:
Theme Manager
- The selection & application of a theme should be moved to the same (or related) area as the Theme Editor, rather than hiding it within the main Settings area.
- 'Apply Theme' should be an explicit option.
Menus
The current 3 menu system should be migrated to a single menu to take upo less screen real estate & provide a consistent UI experience.
Ideally this would be loaded once & then cached (e.g. have the system generate a static menu.js which can then be loaded/cached)
We should always know where in the system we are.
- e.g. Chevron-style breadcrumbs (e.g. http://www.guardian.co.uk/world/usa)
- e.g. Highlight the active menu item using CSS (JS to set this would be in the main body template, rather than in menu.js)
- Web2Py implementation of breadcrumbs: http://www.web2pyslices.com/main/slices/take_slice/47
Icons in Menus?
ExtJS menus are flexible & can allow DRY creation of navigation elements (buttons/menus):
- http://www.extjs.com/deploy/dev/examples/menu/menus.html
- http://www.extjs.com/deploy/dev/examples/menu/actions.html
Alternative layouts
We should include alternate layouts which different views can inherit from (common areas included into these to be DRY):
- Site home & Module homes act as portals, which require a more complex layout, such as:
Q: How to {{include}} content into multiple areas? (How is it done with the JPolite app?)
Can use LOAD to import a component into an area of a webpage. Updates to this component happen independently to the rest of the page:
Right-to-Left theme
We already have a simple:
body {
direction: rtl;
}
This is currently set using the Theme.
We could look at setting this based on a lookup of the current locale.
Print View
Provide a view which allows for better Printing
- CSS sufficient? (
media=print)
Browsers don't print pages in identical ways...if this is key, need to use PDF.
Like for format=ocr.
Mobile View
Provide a cut-down version for use on low-screensize, low-bandwidth devices, such as Mobiles
- CSS sufficient?
- http://mobiforge.com/Designing
- http://www.slideshare.net/nickf/mobile-ux (eye opening examples on mobile usability)
Mobile Emulators:
- http://mobiforge.com/emulators/page/mobile-emulators
- http://www.opera.com/mobile/demo/ (No JavaScript)
- Nokia screen sizes: http://forum.mobiles24.com/showthread.php?t=9980
- Remember that some screen lost for nav tools & that usually used in portrait mode
Could consider using the RESTlike CRUD controller's ?format=plain
Current Issues
- Main page content displays well as text reflows due to nice
- except for Haiti era redesign (such as gis/index) which uses fixed widths hard-coded into the HTML (not CSS)
- Top-menu works fine, but fixed-width means a lot of scrolling
- GIS Catalogue Toolbar also needs scrolling - ugly, but usable
- dataTables work but need some scrolling (not sure this is possible to work around & seems OK)
