> > Why not have a way in which the template says it needs this and that > widget and if those widgets need some parameters from the controller > then these parameters are returned in the dict, are available in the > template so the widget has access to them in the template.
Because then you start stuffing more logic into the template, making things harder to understand. Because it's not only the widgets themselves, it might also be supplementary data that needs to be prepared and so forth. Which IMHO should go to the controller. Actually, the VC of MVC are pretty much the same, it's just about clean separation to allow easy modifications. So my controller contains the python needed to deliver the functionality - and the template the "pure" display logic. Trying to enforce more separation doesn't really help there I'd say. But in the end, it's everybody choice. I for sure know that I want my widgets in the controller. Diez --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" 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?hl=en -~----------~----~----~----~------~----~------~--~---
