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: j o a r <email@hidden>
- Date: Tue, 17 Aug 2004 12:21:29 +0200
It sounds like you would like to work in single-window-mode, as in PB,
rather than in few-window-mode, as in Xcode. Why have separate windows
per mode at all, when you could have had the single window of PB where
you switched between modes using tabs?
The PB I used didn't have an attached editor - it worked in true
single-window-mode - and I'm fairly sure that wasn't the default
workspace configuration even if you might have been able to set it up
to work with separate windows and attached editors (I never tried).
I'm just curious why you bash the comments from the proponents of
single-window-mode, when it sounds like you try to emulate that
environment as best as Xcode allows.
j o a r
On 2004-08-17, at 11.58, Greg Hurrell wrote:
> 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.
[demime 0.98b removed an attachment of type application/pkcs7-signature which had a name of smime.p7s]
_______________________________________________
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.