True, but it's not updated. That's why I was leaning more towards Sphinx. You could document the API and the web2py book at the same time. Again, Django's documentation is always updated when they add new features because they add the documentation to the code and rerun Sphinx. So there's no need to remember to update the book as long as the code is documented.
- Re: [web2py] what about web2py 2.0? Bruno Rocha
- Re: [web2py] what about web2py 2.0? Phyo Arkar
- [web2py] Re: what about web2py 2.0? niknok
- [web2py] Re: what about web2py 2.0? Massimo Di Pierro
- [web2py] Re: what about web2py 2.0? guruyaya
- [web2py] Re: what about web2py 2.0? Massimo Di Pierro
- [web2py] Re: what about web2py 2.0? Ross Peoples
- [web2py] Re: what about web2py 2.0? Anthony
- [web2py] Re: what about web2py 2.0? Ross Peoples
- [web2py] Re: what about web2py 2.0? Robert Kooij
- [web2py] Re: what about web2py 2.0? pbreit
- Re: [web2py] Re: what about web2py 2.0? Vasile Ermicioi