"Michele Cella" <[EMAIL PROTECTED]> writes: > As I said composing widgets to make a layout makes thing increasingly > complex IMHO, you may want to investigate the use of py:layout inside a > widget kid template to do such a thing, this seems like a better way of > doing it IMHO. ;-)
Just as a "feedback", py:layout is applied in the opposite direction of what I wanted. py:layout makes it possible to fill in the base template with information from the "extended" template. In my case, it means that if I used py:layout and the template for the forms had slots, then I could fill in those, but if my template had slots, they couldn't be filled in by the base template. http://kid.lesscode.org/language.html#layout-templates-py-layout The use case, then, would be having the skeleton "<form><button /></form>" and filling in this with either the list or table layout (which is similar to what I wanted and I believe the cause of your reference to py:layout). Thanks. ;-) I'll see what I can do. Maybe I'll play with py:match and see what I get. :-) -- Jorge Godoy <[EMAIL PROTECTED]> --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
