Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!wuarchive!gem.mps.ohio-state.edu!tut.cis.ohio-state.edu!pt.cs.cmu.edu!andrew.cmu.edu!bader+ From: bader+@andrew.cmu.edu (Miles Bader) Newsgroups: comp.sys.amiga Subject: Re: Advantages of keeping binaries out of S: Message-ID: Date: 14 Nov 89 18:22:01 GMT References: <3770@nigel.udel.EDU> <0ZKoagy00UkaFnd_R7@andrew.cmu.edu> <2157@leah.Albany.Edu> , <1940@atanasoff.cs.iastate.edu> Organization: Information Technology Center, Carnegie Mellon, Pittsburgh, PA Lines: 23 In-Reply-To: <1940@atanasoff.cs.iastate.edu> jwright@atanasoff.cs.iastate.edu (Jim Wright) writes: > bader+@andrew.cmu.edu (Miles Bader) writes: > | wfh58@leah.Albany.Edu (William F. Hammond) writes: > | > "devs:printers", "devs:keymaps" are things we already have and "devs:sounds" > > This sounds like the best idea so far. > > | Notice that the printer drivers and keymaps are both files used for > | interfacing with particular devices... Random sounds are not... > > Why call a hardcopy system and an input system "devices", and exclude an > audio system? A sound is to the audio device as a document is to the printer. They are both input. Or an image file to the screen. You don't put your dpaint files in devs: do you? You might argue for putting bell sounds in "devs:conbeeps" (which would be directly referenced by the CONSOLE device) or something, but please don't call it "devs:sounds", because then people will start assuming it is a general storage area for any sound, no matter what the use. -Miles