Path: utzoo!utgpu!water!watmath!clyde!cbosgd!ihnp4!ptsfa!ames!umd5!uther.cs.purdue.edu!gatech!mcnc!thorin!sigma!steele From: steele@sigma.cs.unc.edu (Oliver Steele) Newsgroups: comp.sys.mac Subject: Re: Hypercard User Interface Message-ID: <370@thorin.cs.unc.edu> Date: 11 Dec 87 15:13:24 GMT References: <34557@sun.uucp> <7469@eddie.MIT.EDU> <34647@sun.uucp> <592@atux01.UUCP> <7729@dartvax.UUCP> Sender: news@thorin.cs.unc.edu Reply-To: steele@sigma.UUCP (Oliver Steele) Organization: University Of North Carolina, Chapel Hill Lines: 16 hugo@dartvax.UUCP (Peter Su) writes: >I don't really think that the "non-standard" parts of the HC user interface >are a big problem. I think the big problem is the parts that Atkinson left >out. To wit: > >1) Multiple windows >2) Better support for the Laserwriter. >3) Drawing tools vs. painting tools. 4) Slow movement from one stack to another. This causes input stuttering (the user clicks on a button in the home card, gets no immediate visual response, and clicks again). Combined with the fact that the double-click is already a valid virtual button on the mac, you've conditioned the user to double-click on HC buttons (Skinner would be proud!), and foo then has to outgrow this conditioning. Of the ~10 people I've watched start learning HC, this has been universal.