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 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)
I'd use subrequests, and then wrap that up in some object. I don't
believe Pylons exposes subrequests in a particularly friendly way, but
if you look at paste.recursive it will show you a not-as-friendly way to
do subrequests that you could pretty up on your own.
--
________________________________________________________________
Paul Stevens paul at nfg.nl
NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31
The Netherlands________________________________http://www.nfg.nl
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"pylons-discuss" 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/pylons-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---
