On Sat, Sep 6, 2008 at 5:51 AM, Aidas Bendoraitis <[EMAIL PROTECTED]> wrote: > >> As with all suggestions for enhancements at the moment, the opinion is >> "please wait". We're currently in the process of finalizing the v1.0 >> release, and not really in a position to give a good analysis of >> feature proposals. If you wait a few weeks until the dust has settled >> on v1.0, we will be able to give your proposal the attention it >> deserves. > > So as Django 1.0 has been finally released, should we open a > discussion about templates for standard and custom widgets?
Well, first, this weekend they have a party :) 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! -- Best regards, Yuri V. Baburov, ICQ# 99934676, Skype: yuri.baburov, MSN: [EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
