On Wednesday 31 October 2001 13:26, [EMAIL PROTECTED] wrote: > Tavis Rudd wrote: > >>Yes, and no. It is common to use PSP for the frontend and do all > >> the > > backend processing in pure Python classes that are inherited by the > PSP classes. MS calls this the 'code-behind' method with ASP. > While PSP is better than pure Python for the front-end stuff, there > are alternatives that are better suited for this task.<< > > > When is PSP more appropriate than Cheetah in the Webware context? > If Cheetah is the preferred templating solution, why not just > bundle it with Webware too? > > ...Edmund.
I can't think of any situations where it is more appropriate, but I'm biased. It's kept separate at the moment because Cheetah is developed separately from Webware and both it and Webware have been undergoing some significant changes recently. Chuck's plan was to eventually package a 'batteries-included' version of Webware that has Cheetah and other tools bundled with it. This is probably a few months off yet. I've just added a 'BatteriesIncludedProj' to the new Webware wiki site that can be used to speed up process of designing the BatteriesIncluded version. Tavis _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
