> I haven't gotten through the whole source yet but I noticed preprocess things. > Have you allowed for preprocess and post process of AST/Compile from > something loaded from the outside? > I mean can I extend something without recompiling the project with my code > included.
I don't think so. What "preprocess things" did you notice? The old compiler had an extension-loading mechanism but the new one doesn't as far as I know. We now recommend using the ABC library to postprocess the compiled ABC rather than hooking into the compiler. But only real-world use cases will tell us whether that approach is viable. -Gordon -----Original Message----- From: teoti...@teotigraphix.com [mailto:teoti...@teotigraphix.com] Sent: Thursday, September 13, 2012 3:49 AM To: flex-dev@incubator.apache.org Subject: Re: Is there anything the community can do to help you testing or documenting Falcon and the build process? Quoting Alex Harui <aha...@adobe.com>: >> My top priorities currently are: > 0. Get the MXML handling working. I have been studying the source code quite intently and I have to say, there is a huge amount of potential in this code. Gordon and friends did a wonderful job coding this framework, nice. As this framework is huge, "Get MXML handling working" in my mind is a broad statement. Gordon, do you care to add a bit to this to those that feel like they want to start writing some code against this? BTW, the javadoc for this is incredible. Thank you very much for the effort put into the documentation. I haven't gotten through the whole source yet but I noticed preprocess things. Have you allowed for preprocess and post process of AST/Compile from something loaded from the outside? I mean can I extend something without recompiling the project with my code included. PS I'm up for framework code contribution, I will be the first to admit my experience with large build scripts, ant etc. is very limited so I will be most efficient working within the falcon java code. Mike >> 1. Get the top-level Ant targets working properly. For example, 'ant >> javadoc' >> currently produces compilation errors, probably due to a classpath >> problem, and 'ant main' produces an mxmlc which doesn't work due to >> another classpath problem that you noticed. >> >> 2. Document the build process, either on wiki pages or in the README >> file, so that people understand what environment variables need to be >> set and what Ant targets to use. >> >> 3. Create JUnit tests in which Falcon builds each of the SDK SWCs. >> As part of >> this I want to change the SDK build scripts so that the <compc> tasks >> don't have a bunch of configuration but instead simply load a config >> file. Then the JUnit test can use the same config file to compile the >> SWC in a debuggable way by calling Falcon's COMPC.main() entry point. >> >> 4. Update the SDK code to suit Falcon, because it is stricter than >> the old compiler. >> >> 5. Log bugs for any SDK code that Falcon barfs on (either throwing >> Java exceptions or reporting spurious errors or warnings). >> >> 6. Fix those bugs. >> >> What you like to take on the conversion of the <compc> tasks to use >> config files? >> >> - Gordon >> >> -----Original Message----- >> From: Raju Bitter [mailto:r.bitter.mailingli...@googlemail.com] >> Sent: Wednesday, September 12, 2012 6:41 AM >> To: Gordon Smith >> Cc: flex-dev@incubator.apache.org >> Subject: Is there anything the community can do to help you testing >> or documenting Falcon and the build process? > -- > Alex Harui > Flex SDK Team > Adobe Systems, Inc. > http://blogs.adobe.com/aharui > >
