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?)
- where to place and how to organize the testsa few slices and projects exist on testing web2py. Unfortunately there's yet no "recommended way" officially proposed by web2py
- 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?)
you upgrade web2py to benefit from fixed bugs and new features. As long as your app can accomodate for those, I don't see a real reason why NOT upgrade .
Maybe check Sahana.org
Sahana eden http://eden.sahanafoundation.org
--Rob
Sent from my phone...excuse any typos please!
--
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+un...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.