+ 1 for: @expose(view="foo") rename the templates folder to "views" (@expose(view="views.foo")) pluralise "model" to "models", so that it matches "controllers" and "views/templates"
+/- 0 for: Keeping things as they are - 1 for: @view (doesn't make sense in all cases, therefore it would be better not to make any change) Ed On 8/5/06, Michele Cella <[EMAIL PROTECTED]> wrote: > > Jorge Godoy wrote: > > "Nicky Ayoub" <[EMAIL PROTECTED]> writes: > > > > > I would like to chime in... I agree with Lee and Fred. > > > @expose makes more sense in my mind. I also agree with Lee > > > that a change from 'template' to 'view' would truly accomplish the goal. > > > I can expose methods through the web server without really presenting > > > a 'view' at all, but if I use a template then I really want to see > > > something > > > out the other end. That's more intuitive and follows my thought process > > > more > > > closely. > > > If it's not too late to vote, then -10 on @view and +100 on 'template' > > > changing > > > to 'view' as an argument of @expose... Opps, is it OK to vote more than > > > once??? > > > Nicky > > > > I also like more of this change (template for view and keeping @expose). > > So I > > change my vote. ;-) > > > > +1 makes *a lot* of sense (along with a views subpackge containing > json.py and the templates package): > > @expose(view="templates.list") > @expose(view="json") > > in this way we could also link automatically the view parameter to the > view package. > > Ciao > Michele > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
