Re: Xcode - An Apple Embarrassment
Re: Xcode - An Apple Embarrassment
- Subject: Re: Xcode - An Apple Embarrassment
- From: Jean-Denis MUYS <email@hidden>
- Date: Fri, 02 Mar 2012 13:13:14 +0000
- Thread-topic: Xcode - An Apple Embarrassment
On 1 mars 2012, at 08:35, Rick Mann wrote:
>
> On Feb 29, 2012, at 19:50 , Brian Barnes wrote:
>
>> If you have a tab open, and click the file in the navigator, it will open over that tab; if you double-click, it will open in another tab EVEN if the original already exists.
>>
>> The solution is to just do it the same way NetBeans, Eclipse, and Visual Studio do it. A double click to open a file. If the tab exist, bring that tab to the front. If it doesn't, create a new one. Or give us that option in preferences. The tabs containing the navigation pane (and changing it when they are changed, also in radar) and the weird way it creates tabs are so completely different from other environments that it's quite bizarre the behavior ever got in there :)
>
> This is what I've been most bothered about in Xc4. I've written several bugs about it. I think of it as a document-window binding. That is, a document should "belong" to a window (and vice-versa).
>
> Note that "document" is used loosely. Of course, source files are actual documents, but you can also think of an execution context as a document in this concept. For example, if I debug my app on one device, that should open a debug-specific window (or bring said window forward). That window should remember its shape and position. If I debug my app on the sim, a *different* debug-specific window should open (or come forward).
>
> My project is yet another document...
This has been mentioned several times - here and elsewhere. I called it the "spatial" model, in reference to the spatial Finder that Mac OS X has gotten away from, much to the disappointment of many, especially John Siracusa in his series of Mac OS reviews. I and others have beaten that horse so thoroughly the poor beast is completely dead. Despite un-humanly hurting that animal, Apple has never even once acknowledged the possibility that there might be something to it, stubbornly driving many of us mad until we broke the bank to buy a couple of screens the size of a football field. As we say in French, all that amounted to no more than "pisser dans un violon" (look it up if you like). At this point in time, I have personally lost any hope for Apple to show any care about this issue (as well as about a few others, first and foremost its bug filing tool). I have now come to live with the fact that every time Xcode replaces the content of a pane against my will, God kills a kitten (or two). Yes I know, many dead animals in this sorry story - though not enough bugs.
Jean-Denis
_______________________________________________
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