ForIf it is inside the application bundle and that is inside the Applications folder then users with managed accounts won't be able to allow changes, as in the case of an update. Perhaps this is an unusual situation.
On Jul 22, 2011, at 2:22 PM, Ken Ray wrote: > > On Jul 22, 2011, at 4:12 PM, Scott Morrow wrote: > >> In the case of a "splash screen" application where the executable "appears" >> to have the ability to update itself by deleting the old stack files >> containing the UI / logic and downloading and running new stack file(s), >> where would be the best place to put the UI / Logic files? I had come to the >> conclusion that the user's Application Support folder was best, since a >> user with a managed account could still update the application without the >> need of a system admin. > > Yes, that's one place to keep it - the other is inside the application > bundle. For *me* it comes down to this: will the location of these stacks > need to be "user-accessible"? Meaning, will the user ever need to look at or > manipulate them? If the answer is "yes", then I'd suggest ~/Application > Support/<appName>. If not, then I'd suggest putting it inside the application > bundle. > > > Ken Ray > Sons of Thunder Software, Inc. > Email: k...@sonsothunder.com > Web Site: http://www.sonsothunder.com/ > > _______________________________________________ > 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 _______________________________________________ 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
