Hi Kye,
Sorry for mispelling your name above, but it's a really long thread and
non-native. And I can tell, there's rarely a better way than discussing in
foreign languages to make a nice little fool of myself xD This time I will
share my story with CBV, a story with love, and code and aggressive
Kyle, is it possible to show the code you are talking about ?
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-devel
Hello,
I'm not a Django contributor, just a user, but please allow me to express my
opinion that CBVs are an extra layer of functionality that seems to have made
it into the foreground attention since it was introduced, but I think that that
is very unfortunate:
CBVs bring not only extra funct
Hi Kyle,
My take would be this: What does the code look like if you don't
use FormView but just write a function view? How does that compare
to using a CBV? This may be the simpler method you are missing -
if you are finding you are fighting with inherited functiona
>
> I find it hard to justify adding it to a project just to deal with this.
Why is it hard to justify adding it? django-filter is in the class of very
stable django third party packages, and it's even maintained by Django
fellow Carlton Gibson.
* Is my understanding of the current process corr
Hi,
Sometimes it is appropriate to for a HTML form to use the GET method for
submission (usually search / filter forms).
My impression has always been that in order to build a FormView-based view
that acts on GET data, you have to override a few methods on your class
(which involves understanding
