incubator-flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "" <>
Subject Re: ASC 2.0 and Falcon
Date Thu, 25 Oct 2012 19:44:05 GMT
I had seen that before but had forgotten , thanks for pointing this out, so to summarize any
4.6 based apps will at the very least run on whatever runtimes are put out by adobe for the
next 5 year's , that certainly allows for some time to figure out a forward path, pls correct
if that's the wrong conclusion

Sent from my Virgin Mobile Android-Powered Device

----- Reply message -----
From: "Om" <>
To: <>
Subject: ASC 2.0 and Falcon
Date: Thu, Oct 25, 2012 3:08 pm

From the Adobe Flex Whitepapaper [1]

Adobe runtime support of Flex
> Flash Player 11.2 and Adobe AIR 3.2, which are anticipated to ship in the
> first quarter of 2012, will be tested with applications built using Adobe
> Flex 4.6. *Adobe will test future releases of Flash Player and AIR
> against the Adobe Flex 4.6 SDK and maintain backwards compatibility for
> five years.*



On Thu, Oct 25, 2012 at 12:03 PM, sébastien Paturel

> Hi Thibault,
> Thanks for the precision.
> But one last info needed: will next AIR for mobile runtime will embed only
> the new vm? meaning that only ASNext projects will be able to run with AIR
> on new mobile devices / OS targetted by Adobe?
> Thanks
> Seb
> Le 25/10/2012 17:53, Thibault Imbert a écrit :
>  Hi Sebastien,
>> To confirm, such a framework like Feathers or Starling would have to be
>> updated to ASNext to run on the new VM.
>> Sent from mobile, please pardon brevity/errors.
>> ______________________________**__
>> From: sébastien Paturel
>> Sent: 10/25/2012 8:45 AM
>> To:
>> Subject: Re: ASC 2.0 and Falcon
>> In the short term, it will be needed by flex to run on VM3, to be able
>> to create apps for new mobile hardware, and run better on retina Display.
>> According to jonathan Campos, it is feasable to render flex sdk on
>> starling for the next main release.
>> And if i understand well what thibault said, we don't need anything more
>> then that to run on next VM (for example no need to be AS4)
>> "having a look at Feathers (work from Josh >Tynjala - on
>> top of Starling, which will run beautifully in our next runtime"
>> It still has to be confirmed, but it could be a good short term solution
>> (still relying on Adobe's runtime), to let flex the time to do more deep
>> mutli target long term changes, even if it means starting again from
>> scratch.
>> If the solution is to start over, it could be the perfect time to ask if
>> AS3 is the better choice for a multi target language, and if flex should
>> not leverage what has been done with haxe.
>> thats the question i was asking to Alex (i was not meaning AS4)
>> jangaroo is great, but only for JS transcompilation, and future flex
>> will need to target more platforms, like Haxe does.
>> i wonder how jangaroo resolved issues with AS3 to JS compilation, that
>> haxe resolved by dropping the feature directly from the language?
>> Le 25/10/2012 17:01, Kevin Newman a écrit :
>>> On 10/18/12 7:28 PM, Gordon Smith wrote:
>>>> Yes, the community has to figure out what the essence of Flex really
>>>> is. To me, it's an rapid-development application framework, the
>>>> combination of a procedural language with a declarative language, and
>>>> a widely-deployed runtime that can support RIAs. The runtime of the
>>>> future for RIAs seems to be native code for mobile devices and
>>>> HTML/Javascript for browser apps. The best procedural language is
>>>> anything that can be compiled to these runtimes. MXML is a perfectly
>>>> good declarative language for UIs.
>>> Maybe the real discussion should be less about supporting AVM3 and
>>> more about supporting a native compile framework - something like haXe
>>> NME maybe (already open source). How much of Adobe's LLVM based iOS
>>> AOT source is open? (if any)
>>> For Javascript, there's already Jangaroo (open source):
>>> Kevin N.
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message