Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!unmvax!pprg.unm.edu!topgun!mustang!nntp-server.caltech.edu!news
From: carlos@eeyore.caltech.edu
Newsgroups: comp.sys.next
Subject: Re:NOT (click to type) in NeXTstep?
Message-ID: <1990Nov14.230623.12583@nntp-server.caltech.edu>
Date: 14 Nov 90 23:06:23 GMT
Sender: news@nntp-server.caltech.edu
Organization: California Institute of Technology, Pasadena
Lines: 20
Nntp-Posting-Host: eeyore.caltech.edu

As mentioned in a previous article,
a. point-to-focus is generally better for keyboard intensive interfaces.
b. click-to-focus is generally better for mouse intensive interfaces.

A compromise would be to globally use click-to-focus to activate applications
(since NeXTstep is by definition a mouse intensive interface) and either para-
digm within an application according to that application's needs.

For example:
Terminal is keyboard intensive therefore it would probably use point-to-focus.
This would only affect Terminal's windows. Point-to-click would activate other
applications. (Window's should retain focus until the user switches focus to
another window. You would still have focus even if the mouse was in the
background window.)

Draw is mouse intensive. It would use click-to-focus.

Carlos Salinas
"Use the NeXT Luke. Succumb to the dark side of the cube."
"But which side is the dark side?"