[jifty-devel] Re: [Jifty-commit] r4545 - jifty/trunk/lib/Jifty/Plugin/OpenID

[Kang-min Liu]

sterling:

You're totally right about the new_action() behavior. What's
not-obvious for me, is whether I should patch Jifty::API so that it
looks into those classes defined in Jifty::Plugin::* or not. If this
is the more desired way I'm glad to revert this and patch Jifty::API,
to provide some way such that the action named "Foo" means
"App::Name::Foo" first, then Jifty::Plugin::<PLUGIN
Name>::Action::Foo.

On Nov 28, 2007 12:11 AM, Andrew Sterling Hanenkamp
<sterling at hanenkamp.com> wrote:
> gugod,
>
> It's my understanding that if you:
>
>   $action = Jifty->web->new_action( class => 'AuthenticateOpenID' );
>
> and a plugin provides an AuthenticateOpenID action, what happens is that class loader builds an application class named:
>
>   App::Action::AuthenticateOpenID
>
> that subclasses:
>
>   Jifty::Plugin::OpenID::Action::AuthenticateOpenID
>
> This was intentional and I've been meaning to go back in and alter the way plugins provide models to mirror this. Is there a problem with this behavior?
>





-- 
Cheers,
Kang-min Liu