On Sep 17, 2005, at 5:44 PM, Nick Zitzmann wrote:
If you'd like Xcode to look like CodeWarrior, then you can turn on the condensed interface, which is what I've done.
that's what I ended up doing... and that helps me to manage the complexity of XCode. And enable CW keyboard binding in the Preferences... I feel right at home except the editor's speed.
Also read the doc! It's different from CW. So, fire up those brain cell in learn mode again. Keep an open mind, someone has been putting serious thoughts into version 2.1 and I think they deserve some credits here. Did they open up the XCode WWDC session to the public as well?
I switched from CodeWarrior Pro to Project Builder 1 a long time ago, because PB could build Mach-O binaries long before CodeWarrior could. I didn't think CFM Carbon would stay around forever. I was correct.
depends on who you talked to. I just got involved into porting a tool that's CFM Carbon. If it isn't the Intel announcement, I think the tool will be CFM forever!
I believe the gaming industry are mostly CFM based?
What's the problem with Xcode's UI? You haven't told us anything. I've been using Macs since System 6, and the only problem I have with Xcode's UI is it's not possible to edit framework header settings in condensed mode. The only thing I find frustrating about Xcode is the breakage I mentioned above.
OK, XCode, by nature, is way more complicated (or capable, it's one of those half empty half full thing, isn't it) than CW. What's worse is, from a UI preceptive, it's also way more complicated. Unfortunately it's also the default mode, which put everyone right in front of your face. To me, it does not give a good first impression.
Remember CW modeled after THINK C. Took their best, etc. So moving from THINK to CW took about 0.5 day to get familiar. And many of us has been evolving with CW... learn new features (many from developer's requests) along the way... and honestly CW has done a good job to make our lives easy.
Case in point, create a sample project... in your project folder, create a folder called 'src' and drag main.c into the folder in Finder. Launch XCode project and try to compile... you can't 'cos main.c is nowhere to be find. Repeat the exercise with CW.
Now I am not saying XCode is not usable but we are so custom to all this CW assumptions that XCode could consider some of them? They are not that bad. May be this will make us all happier?
So,
1. Usability study with real CW user, get the best out of them and add them to XCode. 2. Make more real time examples
Another example, I created a Carbon sample app, add a resource fork resource file to the project window, compile... now, open the newly build app, go to myapp.app/Contents/Resources/, and examine the resource file. Repeat the exercise with CW.
Again, XCode 2.1 is good, I can never stand the other XCode's (sorry, don't have time to learn when CW still works) but I can see the new XCode could get better.
pete |