Re: Apple's Tools Strategy

* comprehensive selection popups on dot operators

* delete-line (this could be a webview thing)

* tighten up the block-commenting (mostly doesn't uncomment for me - though i use spaces not tabs..?)

* mouse-wavable fields, locals, variables, #defines etc.

* watch/popup debug visualisers

* code-specific syntax colouring (different colouring for .c++, .xml, definable for others like php etc)

* tighter help integration (toc keeps disappearing, Menu Manager Reference etc not immediately accessable

* Tip of the Day, so newbies like me find out about option-double-clicking for help early on

* another TOD for the power of the Jump To Definition command

* less mention of this ... code-warrior...

DISSOLVE.

181. THE NARRATOR'S FACE.

For the first time we see the Narrator's eyes. They are

bright yellow.

NARRATOR (V/O)

As for the Road Warrior... That was

the last we ever saw of him. He

lives now... Only in our

memories...

Dooh dih deh daw, Dooh dih deh daw, Doodadidalee!

(signifying end music)

FADE TO BLACK.

182. END CREDITS.

On 29/10/2006, at 7:02 AM, Mark Munz wrote:

On 10/28/06, Laurence Harris <email@hidden> wrote:

I agree, but when you have a fundamentally good product -- and CW was
that -- I have no problem with copying the parts that worked well for
people, especially when most of your users are going to be converts
from that product.

I'm still waiting to hear specifics. What part worked well for people?
What is it that you're trying to maintain? This issue cannot be
discussed in generalities because I, and I'm sure many other are in
the same boat, are not yet able to read minds, so I don't know what it
is that you are seeking. What is not in Xcode that existed in CW?
Specifically.

Perhaps there is a solution that already exists, perhaps its a
paradigm shift that makes no sense, but without knowing what
specifically we're talking about, we can't have a real discussion on
the topic.

>> it's time to give us better tools!
>
> Ugh! We all want better tools. Even CW doesn't meet that definition,
> else there wouldn't have been 10 versions of it.

It's not nice to take pot shots at the dead. ;-)

I'm not taking pot shots a the dead. The point was that "better" is
such a subjective term. Each version of CW was better than the last. I
think people need to either specifically state their issues or give it
a rest. These general terms like "better tools" are absolutely
meaningless. Even saying "like CW" is meaningless because there are so
many different aspects of the environment.

--
Mark Munz
unmarked software
http://www.unmarked.com/
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/xcode-users/email@hidden

This email sent to email@hidden

References:
	>Re: Apple's Tools Strategy (From: Turtle Creek Software <email@hidden>)
	>Re: Re: Apple's Tools Strategy (From: "Mark Munz" <email@hidden>)
	>Re: Apple's Tools Strategy (From: Laurence Harris <email@hidden>)
	>Re: Re: Apple's Tools Strategy (From: "Mark Munz" <email@hidden>)