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: Jean-Denis Muys <email@hidden>
- Date: Fri, 25 Mar 2011 09:27:35 +0000
- Thread-topic: Why does XCode 4 always open files up to maximum size?
On 25 mars 2011, at 07:50, Joar Wingfors wrote:
> You're arguing that multiple-window users could tile more content areas on the smaller screen, and I'm arguing that single-window users wouldn't even think to do that.
>
Yes but that's a tautology: they wouldn't think because otherwise they wouldn't be single-window users.
But that leads me to the hammer argument: when the only tool you have is a hammer, every problem looks like a nail.
When your only experience is with IDEs that only offer tiling (panes) - which is admittedly about 100% minus epsilon of all IDEs, so this hypothesis is very common - you evolve behaviors around that model. Then, when other people come to you and tell you that the other model, the one you are not used to, has significant advantages, you naturally tend to dismiss them on the ground that you didn't find a need for that in your model.
The point is: that's not because you can't perceive the issue that there is no issue.
This means that every time we say "multiple windows are better for doing X, because such and such", then replying "but I can also do X with one window the following way" is missing the point. (and replying "but I decree you don't need to do X [often]" even more so).
That also leads once again to the idea of user testing. Wink wink nudge nudge. You ignored the nudge so far. So let me ask you openly:
has Apple done any user testing on this issue?
Because on a growing scale of strength, the arguments so far are:
Anecdotal evidence:
----------------------------
For overlapping model: many testimonies, several use cases described
For tiling model: a few testimonies, some use cases described as "as efficient as..."
Possible bias: the plural of anecdote is not "data". Share of voice is not evidence of correctness. Experience bias. Use cases should be weighted by commonality.
Strength of argument: weak
Abstract theory:
----------------------
For overlapping model: argument from cognitive science (brought up in my earlier message)
For tiling model: none (that I have seen)
Possible bias: theory is only hot air until confirmed by actual data. Plausibility is only a first step towards reality.
Strength of argument: moderate
User study:
----------------------
For overlapping model: none that I know of.
For tiling model: none that I know of.
Possible bias: depends on how well the study is designed. A well designed study can avoid or at least compensate for bias.
Strength of argument: strong
_______________________________________________
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