So I though a bit about it and what I actually would like to have is something like this: https://gist.github.com/1738249
So what I would imagine is that a method decorated with @view_controller is only getting a @view_config when it's class is actually decorated with @view_controller. This makes it able to define default view methods in a base class that don't get added by config.scan. I also want the cleanup method to be called after a view method has returned (if it exists). Of course a method @view_controller should only overwrite the predicates for this single method. What do you think about this? Would you rather go with implementing the processing logic seperated from the view logic? e.g. the view logic could just look for a processing class that can handle the resource. Though this would probably kind of duplicate the view lookup system. Or would you go with a base class, e.g. ViewController from which one can inherit and then decorate the methods? Cheers, Benjamin -- You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en.
