Protecting Plugin stacks
bobs at twft.com
Tue Jul 10 13:49:50 EDT 2012
Reminds me of an old Excel spreadsheet I created that would automatigically create a radio log that the operators followed the following day, which would randomly choose music based on a series of parameters, along with commercials, public service messages etc.
I showed them how to save the template with the macros as a new file, then launch the macro that did it all from the Macro window. Everyone get it? We ok? Great. I get a call a couple days later saying the spreadsheet was broken. Someone had opened the original macro sheet and tried to manually enter the log by replacing everything there with entries they typed in themselves. Then when it was all hosed, they saved it. GAWD! When I tried to tell them not to do that, the gal who did it got teary eyed and everyone was looking at me like I was a ogre. I gave up.
On Jul 10, 2012, at 10:30 AM, J. Landman Gay wrote:
> On 7/10/12 12:17 PM, Peter Haworth wrote:
>> I'm about to make my first plugin stack available and wondering how folks
>> who have released plugins in the past have dealt with protecting them in
>> various ways.
> If you've protected the scripts and hidden all sensitive property values, that's about all you can do. If you want to lock down the stack more than that because you want to protect the user from themselves, my approach has always been to let them ruin it. If they write me after they do that, my answer is "reinstall and don't mess with it." You can only do so much.
> Jacqueline Landman Gay | jacque at hyperactivesw.com
> HyperActive Software | http://www.hyperactivesw.com
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
More information about the Use-livecode