On 9/21/05, Ben Bangert [EMAIL PROTECTED] wrote:
On Sep 21, 2005, at 9:54 PM, Shannon -jj Behrens wrote:
Sorry to keep yacking, but one more thing comes into play. In
Aquarium, I have this thing called inverseExtend. This allows a
parent class, say SharedLayout, to completely and
Shannon -jj Behrens wrote:
Hopefully that actually makes sense. But in short, some template languages
lose a lot of power without the ability to do this kind of hooking into
functions up the inheritance chain. This is why webapp ignorant output
filters running over the output won't work for those
On 9/21/05, Ben Bangert [EMAIL PROTECTED] wrote:
There's so many things a page could require in the header, footer,
etc. just to operate properly I can't see it being realistic to have
a template filter act very reliably on different deployed apps. While
it does take some extra work to make it
On Sep 10, 2005, at 11:39 AM, Ian Bicking wrote:
Thanks for the detailed example, I finally understand now what Paste
does :). One question though, should I use environ for exchanging
data
between applications (e. g. some template object, that partly
rendered
by one application, and
Having multiple levels of shared look and feel is something that
Aquarium does very well in Cheetah using multiple techniques. I do
make use of heavy OO, etc. to make this happen. It's a requirement
for my company where we need multiple applications to look pretty much
the same, but not exactly.
Sorry, I didn't mean to sound like I was bragging. I should note that
imho this is a bit easier to do with Cheetah than with ZPT and Metal.
In Cheetah, if I have a deep inheritance hierarchy:
SharedLayout
AppLayout
SectionLayout
Screen
Then, within Screen I can override, extend, or define
Sorry to keep yacking, but one more thing comes into play. In
Aquarium, I have this thing called inverseExtend. This allows a
parent class, say SharedLayout, to completely and automatically wrap
the child class. It gets to go first, call the child when it wants,
and do with the output what it
Hi,
Sorry if this is a trivial question, but does it sounds reasonable to
use WSGI for pluggable standard applications, instead of usual
Python imports? For example, standard news module, like:
app = NewsApp(path='/site/news/')
The content of news app would be inserted into site template,
Ksenia Marasanova wrote:
Sorry if this is a trivial question, but does it sounds reasonable to
use WSGI for pluggable standard applications, instead of usual
Python imports? For example, standard news module, like:
app = NewsApp(path='/site/news/')
The content of news app would be
Ksenia Marasanova wrote:
2005/9/10, Ian Bicking [EMAIL PROTECTED]:
Ksenia Marasanova wrote:
Sorry if this is a trivial question, but does it sounds reasonable to
use WSGI for pluggable standard applications, instead of usual
Python imports? For example, standard news module, like:
app =
10 matches
Mail list logo
