Re: [FalconJx] MXML implementation notes

2013-01-22 Thread Alex Harui
On 1/21/13 6:46 AM, Michael Schmalle apa...@teotigraphix.com wrote: Ok here is the deal. As of now Alex is using a descriptor type emittion. Creating init objects that initialize a DOM instance. I wrote up the descriptor format. Of course, there could be errors and cases I haven't

Re: [FalconJx] MXML implementation notes

2013-01-21 Thread Michael Schmalle
Alex, Responding inline would be to much of a mess. Basically half of my post was about the data spec. So you asking if I am looking for the data spec, my answer would be yes. I'm just trying to write a list of things I need to generate. To reiterate, I understand we are generating data

Re: [FalconJx] MXML implementation notes

2013-01-21 Thread Michael Schmalle
Quoting Erik de Bruin e...@ixsoftware.nl: On Mon, Jan 21, 2013 at 1:48 PM, Michael Schmalle apa...@teotigraphix.com wrote: he I'm not at all sure I understand the details of what you're discussing, so I'll just ask this one rookie question: will I be able to create something like a

Re: [FalconJx] MXML implementation notes

2013-01-21 Thread Erik de Bruin
Mike, Just to ease my confused mind: Of course, I am writing things along the same lines as the AS visitors BUT there is a semantic difference that we are not exactly translating MXML AST to js, so I need a bit more time figuring out the abstractions. not EXACTLY translating, what does that

Re: [FalconJx] MXML implementation notes

2013-01-21 Thread Michael Schmalle
Ok here is the deal. As of now Alex is using a descriptor type emittion. Creating init objects that initialize a DOM instance. So the ASJS emitter would load up a values object that when the component is created, is populated by those descriptors. Your method is different. Put it this

Re: [FalconJx] MXML implementation notes

2013-01-21 Thread Michael Schmalle
Quoting Alex Harui aha...@adobe.com: There are probably a lot of other MXML-isms like the classfactory handling. But my hope is to get rid of as many as we can. Most if not all of this code gen can be handled better by code in the framework interpreting data. Really, if was practical to

Re: [FalconJx] MXML implementation notes

2013-01-21 Thread Alex Harui
On 1/21/13 9:02 AM, Michael Schmalle apa...@teotigraphix.com wrote: Quoting Alex Harui aha...@adobe.com: There are probably a lot of other MXML-isms like the classfactory handling. But my hope is to get rid of as many as we can. Most if not all of this code gen can be handled better

RE: [FalconJx] MXML implementation notes

2013-01-21 Thread Michael Schmalle
, January 20, 2013 1:50 PM To: dev@flex.apache.org Subject: [FalconJx] MXML implementation notes Hi, Alex this one is aimed at you. I have been studying what you have done for the whole day today and managed by copying about 1000 various lines of code to my prototype MXML emitter got your

RE: [FalconJx] MXML implementation notes

2013-01-21 Thread Gordon Smith
, 2013 10:19 AM To: dev@flex.apache.org Subject: RE: [FalconJx] MXML implementation notes Gordon, every time you reply to something I say, it seems like I'm offending you. I really am not. :) What I meant to say was ActionScript AST flows naturally out to String source code, where as MXML requires

RE: [FalconJx] MXML implementation notes

2013-01-21 Thread Michael Schmalle
, and are sometimes ignored such as with p representing an instance of ParameterElement in TLF. - Gordon -Original Message- From: Michael Schmalle [mailto:apa...@teotigraphix.com] Sent: Monday, January 21, 2013 10:19 AM To: dev@flex.apache.org Subject: RE: [FalconJx] MXML implementation notes

[FalconJx] MXML implementation notes

2013-01-20 Thread Michael Schmalle
Hi, Alex this one is aimed at you. I have been studying what you have done for the whole day today and managed by copying about 1000 various lines of code to my prototype MXML emitter got your Fragment lists to be populated by my traversal. Now the question is, can you in about 5-6