On Sat, Sep 6, 2008 at 6:08 AM, Yuri Baburov <[EMAIL PROTECTED]> wrote: > Second, don't you think having html template for each widget might be > slow and also there is a way to subclass standard widgets and to use > form widget override dict (or old formfield_callback) for replacing > widgets in forms? You will create your abstract form subclass, extend > it as you wish, and subclass required widgets. > For every view using form one might want to use their own widgets -- > your approach is not easily scalable!
I think widgets should use a default template (because 90% of the time, the styling for a given widget on a given site is the same), ... *and* this should be modifiable, i.e. we should be able to set the template for any widget, in each form (maybe using some widget API in the form __init__ method). Regards Rajeev J Sebastian --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
