Re: "where is the..."
Re: "where is the..."
- Subject: Re: "where is the..."
- From: Giulio Cesare Solaroli <email@hidden>
- Date: Fri, 1 Oct 2004 02:00:40 +0200
Hi,
I haven't played a lot with XCode, as I am still a ProjectBuilder (WO) user.
XCode is definitely more complex than ProjectBuilder and thus I
understand that it could take some more time to get used.
To me, what is missing, is the description of the underline
philosophy/metaphor that has driven the design and development of
XCode; with this insights, I think it would be much easier to the up
to speed with XCode.
I have found some documentation on targets, install mode, etc.. but
nothing really effective.
Nobody is expected to learn how to use Autocad (taken as a random
example of complex software) in a couple of days but, coming from the
delighted experience of using ProjectBuilder, I wasn't in the right
mood to start reading a manual before opening XCode.
Giulio Cesare Solaroli
On Thu, 30 Sep 2004 17:43:12 -0600, Markian Hlynka
<email@hidden> wrote:
> it seems to me that we see a lot of questions on this list of the form
> "Where is the ... setting", or "How do I set the...", and so forth.
>
> I realize that an IDE is an inherently complex piece of software.
> Nevertheless, I'm left wondering if there is a problem inherent
> somewhere, and if so, where? The documentation (which we all know is
> improving), the design, or something else I haven't thought of?
>
> I'd be interested in seeing a thread of what people think. Especially,
> if you think there's a more intuitive design for some aspect of Xcode.
> (like the recent pop-up menu/column issue) I realize that this task is
> complicated by the fact that different people demand different things
> from their IDE.
>
> Would it help, for example, if xcode could parse makefiles and make the
> appropriate settings? What if Xcode then told you what settings it had
> changed, and where? (and why?!) What about outputting makefiles?
>
> I'm not saying makefiles are the solution to everything, but at least
> with a makefile I know everything is in that file. The compile-line,
> the compile options, include paths, libraries, headers, compile-time
> symbols, etc. The biggest problem with the makefile seems to be that it
> is (sort of) free-form, and that you have to know what's available in
> order to put it in there! (Though it seems the latter is true of IDEs
> too?)
>
> Thoughts?
>
> Markian
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Xcode-users mailing list (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden