Hi Ben, On Sep 22, 2006, at 11:28 AM, Ben Bangert wrote:
> > I'm interested in helping out on this. I was just talking to some > folks > the other night about adapting TG widgets to work like that. If I > could > get some pointers on what sections of code I should be taking a look > at, it'd be easier for me to get up to speed on possible ways to > resolve the CP dependencies. Alberto and Michele are definitely more knowledgeable than I am about all of the "path acrobatics" that Alberto's alluding to. We've tended to use the request has a threadlocal, request-scoped storage. You'll find evidence of that in turbogears.widgets.forms. That should actually be a pretty easy one to fix if the WSGI environment becomes available. There's another TG dependency in turbogears.widgets.meta (and base) where it handles loading of the templates. Alberto's work to make that support any template engine and what you talked about with Elvelind may make that dependency evaporate. So, breaking widgets out into a separate package is definitely a doable thing, and I'd certainly appreciate the help. Kevin --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
