It seems you're replacing controllers with business objects, which seems like unnecessary complexity for me. That's the usual style of programming in Java and very "enterprisey" but I personally hate it as the business objects tend to grow and grow and eventually you can't keep track of all the side effects you have when you call one of their methods. The way I usually structure my web2py projects is, each entity (together with related entities) is in their own model file, for each entity I also have a controller file with the same name, the controller file has all the usual CRUD methods for that entity. KISS (Keep it simple stupid) Eventually, you will want some of what you call "business objects" but that's something that comes *late* in a project and that you get through *refactoring*, when you can identify components that are quite well self-contained and independent. For instance, in my projects, I have extracted the user notifications logic into their own "business object" as it's something that is independent from all the rest and saves a lot of lines of code in each controller that will want to send notifications to the user. The thing is, you don't know what will make the development and maintenance of code easier until you have a few regular controller functions programmed and you can see what's worth refactoring into a module/"business object".
-- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
