Flash Application development?...
I took the "red pill" and have been diving into the rabbit hole of Flash application development. At this point, I'm still not sure how deep the hole goes. :)
I've been working with Flex since late April and thought it was time to learn more about the underlying Flash technology. So, I worked thru the "Flash to the Core" book (by Josh Davis) and am currently reading thru "Essential Actionscript 2.0" (by Colin Moock). I still haven't finished the EAS2 book, but I've skimmed the OOP Application framework chapters and there's some interesting stuff in there. From what I understand of Flex, it seems that they are using a similar framework when they "compile" MXML to SWF. Basically, you have a "default" FLA file which does nothing other than 1) handle the preloader and 2) instantiate the "application" class and call it's init (or main) method. I haven't been able to verify this, but it seems to make sense. The MXML files are converted to AS classes and then "compiled" to SWF when Flex serves them up.
Interesting stuff, more later...
:)
I've been working with Flex since late April and thought it was time to learn more about the underlying Flash technology. So, I worked thru the "Flash to the Core" book (by Josh Davis) and am currently reading thru "Essential Actionscript 2.0" (by Colin Moock). I still haven't finished the EAS2 book, but I've skimmed the OOP Application framework chapters and there's some interesting stuff in there. From what I understand of Flex, it seems that they are using a similar framework when they "compile" MXML to SWF. Basically, you have a "default" FLA file which does nothing other than 1) handle the preloader and 2) instantiate the "application" class and call it's init (or main) method. I haven't been able to verify this, but it seems to make sense. The MXML files are converted to AS classes and then "compiled" to SWF when Flex serves them up.
Interesting stuff, more later...
:)
