Re: Xcode - An Apple Embarrassment
Re: Xcode - An Apple Embarrassment
- Subject: Re: Xcode - An Apple Embarrassment
- From: Brian Barnes <email@hidden>
- Date: Fri, 02 Mar 2012 10:38:23 -0500
On 3/2/2012 10:00 AM, Alex Zavatone wrote:
On Mar 2, 2012, at 8:13 AM, Jean-Denis MUYS wrote:
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
This is what I have been alluding to as well. Whomever is responsible at Apple for this "whole screen everything" needs to be shot into the sun. It's so terrible that the OS we used to love has taken this direction.
One rotten apple spoils the GUI direction for a whole platform.
WHO LET THIS HAPPEN?
How many years did they spend at Microsoft?
Can we resurrect Steve?
If there is a focus, it should be on fixing what we have now; again, I
use lots of development environments and while I preferred the
multi-window approach, fixing the single window approach as it stands
would go a long way to making this better.
For instance, a lot of people who don't like the single window approach
are actually basing this view on a *broken* single window approach.
This isn't to start an argument on which is better, but you can't even
form an argument when one side is so broken.
Let's get the bug system to work for us. I've submitted an over-all bug
that combines all my other reports, a copy is below:
Title: Tab Pane Behavior
Product: Developer Tools
Classification: UI/Usability
Version: 4.3
Reproducable: Always
Bug ID: 10971356
Summary:
Xcode's single-window tab pane behaves very bizarrely, and doesn't
reflect any other development environment out there. The main problems are:
1) single clicking a file in the navigator refreshes the current tab
2) double-clicking a file will create a new tab regardless if the file
already exists in a tab
3) The tab pane window contains the navigation tree, the console, and
the info pane
The solution would be:
1) single-clicks only select an item in the navigation tree
2) double-clicks only open a new tab if the file doesn't already exist
in a tab. If it does exist, bring the tab to front
3) The navigation/console/info panes should exist outside the tab pane
(and the tabs should only cover the area of the tab pane.)
Steps to Reproduce:
No steps, this is just how the UI works
Expected Results:
n/a
Actual Results:
n/a
Regression:
n/a
Notes:
This is a combination of a couple bugs that I have posted before, but
they all belong in the same area so hopefully this will make them easier
to track.
Anybody that thinks this is a problem, please submit this bug again.
Mention this bug's ID. This is what Apple tells us to do, and I have
faith they are listening :) Let's follow the rules and drop some bug
reports!
[>] Brian
_______________________________________________
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