#6630: Fieldsets for newforms
------------------------------------------------------------+---------------
          Reporter:  Petr Marhoun <petr.marh...@gmail.com>  |         Owner:  
nobody 
            Status:  new                                    |     Milestone:    
     
         Component:  Forms                                  |       Version:  
SVN    
        Resolution:                                         |      Keywords:  
feature
             Stage:  Design decision needed                 |     Has_patch:  1 
     
        Needs_docs:  1                                      |   Needs_tests:  0 
     
Needs_better_patch:  1                                      |  
------------------------------------------------------------+---------------
Comment (by Petr Marhoun <petr.marh...@gmail.com>):

 Added new series of patches. They are based on previous ones, description
 on wiki page, forms-utils and discussion in django-developers:
  * http://code.djangoproject.com/wiki/ImprovementsForDjangoForms#Fieldsets
  * http://bitbucket.org/carljm/django-form-
 utils/src/tip/form_utils/forms.py
  * http://groups.google.com/group/django-
 developers/browse_thread/thread/37e1e8b8313c38de

 Description of individual patches follows:

 Patch 01-move-fields-and-exclude.diff: This patch moves meta attributes
 "fields" and "exclude" from !ModelForm to Form. It is the most complex
 patch.

 There are some changes which could be bug fixes or backward
 incompatibilities:
  * Attributes "fields" and "exclude" apply also for fields defined on
 !ModelForm. It solves (accepted) ticket #8620.
  * With multiply inheritance fields are sorted by method resolution order,
 not by a custom way. I think it is the right approach (and it simplifies
 code) but I am prepared to change it back.

 I also do not know if some classes and methods are part of public API. I
 reworked django.forms.forms.get_declared_fields and renamed
 django.forms.forms.!DeclarativeFieldsMetaclass to !FormMetaclass (it makes
 more things after the change). I also stop using parameters "fields" and
 "exclude" of django.forms.models.fields_for_model but this method is
 exported from this module so I do not change it.

-- 
Ticket URL: <http://code.djangoproject.com/ticket/6630#comment:9>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Reply via email to