Protecting Plugin stacks

[Peter Haworth]

Thanks Jacque.  I've pretty much resigned myself to that approach.  But I'm
still left with figuring out why the plugin doesn't open as a
palette/modeless stack.  Aside from making it slightly less likley that
someone would mess with the properties, that does have the advantage of
forcing the browse tool when the stack is opened.
Pete
lcSQL Software <http://www.lcsql.com>



On Tue, Jul 10, 2012 at 10:30 AM, J. Landman Gay
<jacque at hyperactivesw.com>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:
> http://lists.runrev.com/**mailman/listinfo/use-livecode<http://lists.runrev.com/mailman/listinfo/use-livecode>
>