On Fri, Sep 16, 2011 at 10:42 AM, Guy Nesher <[email protected]> wrote:
> Hi guys, > > Just started learning web2py (have basic python understanding and > played with Django before). > First of all wanted to say its really a nice change from Django > (horrible learning curve) > > While reading the book I did encounter some problems (and had some > suggestions) - I understand some of the core development team is > present and thought you might find this helpful. > > 1. Chapter 02 (help/dir) > I entered the python interpreter using ./web2py.app/Contents/MacOS/ > web2py -S welcome (mac) and while it loads fine it does not recognize > the help(1) command. > gives the following error: "Traceback (most recent call last): File > "<console>", line 1, in <module> NameError: name 'help' is not > defined" > running the same command on my virtualenv works fine. > > 2. Chapter 03 (admin interface) > 1. Images of the site/admin panel do not match the actual visuals. > All the screenshot have to be update, I think it gonna be the time to do it soon when the core team will focused on the documentation... The book is update once a year during fall... I was volontary to make all the screenshot to make them all the same (same browser set up to make keep unity trought out the book). I try a couples of time to make them, but my set up was not optimal and the example from the book were sometimes outdated so I was finding myself hacking more then making screenshot. So I am waiting the examples be revised then I plan to try again to make the screenshots for all of them. > There are some differences to the install process (new simple > application + new application wizard) not a huge problem but might be > worth fixing > 2. I was not asked for an admin password after restarting the server > (according to the book you will need to reenter it on every login) > 3. "You can configure the defaul" should be default > > > General suggestion > Links to web2py commands (such as session) should open in a new > window. > Show an alert if a user leaves the edit screen after making changes to > the code without saving (I actually fell for that a few times) > Chapter 03 - Adding a summery after every project (the move from the > image blog to the Wiki is very sharp) also possibly divide each > project to its own subchapter (separate html) > Richard
