• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Xcode - An Apple Embarrassment
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Xcode - An Apple Embarrassment


  • Subject: Re: Xcode - An Apple Embarrassment
  • From: Fritz Anderson <email@hidden>
  • Date: Fri, 02 Mar 2012 11:07:46 -0600

And here's an example of how different people have different priorities.

On 2 Mar 2012, at 9:38 AM, Brian Barnes wrote:

> 3) The tab pane window contains the navigation tree, the console, and the info pane

> 3) The navigation/console/info panes should exist outside the tab pane (and the tabs should only cover the area of the tab pane.)

I'll restrain myself from the general tone of hysteria, but I believe this isn't how it should work at all.

Suppose your screen isn't infinitely wide. Suppose you want to wire up a XIB. You'll need:

* The XIB outline fully extended.
* An editor containing the XIB.
* An assistant editor containing the counterpart header.
* The Inspector area.

These things take up screen width. Depending on your style, a lot of screen width. And you're working with a 13" MacBook Air. I've actually done this, with a modicum of comfort.

What you don't need:

* Any navigator. It takes up width (depending on your purpose, such as examining error messages or search results, quite a lot of width). You can get by with the jump bar, particularly if you keep your XIBs in a single group. (Yes, I wish Xcode's jump bars would not irretrievably drop context.)

Now suppose you also debug code. For debugging, you need:

* A navigator, for stack traces, or to refer to other files.
* The Debug area, which doesn't figure into this discussion because it doesn't take up width.

You do not need:

* The Inspector area.
* An assistant editor.


Your proposal is that whenever you use a tab to switch tasks, you should have to manually reconfigure the navigator, the inspector, the debugger, and the assistant. Every time you switch files.

Forgive me, but I think that's crazy.

_Xcode isn't TextMate. Not being TextMate is not a bug._ The two applications serve different functions. Just because they both have features named "tabs," that does not oblige Apple to have Xcode's feature do no more than TextMate's. Plain-text editors switch among files. Xcode switches among tasks. Those are different functions, and it's confusing only if you expect an IDE to have no more responsibilities than a text editor.

	— F


 _______________________________________________
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


  • Follow-Ups:
    • Re: Xcode - An Apple Embarrassment
      • From: Brian Barnes <email@hidden>
    • Re: Xcode - An Apple Embarrassment
      • From: Fritz Anderson <email@hidden>
References: 
 >Re: Xcode - An Apple Embarrassment (From: Rick Mann <email@hidden>)
 >Re: Xcode - An Apple Embarrassment (From: Jean-Denis MUYS <email@hidden>)
 >Re: Xcode - An Apple Embarrassment (From: Alex Zavatone <email@hidden>)
 >Re: Xcode - An Apple Embarrassment (From: Brian Barnes <email@hidden>)

  • Prev by Date: Re: Xcode - An Apple Embarrassment
  • Next by Date: Re: Xcode - An Apple Embarrassment
  • Previous by thread: Re: Xcode - An Apple Embarrassment
  • Next by thread: Re: Xcode - An Apple Embarrassment
  • Index(es):
    • Date
    • Thread