I only mention card locking because the elements of a card typically interact with each other quite a bit. Imagine someone renaming a button that a card script accessed by name, or a field that was critical to saving data to a database. Also the process of checking out and in every object in a card could induce insanity.
Bob On Feb 20, 2012, at 10:41 AM, gcanyon+rev wrote: > Agreed that a full implementation would be better; I'm just saying that, > compared to the present setup, where there is no source control whatsoever, a > system that at least allowed merging code in a controlled fashion would be a > huge improvement. > > I would hope we can do better than card-level locking, but better that than > nothing at all. > > Sent from my iPad _______________________________________________ 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
