Thanks for the feedback.
All three approaches (special template engine, components, sub-requests)
look very usefull. I've got some studying and experimentation to do.
Ian Bicking wrote:
Paul J Stevens wrote:
All the example code uses a single controller per page, which is all
good and fine
We're waiting for the art templating system...
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
pylons-discuss group.
To post to this group, send email to pylons-discuss@googlegroups.com
To unsubscribe from this
On Wed, 2007-01-17 at 12:55 +, James Gardner wrote:
Hi Paul,
I'm developing a new templating system called art which handles this
particular case. Instead of using a controller to call a template and
display the result, the template effectively defines which content it
requires and
Hi all,
coming from the world of plone...
All the example code uses a single controller per page, which is all
good and fine for crud operations on a database, but seems rather
limited for what we do.
I'd like to build a website (read a typical portal site) that brings
together several
Hi Paul,
I'm developing a new templating system called art which handles this
particular case. Instead of using a controller to call a template and
display the result, the template effectively defines which content it
requires and calls the different controllers (called plugins in art)
In our projects we used components folder where we put functions like:
def pool(id):
c.pool = model.Pools.get(id)
return render('pool_template')
in template with page we call pool(id) in somewhere we want.
This is very flexible solution. We can decorate function with cache,
Paul J Stevens wrote:
All the example code uses a single controller per page, which is all
good and fine for crud operations on a database, but seems rather
limited for what we do.
I'd like to build a website (read a typical portal site) that brings
together several controllers/views into a
James Gardner wrote:
I'm developing a new templating system called art which handles this
particular case. Instead of using a controller to call a template and
display the result, the template effectively defines which content it
requires and calls the different controllers (called plugins in
