Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!seismo!rutgers!mit-eddie!genrad!decvax!ucbvax!renoir.Berkeley.EDU!robinson From: robinson@renoir.Berkeley.EDU (Michael Robinson) Newsgroups: comp.sys.amiga Subject: Re: SONIX (was Re: Amiga drive noise) Message-ID: <18730@ucbvax.BERKELEY.EDU> Date: Wed, 6-May-87 03:17:06 EDT Article-I.D.: ucbvax.18730 Posted: Wed May 6 03:17:06 1987 Date-Received: Thu, 7-May-87 07:17:20 EDT References: <3501@gitpyr.gatech.EDU> <4688@utcsri.UUCP> <2250@tekgvs.TEK.COM> <18695@ucbvax.BERKELEY.EDU> <755@puff.WISC.EDU> Sender: usenet@ucbvax.BERKELEY.EDU Reply-To: robinson@renoir.Berkeley.EDU.UUCP (Michael Robinson) Organization: University of California, Berkeley Lines: 26 In article <755@puff.WISC.EDU> chin-lon@puff.WISC.EDU (Chin-long Cheng) writes: >Would someone like to elaborate on what a good musical interface >is in a mouse oriented system? I am very interested. Just for starters, it has to allow the user to input the score using the keyboard. NO ONE would tolerate a word processor that required the user to pull each individual character out of a menu and then place it in the text using the mouse pointer. So why do the people who write music programs design the interface in exactly that manner? I guess because they don't have to use them themselves. The mouse should be used for things mice are good at, like selecting and moving blocks of information (text, score, whatever). Editing a score should not be several times more slow and difficult than editing text. ># UUCP: ...!{ihnp4,hplabs,seismo,topaz,etc.}!uwvax!puff!chin-lon ------------------------------------------------------------------------------ "If you study the logistics and heuristics of the mystics, You will find that their minds rarely move in a line" "The Ranger isn't going to like it, Yogi." Mike Robinson USENET: ucbvax!ernie!robinson ARPA: robinson@ernie.berkeley.edu