Ok,

We are on the same page now. I just committed the preliminary MXML traversing and how to get it working with the backends.

There is one test that is really hack that I need to clean up, I haven't figured out how I want to unit test this yet. Whatever...

Still in the tinkering phase.

Mike

Quoting Michael Schmalle <apa...@teotigraphix.com>:


Quoting Erik de Bruin <e...@ixsoftware.nl>:

Ok, I've resolved a few minor conflicts and committed my code for
FalconJx. I completely agree on the formatter thing, the whitespace
stuff is already driving me nuts. I'll follow your lead.

I will get this together, I will set mine up to look as much like Falcon does with it's formatting. Then we will just use the same one, I wonder where we should put it... for other to be able to use if they use Eclipse.


I'll work on the publisher app a bit, but I must say, for a Monday,
things aren't going half bad. I have an AS project with a very simple
MXML to get AS access to spark components, and a 'large' AS file that
will show a button and a label, with a simple click event and handler,
all Flex SDK (spark).

It's an interesting idea, and I never thought about trying to emulate the Spark components in JavaScript. I will be interested how you do with it.

The publisher app takes that AS project, runs it through FJx, runs the
resulting JS project through the 'goog' 'depswriter' script to get
only the library files actually used by the project, adds an
index.html from a template and enters the JS dependencies and then
launches the resulting HTML. So, with a bit of tweaking on my new JS
framework (VanillaSDK, couldn't resist ;-)) and maybe even some of
your MXML magic (no pressure!), in the coming days we should see
something that might open the door to the future of the Flex SDK with
web native playback.

Word, MXML is interesting because it "is" something but it can be anything at the same time. It just depends on what you want it to be. I'll tell you what is crazy, being in the visitDocument method and getting all the Script blocks, looping through there IASNode array and calling getWalker().walk(node) on each of them and it spits out goog javascript right there in the MXML walker, pretty crazy. :)


Or I'll stumble upon a deal breaker; I'll give you even odds on that
happening :-)

Seems like there is innovative electricity in the air, never know where it will take you.

Don't worry about the commit and merge, I will just add my stuff back, it was my fault, I knew your were working on something and I compulsively did the commits. :) Another reason using static utility classes temporarily make sense sometimes.


Mike


EdB



On Mon, Jan 21, 2013 at 10:10 PM, Michael Schmalle
<apa...@teotigraphix.com> wrote:
I'm done, so do what you need to do, I promise I won't touch any files in
SVN until I see your new stuff.

I didn't change much that should affect you really. I haven't committed the
MXML specific api files yet, I'm waiting to get those more concrete but
things are working!

I have the ASBlcokWalker composited in the MXMLBlockWalker perfectly,
sharing the main GoogEmitter in the main walker. This design is showing it's
merit now!

So commit. I'm just going to work on the MXML stuff again. And yeah that is
your Main.mxml file that is cross compiled right now. ;-)


Mike


Quoting Erik de Bruin <e...@ixsoftware.nl>:

Ah, ping me when you're done for the day, so I'll know when it's safe
to figure out where my stuff goes in the new improved scheme :-)

EdB



On Mon, Jan 21, 2013 at 10:05 PM, Erik de Bruin <e...@ixsoftware.nl>
wrote:

Awesome!

You go ahead, play for a while :-) Wouldn't want to break you out of
the zone. My changes can wait, I have other loose ends to tie up.

Have fun!

EdB



On Mon, Jan 21, 2013 at 10:03 PM, Michael Schmalle
<apa...@teotigraphix.com> wrote:

Err...

DO it NOW! :) I am on a roll and at a point where it's safe, let me
commit
one more tiny change.

Check this out. :)


goog.provide('Main');

goog.require('spark.components.Button');
goog.require('mx.events.FlexEvent');

/**
* @param {FlexEvent} event
*/
Main.prototype.creationCompleteHandler = function(event) {
       var /** @type {Example} */ main = new Example();
       this.addElement(main);
       main.init();
}

It's fun playing in the sand!


Mike





Quoting Erik de Bruin <e...@ixsoftware.nl>:

Mike,

In the interest of expediency, will you be checking in a lot more
today, or can I start to merge my local changes with your latest
commits?

EdB



--
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




--
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

Reply via email to