I seriously considered using stack files. It would make a lot of things easier than writing and reading XML in ZIP files. But I couldn't risk having to rewrite everything if the use of stack files was rejected by Apple.
Even with my system of transferring XML, these illegal workarounds would be possible. I could code functionality that does not show up in any way in the submission to Apple, and then trigger it with what's in the XML content later. I don't see how Apple can catch every possibility, even if they review the scripts. As my father says, "Locks are for honest people." - Charles On 13 Sep 2014, at 12:07 PM, Richard Gaskin <ambassa...@fourthworld.com> wrote: > AFAIK*, it should be allowable to even use stack files as content containers, > provided they include no executable code. > > This is a odd area though, since it's possible to set up a system of > behaviors in which one could submit an app with one set of functionality, and > later download behavior-driven stack files that include no code but > completely alter the functionality of the software. -- Charles E. Buchwald CEO/Director General Museografica Digital http://digital.museografica.com Mac OSX 10.9.4, LC 6.6.2 Commercial LC Developer Tools: http://buchwald.ca Email Notice: http://wp.me/P3aT4d-33 _______________________________________________ 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
