Alberto Valverde wrote:
> I'd like to hack a bit when I get the time on packaging all the
> widget code into a separate egg which could be reused on any
> framework supporting template plugins + genshi (or any template
> plugin of your choice thanks to #1086 + formencode.
>
> I'll try my best on keeping the API backwards compatibility intact
> but I'm not sure yet of how easy a task it would be.
>
> What worries me most is that, in order to avoid the dependency on
> cherrypy, I plan to remove the "path" acrobatics which depend on
> cherrypy.request and I need to think of a way to let child widgets
> get their display parameters and validation errors:
> a) without changing the API (this means not passing "errors" as a
> parameter to the form's display when rendering it on a template.
> b) letting widgets be child's of many widgets at the same time (to
> allow WidgetsLists to be reused). This means no modification to child
> widgets when attaching them to a container, for example, by adding a
> 'parent' attribute.
> c) keeping them threadsafe and without using threadlocal storage
> (like cherrypy.request)
>
> This "acrobatics removal" should greatly simplify the code too I
> believe... Let's see how it goes when I give it a shot.
>
> Any suggestions, requests, objections or anyone wants to lend a hand?

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.

Cheers,
Ben


--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to