Well, the example in the blog explained it a lot, though it is in
Actionscript 2.0.

And yes, I wont need Interfaces unless I really feel like I HAVE to use
them.
In my project I have some Panels (screens) in the fla Library and each one
of them is linked to a Class (linkage). Each class or Panel extends an
abstract Class called APanel that extends MovieClip. The APanel Class
contains some features that I need to be shared to all the other Panels. In
the Main class, I managed how to switch them, based on the application flow
and navigation. I use some navigation buttons that slide them to the right
or to the left of the stage.
Till here everything worked fine. But at a certain point I found some
problematic issues. I also need the panels to slide when a certain button is
pressed in one of them. Of course the function I used in the Main Class to
slide the Panels away, wouldn't be available to the other classes unless I
set them to be static, so I could write:

Main.SlideLeft();

Fine. But to make the function static, I'd put in consideration some other
things like turning some of the Main Class Properties used in the function
to static. And that is a problem because library variables cannot be
declared static.

So I think that the use of an interface somewhere would solve the problem.


On Wed, Apr 2, 2008 at 12:24 AM, Muzak <[EMAIL PROTECTED]> wrote:

> >
> > If you're the only person working on a project, interfaces can be less
> > useful unless you know how to use them well.  Putting them in just to
> > put them in serves no purpose other than bloating your code.  But,
> > sometimes you need to do that in order to figure them out.
> >
>
> I'd even go as far as saying that if you don't know what they are, you
> probably don't need them ;-)
> In your typical every day Flex/Flash type of applications they're
> (usually) overkill'll.
>
> You'll see them used in frameworks and microarchitectures, like the Flex
> framework, Cairngorm, etc..
> So they're more of an API-thing rather than an RIA-thing (if that makes
> sense).
>
> Have a look at the available flex framework interfaces (they typically
> begin with a capital I):
> http://livedocs.adobe.com/flex/3/langref/all-index-I.html
>
> regards,
> Muzak
>
> _______________________________________________
> Flashcoders mailing list
> [email protected]
> http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
>



-- 
Omar M. Fouad - Digital Emotions
http://www.omarfouad.net

This e-mail and any attachment is for authorised use by the intended
recipient(s) only. It may contain proprietary material, confidential
information and/or be subject to legal privilege. It should not be copied,
disclosed to, retained or used by, any other party. If you are not an
intended recipient then please promptly delete this e-mail and any
attachment and all copies and inform the sender. Thank you.
_______________________________________________
Flashcoders mailing list
[email protected]
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders

Reply via email to