I didn't mean to imply a feature suggestion, I meant to ask if this is possible already. If not, then is there some way to manipulate the form __init__ (through _meta.fields perhaps?) to accomplish an approximation of what I want?
I'm just looking for a best-practice solution here - am I out of luck on this, or can I get some ideas on how better to handle things? On Tue, May 12, 2009 at 12:26 PM, George Song <geo...@damacy.net> wrote: > > On 5/12/2009 11:22 AM, Luke Graybill wrote: > > Is there a good way to dynamically reorder these fields on the fly? > > Preferably, the code should be contained within the Mixin class. In > > my situation, the mixin fields would be better if placed after all > > the other fields on a model, but in other situations a mixin might > > want a different order. > > Do you have a proposed solution on how to achieve what you want? How > would you express the different "situations" within the mixin? > > -- > 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 -~----------~----~----~----~------~----~------~--~---
