Adrian Holovaty wrote:
Note that this behavior is up for discussion if many people find it inconvenient. My initial thought is that it's a bit unbalanced to allow for the definition of extra fields in a subclass but not allowing the *removal* of fields in the same way.
Building forms is is more an issue of composition than inheritance, so you're probably correct not to provide direct support for extending the fields in a derived class. Along the lines of composition, however, it would be good to have an interface (or just guidelines) to dynamically build forms, establishing field order, etc. -- Jeff Bauer Rubicon, Inc. --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
