This is great. To avoid confusion, though, would it make more sense to move this material into the "URL Rewrite" section of Chapter 4: http://web2py.com/book/default/chapter/04#URL-Rewrite Maybe keep the first paragraph of that section and then mention that there are now two distinct URL rewriting systems -- for most use cases, a fairly simple router-based system (involving dictionaries of routing parameters), and for more complex cases, a powerful regular expression based system. Then create two subsections to explain the two systems (e.g., "Router System" and "Pattern Matching System", or something along those lines). For app-specific routing, we could either keep the "Application-Specific URL Rewrite" subsection ( http://web2py.com/book/default/chapter/04#Application-Specific-URL-Rewrite) and simply expand it to include the new router system, or instead include separate app-specific rewrite subsections within the Router and Pattern Matching sections. It's also probably worth mentioning the following somewhere:
- Although the router example file is called router.example.py, the routers still need to go in routes.py (i.e., not router.py). - You cannot mix router dictionaries with the old regex routes_in and routes_out (yet). - routes_onerror still works the same regardless of which routing system you're using (i.e., still regex based). Anthony On Friday, February 18, 2011 1:16:35 PM UTC-5, cjrh wrote: > On Feb 17, 8:02 am, Jonathan Lundell <jlun...@pobox.com> wrote: > > Please do. Take a look at router.example.py as well; there's at least > one new feature there (path_prefix). I can review the material any time > you're ready. > > Ok, here is a first draft. > > http://web2py.com/book/default/chapter/11#Modify-the-URL-with-the-Router > > I followed your guide pretty faithfully, mosly adding the markmin > markup where application. Now at least you (and others) can refer > people to the formal documentation. > > If you want me to add or change stuff, please email me directly. > Google groups makes it too difficult to keep track of older threads.
