On 12/11/06, Adrian Holovaty <[EMAIL PROTECTED]> wrote: > This is an interesting idea, but I think it's important to remember > the as_p(), as_table() and as_ul() shortcut methods are just > *shortcuts*. There's nothing stopping a developer from writing a > custom method on a Form, nor is there anything stopping a developer > from building the form "by hand" by piecing together the individual > fields. > > as_p(), as_table() and as_ul() are just shortcuts for the common > (lazy) case when the developer doesn't want to spend time customizing > a form's display in the template. In my opinion, it would be > overengineering to create a separate framework (e.g., the proposed > FormFormatters) to provide for generic ways of being lazy. Put another > way, if we had a FormFormatter framework, that would encourage people > to use these "generic" form formats rather than giving tender loving > care to the design of each form, which is what I'd rather encourage. >
I agree with Adrian on this one. There are few common cases that Django should handle... the flexibility is already there to allow non-standard uses. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@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-developers?hl=en -~----------~----~----~----~------~----~------~--~---
