Hmm.
I understand what you are saying but that is what the walker is for
because most output is never going to translate to the existing
structure of what will be output as the case with FlexJS and it's data
structures. In AS we have a 1 to 1 relationship with the AST to source
code.
I see this as duplicate work considering in MXML you are basically
cherry picking what you need and creating an internal model based on
the data parsed which then you will loop through and create the js
class.
But, that is just the way I see it. :)
Mike
Quoting Erik de Bruin <[email protected]>:
Mike,
The idea is to create the same "input == output" tests for MXML as you
did for AS, to check if the emitters are handling all input correctly.
Inheriting from those verifiably 'correct' MXML emitters I will create
JS output, both for FlexJS and VanillaSDK (initially, but others might
be added later), similar to how we do both AMD and 'goog' JS output
from extending the AS emitter class. MXML in my view is a second input
type, next to AS.
EdB
On Wed, Mar 6, 2013 at 7:30 PM, Michael Schmalle
<[email protected]> wrote:
Erik,
I'm just looking at some of the things you have been working on.
I'm a bit confused... My understanding was the MXML emitters needed to
produce relevant AS code of FlexJS IE Alex's data structures.
Am I missing something obvious here that was discussed between you and Alex?
When I created the base walker and emitter I never had intentions of
producing MXML source code from the MXML AST DOM.
Mike
--
Michael Schmalle - Teoti Graphix, LLC
http://www.teotigraphix.com
http://blog.teotigraphix.com
--
Ix Multimedia Software
Jan Luykenstraat 27
3521 VB Utrecht
T. 06-51952295
I. www.ixsoftware.nl
--
Michael Schmalle - Teoti Graphix, LLC
http://www.teotigraphix.com
http://blog.teotigraphix.com
