All good points. I guess I'm thinking of a different situation that multiple people working on the same project. When someone reports a bug that crept into a particular version of an application, it would be useful to see what changes were made to the stack that might have introduced the bug.
But I agree that writing the code to reproduce a stack file as XML would be a lot of work and probably not worth the time and cost - unless someone believed it would be a product that LC developers would buy.... Pete On Mon, Jan 23, 2012 at 9:48 AM, Richard Gaskin <ambassa...@fourthworld.com>wrote: > As for XML version control: > > It's possible to write an XML description of a stack and reproduce it with > complete fidelity. In fact, the ability to set the ID of any object was > added specifically to support such efforts, and I believe such a project is > in development now to help LC devs use standard version control systems for > larger projects. > > But it's a lot of work and a lot of time spent on the version control > process that could be spent on product features, so the cost/benefit > analysis should be done carefully for the project at hand. > > In my own projects I usually have teams of between 3 and 5 devs, and we > usually assign stacks to programmers according to their skills and interest > so there's rarely any overlap. In fact, the largest xTalk project I ever > managed had 20 devs building a CBT system for a Fortune 500 company and we > still used only a stack-based check-in/check-out. > > One of the attractions to more granular version control is the ability to > have multiple devs working on the same objects simultaneously. > > But is that something you really want to do? > -- Pete Molly's Revenge <http://www.mollysrevenge.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