Changeset 1218
- Timestamp:
- 11/13/05 16:59:51 (3 years ago)
- Files:
-
- django/trunk/docs/design_philosophies.txt (modified) (3 diffs)
Legend:
- Unmodified
- Added
- Removed
- Modified
- Copied
- Moved
django/trunk/docs/design_philosophies.txt
r891 r1218 176 176 code. 177 177 178 This is the philosophy behind template inheritance. 178 This is the philosophy behind `template inheritance`_. 179 180 .. _template inheritance: http://www.djangoproject.com/documentation/templates/#template-inheritance 179 181 180 182 Be decoupled from HTML … … 198 200 The template system shouldn't do magic things with whitespace. If a template 199 201 includes whitespace, the system should treat the whitespace as it treats text 200 -- just display it. 202 -- just display it. Any whitespace that's not in a template tag should be 203 displayed. 201 204 202 205 Don't invent a programming language … … 211 214 enough programming-esque functionality, such as branching and looping, that is 212 215 essential for making presentation-related decisions. 216 217 The Django template system recognizes that templates are most often written by 218 *designers*, not *programmers*, and therefore should not assume Python 219 knowledge. 220 221 Safety and security 222 ------------------- 223 224 The template system, out of the box, should forbid the inclusion of malicious 225 code -- such as commands that delete database records. 226 227 This is another reason the template system doesn't allow arbitrary Python code. 213 228 214 229 Extensibility
