🚀 go-pugleaf

In article <dillon.0qh2@overload.Berkeley.CA.US> dillon@overload.Berkeley.CA.US (Matthew Dillon) writes:
| 
|     Go into librarian with all Developer items selected and lookup the word
|     'keyboard'.  Result?  82 entries found.
| 
	Try "keycode", only two entries and if you "find" all references you
stumble into the following:

data.key.charSet indicates the character set and data.key.charCode indicates
the character code, which together correspond to a particular character.  The
key code, data.key.keyCode, which maps to a key on the keyboard, will rarely
be used.  data.key.keyData, which can contain hardware-dependent data, is
undefined for the NeXT keyboard.  See *Keyboard Information: below for more
information.

|     I think part of the documentation problem, and I do stress 'part', is
|     that librarian simply sucks when it comes to finding things.  It takes
|     forever because you invariably get umpteen entries with no
|     prioritization... most of the entries are useless to you and you have
|     to go through them one at a time.  Librarian really ought to prioritize
|     entries meaning that NeXT has to think up of some way to embed specific
|     references in the documentation.
| 
| 					    -Matt
| 

	I agree!  The problem is that NeXT is critically under-staffed in all
areas (except maybe in their assembly factory), probably because of budget
constraints.  What NeXT should do, maybe after the release of NeXTSTEP486, is
move ALL effort to NeXTSTEP4.0.  In this release provide no new functionality,
but focus on fixing bugs, code/documentation clean-up, and pushing performance
to its limit.  Maybe they can get it right this NeXT time around!

--Felix