the thing i really don't like about routes...

2009-02-19 Thread Jonathan Vanasco
is that the 'controller' argument isn't actually the name of the controller. its the name of the package that the controller is in. (?!?) i've mentioned this before, but my hatred for this has only grown tenfold since then. I wanted to gripe while revisiting old code.

Re: the thing i really don't like about routes...

2009-02-19 Thread Ben Bangert
On Feb 19, 2009, at 8:43 AM, Jonathan Vanasco wrote: is that the 'controller' argument isn't actually the name of the controller. its the name of the package that the controller is in. (?!?) Right, its just the package name. This is mainly due to Rails legacy, as thats how they handle it

Re: the thing i really don't like about routes...

2009-02-19 Thread Ben Bangert
On Feb 19, 2009, at 10:51 AM, Jonathan Vanasco wrote: thanks ben! its just so confusing how the find_controller works. It is? What part of it did you find confusing? I thought there were a good amount of comments on any section that might be confusing. I'd be happy to explain it further

Re: the thing i really don't like about routes...

2009-02-19 Thread Jonathan Vanasco
its just so confusing how the find_controller works. It is? What part of it did you find confusing? I thought there were a   good amount of comments on any section that might be confusing. I'd be   happy to explain it further if there was a part that was confusing. Oh, i mean the code is

Re: the thing i really don't like about routes...

2009-02-19 Thread Mike Orr
On Thu, Feb 19, 2009 at 10:21 AM, Ben Bangert b...@groovie.org wrote: On Feb 19, 2009, at 8:43 AM, Jonathan Vanasco wrote: is that the 'controller' argument isn't actually the name of the controller. its the name of the package that the controller is in. (?!?) Right, its just the package

Re: the thing i really don't like about routes...

2009-02-19 Thread Ben Bangert
On Feb 19, 2009, at 12:08 PM, Mike Orr wrote: This came up before in the case of non-Pylons controllers (i.e. WSGI applications pretending to be controllers.). If the class is named differently than PylonsApp expects, you have to assign it to a global variable with the expected name. I had

Re: the thing i really don't like about routes...

2009-02-19 Thread Jonathan Vanasco
mike- i like your concept my issue stems from looking at my routing file, and then thinking for the first time that i was looking at old perl code and not python! should i assume that because of this behavior, people should never have more than one controller in a file?

Re: the thing i really don't like about routes...

2009-02-19 Thread Mike Orr
On Thu, Feb 19, 2009 at 12:51 PM, Jonathan Vanasco jonat...@findmeon.com wrote: mike- i like your concept my issue stems from looking at my routing file, and then thinking for the first time that i was looking at old perl code and not python! The Routes config syntax is not beautiful but it

Re: the thing i really don't like about routes...

2009-02-19 Thread Jonathan Vanasco
On Feb 19, 4:52 pm, Mike Orr sluggos...@gmail.com wrote: Using the standard PylonsApp, no.  The controller class is calculated from the module name, and that doesn't allow for multiple controllers per file. The docs should reflect this then, because this is the first I've ever heard of it!