> Even better: TW doesn't need widgets to be passed in a special attribute > of the template context (to pick up their resources) anymore. As long as > its middleware is configured like shown here [1] (with the > 'inject_resources' flag on) there's no need for 'w' or 'widgets' to be > polluting tmpl_context.
OK. I'll bite. Seems like this is a clean simple way to handle widgets. I remember you saying that you're now using regular expressions for this, and that they were fast enough. But I'm wondering how fast they are. We can always provide a recipe for doing this "manually" in the template, so even if the inject resources way is a little bit slow, it should be fine. BTW, how does TW know what resources to inject. Do you just keep track what needs to be added in the environ? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" 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/turbogears-trunk?hl=en -~----------~----~----~----~------~----~------~--~---
