On Jan 4, 2007, at 2:47 AM, Kevin Dangoor wrote:
On Jan 3, 2007, at 7:43 PM, Ian Bicking wrote:
"workingenv.py -r http://some/place.txt"; is a way you can build
something like a distribution, that's separate from any of the
pieces that make it up. That way you can build a full stack with
all the components, without putting in any requirements in the
individual pieces.
oh yeah, that's handy.
(I told you... ;)
To realistically put multiple end-user-visible applications in
one process you need some styling system (for services/APIs it's
not really important). There's two layers where this can happen:
* You can use a filter that applies styling to unstyled content.
Deliverance, which I'm working on, does this (http://
openplans.org/ projects/deliverance). We're going to add a few
features here and there, but the project is pretty far along. It
works as WSGI middleware, and we've built an HTTP proxy from that
which is what we're actually using in deployment.
There is another solution here. Genshi's match templates can be
used just like XSLT to add styling around the output that's coming
from the inside.
I like this solution better because Genshi is going to be TG's
default templating language so forcing users to learn another way of
doing html transformation doesn't seem right.
A place in environ where controllers could dump their genshi
unserialized stream so upper layers have a chance to filter it and
finally serialize it sounds like a possible way to implement it...
I *believe* Elvelind is interested is interested in this part of
TG... (am I right?)
Alberto
--~--~---------~--~----~------------~-------~--~----~
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?hl=en
-~----------~----~----~----~------~----~------~--~---
