On Mon, Jan 02, 2006 at 08:58:15AM -0800, Michael Schneider wrote: > > Dan, > > I have no beef with Kid. I would like to see the widget templates use > the > same template plug in as expose. > > That way you could develop widgets using any templating language, and > mix the widgets. > > I would like to use kid for the main page, and STAN for the complex > widgets. > (I may port them to kid after I get them going, but I would like to > prototype > with STAN, or fill in your favorite templating language). > > Page-> render > Widget -> render (widget renders XTHML into page) > ... > > > > link to start of thread (only me so far) > http://groups.google.com/group/turbogears/browse_frm/thread/b12609be62408f9c > > I really like the fact that a template is associated with a widget in > TurboGears. It would be really great if TurboGears could leverage the > Template Language plug-in to render the widget. > > Would this solve your use case? > Are there issues with this? > > Thanks > Mike
There's a current implementation problem with just .insert()ing widgets with different templates. The current widget system inserts kid elements into kid templates and things like form values are read from cherrypy's input_values variable. This happens at render() time, not at .insert() time. A bunch of logic would have to change to support pulling input values when the widget is .insert()ed. Jason -- If you understand, things are just as they are. If you do not understand, things are just as they are.
pgpAeJBRVhBAc.pgp
Description: PGP signature
