Well, it's gone Friday, so where's my new AIR app? Unfortunately, I can't give it you yet - although its nearly ready to be unleashed, I can't show it until the next issue of the E-Newsletter is sent out. (That's Marketing for you.) So you'll have to hang on for a few weeks yet.
Nevermind, eh? I certainly learnt a lot playing with Flex builder / Air / AS3, and here's hoping that I'll have some spare time to do a few articles on what I've learnt - pitfalls, theory, code snippets, that kind of thing.
One thing I realised is that your intrinsic knowledge of Flash and it's specialised coding methods mean very little working in Flex, but that certainly doesn't mean it's bad - Flash programming is probably a bit of a niché market in how it's done and works, and I get the impression that the Flex approach is a lot more mainstream theory-wise, so I'm prepared to put the effort into learning to code properly.I
Day 01 -
Starting - Getting to grips with the Flex interface - ripping off some existing examples from the 'net - I got a simple Panel / Accordian combo to read in a hardcoded URL feed.
Day 02 -
Reworking - Experimenting with the Flex components and rearranging our example page to explore how it all fits together. Separated the project into an MXML Application and an MXML Component, and then loaded multiple instances of the two.
Day 03 -
Dynamism - Added ability to add URLs at runtime, and used the Air Filesystem to load and save settings files. Explored Stylesheet skinning. Massive headaches getting to grips with the E4X XML format. Massive headaches working with the mx:Repeater tag and the general theories behind data-binding.
Day 04 -
Eppiphany - Added ability to delete URL feeds - Figured out fullscreen transparency, window settings and animation effects. Lots of cursing the apparent lack of dynamic object properties.
Day 05 -