Quoting Gordon Smith <gosm...@adobe.com>:
I don't object to generating a data structure for V11, but I think
that it makes more sense to do that as a second phase after ABC
generation is working. Otherwise there are a lot of moving parts and
progress will be slower.
Correct me if I'm wrong Alex, but Gordon, I think Alex was talking
about JavaScript data structures produced during crosscompile of MXML.
In Alex's new component prototype he is using descriptor object that
translate MXML tags to a JS Array; IE
override public function get uiDescriptors():Array
{
return [
Label,
null,
"lbl",
2,
"x", 100,
"y", 25,
0,
1
}
Mike
- Gordon
-----Original Message-----
From: Gordon Smith [mailto:gosm...@adobe.com]
Sent: Friday, November 30, 2012 10:54 AM
To: flex-dev@incubator.apache.org
Subject: RE: [FlaconJS] pseudo emitter algorithm
Before I do much more work on Falcon's MXML, we need to decide
whether we're completing MXML->ABC or discarding that work.
- Gordon
-----Original Message-----
From: Alex Harui [mailto:aha...@adobe.com]
Sent: Friday, November 30, 2012 10:46 AM
To: flex-dev@incubator.apache.org
Subject: Re: [FlaconJS] pseudo emitter algorithm
On 11/30/12 10:33 AM, "Michael Schmalle" <apa...@teotigraphix.com> wrote:
My point is, we would create a .js generator for MXML dialect. It
"might" even be adeventagious for us to create this implementation
becasue we "could" treat some parts of MXML differently than a plain
ole ActionScript class.
Yup, but keep in mind that I'm planning to check in code where MXML
generates mostly a data structure, and very little code.
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
--
Michael Schmalle - Teoti Graphix, LLC
http://www.teotigraphix.com
http://blog.teotigraphix.com
