Saving a standalone

[andu]

--On Thursday, June 27, 2002 20:02:34 -0400 Shari <gypsyware at earthlink.net> 
wrote:

>> Such protections are afforded all password-protected stacks, standalone
>> or not.
>
> But if you are creating a standalone to distribute, a password is a bad
> thing.  The objective is to create a program, to distribute, but have
> whatever data you want "hidden" to remain that way even if someone tries
> to get into it.  It is easier to "break into" a stack than a standalone,
> at least in Hypercard.  So I'm assuming that MC is similar.  That's why I
> prefer data not to be in a stack.  But since that is not an option, how
> would one best protect the stack?  So that the standalone can store and
> retrieve data from it, but people can't get into it.

You've heard it at least twice: password protect it. That means all scripts 
are encrypted and the stack requires a password in order to decrypt the 
scripts for reading or editing.

>
> --
> --Shareware Games for the Mac--
> http://www.gypsyware.com
> _______________________________________________
> metacard mailing list
> metacard at lists.runrev.com
> http://lists.runrev.com/mailman/listinfo/metacard
>



Regards, Andu Novac