jlc@atux01.UUCP (J. Collymore) (07/07/89)
I have recently purchased SuperCard and have also been following the
comments some of you have posted regarding it. I have not yet, however, begun
to program in SuperCard myself. I too, am concerned about several things I HAVE
heard on the net, or read in the owner's manual, such as:
1) Any stand alone document automatically becomes 350K in size,
2) All design/programming work must be done in SuperEdit,
3) Only a limited ability to run/test your scripts while in SuperEdit,
4) The scripts, whether converted from HyperCard or created in SuperEdit, run
MUCH SLOWER than the same (funtionality-wise) stack written in HyperCard.
These all seem to me to be MAJOR deficiencies in SuperCard. Since I have not
yet sent in the big 5"x7" comment postcard Silicon Beach includes with the
package, I would like to ask those of you SuperCard users out there to send me
a list of your concerns, comments, and suggestions for improvements to
SuperCard which I would like to include in my postcard/letter to Silicon Beach.
I think this might be a way to get Silicon Beach's attention, and optimize
their response/resolution to these concerns in future releases of SuperCard.
Please e-mail me your concerns in a list format. I will also try to post the
list to the net (since others of you may find it useful).
Thanks for your contributions.
Jim Collymorekurtzman@pollux.usc.edu (Stephen Kurtzman) (07/07/89)
In article <1364@atux01.UUCP> jlc@atux01.UUCP (J. Collymore) writes about SuperCard deficiencies. One of which is: >4) The scripts, whether converted from HyperCard or created in SuperEdit, run > MUCH SLOWER than the same (funtionality-wise) stack written in HyperCard. This is surprising. So how do they justify the name adjective "Super"? I would have thought Silicon Beach would have addressed script execution speed since it is a common complaint about HyperCard. Perhaps HyperCard will be similar to Algol in that it will be a vast improvement over all of its successors.