On Nov 13, 9:31 pm, "PoBK" <[EMAIL PROTECTED]> wrote:
> Umm guys,
>
> I think I'm being a bit dense this evening...
>
> I'm attempting to build set of template tags for some widget framework.
>
> The current way it works is:
>
> {% use_widget [pythonic path to widget] [args if required]%} tag loads
> a module/class. The class does it's magic, and and sets a load of
> variables in the context, to be rendered by the other tag {%
> render_widget_resources [type] %}.
>
> Ok, so I've got the first bit working wonderfully... the widget loads
> and it works perfectly.
>
> Now, the bit that isn't working is the resource rendering. I've hit a
> submerged rock, and I'm not entirely sure how to go about working my
> way around it.
>
> The particular rock I've struck is the context stack. That is for each
> {% block %} tag, the context gets pushed up the stack, and then popped
> at the {% endblock %}. So elements that I put in at one level are gone
> at the next. Which is a slight pain in the rear end.
>
> Anyone have any ideas about going about convincing the Django
> templating engine to play nice and give me back my variables when I
> want them? How do the context processors persist elements in throughout
> the stack?*ping* No ideas? -- Richard --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected] 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 -~----------~----~----~----~------~----~------~--~---
