LiveCode Forums.

Hi,

Once a Stand Alone has been finished, what is the best way to protect it for distribution..?

I have noted that you can Encrypt the Stack in the Application Settings, is that all that is is required to 'seal' the app..?

Thanks
TC

Hi TC,

what exactly do you want to protect?

If you add a password to your stack(s) then at least your scripts cnnot be read, if someone opens the app in a simple Editor.

Everything else is hardly to protect:
Images -> screenshots
Audio/Video -> special screen- and audio-grapp apps
etc...

If oyu wnat to prevent software piracy, this is another beast.
This is possible, but not so easy.

Here the first thought should be: Is is worth the effort?


Best

Klaus

Yes, basically code protection, so the encrypt stack should cover that..?

So effectively no one will be able to read the code with any editor including Studio etc..?

Thanks
TC

Yes

Hi Klaus, How can I test the file to see if the encryption is working..?

Hi TC,

open the standalone or a password-protected stack in any editor (like "TextEdit" on the Mac, sorry no idea of Windows).
You will only see "glibberish"


Best

Klaus

Hi

With notepad yes its gibberish, but if I open it with Studio it opens no problem and code is availble for all to see..?

Why would that be..?

TC

Dear topcat888,

The code is only visible if you forgot to set a password for your stack.

There are two ways to set a password for standalones. You can set a password for each individual stack, e.g. using the message box to execute the following line:
or you can set passwords for all the stack files of your project in the standalone builder settings. If you do this, your stacks are only protected after they have been copied to your standalone, which means that the originals will stay unprotected.

Best,

Mark