On 12/6/12 12:57 PM, "Gordon Smith" <gosm...@adobe.com> wrote:
> But doesn't it make it impossible to use Falcon's shell scripts, which expect
> to find other things in the SDK using relative paths from those shell
> scripts???
You mean like the mxmlc and compc scripts? They take a FLEX_HOME
environment variable and seem to be working.
>
> Falcon isn't going to be independent of the SDK in the sense of being external
> to it. The goal is for it to replace the old compiler *in* the SDK. I don't
> want to be polluting an SDK with Falcon until it is ready, but it made sense
> to me to copy whatever SDK you want test Falcon with into Falcon's directory,
> so that everything is relative to each other as it will eventually be.
>
I guess I haven't given up on the vision of Falcon being so independent that
it doesn't have to be in every SDK release. For sure, I am currently
working on a "new SDK" and I want Falcon and FalconJS to work with it. I
want to finish the vision of not having to change Falcon for every version
of the SDK. That would eventually allow the SDK folder to not contain any
java code, and changing SDK versions becomes a matter of changing SWCs and
not JARs.
And I don't want to eliminate the possibility that someone will take on the
effort to integrate Falcon into an IDE.
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
