Re: NSTableView edit text-field help please?
Re: NSTableView edit text-field help please?
- Subject: Re: NSTableView edit text-field help please?
- From: jgo <email@hidden>
- Date: Mon, 28 Jan 2002 17:24:12 -0800
>
I am interested in how and why people find and fail to find
>
information because I am trying to reorganize it and improve
>
upon it. If I ask questions like "why didn't you do this.."
>
it is because I really want to know why...
>
>
> If it were [I], I'd look for "finish editing", "terminate editing",
>
> then "end editing" before hitting on "endEditing".
>
>
"end editing" works fine for finding the relevant information.
>
See, you would have found it :)
I never said I wouldn't eventually find it, only that finding it would
eat up time which is at a premium. Let's see, we're all trying to
develop software, reading 200-300 messages per day (2 omnigroup lists,
2 Apple lists, mailman list & I probably spend far too much time
composing messages), reading Hillegass, storing quotes from books
I've already read, searching for work, trying to stay in touch with
friends, co-workers & allies, sending out the company news-letter,
trying to maintain some tenuous political involvement so as not to
be blind-sided by the next assault on rights...
After having read through significant portions of the docs, how much
time should one devote to a search for a particular detail? How many
hours are there in a day? I think it boils down to that -- to
extreme time pressure all around causing one to give up on a particular
search too early, often before trying that one more search string
that might have done it -- might have, because the searcher doesn't
know before taking the time to try it.
The tying in of PB to the docs helps, certainly, because it generally
takes one directly to something that has a higher probability of
being what's desired.
>
> Since I'd be searching the AppKit.pdf first, I'd be wading down through
>
>
Why not start with google (on Apple's site or not)?
Too many false positives, as noted previously. But, since you mention
it, the category check-boxes in the "advanced search" always generate
some agony. Unless I'm certain it's in Cocoa, there's no good
alternative most of the time. It'd be nice to have a AppKit &
Foundation & SystemOverview options, and something that would reflect
"command or function in UNIX/Darwin" other than "source code for Darwin".
I'm off-line as I compose this, so will leave it with those examples,
though others would come to mind if it were in front of me.
>
Why not use MTLIbrarian or MarshmallowLibrarian on your own disk?
Call me paranoid & shy. We've got one guy at the office who scans
'round the net & down-loads every toy in sight. His machine crashes
because it's Tuesday; it crashes because it's an even-numbered hour
of the day; it crashes because somebody's dog crossed the street.
He sends me the dumps. He sends them to anybody who will look at them.
I think our director of SW engineering had several hundred before he
left, and I had about 150 from then until I switched to a new machine.
About once a year, we find an extension conflict, or a mistake in
memory management in something. Of course, the boss would like us
to use GIA for all that sort of thing.
>
> it to get to the right one. If it were [something else] in Foundation,
>
> then I'd have to close AppKit.pdf, open Foundation.pdf, search it.
>
> If it were in one of the other assorted docs, I wouldn't find it
>
> until going to ADC, choosing "Advanced Search" because the regular
>
> one flat doesn't work (doesn't even display a form field or let a
>
> search string be entered), and then wading through the (statistically
>
> expected) huge numbers of false positives to get to the right one.
>
> He said he found an "endEditing" for NS Cell, but hadn't for NSWindow.
>
>
>
> > Why didn't you read about the field editors attached to windows?...
>
>
>
> Just because "field editor" doesn't immediately jump into mind
>
>
The point of the question and the part you clipped is that
>
the field editor is prominently mentioned at the top of most
>
cell class documentation....
Yes, if you would check the archives, you would know that I'd been
down that road. It's the same story; lots of false positives.
If persistent, one might find the one reference sought, buried
amongst many others, none of which are well tied together.
Actually, this topic has better contextual ties than most.
But, do you think that merely because a term appears in many places
in the docs that it should be memorable? It's more memorable than if
it had been dropped only once, certainly. But repetition is only one
determinant of memorability. Another is unique aptness -- whether the
situation immediately evokes the term, or others pop to mind before it.
Hence:
>
> If it were [I], I'd look for "finish editing", "terminate editing",
>
> then "end editing" before hitting on "endEditing".
John G. Otto, Eagle Scout, Knight, Cybernetic Praxeologist
Existence, Consciousness, Identity, Life, Liberty, Property, Privacy, Justice
<
http://gosc.nisus.com/~giovanni>