Allow me to correct you. OS X
WAS not fundamentally a command-line user experience. However, as of latter 2007 (couple years before your comment), OS X has "embraced and extended" the Open Unix architecture. (See:
http://www.opengroup.org/openbrand/register/brand3555.htm)
Allow me to disagree. What I wrote is still true: Mac OS X is still not fundamentally a command-line user experience.
The fact that it has command-line tools is not new. It has always had them. And they've always been Unixy commands. Certification of conformance to Open Unix architecture is a nice plus in the standardization direction, but it doesn't fundamentally change anything. The user experience is still not fundamentally command-line oriented.
From the very first release, Terminal.app was there, and a fair number of commands were pre-installed. Installing the Developer Tools added even more, including compilers like gcc. Furthermore, Project Builder (Xcode's predecessor) has always worked by running command-line tools via scripts that build things. This is easily observable in the build log (detailed build output), where the rather lengthy command-lines can be seen. AFAIK, Xcode still works this way: it runs command-line tools like 'clang' to build and link things.
There are also developer details like how apps are launched, and how they receive parameters such as the list of files to open.
Again, Mac OS X is not fundamentally command-line oriented in this regard. If you're expecting main() to receive an argc and argv with the path to the file, you will be dismayed to see no such thing. Instead, files are passed by another mechanism entirely, essentially an event message with a parameter referencing the file(s). Programmers writing apps almost never see this event message, because the frameworks they use hide it, instead providing a callback-oriented architecture.
Yes, I too almost always have Terminal.app running. I've done this since the 10.0 days (2001). My proficiency with Unix commands came long before Mac OS X, so having a command-line available has never been a big deal. The fact that I find a command-line useful doesn't mean that the typical user's experience of Mac OS X is in any way fundamentally command-line oriented.
There seems to be a chip on the shoulders of classic Mac GUI purists, and it is evident in this thread, but I want to thank you anyway. Apparently, we noobs had to get you guys to start ranting so that we could get you to let some of the secrets out.
I see no evidence of chips on anyone's shoulders, least of all "classic Mac GUI purists" (whatever that means). This is a developer forum, and most of the people who post answers here regularly are well aware of command-lines. Certainly those with significant experience of Mac development are well acquainted with command line tools.
The answer to the OP's question is basically "Make sure you're looking in the right folder" followed by "Double-click the Xcode icon you see there". Solutions using both Finder (GUI) and Terminal (command-line) were posted. I don't see how clarifying where one should look, or exactly what action to take, is evidence of a chip on one's shoulder.
And even in my reply, I see no chips on shoulders. I, for one, am simply pointing out inaccuracies in your post, or questioning how you arrived at your conclusions.
As for the Xcode icon. When I installed Xcode on my OS X Lion, it launched the app after the install, and I right-clicked the icon in the dock and told it to stay there. Subsequently, however, I noticed there was NO Xcode icon in my Applications folder. Funny thing was, if I typed 'Xcode' into the magnifying glass, it would show me an Xcode icon in the Applications folder! (raising one eyebrow) I still don't know why this is the case.
Neither do I. If you want an answer to this, you should simply have posted it as a question. You may need to provide more detail to get an answer, however.
I now know that the Xcode icon is really in /Developer/Applications. Thanks for the help.
Glad to see that the earliest replies from 2009 are still accurate.
