The problem was when MooSlidesFx.Elements tried to Extend MooSlidesFx.
Still don't know why, but I don't care now.
I realized I extended MooSlidesFx in MooSlidesFx.Elements and re-wrote
every one of the methods. The only reuse I got out of it was this.el
and a few options.
So ... I separated them into MooSlidesFx.Element, and
MooSlidesFx.Elements.
Then I created a library MooSlidesFx.lib and stored the Fade class
there (MooSlidesFx.lib.Fade).
Now I can just:
MooSlidesFx.Fade = new Class({
Implements: [MooSlidesFx.lib.Fade, MooSlidesFx.Element]
});
MooSlidesFx.FadeElements = new Class({
Implements: [MooSlidesFx.lib.Fade, MooSlidesFx.Elements]
});
And it's amazing. I <3 MooTools. Now it's time to build up the library
with more effect classes!
On May 30, 4:22 pm, rpflo <rpflore...@gmail.com> wrote:
> I'm working on some effects and things to get a handle on Classes/
> Implements/Extends. The examples here are for the base classes
> (MooSlidesFx, MooSlidesFx.Elements) from which to create many effects
> with a project I'm working on, and two child class (MooSlidesFx.Fade,
> MooSlidesEffects.Elements.Fade) that actually do something.
>
> http://paste.mootools.net/m6afc7746
>
> The first Class, MooSlidesFx, sets things up for others, designed to
> just be Implemented.
>
> The second class, MooSlidesFx.Elements, extends MooSlidesFx to
> likewise be implemented, but rather than just animate the element
> passed in, it will animate it's children in order (not looking for a
> lesson Chain right now, but it's next on my list!), and so some of the
> methods are redefined.
>
> The third class, MooSlidesFx.Fade works great. It implements
> MooSlidesFx, defines to little methods, and we're off to the races.
>
> Then the problem. It *seems* like I can just implement both
> MooSlidesFx.Elements and MooSlidesFx.Fade and POW!! I've got a new
> effect that doesn't fade in the element, but rather fade in it's
> children staggered.
>
> Not so, thanks for any help!
