The fields option on the inner Meta class does not appear to function that way in 1.0.2; I presume it is a 1.1 forward feature. (doh, yeah it says development version only in those docs you pointed to)
Here is how I've implemented field ordering for 1.0.2<http://dpaste.org/tzef/>, and it seems pretty good for my purposes while still remaining flexible for any future use I might have for the functionality. In fact, I consider it nearly superior to the Meta.fields solution, as it allows me to theoretically define whatever mixin classes I want, and to allow those individual mixins to modify (or not) the order that their fields are displayed in by default. With a bit more tweaking, this could be extended even further to allow greater control within the ModelForm definition as well. Maybe this will evolve into a feature suggestion after all :) On Tue, May 12, 2009 at 1:17 PM, George Song <geo...@damacy.net> wrote: > > On 5/12/2009 12:12 PM, Alex Gaynor wrote: > > You can control the order of fields on a modelform by settings the > > ordering in the fields option in the inner Meta class. That is if you > > set fields = ['b', 'a', 'c'] that's the same order they will apear in. > > Duh. There you go, problem solved: > < > http://docs.djangoproject.com/en/dev/topics/forms/modelforms/#changing-the-order-of-fields > > > > The changes are fast and furious, hard to keep up with everything. > > -- > George > > > > -- Visit me @ http://killarny.org Sent from Provo, UT, United States --~--~---------~--~----~------------~-------~--~----~ 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+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
