What happened to Xcode 3.2 and script languages?

Today I bought an official Mac OS X 10.6 Snow Leopard. Although I had a developer’s DVD image but I doubted if that was exactly same to a release build.

Anyway, Xcode is my favorite application program on Mac and can’t be the 2nd program to launch. Hmm..

I found some difference between Xcode 3.2 and Xcode 3.1
First, the startup screen.
Xcode 3.2 Startup
I don’t understand it. Why should it display the recent projects’ list when there is a “Recent” menu item?
Also, it doesn’t provide as many information as it did with Xcode 3.1.
On Xcode 3.1 startup dialog box, there were information pages for iPhone, Mac, mailing list, tips. So, you can easily check what information is most-recently available on Apple’s dev site. However, it is now on document viewer window as “Apple Developer Connection”. Hmmm… I like 3.1’s approach more…

Second, most of Ruby-Cocoa, Python-Cocoa binding project template are gone!. Why? Did Apple people decide not to support those script language directly?
Here I found some explanation on the change.

FROM : Chris Espinosa
DATE : Mon Aug 31 19:09:54 2009

On Aug 31, 2009, at 6:43 AM, wrote:

> Can you no longer create PyObjc Cocoa applications in Xcode 3.2? Or
> can I just not find the right place in the interface to create one?

We are deemphasizing Cocoa-Python and Cocoa-Ruby, though existing
project will continue to build in Xcode. You can duplicate one of
your existing projects and use the new Rename command to start a new

Bugs filed against the removal of these templates will be duplicated
to No Python/Ruby templates in Xcode, and
we’ll use that bug to gauge the need for that support in the future.


Didn’t Apple just start emphasizing them in 10.5? Why are you be de-
emphasizing them already?

We have a shipping PyObjC app, so should we be worried about future
support for this?


“De-emphasize” probably isn’t the right word for what happened.

The templates, as provided by the third party developers, move more
quickly than Xcode releases do and are released on a schedule of their
own. Thus, pretty much whatever is shipped with Xcode will be out of
date on day one.

The decision was made to yank the templates and encourage developers
to download the templates directly.

> We have a shipping PyObjC app, so should we be worried about future
> support for this?

There are a bunch of applications and tools that require a working
PyObjC in the system.

Hmmm.. So, you would need to download RubyCocoa, Python-Cocoa template by visiting each project web site.


8 responses to this post.

    • Posted by jongampark on September 3, 2009 at 12:47 PM

      OK, Thanks for your comment.
      It would be much nicer if Apple explains about this change in their Xcode help page.


  1. Posted by Alex on September 3, 2009 at 6:16 PM

    it very suspicious that they put a big word about scripting languages http://www.apple.com/macosx/developers/#languages in xcode here, but provide no way (or giving no explanation how) to use it in xcode. im really confused


  2. […] just install Snow Leopard along with Xcode 3.2, which should have been fine except that Xcode 3.2 no longer has project templates for RubyCocoa. This isn’t a show stopper, but it certainly is a decent hurdle if you’re just starting […]


  3. Posted by jongampark on September 10, 2009 at 7:06 AM

    Wow.. The number of visitors went up a lot due to this post.
    Then, it means that it is not only I who was curious about the disappeared script language projects template!


    • Good to know, because I was wondering about this. Awhile ago I was playing around with the ruby xcode stuff in leopard and was kind of surprised when I couldn’t find it in my snow leopard install of xcode. Of course, I wasn’t even sure if the templates were there to begin with on my leopard install, or if I had installed them with some other package, so I kind of just shrugged and said ‘oh well’.


  4. Posted by Phil on September 10, 2009 at 10:21 AM

    I think the interest is in MacRuby/Hotcocoa


Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: