<?xml version="1.0" encoding="UTF-8"?>
<posts type="array">
  <post>
    <body>Yes it works, but on OSX there's a potential Java hitch to be aware of.

Download "Eclipse Ganymede 3.4":http://www.eclipse.org/downloads/. Unzip Eclipse to a directory (normally Applications).

Download "Flex Builder 3.01 Plugin":https://www.adobe.com/cfusion/tdrc/index.cfm?loc=en_us&amp;product=flex_eclipse.

*BEFORE* you run the Flex Builder Plugin installer on OSX, check that your java version is set to 1.5. However a simple @java -version@ is not enough to satisfy the installer. You also have to @cd /System/Library/Frameworks/JavaVM.framework/Versions/@ and @ls -al@ to check that CurrentJDK -&gt; 1.5.0.

I'd previously installed Java 1.6 on Mac, and although @java -version@ gave me 1.5, the CurrentJDK -&gt; 1.6.0. This seems to have caused my install to fail with the error: 'This installation can still be configured manually as a Product Extension' and soon after an alert with 'a newer file named "com.adobe.flexbuilder.debug.e33_3.0.205647.jar" already exists at "/Applications/Adobe Flex Builder 3 Plug-in/eclipse/plugins" Do you want to overwrite this file?' Trying to follow the instructions offered is a fruitless exercise I won't bother recounting because "someone else already has":http://www.newviewnetworks.com/nvnhome/blog/client/?p=103 (Borg - no permalinks for comments on that site).

Anyway ensuring you have 1.5.0 all the way should guarantee a successful install.</body>
    <created-at type="datetime">2008-11-18T16:45:27Z</created-at>
    <ham-comments-count type="integer">0</ham-comments-count>
    <id type="integer">25</id>
    <permalink>flex-builder-3-01-plugin-in-eclipse-ganymede-3-4-on-osx</permalink>
    <title>Flex Builder 3.01 Plugin In Eclipse Ganymede 3.4 on OSX</title>
    <updated-at type="datetime">2008-11-18T17:06:09Z</updated-at>
  </post>
  <post>
    <body>For those that like a little more than a console window there's "MacVim":http://code.google.com/p/macvim/, but if you want to stick to the console and use MacPorts to install vim, you'll need to replace the installed version.

The FuzzyFileFinder plugin I attempted to use required 7.1, which I thought I'd installed via MacPorts, until I realised @which vim@ pointed to /usr/bin/vim, which was 7.0. Reminded "via":http://blog.fluther.com/blog/2008/10/17/django-vim/, I @sudo cp /usr/bin/vim /usr/bin/vim7.0@ and then @sudo cp /opt/local/bin/vim /usr/bin/vim@.</body>
    <created-at type="datetime">2008-10-31T09:43:44Z</created-at>
    <ham-comments-count type="integer">0</ham-comments-count>
    <id type="integer">21</id>
    <permalink>vim-on-mac-osx</permalink>
    <title>Vim On Mac OSX</title>
    <updated-at type="datetime">2008-10-31T09:43:44Z</updated-at>
  </post>
  <post>
    <body>After tidying up my scaffold-generated tests, everything passed on running @spec spec/@, so I was keen to investigate automating the running of tests.

After a bit of searching I thought I may as well investigate "PeepCode":http://peepcode.com/, so I went for PeepCode Unlimited and ran through "Rspec Basics":https://peepcode.com/products/rspec-basics. I hopped to @sudo gem install ZenTest@ and also ran @rake doc:plugins@ to generate documentation locally, which apparently includes more documentation than is available via the site.

One of the nice bits of information in the screencast was in using Growl with AutoTest. I had to install "Growl":http://growl.info/ first, and then install growlnotify from the extras folder of Growl. I also created an .autotest file in ~ with modified code "from here":http://blog.aisleten.com/2008/02/21/installing-growlnotify-and-autotest-for-bdd-use-with-rspec-on-leopard/. Then it was just a matter of running @autotest@ in the project root, but not before setting the @RSPEC=true@ "environment variable":http://blog.insoshi.com/2008/07/28/running-rails-tests-with-autotest-zentest-and-rspec/.</body>
    <created-at type="datetime">2008-09-17T20:38:12Z</created-at>
    <ham-comments-count type="integer">0</ham-comments-count>
    <id type="integer">6</id>
    <permalink>autotest-rspec</permalink>
    <title>AutoTest Rspec</title>
    <updated-at type="datetime">2008-11-19T20:35:54Z</updated-at>
  </post>
</posts>
