Re: iCode development tool
Re: iCode development tool
- Subject: Re: iCode development tool
- From: Mark Munz (DevList) <email@hidden>
- Date: Tue, 3 Jan 2006 10:54:31 -0800
The reality is that PB/Xcode are basically GUI wrapper around command-
line tools. I see Xcode as trying to be the next MPW environment (all
things to all people).
Xcode is this hybrid-IDE trying to appease the command-line folks and
trying to appease the GUI folks. Unfortunately, the GUI-side suffers
as a result. The trend seems to be more and more skewed towards the
command line. Personally, I don't think there is a need for this in
most cases. Codewarrior proved this.
I shouldn't have to determine what the command-line options are for
most of the functionality. I shouldn't have to use the command line
to setup something as basic as the company name (5 years and
running). Another one is include paths. The fact is that the build
settings don't give a real GUI to the options that are available.
Sadly, the trend seems to be more and more towards using the command
line in everyday activities (certainly for developers). Part of this,
again, comes from the MPW-like direction that tools are going. Xcode
is so generic that the GUI can't be optimized for what most people
use it for.
IMHO, Xcode focuses too much on the 20% and not enough on the 80% in
the 80/20 rule. I believe that 80% of the "users" (developers) are
looking for a fast C++/Obj-C IDE that can create Carbon/Cocoa
applications.
The key here is focus. Xcode 2.x can be made to look more like
Codewarrior, but the essence of a real GUI-IDE is still missing. It
would be nice if some of the requirements folks would work on
bringing some of the essence of CW into Xcode, not just the look.
Mark Munz
On Jan 2, 2006, at 12:50 PM, Markus Hitter wrote:
Am 01.01.2006 um 23:36 schrieb Boyd Collier:
An iCode development tool! That's a great idea.
Isn't that what ProjectBuilder was?
Until the ProjectBuilder/Xcode team got bombed with feature
requests, of course.
I bet there are lots of us who would love to have something like
this.
You'd need at least one version for Cocoa, one for Carbon, one for ...
Getting rid of redundant technologies in the whole Mac OS X would
be another approach. Xcode would clean out by it's self accordingly.
Markus
- - - - - - - - - - - - - - - - - - -
Dipl. Ing. Markus Hitter
http://www.jump-ing.de/
_______________________________________________
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