How to compare bettwen .rev file
Brian Yennie
briany at qldlearning.com
Wed Feb 18 00:31:05 EST 2009
Joe, Tran,
Building on this - instead of counting characters, you could run the
scripts through md5Digest(). Using a hash value is a common approach
to detecting changes that works very well for almost all cases.
It all really depends on the level of changes you need to see - but if
it's just scripting changes, looping through all objects and comparing
their md5Digest() values is a good start. If you want more in-depth
analysis (for example tracking property changes to objects or the
formatting of text), it could be quite a bit more work.
Since there is no "true" version tracking / merging tool for Rev, it
also has a lot to do with your collaborative process. A few people
here have their own homegrown tools for versioning that work quite
well. For those accustomed to CVS / SVN it's not quite the same ball
game, but that's arguably a good thing =).
- Brian
> HI Tran,
>
> This is a fascinating problem; and, probably, not all that difficult
> to resolve.
>
> Write a handler that you attach to a button on each stack that
> creates a numerical list of all the items in the stack, including
> the number of characters in each of the handlers in each of the
> scripts of the items. This might not "always" show differences if
> coincidentally changes are made using the same number of characters,
> but that is not too likely. Send the listings to a file; print the
> file and compare the print-outs. A scripted comparison could be
> made, but is probably not worth doing. This should not be all that
> difficult.
>
> HTH,
>
> Joe Wilkins
>
> On Feb 17, 2009, at 7:53 PM, Nhan, Tran Thi Thanh wrote:
>
>> Dear all,
>>
>> Is there any one who can help answer this question? My group are
>> developing a project and how can we compare the difference
>> between .rev
>> file to know what each one does on the same file because we usually
>> copy
>> the same file to each one's computer and modified.
>>
>> Thanks so much,
More information about the use-livecode
mailing list