Re: Xcode cleaning the project each time I build it
Re: Xcode cleaning the project each time I build it
- Subject: Re: Xcode cleaning the project each time I build it
- From: Greg Hurrell <email@hidden>
- Date: Tue, 17 Aug 2004 11:58:04 +0200
El 17/08/2004, a las 9:17, Andreas Mayer escribis:
Am 17.08.2004 um 01:18 Uhr schrieb Greg Hurrell:
If you don't like them, you can just drag the splitters down to the
bottom of the window, thus hiding the editors. The next time you use
the same window, the editor will still be hidden.
Yes. And when I click on a error message in the build/debug window,
nothing happens. No, I CAN'T just hide those editors. If I do, Xcode
is unusable.
Ah, seeing as I don't use Xcode that way, I didn't know this happened.
I'm all for freedom when it comes to letting people choose how they
work, so it sounds like what is needed is a preference to turn the
attached editors completely off rather than just hiding them.
Anyway, I would like to know in what way they boost productivity for
you. What's the benefit of a file opening in a new editor rather than
in the main one? All _I_ experience is, that I have to switch windows
and search for parts of code more often.
I have a very small screen. So I use a separate build results window.
In that way I can see the warnings/errors, click on them to edit in the
attached editor, and I can see the build log too as well as the
"console" detail.
The "old" Xcode way was a nightmare for me because I was forced to do
one of two ugly things.
Option 1. I kept using the separate build window, but had to switch
back and forth between it and my main editor. On a 12" screen this was
horrible because I couldn't see both windows at the same time but had
to shuffle them like a deck of cards.
Option 2. Forget using the separate build window entirely and instead
depend on Xcode's "Errors & Warnings" Smart Group (this is what you
would have to do now with Xcode 1.5 to avoid the attached editors that
you don't like). But this, too, was horrible on a small screen. If I
wanted to make the screen area in which the Errors & Warnings Smart
Group appeared big enough to make it readable and usable, then I had to
shrink my editor right down. Ditto for the detail view. And I lost
convenient access to the build log and the console details.
For all of these reasons, that's why I was so thrilled with the fact
that Xcode brings back attached editors like Project Builder had. Now I
can work much more efficiently. My work flow is now.
1. Do long periods of editing in the main editor window.
2. When it comes to build time, the build results window pops up and I
can work concertedly in that one window to fix any errors and warnings
that pop up. There's no need to switch back and forth between views,
and I have convenient access to all of the information I might need.
There is seldom anything I need to do which I can't do from that build
results window.
In this way I am spending decent blocks of time in different areas of
the UI (same with the debugger). I much prefer to work this way. -- for
example, 20 mins in the main editor, 3 mins in the build window, 10
mins in the debugger; for three "context switches" in all -- than to
have to flip back and forth between windows (dozens of "context
switches") to get anything done.
Greg
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.