> Also, as to the "if it ain't broke don't fix it" argument: it's not > that "expose" is a giant bit of breakage. It's just that MVC is not a > term invented here and, since validation and error handling are split > off in separate decorators, @view just feels, to me, like a better > description of what that decorator has to say about a particular > controller method (and, by association, URL). > > That said, this is a pure bikeshed moment and I'm not willing to > devote a lot of time to it. The crowd seems about 50/50, so at some > point I'll likely just have to decide something one way or the other. > > I do think people are right about a "views" directory (and json.py > would go in there). That's probably not too onerous a change, because > it wouldn't affect existing projects at all... it'd be a quickstart > template change.
Maybe it's not good to change anything at this moment. This was all based on a single comment by Bruce Eckel (which when I read it, I thought he was wrong... about expose vs view) on his first encounter with TG comming from a completelly different world of programming. Many other people have not had any problem with the @expose name, nor with the template directory.. so why change? BTW. it contains templates, used with template plugins, it's just normal to call it "templates/" --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
