Mark, thanks for the reply.
I don't use Flex builder, just Apache ant and the Flex and AIR SDKs. I was able
to build the Flex/iOS app with both versions of the 15.0.0.302 SDK in their
default configurations, so I guess the one with the new compiler uses the old
one by default. (At least from the command line.) I'm going to stick with the
SDK without the new compiler though, just to be on the safe side.
On Saturday, October 25, 2014 9:39 AM, "'Mark R. Jonkman'
[email protected] [flexcoders]" <[email protected]> wrote:
#yiv7129954014 #yiv7129954014 -- #yiv7129954014
.yiv7129954014ygrp-photo-title{clear:both;font-size:smaller;height:15px;overflow:hidden;text-align:center;width:75px;}#yiv7129954014
div.yiv7129954014ygrp-photo{background-position:center;background-repeat:no-repeat;background-color:white;border:1px
solid black;height:62px;width:62px;}#yiv7129954014
div.yiv7129954014photo-title a, #yiv7129954014 div.yiv7129954014photo-title
a:active, #yiv7129954014 div.yiv7129954014photo-title a:hover, #yiv7129954014
div.yiv7129954014photo-title a:visited {text-decoration:none;}#yiv7129954014
div.yiv7129954014attach-table div.yiv7129954014attach-row
{clear:both;}#yiv7129954014 div.yiv7129954014attach-table
div.yiv7129954014attach-row div {float:left;}#yiv7129954014 p
{clear:both;padding:15px 0 3px 0;overflow:hidden;}#yiv7129954014
div.yiv7129954014ygrp-file {width:30px;}#yiv7129954014
div.yiv7129954014attach-table div.yiv7129954014attach-row div div a
{text-decoration:none;}#yiv7129954014 div.yiv7129954014attach-table
div.yiv7129954014attach-row div div span {font-weight:normal;}#yiv7129954014
div.yiv7129954014ygrp-file-title {font-weight:bold;}#yiv7129954014
#yiv7129954014 #yiv7129954014 #yiv7129954014 -- _filtered #yiv7129954014
{font-family:Helvetica;panose-1:2 11 6 4 2 2 2 2 2 4;} _filtered #yiv7129954014
{font-family:Wingdings;panose-1:5 0 0 0 0 0 0 0 0 0;} _filtered #yiv7129954014
{panose-1:2 4 5 3 5 4 6 3 2 4;} _filtered #yiv7129954014
{font-family:Calibri;panose-1:2 15 5 2 2 2 4 3 2 4;} _filtered #yiv7129954014
{font-family:Tahoma;panose-1:2 11 6 4 3 5 4 4 2 4;} _filtered #yiv7129954014
{font-family:Verdana;panose-1:2 11 6 4 3 5 4 4 2 4;}#yiv7129954014
#yiv7129954014 p.yiv7129954014MsoNormal, #yiv7129954014
li.yiv7129954014MsoNormal, #yiv7129954014 div.yiv7129954014MsoNormal
{margin:0in;margin-bottom:.0001pt;font-size:12.0pt;}#yiv7129954014 a:link,
#yiv7129954014 span.yiv7129954014MsoHyperlink
{color:blue;text-decoration:underline;}#yiv7129954014 a:visited, #yiv7129954014
span.yiv7129954014MsoHyperlinkFollowed
{color:purple;text-decoration:underline;}#yiv7129954014 p
{margin-right:0in;margin-left:0in;font-size:12.0pt;}#yiv7129954014 tt
{}#yiv7129954014 p.yiv7129954014ygrp-photo-title, #yiv7129954014
li.yiv7129954014ygrp-photo-title, #yiv7129954014
div.yiv7129954014ygrp-photo-title
{margin-right:0in;margin-left:0in;text-align:center;font-size:10.0pt;}#yiv7129954014
span.yiv7129954014EmailStyle20 {color:#1F497D;}#yiv7129954014
.yiv7129954014MsoChpDefault {font-size:10.0pt;} _filtered #yiv7129954014
{margin:1.0in 1.0in 1.0in 1.0in;}#yiv7129954014 div.yiv7129954014WordSection1
{}#yiv7129954014 _filtered #yiv7129954014 {} _filtered #yiv7129954014
{font-family:Symbol;}#yiv7129954014 ol {margin-bottom:0in;}#yiv7129954014 ul
{margin-bottom:0in;}#yiv7129954014
I’m guessing it mostly has to do with mxml compiling. The old compiler would
have to handle both types of input – ActionScript and MXML and generate
ActionScript code based on the MXML and then generate the final product. If
your Adobe and you no longer support MXML yourself then there is no reason to
keep it around in future generations of the compiler – especially where speed
becomes an issue. I hit a lot of problems this week with the new fast
compiler. AIR SDK 15 switched from using the legacy compiler to the new fast
compiler as its default compiler. My project uses just a small portion of the
FLEX framework – just enough stuff to connect with the backend server running
BlazeDS and sending stuff over AMF. As a matter of fact we actually put the
classes we used into our own project and as far as we knew, no longer linked
against any of the Flex framework SWCs. However after the switch to the new AIR
SDK 15 the project started blowing chunks. It would not find about 8 interfaces
and classes from the Flex framework. Eventually I traced it down to possible
being the swc cache that Flash Builder stores in the workspace .metadata folder
(I think). I deleted all the files in the swc cache and the errors finally
went away. It took hours to track that down. Then I finally got the project
compile into an iOS IPA file and installed it on my iPad – crash after a few
seconds of running. AIR simulator no problem, iOS Simulator no problem. But a
debug or release runtime and crash.. Then I realized that they had changed the
default compiler to the fast, switched back to the legacy AOT compiler and
everything worked perfectly. Unfortunately if iOS is your target you have
almost no choice but to upgrade to AIR SDK 15. Apple changed the requirements
for uploading and all the old SDKs will not produce an IPA that will be
accepted (unless you experiment with changing the linker and that sounded more
like Voodoo then a long term solution). And the AIR SDK must be the one from at
least Oct 14, 2014. If you did not already know – The AIR SDK is located in
two places one is the Flash Builder 4.7/eclipse/plugin folder (Used by
ActionScript projects) and the other is in the Flash Builder 4.7/sdks folder.
The plugin folder is for ActionScript only projects and the other in the sdk
folder is for Flex projects. At least as near as I can determine. I would
download the default AIR SDK to use with any ActionScript projects – it’s the
SDK that gets put into the eclipse/plugin/actionscript compiler…. Location.
For Flex projects, download the alternative and drop it into the sdks/4.6.0
folder in Flash Builder. This way you have both compilers setup and useable
based on the type of project your working on. If you hit the same situation I
did with iOS output, then on the project settings, iOS settings – click
customize launch button, click add parameter, enter –useLegacyAOT for name and
for value enter yes. Then click the before.. radio button and choose
–provisioning_profile (or something like that). I don’t have my work computer
open so I might be off on a couple of name of the before radio button and the
entery in the drop down list – but it’s the only entry with provision profile
or similar in the name. Sincerely
Mark R. Jonkman From: [email protected]
[mailto:[email protected]]
Sent: Thursday, October 23, 2014 12:40 PM
To: [email protected]
Subject: Re: [flexcoders] Which AIR SDK to use with Flex? [1 Attachment]
[Attachment(s) from Dave Glasser included below]
From the PDF I gather that you can't build Flex apps with the AIR SDK, which
makes sense. But the notice on the page suggests that you should not package
Flex Apps as AIR apps using the full AIR SDK, but rather the stripped down AIR
SDK. I tried using the ADT from the full AIR SDK to package my Flex app for iOS
and it works. So I'm wondering why Adobe has a separate AIR SDK for Flex apps.
I wouldn't think the minor difference in download file sizes would be the sole
reason. On Thursday, October 23, 2014 12:20 PM, "John McCormack
[email protected] [flexcoders]" <[email protected]> wrote:
[Attachment(s) from John McCormack included below] The link "Read the
ActionScript Compiler 2.0 (PDF, 20Kb)"
explains that "... it does not support mxmlccompccompiling Flex applications"
Maybe its because some of Flex code is now run by Apache Foundation.
John
On 23/10/2014 16:26, Dave Glasser [email protected] [flexcoders] wrote:On the
download page for the AIR SDK:
http://www.adobe.com/devnet/air/air-sdk-download.html It says: Note: Flex
users will need to download the original AIR SDK without the new compiler. and
provides separate links to SDKs that are about 15% smaller. Does anyone know
the reasoning behind this? Are there compatibility reasons not to use the main
AIR SDK that has a compiler? I'm still compiling my SWF with the compiler from
the Flex SDK.
