Huh. I was wondering about quite some mails I’ve received and different Twitter questions about: “How do I install the 3.2 AIR SDK in my FDT5?”. I didn’t think it’s such a deal but I’m gonna sum it up for you quickly now. And as I’ve once published a blogpost about “From Scratch to Device”, I actually thought of showing you this in a little video. Btw. I’m sorry I had to skip speech for this video as my voice is currently crippled by a flu and you really don’t want to hear me talking at the moment :) This by the way is again just a quick proof of concept. Of course the Debug-Workaround with 4.6 is around and FDT should set itself the app-descriptor right. But yea.. I hope you know what I mean.
Edit: Okay, I’ve heard that nobody knows what I mean :) The following video is a “How freaking fast can you deploy something with FDT?”. It’s actually a dirty example of starting a mobile project because I’d recommend to doublecheck the App-Descriptor and set up width&height there – as well as in the compiler-arguments. Furthermore you better set up the ADL before actually deploying the app so you get a better idea of how the mobile screen differs from your usual workflow. And setting up the ADL forces you to sort out your run configurations. So – of course the time doesn’t matter at all, but it’s nice to know in case you’re simply up for some tests.