Re: Why does XCode 4 always open files up to maximum size?
Re: Why does XCode 4 always open files up to maximum size?
- Subject: Re: Why does XCode 4 always open files up to maximum size?
- From: Matt Neuburg <email@hidden>
- Date: Tue, 22 Mar 2011 17:23:17 -0700
On Tue, 22 Mar 2011 11:47:30 -0700, Nathan Sims <email@hidden> said:
>On Mar 21, 2011, at 8:13 PM, Marco S Hyman wrote:
>
>> Any application that makes it hard to arrange my windows for my current
>> task and keep that arrangement is an application that gets cursed, not
>> praised.
>
>One might surmise that "screen clutter" was identified by somebody as a "problem that needed to be fixed", and thus Xcode 4 was born.
>
>I just took stock of my screen where I'm developing with Xcode 3.2.6: I have 38 windows up (21 of which are source code files, 8 are multiples of the same file, but centered on different spots in the code) and am working on 3 projects at once (an OSX app, an iOS app, and a library). Why? Because they all need to be developed in tandem.
>
>How does one do this in Xcode 4?
Okay, but the thing is you *can* do that in Xcode 4. First of all, all 3 projects can be brought together in a workspace, which can be used as the "master window" for the whole affair. That's pretty cool. Then, to open something an another window, just double-click it in the Project navigator (command-1). If what you want is 38 windows you'll soon have 38 windows. You could also set things up so that option-clicking it (or option-choosing it in the jump bar) also opened it in another window.
However, I think part of the problem for you is that when such a window opens it is initially configured as a duplicate of the parent that spawned it. Thus each time you spawn off a window you may have to spend a little time configuring it.
What you are pointing out, and what I think Joar is not quite grappling with in his responses, is that to you a window represents *the thing* it shows. Thus, you would like a certain file to open its window in a certain position and configuration *every* time - you think of the window and its position as a property of the *file*. (As someone pointed out, that's how BBEdit works.) This is what Xcode completely does away with.
It's the same with my little tip about the Console that I mentioned earlier. It solves the problem of seeing the Console full-page in *this* project, once you've set it up, but in another project you'd have to set it up all over again. This is frustrating because what we are trying to configure is a totally independent universal, The Console. To Xcode, it is merely yet another window of *this one project* (or workspace).
So I'm suggesting that the clash of worlds we're seeing here surely cannot come from the "one window" model of working in Xcode 4, because that's just a fallacy; you can have as many windows as you like, there is no "one window" model. It's a difference over what a window *is* and what it belongs to. m.
--
matt neuburg, phd = email@hidden, <http://www.apeth.net/matt/>
A fool + a tool + an autorelease pool = cool!
Programming iOS 4!
http://www.apeth.net/matt/default.html#iosbook _______________________________________________
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