Re: [flexcoders] Which AIR SDK to use with Flex?
The main issue is, as suggested, that ASC2.0 is not certified to compile MXML, only AS. If it worked in Ant, I’d guess you loaded the Flex SDK’s ant tasks which would run the Flex SDKs compiler. -Alex From: flexcoders@yahoogroups.commailto:flexcoders@yahoogroups.com flexcoders@yahoogroups.commailto:flexcoders@yahoogroups.com Reply-To: flexcoders@yahoogroups.commailto:flexcoders@yahoogroups.com flexcoders@yahoogroups.commailto:flexcoders@yahoogroups.com Date: Saturday, October 25, 2014 at 6:23 AM To: flexcoders@yahoogroups.commailto:flexcoders@yahoogroups.com flexcoders@yahoogroups.commailto:flexcoders@yahoogroups.com Subject: Re: [flexcoders] Which AIR SDK to use with Flex? 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' mark.jonk...@comcast.netmailto:mark.jonk...@comcast.net [flexcoders] flexcoders@yahoogroups.commailto:flexcoders@yahoogroups.com wrote: 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: flexcoders@yahoogroups.commailto:flexcoders@yahoogroups.com [mailto:flexcoders@yahoogroups.com] Sent: Thursday, October 23, 2014 12:40 PM To: flexcoders@yahoogroups.commailto:flexcoders@yahoogroups.com Subject: Re: [flexcoders] Which AIR SDK to use with Flex? [1 Attachment] [Attachment(s)https://us-mg6.mail.yahoo.com/neo/launch?.rand=4d328m9fkp613#TopText from Dave
RE: [flexcoders] Which AIR SDK to use with Flex?
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: flexcoders@yahoogroups.com [mailto:flexcoders@yahoogroups.com] Sent: Thursday, October 23, 2014 12:40 PM To: flexcoders@yahoogroups.com 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 j...@easypeasy.co.uk [flexcoders] flexcoders@yahoogroups.com wrote: [ https://us-mg6.mail.yahoo.com/neo/launch?.rand=4d328m9fkp613#TopText Attachment(s) from John McCormack included below] The link Read the ActionScript Compiler 2.0 (PDF, 20Kb) http://wwwimages.adobe.com/content/dam/Adobe/en/devnet/flashplayer/pdfs/adobe-actionscript-compiler-20-release-notes.pdf file explains that ... it does not support mxmlc compc compiling Flex applications Maybe its because some of Flex code is now run by Apache Foundation. John On 23/10/2014 16:26, Dave Glasser dglas...@pobox.com [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
Re: [flexcoders] Which AIR SDK to use with Flex?
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: flexcoders@yahoogroups.com [mailto:flexcoders@yahoogroups.com] Sent: Thursday, October 23, 2014 12:40 PM To: flexcoders@yahoogroups.com 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 j...@easypeasy.co.uk [flexcoders] flexcoders@yahoogroups.com 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 dglas...@pobox.com [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.
Re: [flexcoders] Which AIR SDK to use with Flex?
If you can also add the command line option -useLegacyAOT yes to make sure. The issues with new compiler 'fast compiler' seem to be with overridden methods not having same number of parameters and using swcs compiled with older versions of the compiler. So your mileage may vary from mine or others depending on your project. My project is huge so it would take hours to unwind issues caused by the fast compiler. Though my iOS builds which average 30min went down to 15 min with new compiler. Mark On Oct 25, 2014, at 10:23 AM, Dave Glasser dglas...@pobox.com [flexcoders] flexcoders@yahoogroups.com wrote: 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' mark.jonk...@comcast.net [flexcoders] flexcoders@yahoogroups.com wrote: 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: flexcoders@yahoogroups.com [mailto:flexcoders@yahoogroups.com] Sent: Thursday, October 23, 2014 12:40 PM To: flexcoders@yahoogroups.com 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
Re: [flexcoders] Which AIR SDK to use with Flex? [1 Attachment]
The link Read the ActionScript Compiler 2.0 (PDF, 20Kb)file http://wwwimages.adobe.com/content/dam/Adobe/en/devnet/flashplayer/pdfs/adobe-actionscript-compiler-20-release-notes.pdf explains that ... it does not support mxmlc compc compiling Flex applications Maybe its because some of Flex code is now run by Apache Foundation. John On 23/10/2014 16:26, Dave Glasser dglas...@pobox.com [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.
Re: [flexcoders] Which AIR SDK to use with Flex? [1 Attachment]
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
j...@easypeasy.co.uk [flexcoders] flexcoders@yahoogroups.com wrote:
#yiv2173584811 #yiv2173584811 -- #yiv2173584811
.yiv2173584811ygrp-photo-title{clear:both;font-size:smaller;height:15px;overflow:hidden;text-align:center;width:75px;}#yiv2173584811
div.yiv2173584811ygrp-photo{background-position:center;background-repeat:no-repeat;background-color:white;border:1px
solid black;height:62px;width:62px;}#yiv2173584811
div.yiv2173584811photo-title a, #yiv2173584811 div.yiv2173584811photo-title
a:active, #yiv2173584811 div.yiv2173584811photo-title a:hover, #yiv2173584811
div.yiv2173584811photo-title a:visited {text-decoration:none;}#yiv2173584811
div.yiv2173584811attach-table div.yiv2173584811attach-row
{clear:both;}#yiv2173584811 div.yiv2173584811attach-table
div.yiv2173584811attach-row div {float:left;}#yiv2173584811 p
{clear:both;padding:15px 0 3px 0;overflow:hidden;}#yiv2173584811
div.yiv2173584811ygrp-file {width:30px;}#yiv2173584811
div.yiv2173584811attach-table div.yiv2173584811attach-row div div a
{text-decoration:none;}#yiv2173584811 div.yiv2173584811attach-table
div.yiv2173584811attach-row div div span {font-weight:normal;}#yiv2173584811
div.yiv2173584811ygrp-file-title {font-weight:bold;}#yiv2173584811
#yiv2173584811 [Attachment(s) from John McCormack included below]
The link Read the ActionScript Compiler 2.0 (PDF, 20Kb)
explains that ... it does not support mxmlc compc compiling Flex applications
Maybe its because some of Flex code is now run by Apache Foundation.
John
On 23/10/2014 16:26, Dave Glasser dglas...@pobox.com [flexcoders] wrote:
#yiv2173584811 #yiv2173584811 -- #yiv2173584811
.yiv2173584811ygrp-photo-title{clear:both;font-size:smaller;height:15px;overflow:hidden;text-align:center;width:75px;}#yiv2173584811
div.yiv2173584811ygrp-photo{background-position:center;background-repeat:no-repeat;background-color:white;border:1px
solid black;height:62px;width:62px;}#yiv2173584811
div.yiv2173584811photo-title a, #yiv2173584811 div.yiv2173584811photo-title
a:active, #yiv2173584811 div.yiv2173584811photo-title a:hover, #yiv2173584811
div.yiv2173584811photo-title a:visited {text-decoration:none;}#yiv2173584811
div.yiv2173584811attach-table div.yiv2173584811attach-row
{clear:both;}#yiv2173584811 div.yiv2173584811attach-table
div.yiv2173584811attach-row div {float:left;}#yiv2173584811 p
{clear:both;padding:15px 0 3px 0;overflow:hidden;}#yiv2173584811
div.yiv2173584811ygrp-file {width:30px;}#yiv2173584811
div.yiv2173584811attach-table div.yiv2173584811attach-row div div a
{text-decoration:none;}#yiv2173584811 div.yiv2173584811attach-table
div.yiv2173584811attach-row div div span {font-weight:normal;}#yiv2173584811
div.yiv2173584811ygrp-file-title {font-weight:bold;}#yiv2173584811
#yiv2173584811 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.
