Ah, it’s an open source code solution. I’ve seen a lot of those. FAME isn’t fully open source, so I’m recommended to check AMES, but if Flashout is free, I don’t see any big problem with FAME or FAMES. Still, I don’t see much reason to use that stuff if you want a free animation tool. The best thing about the Flash IDE is how convenient it is. You load it and it has everything you need to make a game or an animation. If there’s an open source alternative to the Flash IDE, I’d love to see it, but everything I’ve seen focuses on the coding only.

In other words:

ASDT + Ant (The A is overloaded) :)
MTASC
Eclipse
Swfmill

Viva AMES!

type error MovieClip should be Test

at line >>> this = scope

type error MovieClip should be XMLExposer2 at line >>> this = scope

João Carlos

Thanks for the use cases — I can definitely see how it would be useful to use composition to add a level of abstraction in the manner you described — I’m just not sure whether the reference to the symbol you described belongs in your view or in your controller. eg. When you mention publishing drawing commands to or accepting click events from FCS — that sounds very much like business logic to me. What you do with these (eg. updating the presentation as a result of click events from FCS) are definitely view-related.

I used this sort of approach in my MXDU 2003 flash GIS application and I’m currently toying with it as the basis of a lightweight UI framework (yet another one).
You asked for a potential use case where a view wouldn’t extend MovieClip. In my toy framework there is only one symbol containing a bounds rectangle and each view instance “has-a” reference to an instance of the symbol on the stage.
The view classes aren’t movie clips – movie clips are specific to things on the stage of a Flash application, the views are more abstract and represent rectangular areas we can draw on and receive user interactions through – the methods and events might be the same or similar to a movie clip but the implementation of the methods could change – examples might include publishing the drawing commands to / accepting click and change events from an FCS stream (Flash VNC anyone?) or implementing an Excel-like “freeze panes” scroll view where one view is rendered on four movie clips with independant masks and scroll positions.
So, while most Flash application views will be movie clips, it doesn’t have to be the case all the time, in fact there is a fairly rich vein of possibilities to explore when you consider separating the two.

@Carlos: Regarding not making views inherit from MovieClip — I can’t think of any scenario where a view (in a Flash application) would not inherit from MovieClip (even if it extends, say, UIObject or some other form class, those would extend MovieClip, no?) Am I missing a potential use case?

Good to see you trying and enjoying FAME. I like your new approach to application init code too. Although I think both approachs are welcome as not always we need to inherith from MovieClip and make our application mc-dependent in each application view.

I think both are good practices and you must apply each one depending on your application’s necessity.

Look at the picture below the code to see what I mean… TRACE rocks!

http://www.jessewarden.com/archives/2005/05/fame_chronicles_1.html