And to be completely honest here, so you have the proper expectations;
I usually before starting something like the MXML task, turn up
psychedelic trance music really loud, stare at the screen for a couple
hours, write some code, refactor the code. Stare at it again for about
1 day, look through the falcon compiler source code and api for
another 4 hours. Return to my original code, with the trance music
still playing and finally start writing implementations. ;-)
That's how I do it and why I love not working for a company!
SideNote; My point is, inside I feel there is an answer to every
question in the world. The answer for MXML is waiting patiently to be
found. When the time comes to find it, it will be sitting in front of
us found.
That is why I said, for now I am finishing AS3, because the MXML
solution already exists, except in the future, not right now. ;-) heheh
Mike
Quoting Michael Schmalle <apa...@teotigraphix.com>:
Quoting Erik de Bruin <e...@ixsoftware.nl>:
Mike,
I'm not trying to get you to do stuff, certainly not 'out of order'.
First things first, and we'll have our hands full on AS -> JS, to be
sure.
Just thinking out loud: at some point I saw a video where an Adobe guy
explained one of the early FalconJS prototypes (Pete?) and he worked
around MXML by using intermediary MXML -> AS output and stuff that
through his compiler, instead of working directly on MXML. At some
point (after all else is said and done), might that be an option?
Are you talking about producing a Class for the MXML file, then
parsing the class?
MXML WILL get done. I spent 2 hours last night looking at all the
HACKING Alex had to do, to get it "working".
Mike
EdB
On Fri, Jan 18, 2013 at 12:49 PM, Michael Schmalle
<apa...@teotigraphix.com> wrote:
Erik,
MXML comes after ActionScript. Sorry but I have to do things in order. This
is where projects go wrong, where people start cutting corners and skipping
things they should finish. 10 years experience with this stuff and various
architectures tells me finish the foundation before we do anything
else that
is external to the core cross compiler.
Remember, MXML is not ActionScript and the first order of business is an
AS3->JS cross compiler, MXML is Flex specific.
I have a flaming blog post on deck about this project.
As far as doing things with AST IE MXML AST, I can manage anything here I
just need to finish something before I completely focus on MXML.
Mike
Quoting Erik de Bruin <e...@ixsoftware.nl>:
Mike,
how does that relate to MXML (if at all...)?
wrt. MXML, will you (someone) be able to take what Alex did for
FalconJS and put that in FalconJx, or does it not work like that?
I'm trying to get a feeling for where we are in relation to the two
other Falcons and MXML seems to be a big thing for both of them...
Thanks,
EdB
On Fri, Jan 18, 2013 at 12:19 PM, Michael Schmalle
<apa...@teotigraphix.com> wrote:
Hey all,
Since the project is really taking shape thanks to our great cooperation,
I
am going to focus on the nemesis I have left and that is finishing of the
ActionScript emitter.
This project blew up fast with Erik contributing, I didn't get a chance
to
fully finish the ActionScript impl. Yes, I might have plans down the road
to
make a read/write AS DOM and having a fully functional AS3 emitter is
essential.
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
--
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
--
Michael Schmalle - Teoti Graphix, LLC
http://www.teotigraphix.com
http://blog.teotigraphix.com
