On Aug 31, 2012, at 3:54 PM, J. Landman Gay wrote: > On 8/31/12 4:29 PM, Bob Sneidar wrote: >> True enough, but password protecting the other stacks encrypts the >> code in them, so I am not sure what the risk is. I suppose to prevent >> the stacks from being used by themselves, you can add some code in >> preOpenStack that checks what the parent stack is. > > Another reason is that loose files can get lost. That's mostly true on > Windows and Linux because they aren't inside an app bundle. Whenever possible > I try to keep everything in a single file, but sometimes you can't. >
Of course, the big advantage of the splash screen approach is that you can update components of the application without recompiling it (at least on desktop systems.) Devin Devin Asay Office of Digital Humanities Brigham Young University _______________________________________________ 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
