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: Igor Delovski <email@hidden>
- Date: Mon, 06 Feb 2017 21:28:45 +0000 (UTC)
Well, I was one of those 3.2.6 die hards before I found out how to make Xcode 4 and all the later versions behave.
Here is a link to a small album with a few screen shots: http://imgur.com/a/5zNFC
All of my projects have these several dummy files I have in separate windows so I can consistently and constantly use these windows for their designated purpose.
A special search window, console window, run-debug window....
I takes some discipline and getting used to, but now it's a second nature. For example, before running a project I need to switch to that run-debug.h window and start from there. That window is already partitioned for debugging and when I land somewhere with a breakpoint my regular editing windows remain intact, positioned where I left them.
I can go into more details, but these few images should tell you everything you need to start on your own.
Igor
--------------------------------------------
On Mon, 2/6/17, Quincey Morris <email@hidden> wrote:
Subject: Re: Xcode 3.2.6 to the latest Xcode - what might I lose?
To: "Stephen Hershey" <email@hidden>
Cc: email@hidden
Date: Monday, February 6, 2017, 7:44 PM
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.
-----Inline Attachment Follows-----
_______________________________________________
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
_______________________________________________
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