On Apr 27, 9:17 am, Ejah wrote:
> 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.
As it happens, the godjango videos didn't cover the templates, but
they did provide some clues - enough to get me going. So I'm
I'll take a look - many thanks, Ejah.
steve
On Apr 27, 9:17 am, Ejah wrote:
> 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.
--
You received this message because you are subscribed to the Google Groups
"Djan
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
p
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"?
4 matches
Mail list logo
