On 7/31/05 9:44 AM, a.d. jensen didst favor us with:
> On Jul 31, 2005, at 3:51 AM, Laurence Harris wrote:
>> The only hope I suppose we have is that now that the rest of the CW user base
>> will be switching to Xcode (or at least those who decide to continue doing
>> Mac development), maybe Apple will get more feedback that will result in
>> Xcode being better than it is. Personally I hate it the way it is now too.
>
> I'm not the biggest fan either, but it's starting to grow on me. The
> hardest thing was (and still is) finding your way around all those
> "Get Info" panels.
>
> My suggested "to do" list for xCode:
This is not the best place for this. The best place would be Radar entries
or posts to the Xcode mailing list.
> 1) Speed up the compiles!
>
> 2) Come up with some sort of organizer where all those info panels
> can be accessed in one place for the current project. You can leave
> the existing things where they are, but one central place, with
> notations of what means what, would be extremely helpful
I've fiddles some with Xcode and really did find it's approach to setting
various options and settings to be confusing. It's like Xcode is one step
away from a text file full of environment variables, whereas I want a real
GUI on them, and organized in a way I can find them easily.
> 3) Provide versioning support that doesn't require a freakin' phd to
> set up. I tried following the instructions, letter for letter, to no
> avail and finally gave up. Give me a button that says "use
> versioning" and step me through the process of setting it up
>
> 4) Take the stupid COMMAND-/ key code off that Applescript.
> COMMAND-/ is used in Metrowerks and you can't reassign it in Xcode
> without going out to the Finder and throwing away that Applescript
> file. Not that I could find anyway
>
> My biggest beef, however, the speed, was resolved by me getting a
> much faster machine than the 400mhz G4 I had been using. That's not
> a solution for everyone, so I hope that they'll put some work into
> optimizing GCC.
This is never the right answer IMO. This is like saying the way you solved
getting bad gas mileage was to get a bigger gas tank. No matter how fast
your computer is, the faster your compiler is, the more productive you'll
be. A faster computer just makes the problem less painful.
Larry
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Carbon-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/carbon-dev/email@hidden
This email sent to email@hidden
