I'd vote for CHAPTERS as well, with the previously mentioned caveat that searches would need to be able to jump to the relevant section(s) within a chapter.
Also, I think a fixed (ie, non-scrolling and always on-screen) sidebar with the current chapter's section table of contents allowing easy navigation within the chapter would be better than a bunch of 'Back to Top' links (although it wouldn't hurt to include those for those who prefer that type of navigation). As a relatively new user of web2py (<1 month) I have found the section breaks frustrating at times. I usually know which chapter a topic belongs in, but can't always figure out specifically what section it should be in. Here's a quick example: I was trying to find the function ._lastsql. I remembered reading about it early on when I had read most of the DAL chapter in a single shot, but couldn't remember where I'd seen it or what the function name was. Since I couldn't remember the function name, I couldn't perform an effective search. So I went to the sections that seemed most likely to have the info: - 6.7. How to see SQL - 6.5. Query, Set, Rows - 6.2. Connection Strings - 6.3. DAL, Table, Field I finally gave up and then remembered that I had used the function in some of my very early code. I checked my code, found the function named ._lastsql, then did a search in the book for lastsql, and was still skeptical when I saw that it was actually in 6.4 Migrations. My point is if I could have just scrolled top to bottom of the entire DAL chapter I probably would have found what I was looking for. On Jul 27, 11:20 am, Jonathan Lundell <jlund...@pobox.com> wrote: > On Jul 27, 2010, at 4:51 AM, mdipierro wrote: > > > web2py.com/book was broken into section > > web2py.com/book2 is broken into chapters > > > what is better? > > Once printed it will be the same. > > Offhand I'd say chapters, so I can use my browser-native search more > effectively. > > In that case, it might be that some existing chapters that treat more than > one subject could be split.
