Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: flex-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of omuppi1@gmail.com designates
 209.85.217.175 as permitted sender)
MIME-Version: 1.0
Sender: omuppi1@gmail.com
In-Reply-To: <20121018175514.16881w6g9bbo5nlu@www.teotigraphix.com>
References: <CCA5B26E.11C44%timbert@adobe.com>
 <20121018175514.16881w6g9bbo5nlu@www.teotigraphix.com>
From: Om <bigosmallm@gmail.com>
Date: Thu, 18 Oct 2012 15:01:21 -0700
Message-ID: 
 <CACK5iZeyg7zORV6EsPDG=UsB=b1Hkdxca_YhYX45oXnKZQbXRA@mail.gmail.com>
Subject: Re: ASC 2.0 and Falcon
To: flex-dev@incubator.apache.org
Content-Type: multipart/alternative; boundary=f46d04071259d4ba3404cc5c8861

--f46d04071259d4ba3404cc5c8861
Content-Type: text/plain; charset=ISO-8859-1

>
> Just a heads up, given the architecture changes of the next-gen runtime,
> Flex will not be able to run in it. I would "highly" recommend you guys
> having a look at Feathers (work from Josh Tynjala - feathersui.com) on top
> of Starling, which will run beautifully in our next runtime.


Could you please give us some technical details as to why Flex wont be able
to run in the new runtime?  This would help us figure out what we can/need
to do given where we are currently.

Of course, any other information you can provide to help us move Flex
towards Stage3D/Starling would be beneficial.

Thanks,
Om


On Thu, Oct 18, 2012 at 2:55 PM, Michael Schmalle
<apache@teotigraphix.com>wrote:

> Quoting Thibault Imbert <timbert@adobe.com>:
>
>  Hi Mike,
>>
>> This is true, but ASC is already moving to ASNext targeting the next
>> generation runtime which is targeting game developers. So our resources
>> are assigned to that and the time we have to take ASC 2.0 changes to
>> Falcon, are limited. Gordon will bring key/showstopper bugs fixed in ASC
>> 2.0 to Falcon, we cannot commit to anything more.
>>
>> Just a heads up, given the architecture changes of the next-gen runtime,
>> Flex will not be able to run in it. I would "highly" recommend you guys
>> having a look at Feathers (work from Josh Tynjala - feathersui.com) on
>> top
>> of Starling, which will run beautifully in our next runtime.
>>
>
> I have just started working with Josh and this component architecture, it
> is very nice. I spoke of feathers earlier today and was talking with Josh
> about MXML support.
>
> So your saying there needs to be a component framework developed that will
> run in the new architecture to be cross compatible? I don't quite
> understand what you are saying.
>
> Mike
>
>
>
>
>  Some videos:
>>
>> https://vimeo.com/51010861
>> http://www.youtube.com/watch?**v=DGRy7H17MkA&feature=youtu.**be&hd=1<http://www.youtube.com/watch?v=DGRy7H17MkA&feature=youtu.be&hd=1>
>>
>>
>> Thibault Imbert | sr. product manager gaming (Graphics, Language, VM,
>> Compiler) | Monocle | adobe systems
>> gaming.adobe.com <http://gaming.adobe.com/> | bytearray.org
>> <http://bytearray.org/> | @thibault_imbert
>>
>>
>>
>>
>>
>>
>> On 10/18/12 11:36 AM, "labriola@digitalprimates.net"
>> <labriola@digitalprimates.net> wrote:
>>
>>  We have no plans keeping ASC 2.0 (and above) in sync with Falcon, as I
>>>> said previously, today the compilers are different projects and
>>>> targeting two different audiences.
>>>>
>>>
>>> Yeh, we totally get why parsing the AS language and generating bytecode
>>> will be very different for the game market. I can't imagine the amount of
>>> time you guys are spending on the differences in for loops alone....
>>>
>>> Mike
>>>
>>>
>>
>>
> --
> Michael Schmalle - Teoti Graphix, LLC
> http://www.teotigraphix.com
> http://blog.teotigraphix.com
>
>

--f46d04071259d4ba3404cc5c8861--