DISQUS

marius · 1 year ago

Thanks, Raphael ;-)

Raphael · 1 year ago

Thanks! :-)

Dave · 1 year ago

Is there something that one must do for this package to work with Xcode 3.1 for iPhone?

http://img.skitch.com/20081002-3xnehbyh2p6a9uph...

Raphael · 1 year ago

No, this is am known Bug, i'm not 100% eure why the Syntax coloring sometimes not work.
If you open the file again it works normaly.
Try to fix it in the next version!
Their are more open fixes for the next version.

-raphael

Andrew · 1 year ago

I have noticed since 3.1 Xcode syntax coloring has been kind of hinky in general.

Steven Troughton-Smith · 1 year ago

Very nice work here, going to enjoy this a lot.

milestinsley · 1 year ago

Whenever I "Build and Go", only the AppController.j is packaged into the debug build. That is to say, my other classes never appear in the debug build folder. Once I copy and paste the missing classes, the app runs fine.

I am new to Xcode and feel like I am missing something obvious...!!

boucher · 1 year ago

I've also run into this. Raphael, any suggestions?

milestinsley · 1 year ago

Hey, I have just worked out the solution. In the Groups & Files list, you need to drag the new classes you have created (i.e not AppController.j) into the Sources folder of your app in the Targets section. I think this just tells the compiler to include the new files when it builds you app. Although, I am sure someone can explain it much better! It works though :P

Raphael · 1 year ago

Hi,
yes this is the solution, normaly the xcode project copies by default the file into the right
build phase.
Currently you have to copy the files into the target where it has to be after the build.

For example you create a new j source file you have to drag the file inside Source and so on.
I work on a version that filter the files and copy it to the right target.

-raphael

Tim Henrion · 1 year ago

After installing this on XCode 3.1, Build and Go would not work on a created skeleton app created from New Project. I debugged this down to the /Developer/Cappuccino/Frameworks directory being empty after the install. I copied all of the folders from the Frameworks directory in the "Starter" ZIP file to this directory, re-generated the project and this seems to work.

Glenn Rempe · 1 year ago

I also had problems with this (as a cappuccino newbie).

First problem, this seems to install and entirely separate installation of Cappuccino than the one that is installed by downloading and installing as recommended on the download page. This XCode tool seems to install to /Developer/Cappuccino and the official install goes into /usr/local/share/objj and /usr/local/bin. Can you make it so that the Xcode plugin uses the same installation?

Second problem is that you installer seems to install all of your tools under /Developer/Cappuccino as root owned and rwx permissions for ALL users. This should clearly be more restrictive.

As mentioned by someone else, the /Developer/Cappuccino/Frameworks dir is empty by default. So even the sample project template as generated by Xcode does not work when you do build and go.

I think its an awesome start. I look forward to the next version that hopefully clears up the remaining issues. Is there a project home page for this new tool?

Thanks!

j4johnfox · 1 year ago

Hi Folks:

The Xcode plugin is a glorious thing, but I'm having a bit of trouble with one thing. In my Xcode preferences, I have it set so that closing brackets are automatically added, and the tab key will indent any selected text. For some reason, these preferences don't work for Cappuccino projects.

Here's a quick screen movie that demonstrates what I'm talking about:

http://memoryminer.com//video/XcodeCappuccino-w...

Is this a known issue, or is there something I can do to help fix this?

I would very much love to use Xcode to both edit, and build (including bake).

stuffmc · 9 months ago

Is this Plugin being updated one day? :-)

bensyverson · 8 months ago

I'm anxious to see an update too... Currently, the skeleton apps bail with errors.

dparizek · 8 months ago

Any way the source of the plugin could be released or open sourced so that others can add to it?

boucher · 8 months ago

Another user contributed a new xcode plugin, which is in the source
repository. It should be a lot easier to extend, but it doesn't do
quite as much as the old one just yet.

beefon · 7 months ago

Thanks!! Great!!!

odotash · 3 months ago

Hi,

I tried to add the tools to Xcode 3.2 under Snow Leopard.
The folders in the Developers/Cappuccino stay empty.

Is it mine bad manipulation or the Cappuccino_Developer_Tools.pkg is not compatible with those versions ?

boucher · 3 months ago

It's probably not compatible. You might want to try the newer plugin
that's in the github repository.

robde · 3 months ago

http://github.com/rbartolome/xcode-cappuccino/