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) automatically.
The individual plugins can run on multiple servers so that content can be pulled in from remote locations and all the fetching is done in parallel with threads so performance is pretty good.
There are some other features too such as the ability to define templates from layout objects so that the people making the templates don't necessarily need to know HTML, they just choose a header, footer and two columns say.
If you are interested I'll try and put the latest code up in the next few days.
Of course, in Pylons you can always have a single controller call actions from other controllers (they are just WSGI applications) and then assemble them yourself?
Cheers, James
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 controllers/views into a single page (i.e. /doc/view/123, /news/latest, /user/list, /user/view/myid) How to do this in pylons? Is this a templating issue? Is it possible to render a template fragment using a different controller? thanks a lot for our insight.
--~--~---------~--~----~------------~-------~--~----~ 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 group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
