On Tue, Aug 27, 2013 at 7:19 AM, Richard Gaskin <ambassa...@fourthworld.com>wrote:
> I wonder if perhaps you could split the difference, and have your > property-checking routine done during development to build a list that's > used at runtime. That would keep runtime lean and efficient, and unless > you plan on abandoning the utility (which wouldn't make sense of course > after putting so much time into it) you'll probably be releasing new > versions anyway, so keeping it updated with the engine probably won't need > much greater frequency of updates than normal enhancements and bug fixes > would require anyway. I'm thinking of using Bjornke's approach with Docu 2 where his database is tied to a specific version of LC. Whenever a user upgrades to a new version, a new database is created but on subsequent runs, no db creation is needed. Pete lcSQL Software <http://www.lcsql.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