Thursday, September 6, 2007
I am building out an AIR application where I am basically learning AIR as I build. I can't wait until AIR is out of beta and into a release so I can go out and purchase a proper Reference Book on all the sweet APIs. A cookbook would indeed be nice as well. Anyway, the whole framework is a joy and does so much heavy lifting that its quite a lot of fun, even when perplexed over something that seems like it will be easy but as of yet the code has been undiscovered by me at that moment. Strange sentence there.
I haven't been coding much AS3 until now, with the penetration numbers out and looking so shiny, I thought it best to start diving in on a much more regular basis. Its so difficult to go back and code things in AS2 now (except for AS3 components... I haven't really tried that yet, is there a very concise guide available anywhere in regards to this yet? Or I imagine a book must be in the works -- I'll buy it).
I've had Moxie crap out on me a little... namely in the application XML file for AIR... when playing with the rootContent node, I'd set the application to no chrome, test it, then set it back to standard, and it seems like Moxie was caching the value... it simply wouldn't see the change in the XML I just made. Odd that. Discovering lots of little things to place in the application MXML declaration to hide the status, hide Flex controls, etc. Fun this. A fine day indeed.
1 Comments:
-
Mike J said...
-
“Sounds like good fun. Have you done any experimentation with compiling AIR from strictly Flash Develop ? I haven't seen any information on it yet personally, though I'd love to figure out that workflow and start playing with it.
Also, any links you'd recommend on getting started with creating AIR apps ?”






