Why only for LiveCode Community? It might be nice to sandbox the running of any stack on any version. There's currently a discussion on the engine contributors forum about needing an option to disallow the setting of scripts entirely in a running standalone for security reasons. Perhaps there's a broader scope to the issue. Maybe the stack that's loading a stack should be able to give it rights to access libraries, set globals etc. Lots to consider there.
On 16/04/2013, at 11:52 AM, Alejandro Tejada wrote: > How does Sandboxing code works in LiveCode Community? -- M E R Goulding Software development services Bespoke application development for vertical markets mergExt - There's an external for that! _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
