On Thu, Feb 19, 2009 at 10:21 AM, Ben Bangert <[email protected]> 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 name. This is mainly due to Rails legacy, as
> thats how they handle it as well. It wouldn't make sense for the controller
> (which appears in the URL in many cases) to be the class itself,
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 suggested having an optional
global variable with a well-known name (e.g., 'controller'), which
would override the normal lookup. This would just be a little patch,
but it would help both with foreign applications that are not called
"*Controller", and also with controllers containing acronyms (e.g.,
"MyURLController"), which look bad when they're recapitalized to match
the convention ("MyurlController").
controller = MyURLController
controller = Plone
--
Mike Orr <[email protected]>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"pylons-discuss" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/pylons-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---
