Hi Bob, As mentioned in my original email, I don't consider detecting changes in data part of this project. It would be kinda like asking the tool to check the contents of two snapshots of an SQL database that is somehow linked to a stack. That's not to say it's not important, just beyond the scope of what I have in mind (if I ever do anything!).
There's definitely more issues that would have to be resolved, one of them being what you mentioned - dynamically created/deleted objects. Off the top of my head, I'd say that the versioning would have to look at the base version of such a stack (with no dynamic objects) and rely on changes in the scripts that create/delete objects dynamically to detect changes in how and when that is done. Plus there's a bunch of other custom objects out there that would have to be dealt with. As an example, I'm just checking out the Data Tree product which probably has its own set of issues to consider in terms of versioning. Pete On Tue, Feb 21, 2012 at 9:40 AM, Bob Sneidar <b...@twft.com> wrote: > The temporary objects in a datagrid change dynamically IF data is > reloaded. What if the developer is using a datagrid as a static list and > needs to restore the contents? I think the solution is to bypass the > temporary objects of a datagrid, instead saving the datagrid data in some > fashion (see my functions for converting an array to text and back again) > as a special case. The first time a stack is "versioned" it could present > the dev with a list of datagrid objects and allow the dev to choose between > versioning the contents or the structure + data. > > Where things are going to get really dicey is stacks that are constantly > creating and deleting objects and groups. I am not a big fan of using > Livecode this way, but people do, so there you are. > -- 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
