plea! (was Re: Two enhancement requests)
plea! (was Re: Two enhancement requests)
- Subject: plea! (was Re: Two enhancement requests)
- From: Roy Lovejoy <email@hidden>
- Date: Sun, 8 May 2005 22:33:27 -0700
On May 8, 2005, at 9:56 PM, Chris Espinosa wrote:
On May 8, 2005, at 9:44 PM, Larry Gerndt wrote:
1. Syntax Coloring - Be able to syntax-color both system-defined
API's (Carbon and Cocoa) and user-defined symbols (functions,
classnames, and methods).
2. Editor - Be able to special-click to select subwords.
Larry, thanks for the support.
Enhancement of syntax coloring is oft-requested, probably the
most requested enhancement.
This is not an XCode bash by any means.. This is simply a plea to make
the transition to XCode a pleasurable experience, and not one filled
with depression & regret...
You guys do know that you would gain 100% mindshare if you offered as
complete a "virtual codewarrior" as you could.. (alternate UI/ window
grouping/key binding etc)
Some of us have lived & breathed by metrowerks IDE, since we lived &
breathed by Think C before it.. (and Think Pascal.. and TML Pascal...)
despite all the way-cool _engineering_ features in XCode, and the
hand-glove fit of IB/Cocoa/XCode, to a majority of Codewarrior folk,
XCode just feels... 'wrong' to a "project thinking" developer..
hard to put a precise finger on it, but my vague, 'from the hip
assessment' is that XCode feels more like Visual Studio, than it does
any mac program on the market..
key bindings are an obviously good, high traffic step, though when I
selected those, very few actual binding analogs were changed (see other
posting).. I had to hand-enter all my beloved, decade-old, muscle
memory strokes..
the whole concept of 'project manager' in XCode may be much more
'powerful' or 'liberating', but again, to me, it screams 'thinly veiled
make file'.. In Codewarrior I had infinite control on how I group my
source files, association by function, etc.. (Hiding third party source
completely). Please tell me I'm missing something, because now, all the
sources are grouped into ONE "Sources" hierarchy??? I have to sift
through all the third party stuff next to my source??
another quick anecdote is that I've just started a contract where the
folks are pretty fresh with XCode themselves.. I couldn't figure out
why their nibs weren't in their final build, as they were in (what I
considered to be) the 'project'..
turns out they were in the "Nib file group", but not in their "Bundle
Resource" build phase..
this thoroughly confused this veteran mac developer (circa 1984), as it
begs the obvious question, why would a nib be *in* a project but not be
"IN" a project..
(okay, i can see some low-traffic possibilities, but i would think by
_default_ they would be..)
I don't know if Codewarrior 'coddled' the developer, or just had it's
defaults magically set up to do what the developer wanted 95% of the
time, (so it just _seemed_ to always do the right thing the first
time), and left the 5% to be later edited by hand. (as opposed to what
feels like XCode not doing anything by default, and leaving 100% to be
hand tweaked).
it _seems_ like XCode is powerful enough and flexible enough to present
the project information in a myriad of ways..
i'm just asking for a little bit of 'emulated' sanity for us metrowerks
expatriots, "on the side", "as an alternate", etc.. once we understand
the infinite power, THEN let us flip to the 'native' mode...
there was a _reason_ why folks used metrowerks (and think c) over MPW
all those years... :-)
_______________________________________________
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