When writing a pylons app, how much code do you put into your controller? One thought I had was to put enough code in to handle basic operations, but, if the controller required more than 20 or so lines of code, put that into a class or function so that the controller itself was reasonably lightweight and easy to follow. But some controllers only have a few actions, and putting 100 or so lines of code into 3 actions seems functional and easier to follow with less indirection.
Some of my actions have 3-5 lines of code after the decorator and definition, but, some actions are quite complex. Any suggestions or guidelines? -- 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.
