A lurkers ravings (was RE: Smalltalk beep -> XXX beep?)

Russell Penney rpenney at genesyslab.com
Tue May 13 01:21:49 UTC 2003


I disagree.

Why is beep in Object at all? All the objects in Squeak don't need to
know how to beep. The sound system needs to know how to beep.
It seems to me that this is the reason Squeak is spaghetti code in the
first place, people aren't sure where to put something so it goes in
object and now us newbies cant find anything or figure out what to use.
Plus you are teaching us bad object design habits! :-)

IMHO AbstractSound should be in the Kernel with the base methods
(beep,etc) as primitives. When the Sound module gets loaded they are
overwritten (or tests are used instead) to play actual sounds.

Andreas you commented in AbstractSound "beep in the presence of the
sound system. this method may still #primitiveBeep if sound	support
is disabled or doesn't work or whatever". So use that please don't clog
up Object with methods that aren't required.

Object>beep should be depreciated.

Russell

-----Original Message-----
From: squeak-dev-bounces at lists.squeakfoundation.org
[mailto:squeak-dev-bounces at lists.squeakfoundation.org] On Behalf Of Tim
Rowledge
Sent: Monday, 12 May 2003 8:36 AM
To: squeak-dev at lists.squeakfoundation.org
Subject: RE: Smalltalk beep -> XXX beep?

"Andreas Raab" <andreas.raab at gmx.de> wrote:

> Stef,
> 
> I think this should be factored along the lines of:
I'll second that; typically #beep hooks up to the ascii control-G type
beep that just about any machine can make some sort of attempt to
render.

tim

-- 
Tim Rowledge, tim at sumeru.stanford.edu, http://sumeru.stanford.edu/tim
Useful random insult:- Can't find log base two of 65536 without a
calculator.



More information about the Squeak-dev mailing list