El miércoles, 25 de marzo de 2015, 4:19:31 (UTC+1), Massimo Di Pierro escribió: > > Anyway, it would be nice to have more material about teaching web2py > and/or teaching with web2py. Perhaps we could crowdsource the effort. If I > have a list of 10 topics that people would want me to cover in detail I can > make some short videos. I am sure other people here would be willing to > help. >
This is very personal, but: At some points I have felt the need to read, fix or copy-paste-modify the gluon code, and I was able to do it. The code is there, it's really nice, it has docs and comments and is otherwise self-explanatory. And most of the time there was a way around messing with gluon. What I would love to see is more tips on architecture of complex web2py applications. web2py is amazingly simple and robust for simple applications, but when my project started to grow, I got lots of hints that there were a lot to do to organize the code that is not covered in the manual. I acknowledge many issues are probably not web2py specific but still, I see a big difference between small and complex web2py apps. For simple apps, I find that in web2py "There is one-- and often only one --obvious way to do it.", but for complex apps, I feel it's a lot more up to the developer. I'll try to be more specific: I would love to read some stories like these for web2py projects: http://aosabook.org/en/index.html By the way, I don't know if this would help, but I'd also love to drop some cash! There's no donate button for web2py... Regards! -- 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.
