That's smart Mark - if I have got you right. That would make your diffs a "diff script" - that is a shorter script that you can execute on a stack to make an update? Or am I dreaming :)
On 03/03/2008, Mark Wieder <[EMAIL PROTECTED]> wrote: > > David- > > > >I use a similar technique for storing stacks in SVN. When scripts are > saved > > I have hooks which also export text files to SVN and write out metadata > > for > > indexing purposes. > > > > What I have settled on is saving a stack as a text file series of xtalk > commands for recreating it: > > create button > set the name of it to "btnCancel" > etc... > > Then I archive the previous version as only the properties that have > changed: > > set the name of button "btnCancel" to "button" > > That way I can recreate a stack quickly without having to traverse a chain > of changed properties and not have to worry about the integrity of the > archive. > > ...and voila! instant diffs. > > > -- > > Mark Wieder > [EMAIL PROTECTED] > > > > _______________________________________________ > use-revolution mailing list > use-revolution@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your > subscription preferences: > http://lists.runrev.com/mailman/listinfo/use-revolution > _______________________________________________ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution