Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!cs.utexas.edu!tut.cis.ohio-state.edu!bloom-beacon!husc6!psuvax1!psuvm.bitnet!cunyvm!byuvax!taylorj
From: taylorj@yvax.byu.edu
Newsgroups: comp.sys.mac.hypercard
Subject: RE: Any info on how Supercard STACKS up ?
Message-ID: <640taylorj@yvax.byu.edu>
Date: 21 Jun 89 00:13:29 GMT
Lines: 22

I've played with SuperCard for a little bit, and altough I was very excited and
pleased at first to see wonderful features such as full color support, card
sizes up to 32'x32' (yes, that's feet!), draw-oriented graphics (bitmaps are
supported as draw objects), PICS animation, multiple windows, any style window
(including dialog boxes and floating windoids), built-in icon and cursor
editors, full control over all menus, and much much more, the more I use it the
more I have misgivings.  SuperCard just doesn't "click" like HyperCard.  It has
lots of little quirks and annoyances.  It's much harder to develop and debug
with.  There is a separate editor, so you have to switch to the interpreter
before you can run things.  There is a "runtime editor" (written in SuperTalk,
believe it or not) that let's you do basic editing at runtime, but it's pretty
cumbersome.

I fully expected to switch a lot of my HyperCard projects over to SuperCard,
but I'm having second thoughts.  However, many of SuperCard's extended features
are very useful and will be invaluable for some of the more complicated
projects.  My recommendation would be to wait for HyperCard 2.0 and only switch
to SuperCard if HC 2.0 doesn't cut it.

Disclaimer: Keep this and all other postings out of reach of children.

Jim Taylor
Microcomputer Support for Curriculum
Brigham Young University
taylorj@byuvax.bitnet