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: JongAm Park <email@hidden>
- Date: Thu, 24 Mar 2011 08:33:03 -0700
Hi, Joar
On 3/24/2011 12:20 AM, Joar Wingfors wrote:
Hello JongAm,
On 23 mar 2011, at 09.06, JongAm Park wrote:
<snip>
Xcode 4 allows to host multiple projects on one workspace. However, it means that you need to introduce another file, i.e. workspace file, or adding a project to existing project's workspace. Sometimes it is good, but for certain occasions you would want to avoid the case. Also, having two separate project window gives you more freedom that to have one workspace with two projects. For example, let's say you want to confirm project settings of the two. As Jean-Deans explained, windows can be overlapped. So, you can utilize the screen real-estate maximally, and thus have two project settings window can reveal enough information to compare manually and visually.
I'd argue that it's as easy to compare build settings from two separate projects in Xcode 4 as it was in Xcode 3 (even if they happen to live in the same workspace). You can choose to view the two project editors side by side in a split view in one window, or you can choose to open them into two separate windows and put them side by side like you would in Xcode 3.
Well.. yes. I know that.. but you know my point right?
<snip>
What about search result?
Currently the search result is captivated on the slim left pane. You can resize it. OK. Good.
So, if the width of the slim left pane is not enough wide for you to check which lines of codes you are interested in, you can make it wider and click it to see the actual lines in the source editor. However, because they are side-by-side, the width of the source editor is shrunken.
So, you need to make it wider again, then your slim left pane, which is search result pane, is narrowed again. Then, if you think that you are interested in other lines of search results... you know what I mean, right?
I do. Although that said, I find that this has turned out to be much less of an issue for me in practice (I don't feel that I need that much context for find results). Give it a couple of months and see what you think.
I already filed this to radar a while ago, and I got messages from Apple
people saying that it was a known issues and they were working on it. (
I don't think they are working on it now. They have lots of things to do
and I interpret that comment as "it is in the "to do" of some
programmers there. He/she would tackle down one by one. )
For search result list, or anything similar to the behavior, Xcode 3's
were better, because you don't need to repeating "this pane wider, that
pane wider, this pane wider, that pane wider........ " When the list of
search result is long, you get to waste lots of time for doing that.
Also, when you want to see some explanation on document view, with Xcode 3, you can see through between windows. You put source editor window related to the document up there, and put some NSWindow instance of IB a little bit right side of the source editor while put its property accessory window to a little down. You have hole on your screen now. You want to see all of them because they are related in your project and your logic in your brain. You think, "Oh.. I want to have this view on this window behave like this, and then in this source codes, hmm.. this can be better to be changed this way... then.. will there be easy method to do that for me? let me check document. Oh.. hmm. this parameter is interesting. Hmm.. oh.. you know what? I may need to use some other class for carrying the parameters, because this class has different methods working with different parameters and one of the different parameter which is in another class can be better. So, instead of using this method, I think using that method with the better parameter looks better to me. Then, OK. I would like to open the document by clicking the class name" While your brain is busy in relating all those information and continually checking UI resources and your source codes, you are confirming if your approach can be good while reading the document.
Xcode 4 makes this a little difficult.
That's basically saying that you like the multi-window approach better, is it not? I think I'd better stay out of any argument about which mode is better... ;-) Each side have their opinions - ranging from totally subjective to almost objective - about why they like their approach.
You are right. However, as someone pointed out in his post, Xcode 3
allowed various configuration, i.e. All-in-One, Compact, Default. So, it
can satisfy different people with different needs. However, Xcode 4
doesn't allow it. It can mimic compact configuration, but.. you know
what I mean, right?
<snip>
Criticizing is easy and bring up original ideas are hard.
I really appreciate Xcode team's hardwork. Truly, there are really good things in Xcode 4 also.
Thanks! With your help, we'll make it even better over time.
This is why I love Apple! :)
Thank you, Joar!
_______________________________________________
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