On Jul 14, 4:15 pm, SmileyChris <smileych...@gmail.com> wrote: > We also need d) Media hooks for a single widget - whether this can be > done in only the template layer is a tricky problem... > > I'm still struggling with how you'd be able to render all the media at > the top of your template for the form. I guess you'd have to define > any field widget overrides in that block, before rendering the form > media.
Yeah, this is tricky. For JS generally it shouldn't be rendered until the bottom of the template, for page-speed reasons, but the reverse is true for CSS. I don't think there's yet been a proposal in this thread for how to enable rendering widget media before the form is rendered, both proposals so far would have you specifying/overriding chrome (or widget templates) only at form-render time. Obviously it'd also be good to be able to split CSS from JS, like the Media framework allows. One half-baked idea: what about annotating the form object itself with information about customizations you've made: paths to form-rendering templates and widget templates? So you could use the same customization syntax when rendering the form or rendering the form media, whichever you do first, and it would remember those customizations for later? This introduces a little more cleverness than I'd prefer, but if the only other option is repeating every customization twice... I'm also not sure how this would interact with the idea that the "form media render" tag should accept multiple form objects, so even if you use the same widget/chrome in multiple forms on a page, its media still only gets rendered once. Carl -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
