Open up Flex > Project > Project-config.xml. You’ll notice this is the schematic of a file which is created automatically when you create an Flex 3 project. Unfortunately, the Project-config.xml schematic in the Flex bundle lacks these two sample nodes that are in the ActionScript 3 bundle. These are:

<!-- Example library linkage -->

<!-- for swc's
  <library-path append="true">
<path-element>../lib/bin/</path-element> </library-path> -->

<!-- for src
<source-path append="true">
<path-element>../lib/src/</path-element> </source-path>
-->

This file acts as a project-level override to the general configuration file found in the SDK directory. Close the bundle editor. You’ll want to add the following to your project’s configuration xml which lives in ’src’:

<library-path append="true">
  <path-element>../libs/</path-element>      
</library-path>

Now you can create a new directory named ‘libs’ parallel to ’src’ and drop into here all SWC files that your project depends on. Save the configuration file and you should be able to build. Now anyone with the Flex SDK will be able to save your project directory locally and jump right into compiling

Quick tip that I found when searching to find out how to get syntax highlighting in your Gemfile if you are using TextMate Ruby on Rails bundle.

In Textmate, select the Bundles menu => Bundles editor

Select languages instead of show all.

Select the Ruby on Rails language within the Ruby on rails bundle

Change this line:

fileTypes = ( 'rb', 'rxml', 'builder' );

to this:

fileTypes = ( 'rb', 'rxml', 'builder', 'Gemfile' );

Go to Bundles => Bundles Editior => Reload Bundles.

Reopen your Gemfile and you should now be getting the syntax highlighting.

Text editor development has been stagnant for several years. It’s time for developers to take the text editing experience forward into 2010!

PeepOpen is a file navigation application that works with TextMate, Coda, MacVim, and Emacs (Mac OS X Snow Leopard on 64-bit Intel required, support for other editors is coming soon). Search on both paths and filenames, and easily open the file in your text editor with a single keypress. Useful metadata helps you quickly choose the file you’re looking for.

I am really pressing to make Textmate my editor of choice for most all my coding so when I find little gems like this that will make that environment even better I jump at the chance to give them a try. This plugin is simply, badass.

I am being very hard headed and determined that I am going to give Textmate a solid try for my actionscript and flex projects. Work on the bundle has been a little lacking but what has been developed so far is pretty great.

I have run into some slight issues but able to figure them out and get things set up pretty well and I have already dug in and started customizing the snippets to suit my needs.

One thing that I have not been able to fix, figure out or find a straight answer for is regarding working with MXML files. AutoComplete for Actionscript files seems to work great but I don't seem to get the same result when I am editing Actionscript inside the script block in a MXML file.

I am hoping that someone that uses Textmate all the time could through some suggestions my way to help track down the issue. If I am in the actionscript code block and hit (option + esc) I get "no completion available" message.