home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!ogicse!reed!sharvy
- From: sharvy@reed.edu (V Headshape)
- Newsgroups: comp.sys.mac.programmer
- Subject: Hypercard & OOP
- Message-ID: <1992Jul23.074204.6270@reed.edu>
- Date: 23 Jul 92 07:42:04 GMT
- Article-I.D.: reed.1992Jul23.074204.6270
- Organization: Reed College, Portland, Oregon
- Lines: 19
-
- I recently read a book on object-oriented programming (which I have
- never tried) , and was struck by the correspondences to hyperCard. It
- seems like backgrounds are analogous to abstract classes in OOP, while
- cards function as specific instances of a class. So, for instance,
- you could define generally an object (say, a house) in a background script,
- and then the cards of that background would be particular instances of that
- object, which would "inherit" the general characteristics defined at the
- background level; the card script would then define the particular
- properties of the particular object that the card represented.
-
- Unfortunately, backgrounds cannot contain other backgrounds, and cards cannot
- contain other cards, so the inheritance is limited to single level, which
- leaves us with a rather toy-like version of true OOP. I hope future versions
- of hyperCard will develop the OOP potential of hyperCard, or that some
- implementation of OOP for the Mac in the user-friendly, GUI, spirit of
- hyperCard will be developed. Seems like an exciting area.
-
- --
- Liberate the Weirdoes and You Liberate the Squares
-