Andrew Gianni wrote:
> Dotan, are your mixins simply providing additional non-CGI::Prototype
> functionality, i.e. not overriding core CGI::P methods?
>
>
Yep. That's why my mixins are "Utils" rather than pages. If you could
build an ordered chain of render_enter methods or whatever, the
a
On 8/16/07 1:32 PM, "Randal L. Schwartz" <[EMAIL PROTECTED]> wrote:
>> "Andrew" == Andrew Gianni <[EMAIL PROTECTED]> writes:
>
> Andrew> Dotan, that looks like what I'm looking for and it's roughly what I
> Andrew> had in mind although I didn't realize that a Class::Prototyped class
> Andrew>
> "Andrew" == Andrew Gianni <[EMAIL PROTECTED]> writes:
Andrew> Dotan, that looks like what I'm looking for and it's roughly what I
Andrew> had in mind although I didn't realize that a Class::Prototyped class
Andrew> could have multiple parents, which resolves the question of multiple
Andrew>
Dotan, that looks like what I'm looking for and it's roughly what I had in
mind although I didn't realize that a Class::Prototyped class could have
multiple parents, which resolves the question of multiple mixins. How are
they evaluated for execution? For example, if you override render_enter in
Mi
Hi Andrew,
CGI::Prototype as a framework is something of a bit of string lashed
around a set of power tools.
These tools can do anything you need, but the "framework" provides no
guidance about how to do it, beyond the "with this" inherent in
Randall's choice of tools.
Instead of 'use base',
I'd like to figure out how to get mixins up and running under
CGI::Prototype. I think I understand the technical aspects of
Class::Prototyped well enough to pull it off, but I have design questions
that I'd like feedback on. Assuming all goes well, I'd be happy to
contribute a CGI::Prototype::Mixin
