> > 1. The pattern router should be named the 'comprehensive' router. > > 2. The parametric router should be named the 'easy', 'lite' or 'limited' > router. It should start off by stating its limitations. Developers can > then immediately discard it when it doesn't meet their requirements. >
Have you read through this section: http://web2py.com/books/default/chapter/29/4#URL-rewrite. I believe it communicates exactly what you suggest above. Some excerpts: web2py includes two distinct URL rewrite systems: an easy-to-use * parameter-based* system for most use cases, and a flexible *pattern-based* system for more complex cases... The parameter-based (parametric) router provides easy access to several "canned" URL-rewrite methods. Its capabilities include: [goes on to list specific capabilities]... Although the *parameter-based* system just described should be sufficient for most use cases, the alternative *pattern-based* system provides some additional flexibility for more complex cases... Regarding the naming, I'm sure opinions will vary (I prefer the more functionally descriptive "parameter-based" and "pattern-based"). Anyway, the naming isn't part of the API, just a shorthand reference for documentation and discussion. > Or, better still, a dict solution for all plugins: > alt_names_for_plugins = dict(plugin_wiki=myprettyname) > Yes, that would be great. Anthony
