moriarty@tc.fluke.COM (Jeff Meyer) (09/25/89)
Well, I've spent five days trying to move my favorite HyperCard stacks --
the initial version of Focal Point -- to SuperCard; and after a particularly
fruitless weekend, have decided to call it a day. I'd class myself as a
mid-level HyperCard programmer, but this program stumped me quite a few
times -- I'd hate to think what the problems a novice would have converting
HyperCard stacks. A few comments/complaints:
1) The documentation. God above, but it sucks. The over-all format --
intro, tutorial, object-by-object description -- is a fine idea, but the
book goes NOWHERE into the amount of detail one needs for putting a
halfway-complex stack together. The seperate scripting booklet (more like a
pamphlet) doesn't even give examples for every command, and the index for
the main manual is laughable. Think of it as a user's manual without the
corresponding reference manual.
Now, of course, HyperCard was this way, too; any useful work was impossible
without Danny Goodman's HYPERCARD HANDBOOK (or some other book). However, I
didn't pay $100 for HyperCard, so I could live with the extra expense. I
know there's a SuperCard Handbook out there for ~$30, but I didn't think it
was essential equipment for use with SuperCard. (And, for all I know, maybe
it's as inept as the manuals.)
Not that the User's manual is all that hot -- quite a few of the tutorial
lessons aren't accurate. The user is suddenly asked to make choices by
SuperCard that aren't described in the step-by-step tutorial, which makes
things pretty confusing for a beginner. I luckily drop-kicked the tutorial
after about a half-hour, but sheesh... Oh, and some of the scripts provided
for use in our own projects don't work. What fun...
So, I've spent about 20 hours discovering things by trial-and-error that the
manual should have helped me with, making design choices that I wouldn't
have taken otherwise. I could have used those 20 hours working on a design
that *would* have worked under SuperCard... Grrrr....
2) My particular bane was absorbing HyperCard stacks into SuperCard. It
took me a while to discover (finally found the info in one of the Q&A
projects) that when you change the font of a background field, it only
changes for the card you've selected. OK, had to make a script that ran
through every card and changed every card in my ToDo stack (732 cards) to
the right font, size, height and font style. Takes a while to run -- only
to discover that it wasn't doing the job. Seems there's a bug that either
a) sets the height correctly, but won't set the font or font style or b)
sets the font and font style correctly, but sets the font size to 0; which
way it goes is dependent on the order in the script for the set
font/style/size command. Lots of trial and error on that one.
3) Not a problem for everyone, but a big one for me: as soon as you put
your cursor in a field that has the "Show Lines" attribute set, the lines
disappear. Plus, you can't move your cursor to any line in a field -- there
has to be newlines on every line before that one before you can place the
cursor there. I know, I know -- that could be useful in some cases. Not
for me in this case, and, more importantly, it's a fair-to-middlin'
difference from HyperCard.
-----
If anyone has workarounds/fixes to these particular problems, I'd love to
hear them. What makes it so damn frustrating is there is a lot about
SuperCard to like, from the scripter's perspective. At this time, I'd say
that if you were building a complex project from the ground up, I'd go for
SuperCard; but if you're planning to absorb a HyperCard stack to build
around in SuperCard, watch out. The pitfalls may be larger than you think.
You're listening to WKDU. No one else is, but you
are.
---
Moriarty, aka Jeff Meyer
INTERNET: moriarty@tc.fluke.COM
Manual UUCP: {uw-beaver, sun, hplsla, thebes, microsoft}!fluke!moriarty
CREDO: You gotta be Cruel to be Kind...
<*> DISCLAIMER: Do what you want with me, but leave my employers alone! <*>