Hi, To explain a little more my request, I explain you a new time more precisely.
Adobe, with AIR 3.7, scared us because they decided without consulting anyone not to be compatible with Flex. When I saw this ad, I voted directly to try to make things happen, but the damage is done, Adobe gives us a reprieve compatibility. If Adobe maintains compatibility as long as possible, that's good, but we are not protected that they do it again. So I analyzed our projects with Apache Flex 4.9 and AIR 3.6, and I say that a solution exists to anticipate Adobe decisions: migrate our Flex MXML projects TO "AS3 Project". The biggest problem would be to re write parts of the Flex framework that we used in "Pure AS3". So my idea would be whether the Flex framework can be compiled "Pure AS3" without any MXML file, as it could still use the Spark components, and all the Flex environment, but we "just" need to migrate our projects "pure AS3 "too. I think the best sustainable solution could be this one: to continue to develop the Flex framework, but in "Pure AS3", without any MXML. This could allow people to use in projects "Pure AS3" with ASC 2.0 and Scout easily. And if not, wait for the Falcon compiler if people want to continue to develop in MXML. This could give a "second life" for the Flex framework. What do you think? -----Message d'origine----- De : Alex Harui [mailto:aha...@adobe.com] Envoyé : jeudi 11 avril 2013 20:28 À : dev@flex.apache.org Objet : Re: [jira] [Commented] (FLEX-33445) Provide Flex librairies in pure AS3 I think it was something about Scout showing AS files in its UI? On 4/11/13 10:34 AM, "OmPrakash Muppirala" <bigosma...@gmail.com> wrote: > On Thu, Apr 11, 2013 at 8:52 AM, Alex Harui <aha...@adobe.com> wrote: > >> I haven't tried Scout myself, but I thought it couldn't show you MXML >> files. >> I'd be glad to be wrong. >> >> > I have been using this method to enable advanced telemetry in my Flex > apps for profiling with Scout: [1] > > Although, I am now curious to know if some features of Scout are > disabled for MXML content. > > Thanks, > Om > > [1] > http://renaun.com/blog/2012/12/enable-advanced-telemetry-on-flex-or-ol > d-swfs-w > ith-swf-scount-enabler/ > > >> >> On 4/11/13 8:45 AM, "OmPrakash Muppirala" <bigosma...@gmail.com> wrote: >> >>> On Apr 11, 2013 8:14 AM, "Alex Harui" <aha...@adobe.com> wrote: >>>> >>>> Also, an AS-only project would work better with the Scout profiler. >>> That's >>>> another reason I'm trying to change Falcon codegen for MXML to >>>> generate >>> more >>>> data instead of code, so the parts you can't see don't matter. >>>> >>>> >>> >>> I can profile my current Flex projects with Scout just fine. What >>> kind >> of >>> advantages would an AS only project have? >>> >>> Thanks, >>> Om >>> >>>> On 4/11/13 4:27 AM, "Justin Mclean" <jus...@classsoftware.com> wrote: >>>> >>>>> Hi, >>>>> >>>>>> Interesting... I'd like to see how far they can take that. Not >>>>>> sure why though >>>>> >>>>> I think the original intention was to get AIR 3.7 with the ASC 2.0 >>> working >>>>> with their project but again not 100% sure. A little has been lost >>>>> in translation I think :-) >>>>> >>>>> Justin >>>> >>>> -- >>>> Alex Harui >>>> Flex SDK Team >>>> Adobe Systems, Inc. >>>> http://blogs.adobe.com/aharui >>>> >> >> -- >> Alex Harui >> Flex SDK Team >> Adobe Systems, Inc. >> http://blogs.adobe.com/aharui >> >> -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
