Xcode workflow
Xcode workflow
- Subject: Xcode workflow
- From: Stephen Hershey <email@hidden>
- Date: Fri, 01 Apr 2011 10:45:45 -0400
From: Nathan Sims <email@hidden>
Subject: Re: XCode 4 - Thank You!!
On Mar 29, 2011, at 1:12 PM, Paul Franz wrote:
On Tue, Mar 29, 2011 at 3:06 PM, Nathan Sims
<email@hidden> wrote:
On Mar 29, 2011, at 11:46 AM, Chris Cleeland wrote:
When you first said "Eclipse", I had to choke back a little
regurgitant, because Eclipse is about the worst environment I've
ever
used...for C/C++. For Java it's not so bad though I do find it
to be
a ridiculous resource hog.
I was talking with another developer about Xcode 4 and he equated
it to "New Coke".
Since there are two quite distinct developer camps, Xcode should
have two modes: one which imposes a workflow, and one which
doesn't. Everyone is served, and the problem is solved.
Isn't that called an editor? Because all IDE's are designed to create
a structured environment usually using projects.
No, I'm talking about imposing a workflow (Xcode 4), not merely a
structured environment (Xcode 3).
Xcode 3.1 supports my standard workflow:
(1) create / edit source files
(2) compile
(3) link
(4) execute / debug
(5) repeat 1..4 until satisfied
Does Xcode 4 radically depart from this model? If so, how?
I recall that setting up a new project in Xcode 3 was rather
unpleasant, but it's been quite some time since I've had to do this,
so the memories have mostly faded. If the Xcode team has made
improvements in this department for Xcode 4 - great!
All of my recent apps are 'console' apps. They implement a command
line interface and make no direct MacOS system calls of any kind. If
the Xcode 4 GUI contains features that makes development easier for
folks doing a certain kind of development (for example iOS-based),
that's fine, but these new features shouldn't compromise those of us
doing other kinds of development.
Disclaimer: I have not yet installed Xcode 4, so I'm piggybacking upon
the complaints of those intrepid folks who have actually installed it.
My intention is just to remind the Xcode development team that their
tool has a wide variety of valid uses that should be accommodated. I
hope that mine is one of them :-)
Steve
_______________________________________________
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