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: Michael Tindal <email@hidden>
- Date: Thu, 24 Mar 2011 19:42:26 -0500
I've been reading mostly, but have kept to myself, but I do agree that this seems to be rather subjective. I'm currently working on a game that encompasses 293 source files (including headers), has a custom scripting language based on C syntax mostly compatible with C and Objective-C libraries, and isn't even in what I would consider alpha stage yet. I typically work on several components at the same time, for instance, last night I upgraded my language to include the ability to pass pointers to objective-c and c types (using casting), and that involved editing about 4 different classes and adding unit tests. I did all of that in what I would consider efficient using one window, and flipping between them. I'm not saying that my approach is right or yours is wrong, simply that what works for me might not work for you. Vice-versa, what works for you might not work for me. I agree that perhaps xcode 4 should have included the ability to toggle between single window and multiple window, but that doesn't mean that xcode 4 is inherently bad for everyone that uses it. I personally love Xcode 4 and have been using it fairly exclusively since DP2.
On Mar 24, 2011, at 7:11 PM, Lee Ann Rucker wrote:
>
> On Mar 24, 2011, at 10:55 AM, Joar Wingfors wrote:
>
>>
>> On 24 mar 2011, at 10.09, Scott Ribe wrote:
>>
>>>> How about I make the counter argument that single-window users would be less affected by moving to a smaller screen, because they don't have a workflow that depends on having lots of different documents visible at all times?
>>>
>>> The problem with that argument: if a task is inherently complex and involves working with multiple documents simultaneously, there's no way that not being able to see them simultaneously can increase efficiency.
>>
>>
>> Sure, but whether or not a task really requires working with multiple documents visible at the same time seems - for the most part - rather subjective to me. In my opinion most tasks, the bulk of what we do, don't fall into the "inherently complex and involves working with multiple documents simultaneously" bucket. That said, I understand that if you're a multiple-window person you may have a different opinion.
>
> Right now I'm refactoring code between two class hierarchy trees (collectionViewItems and their representedObjects). I've got about 5 classes total in each tree, so there's 20 already counting headers, plus the CollectionView delegate that manages them and the classes that use them. While at any given moment I might only have 4 of them mostly visible, I am flipping between them all often enough that I want them all open.
>
> This is a normal day for me. _______________________________________________
> 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