Live data from Hacker News

Announcing Cappuccino 0.9.5

cappuccino.org

11–20 of 22 posts

Re: Announcing Cappuccino 0.9.5

#15

Any tutorial for using all this stuff together in Xcode? There's a 3rd party package on the site that is probably supposed to add syntax highlighting and such but it seems out of date as of Xcode 4.2.

Syntax highlighting in Xcode isn't working so well with Xcode 4. TextMate and Sublime Text 2 are the more popular environment for Cappuccino editing right now, I think, while using Xcode only to edit the UI files.

Re: Announcing Cappuccino 0.9.5

#17

And here I thought all the coffee names were stolen by Java...

Cocoa was given its name because, at the time, it was intended to be built on Java. Cappuccino is a play on Cocoa. So while it may not be directly built on Java, its name did descend from Java.

Re: Announcing Cappuccino 0.9.5

#18

The past year I've spent a lot of time developing with Cappuccino and it's been great. I started using Atlas. I wonder if Atlas will get any love, or if I'll have to figure out how to convert my CIBs to XIBs?

The comments on the post seem to suggest that Interface Builder w/ XcodeCapp is the way of the future.

As a non-OS X user this makes me sad as well, but I'm guessing there are lots of legit reasons for 280 North to decide not to focus on it.

Re: Announcing Cappuccino 0.9.5

#19
post #18

The past year I've spent a lot of time developing with Cappuccino and it's been great. I started using Atlas. I wonder if Atlas will get any love, or if I'll have to figure out how to convert my CIBs to XIBs?

The comments on the post seem to suggest that Interface Builder w/ XcodeCapp is the way of the future. As a non-OS X user this makes me sad as well, but I'm guessing there are lots of legit reasons for 280 North to decide not to focus on it.

280North doesn't exist anymore, that's why they aren't focusing in it anymore. :)

Re: Announcing Cappuccino 0.9.5

#20
post #19
post #18

Earlier quoted context omitted.

The comments on the post seem to suggest that Interface Builder w/ XcodeCapp is the way of the future. As a non-OS X user this makes me sad as well, but I'm guessing there are lots of legit reasons for 280 North to decide not to focus on it.

280North doesn't exist anymore, that's why they aren't focusing in it anymore. :)

Heh, OK I'd missed that development. Thanks for filling me in :)
Post reply on HN