Re: Xcode 3.2.6 to the latest Xcode - what might I lose?
Re: Xcode 3.2.6 to the latest Xcode - what might I lose?
- Subject: Re: Xcode 3.2.6 to the latest Xcode - what might I lose?
- From: Quincey Morris <email@hidden>
- Date: Mon, 06 Feb 2017 10:44:58 -0800
On Feb 6, 2017, at 06:58 , Stephen Hershey <email@hidden> wrote:
== CAPABILITIES I USE ==
User Interface:
+ scatter source code editor windows across multiple monitors
This is the only one that’s likely to be a problem. Xcode now tends to privilege a window-per-project arrangement, with a single main editing pane plus an assistant pane (.c or .m file in main, corresponding .h file in assistant, frequently). New UI behaviors provide many ways to jump around between actively edited files in the main pane.
It’s certainly possible to open files in their own windows, but it’s not going to be the experience you are used to. After so many years, though, it’s not a discussion worth having — Xcode is what it is, and you’ll like it or you won't.
There are other ways of doing your editing if you don’t happen to like Xcode’s. You could use a text editor like BBEdit, or an IDE like Visual Studio Code. So long as their source file editors use file coordination, editing changes in other apps (whether saved or not) should be seen by Xcode when you go to build. |
_______________________________________________
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