Re: DeleteView example with template

As the docs mention, yes, it does.
You provide a pk or slug via the url, identifying the object to be
deleted. You can add a form_class to specify the content of the
associated form, a model to tell django which model to use when
looking for the object to delete and a template_name to layout your
page.
In case of DeleteView your cont ext contains form.
DetailView contains object, unless you specify context_object_name.
UpdateView and CreateView also put form in the context.
You might want to take a look at godjango.com for some nice short
intro videos on generic class based views, and the source code.
Hth

On 26 apr, 22:41, Steve Kilbane <st...@whitecrow.demon.co.uk> wrote:
> Hi all,
>
> I've been banging my head against the docs, but I'm struggling with
> the generic views. I get the concept of the views, but I'm finding it
> difficult to work out what I should put in any given template. Am I
> right in thinking that a GET of a DeleteView should generate a form
> called "form"?
>
> I'd find it helpful if each generic view also had an associated
> generic template that rendered each of the view's context variables
> (with their default names).
>
> steve

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to django-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.