devel:blueprints:django_template
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
devel:blueprints:django_template [2010/01/13 10:50] eide template variables |
devel:blueprints:django_template [2010/01/13 12:16] (current) eide a little 'bout the base template |
||
|---|---|---|---|
| Line 5: | Line 5: | ||
| ===== Django systems ===== | ===== Django systems ===== | ||
| - | Something smart here | + | In the lib-python directory there's a base template, simply called base.html. Subsystems should extend this one (probably with their own base.html) and the base_content block in it. |
| + | |||
| + | base.html provides the header and footer for pages, so subsystems need only contribute the content. | ||
| ==== Context processors ==== | ==== Context processors ==== | ||
| Line 11: | Line 13: | ||
| Some features of the templates, such as debug, version number and account/user info and preferences requires 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. | + | Context processors are not passed to templates by default with render_to_response(), a RequestContext object must be passed to render_to_response to get them. |
| - | === Debug === | + | Without the account_processor all user specific content in templates will not work. |
| - | Provides a SQL debug table at the bottom of every Django page if the DEBUG setting is set to true. | + | <code> |
| + | render_to_response( | ||
| + | 'path/to/template', | ||
| + | {'some_context': var}, | ||
| + | RequestContext(request) | ||
| + | ) | ||
| + | </code> | ||
| - | === Account_processor === | + | ^ NAV context processors ^^ |
| - | + | | debug | Provides a SQL debug table at the bottom of every Django page if the DEBUG setting is set to true. | | |
| - | 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). | + | | account_processor | Provides account object for current user, a flag telling if he/she is and admin, messages for the user and custom navigation bar. | |
| - | + | | nav_version | The version number from nav.web.buildconf | | |
| - | === nav_version === | + | | toolbar | All available tools from the toolbox (not enabled by default) | |
| - | + | ||
| - | Returns the version number from nav.web.buildconf | + | |
| ==== Template blocks and variables ==== | ==== Template blocks and variables ==== | ||
| Line 54: | Line 60: | ||
| Compability with Django templates are done seamless. The MainTemplate includes nav.webfront.compability.Cheetah which provides two methods called footer and header. These two methods are simply printed, and thus the header and footer appears. | Compability with Django templates are done seamless. The MainTemplate includes nav.webfront.compability.Cheetah which provides two methods called footer and header. These two methods are simply printed, and thus the header and footer appears. | ||
| + | |||
| + | MainTemplate will automatically populate the needed instance variables for the Cheetah compability class. | ||
| ==== Additional <head> content ==== | ==== Additional <head> content ==== | ||
devel/blueprints/django_template.1263379829.txt.gz · Last modified: 2010/01/13 10:50 by eide
Page Tools
