Version 40 (modified by 15 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.
Main outstanding task on this is to have the Modules menu show which module we're currently in.
- The Auth menu already does this.
The Modules menu could be moved to a single dropdown - located below the Login box.
The Auth menu should be migrated to using the same style as the Modules/Options menus?
The CSS could still do with some cleaning up to remove unused styles.
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?)
Maximal usability ideas:
Replace the current menus with Breadcrumb-style Chevrons, e.g.:
Enhance these with dropdown menus, like in T3:
Relevant Bugs:
CSS can be previewed in different browsers, however no interaction is possible:
Original Sahana CSS documented here: DeveloperGuidelinesCSS
Right-to-Left theme
Ideally this should be as simple as:
body { direction: rtl; }
This could be dynamically loaded into the view layout based on a lookup of the current locale.
Print View
Provide a view which allows for better Printing
- CSS sufficient? (
media=print
)
Mobile View
Provide a cut-down version for use on low-screensize, low-bandwidth devices, such as Mobiles
- CSS sufficient?
- http://mobiforge.com/Designing
Use the RESTlike CRUD controller's ?format=plain