On 6/29/07, Sebastian <[EMAIL PROTECTED]> wrote: > Im still not sure, however, that the definition > of how it gets rendered > in hml should be anywhere but the template.
Ah, so if I read that right, you'd be in favor of an optional mapping from field to widget supplied by the template. Right now a template is a tree of nodes which return byte strings. Templates don't know anything about widgets. Maybe a subclass of Template could provide that mapping and get_template and friends could take an optional parameter for which Template class to use. Or would you need mappings based on something other than template type? If I'm on the wrong track, please outline what you think is a sensible API. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@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-users?hl=en -~----------~----~----~----~------~----~------~--~---
