#9958: Split contrib.comments CommentForm class to allow easier customization
-------------------------------------+--------------------------------------
 Reporter:  arne                     |       Owner:  nobody    
   Status:  new                      |   Milestone:            
Component:  django.contrib.comments  |     Version:  SVN       
 Keywords:  comments, customization  |       Stage:  Unreviewed
Has_patch:  0                        |  
-------------------------------------+--------------------------------------
 The !CommentForm class in contrib/comments/forms.py is very monolithic and
 contains all spam-checking code and the application-specific code.
 Splitting the Form into a !BaseCommentForm class which contains only the
 spam-checking code and a !CommentForm class which only contains the
 application-specific code would allow much easier customization of the
 comments-app.

 Using the hooks from #8630 and defining your own model and form (which for
 example don't include fields for email and url) would either need a copy
 of the whole form-class code including the modification (about 100 lines
 of code) or one must subclass the current !CommentForm class and manually
 delete the fields (email and url in this example) before using the form.

 The appended patch splits the current !CommentForm class into two classes
 which would allow easier customization of the comments-app. When reviewing
 this ticket please also see #8630 for more details.

-- 
Ticket URL: <http://code.djangoproject.com/ticket/9958>
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 [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to