Hi Dennis,
On Aug 22, 2006, at 12:09 PM, mulicheng wrote: > Problems with using one code base: > 1) authentication is not exactly the same between sites. (Possibly > could be solved by using a site specific filter) > 2) kid templates need to be in the .templates directory unless they > are inlined into the .py file (which would be extremely ugly and hard > for the designers.) > 3) kid templates should inherit from a master so the look and feel of > the site is standard, but what if the master template is Yeah, the goal is to be able to install an egg and reuse bits of it quite easily. Currently, you can use "sitetemplate" with Kid to hold the common stuff that you want to customize between sites. You might seriously consider looking at Markup, though, because it is very flexible in how you include things. Widgets aren't the way to go, because they are designed to be view- layer (and you'll probably be fighting the framework to make it work with the database). Kevin --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
