The really compelling reasons for me is properties, and certain limits placed on a compiled app. I got into the habit of using properties to store information from session to session, and since a compiled app cannot be modified, I cannot do that. At least that is my understanding.
Bob On Aug 31, 2012, at 3:03 PM, Peter Haworth wrote: > Yes, it's kinda the general untidiness of the splash stack approach that > gets to me. One compiled file is much better untless there's a really > compelling reason why you can't do that. > Pete > lcSQL Software <http://www.lcsql.com> > > > > On Fri, Aug 31, 2012 at 2:54 PM, J. Landman Gay > <jac...@hyperactivesw.com>wrote: > >> 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. > _______________________________________________ > 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
