<br>I think I will try using this as part of "Add Flex3 libs to OL distro" task. <br><br> <a href="http://jira.openlaszlo.org/jira/browse/LPP-5694">http://jira.openlaszlo.org/jira/browse/LPP-5694</a><br><br><br>
<br><div class="gmail_quote">On Mon, Jun 2, 2008 at 1:17 PM, P T Withington <<a href="mailto:ptw@pobox.com">ptw@pobox.com</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Turn this into a Jira improvement task?<div><div></div><div class="Wj3C7c"><br>
<br>
On 2008-06-02, at 12:48 EDT, Henry Minsky wrote:<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Andre found this document which describes how to invoke the Flex compiler<br>
as a Java API<br>
<br>
<a href="http://livedocs.adobe.com/flex/3/compilerAPI_flex3.pdf" target="_blank">http://livedocs.adobe.com/flex/3/compilerAPI_flex3.pdf</a><br>
<br>
There are some very useful looking pieces there, including an API for<br>
getting the compiler warnings passed out in a structured way, and also a<br>
"virtual filesystem"<br>
API of some kind, so you can pass a set of source files which are only<br>
resident<br>
in memory, not on disk. I suppose we may eventually want to use this,<br>
although<br>
for the foreseeable future, it is good to have all the intermediate .as<br>
files available<br>
in the tmp directory to browse through when debugging.<br>
<br>
<br>
<br>
<br>
-- <br>
Henry Minsky<br>
Software Architect<br>
<a href="mailto:hminsky@laszlosystems.com" target="_blank">hminsky@laszlosystems.com</a><br>
</blockquote>
<br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Henry Minsky<br>Software Architect<br><a href="mailto:hminsky@laszlosystems.com">hminsky@laszlosystems.com</a><br><br>