ANN: GLX2 3.0.10

[Alex Tweedly]

In this case, it was a revServer script (i.e. simple text file), so 
lcStackDiff wasn't directly applicable, but the display of differences 
in a script in lcStackDiff looks really helpful; you could maybe 
consider extending lcStackDiff to cover .lc and .livecode text files as 
well as scripts within stacks.

-- Alex.

On 04/08/2012 23:57, Peter Haworth wrote:
> Can't kelp putting in a plug for my lcStackDiff plugin.  It will show you
> the differences between two versions of a stack file, including exactly
> which lines were changed in scripts.
>
> Not a replacement for undo, just another tool to add to the arsenal to
> figure out what you might have done to cause a bug to appear..
>
> Pete
> lcSQL Software<http://www.lcsql.com>
>
>
>
> On Sat, Aug 4, 2012 at 2:50 PM, Alex Tweedly<alex at tweedly.net>  wrote:
>
>> I can immediately think of a use case for it. In fact, I experienced it
>> about 10 minutes before seeing this email.
>>
>> In Coda2, editing a revServer file. Save it, upload ("publish") it, test
>> it - disaster. I've messed up something badly, not obviously anything to do
>> with wha I intended to change.
>>
>> Fortunately, Coda2 does "Undo" beyond saves, so I simply "Undid" a few
>> things until I saw a change I hadn't intended, fixed that - and carried on
>> very quickly and easily.
>>
>> Of course, i could have got around it other ways (Dropbox had the
>> previously saved 'good' copy, etc.) but the convenience of just Undo-ing
>> was very helpful.
>>
>> -- Alex.
>>
>>
>> On 04/08/2012 01:55, Mark Wieder wrote:
>>
>>> Bob-
>>>
>>> Friday, August 3, 2012, 8:38:03 AM, you wrote:
>>>
>>>   No no problem, it's just that it's fairly typical to only be able
>>>> to undo back to the last save. I can see myself in a fit of undo's
>>>> after making some horrible coding error that made everything go
>>>> wrong, hitting undo lots of times. I guess I will have to avoid
>>>> that. :-)
>>>>
>>> OK. I'll put that on my to-do list. I was thinking that keeping the
>>> undo list back as far as possible was a benefit, but I can't come up
>>> with much of a use case where I'd want to keep it past the last save.
>>>
>>>
>> ______________________________**_________________
>> use-livecode mailing list
>> use-livecode at lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage your
>> subscription preferences:
>> http://lists.runrev.com/**mailman/listinfo/use-livecode<http://lists.runrev.com/mailman/listinfo/use-livecode>
>>
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode