The process of generating a .AIR (or .AIRI) is actually generating a .SWF with the AIR internals linked, then passing it to the AIR packager (which takes that SWF and puts its packaging around it.
If you've ever broken apart a .apk, you will see a bunch of runtimes and a huge chunk of code that is a straight SWF. I'm playing with semantics on that a bit -- because the end user won't ever really see the SWF file as the intermediate. Do you have a better way to word that? I'll fix the project history page. That was imported straight from our existing site (it was one page that had some pretty inconstant MDTEXT that I was testing my import script on). -Nick On Wed, Feb 10, 2016 at 12:41 AM, Justin Mclean <justinmcl...@me.com> wrote: > Hi, > > > You can see a preview of it here : http://flex.suroot.com > > Looking good. > > A couple suggestions: > - list the dates in reverse order on the project history page > - I thought the facebook, twitter and linked in buttons were for Apache > (given there proximity to the Apache logo) rather than Flex. Perhaps put > them under the text below them? > > While I like this: > "The Open-Source ActionScript Framework that creates web, mobile, desktop > applications from a single code-base as either JavaScript or SWF.” > > id “or SWF” actually correct when referring to AIR applications? > > Thanks, > Justin > >
