Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!usc!wuarchive!sdd.hp.com!elroy.jpl.nasa.gov!ncar!zaphod.mps.ohio-state.edu!lavaca.uh.edu!menudo.uh.edu!sugar!peter From: peter@sugar.hackercorp.com (Peter da Silva) Newsgroups: comp.sys.amiga.advocacy Subject: Re: Hooks into the OS vs doing it all yourself (Was Re: Clueless Mac<>) Message-ID: <7689@sugar.hackercorp.com> Date: 3 Feb 91 00:54:59 GMT References: <1991Jan31.011702.12095@Neon.Stanford.EDU> <1991Jan31.044116.25645@mintaka.lcs.mit.edu> <1991Feb1.032445.15245@Neon.Stanford.EDU> Distribution: usa Organization: Sugar Land Unix -- Houston, TX Lines: 28 In article <1991Feb1.032445.15245@Neon.Stanford.EDU> torrie@cs.stanford.edu (Evan J Torrie) writes: > This sounds like more of a hacky solution that the Apple method of > having a window definition function. It is. Each system has their own strengths. The Amiga's is the basic system software: it's by far the best commercial system shipped with any PC for any price. Apple's Multitasking Charade using the DAs hooks is a kludge by comparison. And the Amiga's method of changing global window behavior at the lowest level is a kludge compared to what the Mac does. A saving grace to the Amiga's method is that it can be done efficiently without making normal applications unnecessarily chummy with the window system internals. And the Amiga's method of handling higher level events through messages is *much* cleaner. Message passing is about the easiest way to synchronise concurrent processes and pass information betwen them. > The places where it is used on the Mac, is in programs which want to > do dynamic updating of displays... > How would you do a similar thing on the Amiga? You set the gadget to send MOUSEMOVE messages and update the number in the display as you get MOUSEMOVE messages from that gadget. -- Peter da Silva. `-_-' .