I tried this, and I get mismatched tag errors. >From what you said above, KID seems to be importing in a different direction. I would think that if I render welcome.kid in my controllers.py for a specific class member, KID would pull master.kid into the welcome.kid, and then expand master.kid into it. You said this:
"The code following the declaration of your body tag essentially takes the entire contents of the body tag of any kid pages that build on master.kid and places it in your master.kid." which is a bit confusing. I thought the expansion woudl go the other way, FROM master.kid TO some other KID template page. Am I missing something? Also, I am assuming that because of this import between pages, if I am pulling a HEAD section from one page into another using the syntax you specified, the recipient page does not need a HEAD section, and will not fail without it. Is this correct? I am getting errors now, so it's difficult for me to tell. I am hoping for some complex examples of KID page nesting, to show me different ways to set up master and sub templates. I wish to be able to set up a master css layout, and master images. Example: I want to be able to call my clientData member of my root controller class, and not suffer from this nesting of image paths: [2006/03/20 19:20:02] "GET /clientData/static/css/summary.css HTTP/1.1" 200 114 when I call this member of my root controller: clientData = ClientsData() I invoke it like this: http://69.20.118.152:1111/clientData/?clientId=787 My images and css are under static, not clientData.static. I need some way of telling every page: Get ALL of your basic layout and banner images from static/... and get your relative images from clientData/static.... Thank you in advance, Gloria --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" 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 -~----------~----~----~----~------~----~------~--~---
