Django

Code

Changeset 283

Show
Ignore:
Timestamp:
07/21/05 14:05:10 (3 years ago)
Author:
jacob
Message:

Rolled a number of comments into documentation; thanks to all those who contributed.

Files:

Legend:

Unmodified
Added
Removed
Modified
Copied
Moved

  • django/trunk/docs/cache.txt

    r226 r283  
    2121like to use. Do this by setting the ``CACHE_BACKEND`` in your settings file. 
    2222 
    23 The CACHE_BACKEND setting is a quasi-URI. Examples:: 
     23The CACHE_BACKEND setting is a "fake" URI (really an unregistered scheme).  
     24Examples: 
    2425 
    2526    ==============================  =========================================== 

  • django/trunk/docs/model-api.txt

    r265 r283  
    279279 
    280280``FloatField`` 
    281     A floating-point number. Has two required arguments: 
     281    A floating-point number. Has two **required** arguments: 
    282282 
    283283        ======================  =================================================== 

  • django/trunk/docs/templates.txt

    r145 r283  
    4141    {% endfor %} 
    4242    {% endblock %} 
     43     
     44.. admonition:: Philosophy 
     45 
     46    Why use a text-based template instead of an XML-based one (like Zope's  
     47    TAL)?  We wanted Django's template language to be usable for more than 
     48    just XML/HTML templates -- at the Journal-World we use it for emails,  
     49    Javascript, CSV -- you can use the template language for any text-based 
     50    format. 
    4351 
    4452What's a variable? 
    …… 
    199207    * We often prefer to use three-level inheritance: a single base template 
    200208      for the entire site, a set of mid-level templates for each section of 
    201       the site, and then the individual templates for each page.  This 
     209      the site, and then the individual templates for each view.  This 
    202210      maximizes code reuse, and makes it easier to add items to shared 
    203211      content areas (like section-wide navigation).