On Fri, Feb 3, 2012 at 12:18 PM, Chris McDonough <chr...@plope.com> wrote: > On Fri, 2012-02-03 at 12:12 -0800, Jonathan Vanasco wrote: >> great. that looks good. >> >> I need to read up more on views vs handlers. >> >> since i use "render_to_response" for most things, I should have an >> easy transition > > Handlers are views too. So this works there as well, if you'd rather > continue using those.
Chris, Blaise, something to think about for the documentation: People are getting the idea that handlers are some big separate thing; i.e., more than they are. I think this is due to how pyramid_handlers was originally marketed. Part of it I think was an expectation that ex-Pylons developers wouldn't accept the standard Pyramid API, whereas actual experience has shown that they're more accepting of it than we thought. So in my Pyramid/Pylons guide (and in the Akhet manual) I've tried to emphasize that a handler is just another name for a view class (i.e., a class containing view methods). What pyramid_handlers really gives you is config.add_handler() and @action. It doesn't give you a base class: that's an Akhet invention (to parallel Pylons' Base controller). So I think that where the docs talk about view classes, they should mention that handler is a common term for a view class, but it means nothing more than that, and that pyramid_handlers is just one way of managing them. -- Mike Orr <sluggos...@gmail.com> -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to pylons-discuss@googlegroups.com. To unsubscribe from this group, send email to pylons-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
