This is something I've come back to a few times, and put a bit of thought into.
Seems like its been on a few people's minds! :-)
Using movieclips for classes and duplicates for instances is not too complex, and passing objects by reference could be achieved
too, at the cost of a path evaluation for every object lookup. It's likely that you would have to enforce strict typing though, in
order for the compiler to be able to handle inheritance correctly. This is all a lot of memory overhead, programs would run
incredibly slowly and there is no attachMovie... But the real show-stopper really is garbage collection. You'd have to clean up all
of those movieclips manually. I couldn't even contemplate designing GC routines with only F4 bytecodes!
Peter
www.peterjoel.com
www.macromedia.com/go/team/
----- Original Message -----
From: "Nicolas Cannasse" <[EMAIL PROTECTED]>
To: "Open Source Flash Mailing List" <[email protected]>
Sent: Tuesday, July 19, 2005 9:10 AM
Subject: Re: [osflash] MTASC for FlashLite
I was thinking about this recently also. I think Richard gave a good
summary of the points to consider. Something else to think about is how
tied some developers might be to the IDE with the new emulator that will
be included. Kevin Lynch talked about the emulator and showed it in
action at the FlashForward keynote. I think it's probably best to wait
and see what the demand/interest is for a Flash Lite MTASC version.
Tim
I would like to add that I have no experience with FlashLite right now, but
if the required bytecode version is Flash5, it might need some additionnal
work. However, there is no big problem at using AS2 syntax and typechecking
for targetting Flash5. If it's really Flash4 then it's more more difficult.
Nicolas
_______________________________________________
osflash mailing list
[email protected]
http://osflash.org/mailman/listinfo/osflash_osflash.org
