Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: flex-dev@incubator.apache.org
Received-SPF: softfail (nike.apache.org: transitioning domain of
 david@davidarno.org does not designate 209.85.212.175 as permitted sender)
Received-SPF: pass (google.com: domain of david@davidarno.org designates
 10.180.86.105 as permitted sender) client-ip=10.180.86.105;
From: "David Arno" <david@davidarno.org>
To: <flex-dev@incubator.apache.org>
Subject: RE: [gosh] Compiler choice [was Goshawk language choices and more]
Date: Tue, 21 Feb 2012 10:06:36 -0000
Message-ID: <01f501ccf080$7f755da0$7e6018e0$@davidarno.org>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
Thread-Index: AczwgH67B+Y+kNvrQf6zJF0rfBQyRA==
Content-Language: en-gb

> From: Omar Gonzalez [mailto:omarg.developer@gmail.com] 
> Sent: 20 February 2012 15:19
>
> Just wanted to point out here that according to Gordon Smith, I believe,
> the statement that we would have to deal with MXML in the compiler post 
> donation is incorrect...
I sought clarification on this from Deepa at Adobe's Update on Flex session
in London last night. Apparently there will basic MXML support in the
compiler when it is released to Apache at the end of the year, but Adobe
fully expect the community to have to do most of the work in getting full
MXML support into the compiler. I did ask if they could release the MXML
part to us earlier so that we can start work on it sooner, but the answer
was no, for the two are too tightly bound together.

Frustrating, but not unexpected, news I feel.

David.