TextMate and Flex 2

Hi Daniel,
cool! I started to do one myself, but Yours is much better!
I try to come up with some new ideas…
-karsten

Woa what a nice thing! it rocks!!!!

But I add this trick to bind at Command-Enter for quick export 🙂
I was wondering for two things…
Since you can validate mxml, is it possible to make a quick validate syntax bind at Shift-Control-v just like in php (the result show in tooltip)
And would it be possible to build the flex app in a different folder than the mxml file?

Thanks so much sir

Dude this is awesome, thanks.

I have a question about compile time, I have the beta of Flex Builder for the mac and it compiles projects in a couple of seconds while the SDK takes 10-30 seconds which is a looooooooooong time when debugging.

I know the first time Flex Builder compiles it also takes a while but then uses some kind of caching. Do you know if there’s a way to speed up the SDK compile time?

thanks again!

oh bless you and your fine little tmbundle of joy. people like you make coding worth doing.

yes! thanks indeed, its a great way to use textmate good job!

Here’s a patch to the BuildProject.tmCommand file, which lets it know about the default install paths for the Flex Builder 2 product and lets the user override with a shell environment variable:

$FLEX_HOME = ENV[“FLEX_HOME”] || “”
unless File.directory?($FLEX_HOME) then
dirs = [
“~/Flex”, “~/flex_sdk_2”,
“/Developer/SDKs/Flex”, “/Developer/SDKs/flex_sdk_2”,
“/Developer/Applications/Flex”, “/Developer/Applications/flex_sdk_2”,
“/Applications/Adobe Flex Builder 2/Flex SDK 2/”,
“/Applications/Adobe Flex Builder 2 Plug-in/Flex SDK 2/”,
“/Applications/Flex”, “/Applications/flex_sdk_2”
]

dirs.each do
|dir|

if File.directory?(dir)
$FLEX_HOME = dir
break
end
end
end

Nice work, thx!!!
Any plans to use fcsh?
I don’t know how to communicate with it, though 🙁

I have downloaded and installed to Textmate, then manually added in Andrew Shebanow patch. I am still getting NoClassDefFoundErrors

Exception in thread “main” java.lang.NoClassDefFoundError: Flex

I have $FLEX_HOME pointing to my extracted SDK and $FLEX_HOME/bin is on my $PATH. Any ideas?

There’s a bug in this: when your Flex SDK is in a home dir, and you are using something like “~/Flex” to point at it, the script doesn’t do path-expansion and it can’t find the SDK. The fix is easy though… at the top of the code (line 10) replace this block:

dirs.each do
|dir|

if File.directory?(dir)
$FLEX_HOME = dir
break
end
end

with this:

dirs.each do |dir|
fulldir = File.expand_path(dir)
if File.directory?(fulldir)
$FLEX_HOME = fulldir
break
end
end

and the “Build” command should work fine.

I patch my bundle but always same error
“Exception in thread “main” java.lang.NoClassDefFoundError: Flex”

dirs = [
“~/Flex”, “~/flex_sdk_2”,
“/Developer/SDKs/Flex”, “/Developer/SDKs/flex_sdk_2”,
“/Developer/Applications/Flex”, “/Developer/Applications/flex_sdk_2”,
“/Applications/Adobe Flex Builder 2/Flex SDK 2/”,
“/Applications/Adobe Flex Builder 2 Plug-in/Flex SDK 2/”,
“/Applications/Flex”, “/Applications/flex_sdk_2”
]

dirs.each do
|dir|

fulldir = File.expand_path(dir)
if File.directory?(fulldir)
$FLEX_HOME = fulldir
break
end
end

I was getting the “Exception in thread “main” java.lang.NoClassDefFoundError: Flex” error. I have Flex Builder 2 installed under Applications.

I found that I could compile my mxml file with the mxmlc compiler in the Flex SDK 2/bin folder, so I munged the Flex bundle like this (hard-coding the path to my Flex install):

#MXMLC=”java #{VMARGS} -jar #{$FLEX_HOME}/lib/mxmlc.jar”
MXMLC=”/Applications/Adobe\\ Flex\\ Builder/Flex\\ SDK\\ 2/bin/mxmlc”

I’m not a Ruby guru, there’s probably some cleaner way to do this. The double-backslashes are needed to escape the spaces in the pathname for the shell.

Works for me!

actually, I just noticed that it’s outputting to the same direcotry as the mxml flle…would you know how tochange the output path? (I’d just like to change it to ‘bin’ which is in the same directory that the swf is currently being outputted to).

@Steve Ametjan

It may also be the fact that Flex Builder is Java-powered, so the overhead of firing off the compiler (which is Java-based as well) may be reduced (and in fact, on Windows at least, it doesn’t spawn a separate process) inside of FB, while the command-line builds/tearsdown a full process (including Java runtime) each time.

Hi,

One thing; if I want to use scripting in the MXML file; as this has to go in a CDATA section, there is none of the formatting you would find in a normal action script file in TextMate. Is there an easy way to combine the formatting so the code in the CDATA section looks like action script and not just a normal CDATA section? This would make things much clearer in the MXML file.

Obvioulsy I could just move most of the action script to a separate AS file but it would be nice to have the best of both worlds 🙂

Cheers,
Paul

Dan, this is an awesome little bundle. Flex Builder runs butt-slow, and it’s great to be able to use TextMate instead.

@Jeff – thanks a bunch! I couldn’t get it to work without your path fix. Now I can build away.

Uss George Washington

Hi Daniel,

I was using another TM bundle (feel ashamed) and recently discovered yours which is much better. I have a few suggestions / questions to you which I hope you could answer:

1) Would be cool if you add a new environment variable where to add compiler specific parameters such as target-player, library-path, … Furthermore, maybe just a custom mxmlc args variable or so.

2) Would be nice to have a build&run command

3) There’s an issue with directory names with spaces (fcsh won’t work). I have a workaround which consists on cancelling the build, then launch fcsh from project’s directory (manually), and run the first mxmlc command manually just using relative files such as mxmlc -o=MyApp.swf MyApp.as. From this point every build command will work (since compile 1 is used). Would be possible to kind of automate that? Force terminal launch under project’s directory?

thanks a lot for your excellent work!

Cheers,
Edu