home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.mac.programmer
- Path: sparky!uunet!darwin.sura.net!udel!gvls1!dave
- From: dave@prc.unisys.com (David Lee Matuszek)
- Subject: Re: MacOberon
- Message-ID: <1992Jul29.154809.16204@gvl.unisys.com>
- Sender: news@gvl.unisys.com (IEE news user)
- Nntp-Posting-Host: yggdrasil.prc.unisys.com
- Organization: Paoli Research Center - Paoli, PA
- References: <1992Jul28.231712.27337@fcom.cc.utah.edu>
- Date: Wed, 29 Jul 1992 15:48:09 GMT
- Lines: 42
-
- In article <1992Jul28.231712.27337@fcom.cc.utah.edu> kofoid@bioscience.utah.edu (Eric C. Kofoid) writes:
- >Several months ago, I downloaded MacOberon, crashed my system several
- >times trying to run it, and eventually threw it away.
- >
- >Recently, a newer port appeared on the archives (2.4(0)). Again, I tried
- >it with little success. The expected screen size is a large part of the
- >problem. I can't fault anybody who goes to the time and trouble of
- >porting something to the Mac for free. However, the installed base of
- >Macs with small screens is enormous, and all it takes is a quick look at
- >screenBits.bounds to decide where to put your windows and dialogs.
-
- MacOberon "works" on my Mac (13" monitor). However, the interface is
- a real show stopper. Even if you assume the author had no particular
- reason to follow Apple's interface guidelines, it's still a disaster.
- For example, the "scroll bars" work by holding down some modifier key
- while you click with the mouse to move the selected line to the top of
- the window--but this leaves you with NO WAY to scroll backwards!
- Although MacOberon seems to have quite a bit of documentation, you are
- on your own when it comes to figuring out what to read first.
-
- I downloaded MacOberon because I wanted to find out something about
- the Oberon language, but decided I didn't want to know badly enough to
- hassle with the brain-dead interface. (My interest was only casual;
- someone with more motivation could probably succeed.)
-
- I don't know if the interface is incidental or integral to Oberon. If
- incidental, then, as you say, you can't fault somebody for making a
- free port, and maybe somebody will someday do a better job. But it
- looked as if the interface was part of the Oberon design, and in that
- case you have to wonder if the rest of the language is done as badly
- and with as little regard to state-of-the-art techniques.
-
- Comments are welcome. I'd be especially interested in hearing whether
- anyone thinks Oberon itself is neat enough to be worth the trouble of
- learning the interface.
-
- --dave
-
- --
- - - - - - - - - - - - - - - - -
- I stand by all the misstatements that I've made.
- -- Vice President Dan Quayle
-