I’m very interested to hear that you got FCSH working with the 3.1 SDK.

When I tried to get FCSH working with the 3.0 SDK, I got errors saying that FCSH couldn’t find flex2.tools.Shell. I hunted around the web and found this very page that says:

“If you only have Flex SDK 3 installed, you’re out of luck because flex2.tools.Shell is no longer distributed.”

So I guess he and I agree that FCSH shouldn’t work with SDK 3.0.

So how have you got it to work?

Thanks

Ed.

As for the new features that I plan to add, they may not be available in the near future. I no longer feel comfortable to give another ETA…

Also, is there any way to use it via a normal ant task or command line call?

I decided to see if I could find the source code, since this is now an Open Source project. I did, but then wasted several hours trying to figure out what to do with the code and ant targets that I downloaded. [Note to Self--Idiot, never check code out from the trunk. They are well on their way to refactoring for Flex4, and that creates a rather different environment concerning SimpleShell, now renamed Fcsh.]

When I managed to check out the sources for 3.1.x, the build process worked better for me. So, in addition to confirming that fcsh works just fine with the latest release, I would be happy to pass along to anyone who would find it useful, some changes to make it easier to work with AIR.

01. I added a command that you enter like this:

ax SomeAIR.mxml

and it fixes the command line to emit this:

mxmcl +configname=air SomeAIR.mxml

No, it’s not rocket science, I never said it was — but it saves you keystrokes.

02. I added a command that you enter like this:

adl SomeAIRApplication

and it fixes the command line to emit this:

adl SomeAIRApplication-app.xml

Same comment as above, but in this case, as I am sure you have imagined, the command line it turned over to the Java RunTime. So now you don’t have to keep a second command line window open just to test what you have just compiled.

Maybe all the rich guys at Adobe have three monitors and don’t care about screen real estate but any of us who are still using vi and mxmlc have to get by with a lot less.

I am looking at this page because I am starting to use amxmlc more than mxmlc — yes I know I could just type in the configname. So, after submitting an enhancement request, I started looking to see how hard it would be to fix it myself. I have not yet done that, but I just want to report that I have been happily using fcsh with FlexSDK3.x for more than 6 months — it works fine and saves me hours per day.