Hello,

Recieved quite a few emails so, I will explain this a bit more.

These screen shots were taken pre-beta2, so this UI got trash canned. No need wasting time changing names and things. Basically, I was using the one panel drill down method in my debugger of previous but, have some new ideas.

You start by creating a project, this could be a FlexComponentProject or TutorialProject or whatever. Next if you created a FlexComponentProject you would set some source stuff like classpaths, analyze algorithm etc.

One of the main things you need to do is add some classpaths to the mix. The way I have programmed this is for ‘multiple mixing’. Basically you can load mulitple classpaths that obviously the compiler would not complain about name collisions. This way, once the Flex framework is out there, you can just add it to the classpaths list and get the full meal deal when parsing all of or your class dependencies(if on your own machine).

This image is parsing AS2 classes, oh yeah did I mention that I wrote an AS2 parser also? Well, anyway, this is where we start, alittle recusion happens, we find files and strucutre and this step is completed.
Source ::

This part is still being refactored. We have a three step process going here.

1) Analyze

2) Parser

3) Renderer

The analyzer can be fine tuned for what you want it to analyze and what you don’t want to analyze. This means speed up performance or slow down performance(with greater look ahead)

The parser is the main engine for getting it done. This is also a Builder pattern, so the product it returns is a IParserModel. The analyzer uses the same pattern.

The renderer; this talks more with the file system and is unique based on the format you need. Plus you could print straight from Flex using plugin component renderers.

Analyzer ::

The dependencies just shows how powerful my search algorithms are. This example selects one class, recursivly parses all of the dependencies through the imports. This is another performance feature that can branch off to where you do not need to actually analyze/parse a whole classpath. Plus some other things.

Dependencies ::

Anyway, I will be showing more things about this as the time grows near but, look for this as an entry to the Developer’s Derby that Adobe is sponsering in 1 month!

Oh yeah, I mentioned this was going to ONLINE as well as offline local.

Peace, Mike

This entry was posted on Wednesday, March 29th, 2006 at 3:25 pm and is filed under general, flex2, components, flex2 projects, as3, amfphp. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.