I'm curious how the admin creates the templates for any object in the
database...
I'm using the object_detail generic view, but would prefer having
Django use the parameters of the object to generate the template,
rather than me having to hardcode the parameter names into the
template.
The admin does this when you create new objects - how? The docs don't
seem to lead me to this.
<< On the admin site’s edit forms, each field’s label is generated
from its model field name. The algorithm is simple: Django just
replaces underscores with spaces and capitalizes the first character,
so, for example, the Book model’s publication_date field has the label
“Publication date.” >>
Where in the django.contrib.admin code is this logic found? I would
like to utilize it.
On Jul 2, 4:02 pm, Technicalbard <rodwe...@gmail.com> wrote:
> I'm curious how the admin creates the templates for any object in the
> database...
> I'm using the object_detail generic view, but would prefer having
> Django use the parameters of the object to generate the template,
> rather than me having to hardcode the parameter names into the
> template.
> The admin does this when you create new objects - how? The docs don't
> seem to lead me to this.
On Fri, Jul 3, 2009 at 6:06 AM, TechnicalBard<rodwe...@gmail.com> wrote:
> To clarify, the djangobook states:
> << On the admin site’s edit forms, each field’s label is generated > from its model field name. The algorithm is simple: Django just > replaces underscores with spaces and capitalizes the first character, > so, for example, the Book model’s publication_date field has the label > “Publication date.” >>
> Where in the django.contrib.admin code is this logic found? I would > like to utilize it.
This is part of the forms library - django.forms.forms.pretty_name [1] is used [2] to generate a label from the field name if a label was not given when the field was instantiated.
> On Fri, Jul 3, 2009 at 6:06 AM, TechnicalBard<rodwe...@gmail.com> wrote:
> > To clarify, the djangobook states:
> > << On the admin site’s edit forms, each field’s label is generated
> > from its model field name. The algorithm is simple: Django just
> > replaces underscores with spaces and capitalizes the first character,
> > so, for example, the Book model’s publication_date field has the label
> > “Publication date.” >>
> > Where in the django.contrib.admin code is this logic found? I would
> > like to utilize it.
> This is part of the forms library - django.forms.forms.pretty_name [1]
> is used [2] to generate a label from the field name if a label was not
> given when the field was instantiated.
|
