Personally, I would recommend you re-evaluate. What's so wrong with allowing your users to share the scripts? Is it really so bad? Much better for everyone.
That said, you can look at using JSXBIN, Adobe's binary format for scripts. But it's a maintenance hassle (among other things).
1 person found this helpful
marc autret has a bit on jsxbin here on his website:
At the same time the OP in a separate post mentioned Mac & AppleScript… In AppleScript you can keep a script file as an editable document but distribute it as 'run only' this will result in a similar thing to exporting to binary from ESTK… In both cases there should be ways in which you can restrict the usage… Say to the mac addresses or machine UUIDs… With ID you can use app.doScript() so in either language you should be able to come up with some thing that won't pose too much trouble…
Thanks for your input.
We are already utilizing JSXBIN files.
The only "issue" with sharing is our competitors have an excellent chance of receiving our scripts because we are handing them over to clients.
Our scripts aren't uber-complicated but we'd like to avoid giving them away.
That being said, I agree, sharing knowledge is great for all parties involved.
And, if our competitors happen to ask a question on this forum that we may be able to answer we would unknowingly be helping them too.
I think we are looking more for a cool way to utilize our script but not have the user be totally aware they are using a script.
If your company can afford to pay for a solution, you can send me a message...
Let me quantify that.
If you simply want to limit script use to specific machines, you should check out APID: http://www.rorohiko.com/wordpress/indesign-downloads/active-page-item-developer/
If you want a solution for deployment and use control, let me know, and I can explain where I might be able to help.