Re: Xcode 4 UI customizability curiosities
Re: Xcode 4 UI customizability curiosities
- Subject: Re: Xcode 4 UI customizability curiosities
- From: Rick Mann <email@hidden>
- Date: Wed, 23 Jan 2013 21:06:00 -0800
On Jan 23, 2013, at 19:05 , Joar Wingfors <email@hidden> wrote:
> Now, you can configure Xcode to provide much of what both of you are asking for here. The key is making good use of Behaviors. A good introduction to Behaviors would be the "Working Efficiently in Xcode" session from WWDC 2012.
Sorry, Joar, what's there still isn't really good enough. One aspect I left unsaid was that documents should remember their windows, so that if a document is not currently open in a separate window, but I do something that causes it to be opened in a separate window, it opens to where it was. I just tried this with command-double-click on a symbol, and it did not re-open the window in the same place it was before.
Regarding command-click: I have to command-double-click, which is sometimes hard. I want to configure command-click to go to the existing window, or to open a new window if it's currently closed (remembering the last state of the window when that file was open). If that file has never been open in a separate window before, then it should open in a suitable default that I can configure (staggering is okay, but shape and config should be the same).
I watched Chris' part of that video. It has allowed me to set some things, but I think with the sort-of halfway-there behavior, it might be worse than just staying in one window. I'll give it a shot.
By the way, this model Xcode has, of making me go to a behaviors pref pane and pre-program how I want things to be goes against the direct manipulation paradigm of good UI design. I'd rather just set my window, and have it be remembered.
Another thing: there's no way to show just the project stuff, is there? Files & Groups, etc?
Really, the other thing Xcode needs is different classes of windows. All windows are the same, in that they can all be configured to be anything. But I want there to be one (and only one) "Project" window, which is a parent to all the windows that spawn from it (not a visual parent, mind you). That is, if I close it, I want all the other windows to close. When I re-open the project, I want that window to open (plus any others that were open before).
I really want a traditional document model, not a browser model.
I'll try experimenting with the behaviors more. They're still not doing the right thing, but I think some of what I'm seeing is a bug.
Any way to get a separate search & replace dialog instead of that banner across the top?
--
Rick
>
> Joar
>
> On 23 jan 2013, at 17:47, Rick Mann <email@hidden> wrote:
>
>>
>> On Jan 23, 2013, at 8:07 PM, Gavin Stokes wrote:
>>
>>> Nope. I filed a bug against this years ago. Every time you hit a breakpoint, Xcode changes the contents of the currently selected tab to show the code at the breakpoint, instead of simply switching to a tab in which that file is already open. If you hit the breakpoint enough times, every tab on your screen will eventually be showing the same file. Ridiculous.
>>
>> This is the single most important behavior I wish Xcode would support (optionally, for those who like it the way it is). Without it, you lose copious amounts of contextual information that's otherwise available to you, namely the spatial context associated with window position and shape.
>>
>> Research shows this helps avoid the kind of distraction that severely hampers a programmer's productivity and quality (see "Associative Memory"):
>>
>> http://blog.ninlabs.com/2013/01/programmer-interrupted/
>>
>> Once that's in place, a number of minor enhancements to reduce the required chrome on every window, and Xcode would be stellar.
>>
>> --
>> Rick
>>
>>
>>
>>
>> _______________________________________________
>> 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
>
--
Rick
_______________________________________________
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