That's a very good idea, though I still think a short version (which
is all I've written) belongs in the docs. Here's the relevant part:
Index: django/docs/newforms.txt
===
--- django/docs/newforms.txt(revision 6979)
+++ django/d
On Dec 28, 2007 3:04 PM, Todd O'Bryan <[EMAIL PROTECTED]> wrote:
>
> I have a use case where a Form superclass includes fields at the top
> and bottom of the form, with the subclasses providing the fields in
> the middle. Obviously, there's no easy way to fix the ordering using
> simple declaratio
I have a use case where a Form superclass includes fields at the top
and bottom of the form, with the subclasses providing the fields in
the middle. Obviously, there's no easy way to fix the ordering using
simple declaration. I went on IRC and someone told me about overriding
self.fields.keyOrder
