This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | Next revision Both sides next revision | ||
devel:blueprints:django_template [2010/01/13 10:06] eide code tags |
devel:blueprints:django_template [2010/01/13 10:34] eide django and context processors |
||
---|---|---|---|
Line 2: | Line 2: | ||
In the future NAV should mainly use Django templates, falling back to cheetah on old subsystems. | In the future NAV should mainly use Django templates, falling back to cheetah on old subsystems. | ||
+ | |||
+ | ===== Django systems ===== | ||
+ | |||
+ | Something smart here | ||
+ | |||
+ | ==== Context processors ==== | ||
+ | |||
+ | Some features of the templates, such as debug, version number and account/user info and preferences requires context processors. | ||
+ | |||
+ | Currently these context processors are: debug, account and nav_version. | ||
+ | |||
+ | === Debug === | ||
+ | |||
+ | Provides a SQL debug table at the bottom of every Django page if the DEBUG setting is set to true. | ||
+ | |||
+ | === Account_processor === | ||
+ | |||
+ | Provides the account object for the current user, a flag telling if he/she is an admin, messages for the user and the custom links found in the navbar (includes quick links). | ||
+ | |||
+ | === nav_version === | ||
+ | |||
+ | Returns the version number from nav.web.buildconf | ||
===== Backwards compability ===== | ===== Backwards compability ===== |