Code

Changes between Version 31 and Version 32 of NewformsAdminBranch


Ignore:
Timestamp:
09/17/07 06:45:56 (7 years ago)
Author:
robillard.etienne@…
Comment:

Let's make this clear and bold (litterally!) :->

Legend:

Unmodified
Added
Removed
Modified
  • NewformsAdminBranch

    v31 v32  
    109109 
    110110In this example, the admin options still live in the {{{models.py}}} file. But there's nothing that requires them to do so. The only requirement is that the {{{register()}}} calls are executed at some point, and putting them in the {{{models.py}}} is an easy way to ensure that. We'll likely come up with a nice convention for this.[[BR]] 
    111 A proposal convention: Specifying all admin options in a file called {{{admin.py}}}, and import it in the {{{__init.py}}} file of your application module to do the registering during the initialization. 
     111 
     112'''A proposal convention''': Specifying all admin options in a file called {{{admin.py}}}, and import it in the {{{__init__.py}}} file of your application module to do the registering during the initialization. 
    112113 
    113114You'll notice the {{{BookOptions}}} class looks a lot like the old-style {{{class Admin}}}. Almost all of the old {{{class Admin}}} options work exactly the same, with one or two exceptions. (For the options that have changed, we've made them '''much''' more powerful.) In addition to the classic options such as {{{list_display}}} and {{{ordering}}}, the {{{ModelAdmin}}} class introduces a wealth of extra hooks you can use to customize the admin site for that particular model. For example: