Hello: I'm about to start my next sprint with my project karakolas, and this time the main goal is to clean, refactor, tidy... I've read the web2py book, but I need advice about good practice when a web2py project starts to become too complicated. I don't have time to use a frontend framework, thought I definitely have to use bootstrap better. However, my main concerns are: - where to place and how to organize the tests - read batteries of tests that other people have written to make sure I test all that can be tested - when to use a model, or a module, or a conditional model - any caveat in using lazy tables all the time? - where to place files generated by an external program - version upgrades, and specifically if an upgrade of your app goes hand-in-hand with an upgrade of web2py (should I release the app bundled with web2py to solve that?) ...that sort of thing. I also have to put some functionality into plugins, but I know where to find theory and examples for that. I just want to wait till I get the rest right, so that making a plugin doesn't spoil the rest. So I ask either for references or for open source web2py apps of great size and complexity. Performance is not as important as order. Thanks
-- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
