I've decided to go the Java route for the time being. XCode 2.0's
support for Java is very rough around the edges but works. Apple Xcode
engineers should take a look at JCreator at http://www.jcreator.com/
for an example of what a good Java IDE should look like. Things I'd
like to see: a configurable path to the java compiler that XCode is
using, a configurable path to the java virtual machine that XCode is
using, Java-specific compiler parameters rather than a whole bunch of
irrelevant C/C++ gcc parameters, configurable CLASSPATH (named as
such), etc...
While I'm in whining mode, I'll mention that Apple provides a whole
bunch of ready-to-run Java source code, which is great, but I didn't
see an index for this code, so if I want to learn how to do something,
it's not clear where to go for an example.
Patrick Machielse - 29 Jun 2005 16:08 GMT
> Things I'd like to see: a configurable path to the java compiler that
> XCode is using,
That's in the target settings (extpert view)
> a configurable path to the java virtual machine that XCode is using,
Change this under the 'extecutables' section
> Java-specific compiler parameters rather than a whole bunch of irrelevant
> C/C++ gcc parameters,
That's indeed unfortunate, but just ignore those :-)
> configurable CLASSPATH (named as such), etc...
Target settings again.
You'll have to learn to do things the Xcode way, but after you figure it
out there really _is_ logic behind it...
patrick