The problem for me is not being able to mix the new parameter-based routing with the pattern-based system (my regex skills are not good enough to make the patten system do what I want....) .
Is it possible to have parameter system in the global routes.py and then pattern system in the app-specific routes.py? That would solve my issues! On 24 March 2011 16:06, Anthony <abasta...@gmail.com> wrote: > I believe this is already possible, no? > > The book describes app-specific routing for the old system: > http://web2py.com/book/default/chapter/04#Pattern-Based-System > > And for the new system, the router.example.py file ( > http://code.google.com/p/web2py/source/browse/router.example.py) mentions > you can have an app-specific router in applications/app/routes.py. > > Anthony > > On Thursday, March 24, 2011 11:49:58 AM UTC-4, Martin.Mulone wrote: > >> I really want to see routes in the application folder. Routes in the past >> was hard to follow, now I think the work of Johnatan make it more easy. But >> when you have many applications, the routes for all is a bit messy. I don't >> know if this can be done: >> >> For example a simple case: >> >> Main routes.py: >> --------------- >> >> Domain Application >> --------------------------------- >> www.domain1.com domain1 >> www.domain2.com domain2 >> >> >> >> Aplication: applications/domain1/routes.py: >> ------------------------------------------- >> >> >> [routes In] >> In Out >> ---------------------------------- >> /favicon.ico /static/favicon.ico >> >> >> [routes Out] >> In Out >> ---------------------------------- >> default/index / >> plugin_i2p/view/333 /view/333 >> >> >> 2011/3/24 VP <vtp...@gmail.com> >> >> Noticing the version of web2py keeps interestingly increasing to 2.0, >>> I think this is something Massimo might want to spend sometime >>> thinking about. >>> >>> As I understand it, because of "exec", controllers are called *after* >>> the request arrives. This allows web2py to do a few interesting >>> things that other frameworks can't. >>> >>> On the other hands, this is an example that shows an advantage of >>> being able to manipulate controllers (concisely) *before* the request >>> arrives. >>> >>> I found myself constantly type checking controller arguments (e.g. >>> making sure an "id" is a number). This is another example where being >>> able to specify a certain syntax to the URL is very helpful. >>> >>> >> >> >> -- >> Pablo Martín Mulone (mar...@tecnodoc.com.ar) >> http://www.tecnodoc.com.ar/ >> >> My blog: http://martin.tecnodoc.com.ar >> Expert4Solution Profile: >> http://www.experts4solutions.com/e4s/default/expert/6 >> >> >>
