Hello, I'm in the research phase of a new project that eventually will be replacing a legacy PHP web application. 85-90% of the legacy site is going to be stupidly easy to implement ( blog, event calender, user profile/detail, forum/messageboard, etc ) but the one weird thing I want to try and get ironed out is the website frontpage.
What I'm trying to accomplish is to have a backened/DB driven frontpage where an Admin can change at will what content is displayed. Say have a user login widget/block to the left, an event calender block and or whatever else on the right, and then whatever they want in the middle ( perhaps a DB stored semi-static page ). Best way to think of this is the versatility of a CMS frontpage. The two approaches I've thought up would be: Pylon's routes to a FrontPage controller, which polls an ActiveWidgets model which gets a list of pairs ( controller & method ) and where they're rendering ( left, right, center, bottom, mid-top, etc ). Then I'd pass each pair individual to a renderSubview utility method which would instantiate each controller, call the corresponding method, and return back a string of the sub view. It seems like it would work and for most of the entire process I could cache everything.... but I got this weird feeling I'm making a mistake or doing things in an Anti-python way ( c/c++ & PHP background ). And alternative idea that doesn't seem right to me, would to use the Pylons controller.util.forward function, and instantiate each controller path inside my renderSubview ( using the routes url helpers ). Any suggestions or criticism is welcome, I've got a rare opportunity ( 2-3 months ) to design this application to shine so I'm taking each step in the whole process a little bit deeper then normal. Thanks, David --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
