On 7/30/06, Kevin Dangoor <[EMAIL PROTECTED]> wrote: > > Bruce Eckel's recent blog posting made an excellent point... > TurboGears is a model/view/controller-based framework, and we have > conveniently named "model" and "controllers" files. The view for a > given request is really represented by the @expose decorator. The > name expose is a CherryPy carryover, but turbogears.expose is nothing > like cherrypy.expose. > > I'm interested in taking up Bruce's suggestion of naming the > decorator @view. @expose will continue to work, and I'm not even > proposing a real deprecation of @expose at this time (that would come > later on). I'm suggesting that we make @view available and start > using it in docs and whatnot. > > Thoughts?
Then what are the templates? Aren't the templates the "view" part? Wont my templates have an identity crisis? Who's gonna pay for their counselling? Elver --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
