Hey that is a great tip! I used to use an old OS 9 utility to do something
similar between old and new code bases.
Bob
On Aug 9, 2012, at 8:50 PM, J. Landman Gay wrote:
On 8/9/12 10:42 PM, Kay C Lan wrote:
Then there is the process of retrieving lost data. You can't just open up
any of
Mike-
Thursday, August 9, 2012, 1:09:39 PM, you wrote:
Are we taking suggestions in this thread? If so:
1) The parser should, when colorizing and capitalizing control structures,
include the IF keyword (THEN, ELSE and END are included)
2) Code collapse/hiding with disclosure triangles, and
I was too lazy to create a profile, which is why I did it anonymously.
--
On the first day, God created the heavens and the Earth
On the second day, God created the oceans.
On the third day, God put the animals on hold for a few hours,
and did a little diving.
And God said, This is good.
whoops - it looks like I do have a login #failMe
___
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
Kay: It's been pointed out here before. (I'm sorry I don't remember by whom...
was it you, Jacquie?) that you can use Dropbox in this way. Of course you need
a net connection. If you keep your stacks in your Dropbox desktop folder,
Dropbox will store 30 days worth of previous versions, or ALL
On 8/9/12 12:28 PM, Charles E Buchwald wrote:
Kay: It's been pointed out here before. (I'm sorry I don't remember
by whom... was it you, Jacquie?) that you can use Dropbox in this
way. Of course you need a net connection. If you keep your stacks in
your Dropbox desktop folder, Dropbox will store
Are we taking suggestions in this thread? If so:
1) The parser should, when colorizing and capitalizing control structures,
include the IF keyword (THEN, ELSE and END are included)
2) Code collapse/hiding with disclosure triangles, and construct lines
would be great.
--
On the first day, God
Mike-
Thursday, August 9, 2012, 1:09:39 PM, you wrote:
Are we taking suggestions in this thread? If so:
No, I don't want to pollute this list with suggestions and bug
reports. Please file those as issues at the bitbucket site.
--
-Mark Wieder
mwie...@ahsoftware.net
Charles-
Thursday, August 9, 2012, 10:28:41 AM, you wrote:
I haven't had to use it yet,
I have, several times. It's on my list of bacon-saving devices.
--
-Mark Wieder
mwie...@ahsoftware.net
___
use-livecode mailing list
Kay-
Wednesday, August 8, 2012, 9:29:42 PM, you wrote:
Please don't stop working on GLX2 Multi-Undo, because I don't see Versions
coming to LC anytime soon, it's just that I hope it does come because, when
done properly, it will be so much better than what we have now.
Well, undo/redo in
On Fri, Aug 10, 2012 at 8:57 AM, Mark Wieder mwie...@ahsoftware.net wrote:
I have, several times. It's on my list of bacon-saving devices.
Yes, and on my list as well, along with TimeMachine and Carbon Copy Cloner.
But my comments were more a reflection of how complex, laborious and space
On 8/9/12 10:42 PM, Kay C Lan wrote:
Then there is the process of retrieving lost data. You can't just open up
any of these backups because they have exactly the same stack name as the
stack you are working on.
It's not what you're looking for (which would be great, I agree) but on
desperate
The Unix diff command can compare two files and create a set of edit
statements to recreate one from the other. I'm assuming GLX2 could make
use of that when storing new versions of scripts. Moving from there to
store edit statements to recreate a complete stack file would be possible
but I
On Fri, Aug 10, 2012 at 11:50 AM, J. Landman Gay
jac...@hyperactivesw.comwrote:
It's not what you're looking for (which would be great, I agree) but on
desperate occasions I have opened two stacks as text files in BBEdit and
run find differences on them.
Yep, when I know it's just script
As I've followed this thread I've thought what an absolutely marvellous
concept; the ability to Undo, not just multiple times, but even past
previous saves! And not just script changes, but entire Object property
states. But what about an even better feature, the ability to Undo past
actual
Mark Wieder wrote
Ick! No, I would never suggest something as cumbersome as that!
It's as simple as adding another dimension to the undo array.
Here's a minor adjustment to the Undo.Push and Undo.Pop commands in
the code I posted earlier.
[snip amazing LiveCode Script]
Ok, Now I get it.
Alejandro-
Tuesday, August 7, 2012, 10:44:58 AM, you wrote:
Hopefully, you will find time to create (and sell)
a robust and general solution that could work with
any kind of application created in this platform.
OK. I uploaded libUndo to revOnline as a general purpose mechanism.
Turns out
Hi Mark,
Look, for example, the contents of an element
of the Undo Array. The Undo Array contains
a xml description of all controls placed in
a single card:
The Unique Key for each control is the AltID
of the control, that is set at the moment of
its creation. So, always there is only one
Alejandro Tejada capellan2000@... writes:
Look, for example, the contents of an element
of the Undo Array. The Undo Array contains
a xml description of all controls placed in
a single card:
I think xml is probably the wrong format for this data. In order to determine
the difference between
Mark Wieder wrote
I think xml is probably the wrong format for this data. In order to
determine
the difference between versions you're going to have to unpack the xml
data,
find what has changed, pack that data back into xml, and store that.
That's a
lot of unnecessary work.
Yes, but
Richard Gaskin wrote
This may help:
function MergeArray pSourceA, pDeltaA
-- Merges the elements in the array pDeltaA with
-- the array pSourceA, returning an array which
-- contains the values of pDeltaA for any key
-- which is also in pSourceA, and any keys in
--
Alejandro Tejada wrote:
Richard Gaskin wrote
This may help:
function MergeArray pSourceA, pDeltaA
-- Merges the elements in the array pDeltaA with
-- the array pSourceA, returning an array which
-- contains the values of pDeltaA for any key
-- which is also in pSourceA, and any
Alejandro-
Saturday, August 4, 2012, 1:55:49 PM, you wrote:
I agree that allowing undos past the last save is a huge advantage.
Well, this is turning out to be a more interesting conversation than I
expected. At first I thought that unlimited undos was the holy grail
of an undo mechanism. Then
Richard Gaskin wrote
I'm not sure I follow, since the keys of an array will be unique so
there will be no opportunity to find matching keys within the same array.
If you just want matching values maybe you could write a loop that walks
through each element and turns that element into a
Alejandro Tejada wrote:
As I understand, GLX2 version 3.0.10 includes an Undo for everything
that you wrote in the Script Editor. I am just trying to adapt this Undo
code
for vector graphics and all their attributes.
If the code is well done, it could be extended to every control in the card,
Alejandro-
Sunday, August 5, 2012, 5:35:15 PM, you wrote:
As I understand, GLX2 version 3.0.10 includes an Undo for everything
that you wrote in the Script Editor. I am just trying to adapt this Undo
code
for vector graphics and all their attributes.
If the code is well done, it could be
oops-
single array in a multidimensional array
er... make that
single element in a multidimensional array
--
-Mark Wieder
mwie...@ahsoftware.net
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe,
Allowing undos past the last save is a huge advantage, as frequent saving is
often used to mitigate the risk of instability, rather than create a hard
'version'.
Cmd-S (or Ctrl-S) is your friend when developing or working with flaky apps or
IDEs.
However, consider the constant saving in
Hi Keith,
Keith Clarke wrote
Allowing undos past the last save is a huge advantage, as frequent
saving is often used to mitigate the risk of instability, rather than
create a hard 'version'.
Cmd-S (or Ctrl-S) is your friend when developing or working with flaky
apps or IDEs.
I agree
Never mind an IDE that prevents the creation of dodgy code - right now I'd be
delighted to get a fix for Mountain Lion so that it doesn't crash before I even
get my development environment back up and running.
Life for me has suddenly reverted to the instability of 20th century Windows.
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.
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
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
Good idea Alex. The scripts are written out to plain text files to do the
comparison so the mechanism for checking any type of plain text file is
already in place.
Unfortunately, I've never used revServer so I'm not familiar with where the
.lc and .livecode files are kept. Are they kept in
Hi Alex and Peter,
Alex Tweedly wrote
[snip]
you could maybe consider extending lcStackDiff to
cover .lc and .livecode text files as well as scripts
within stacks.
This would be excellent!
Could you extend this script to produce
the differences between the text of two
elements in an
Hi Alejandro,
In theory, yes that could be done.
Are you wanting to compare two arrays that are stored somehwre in two stack
files, custom properties perhaps? Or are the arrays in script variables?
If the latter, I couldn't do that within the bounds of lcStackDiff but I
might be able to pull
Hi Peter,
Peter Haworth wrote
[snip]
In theory, yes that could be done.
Are you wanting to compare two arrays that are stored somehwre in two
stack
files, custom properties perhaps? Or are the arrays in script variables?
If the latter, I couldn't do that within the bounds of
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. :-)
Bob
On Aug 2, 2012,
A stupid question, not having used GLX since LiveCode was Rev Studio/Enterprise
etc.
How do I install it? There appear to be no instructions in the download at all,
other than some mentions of a plugin folder in the GLX2 Macros.txt file.
:-(
Ian
___
Ian Wood revlist@... writes:
A stupid question, not having used GLX since LiveCode was Rev
Studio/Enterprise etc.
How do I install it? There appear to be no instructions in the download at
all, other than some mentions of a
plugin folder in the GLX2 Macros.txt file.
There's a wiki at:
On 3 Aug 2012, at 20:19, Mark Wieder wrote:
There's a wiki at:
https://bitbucket.org/mwieder/glx2/wiki/Home
which points to documentation at:
http://glx2.ahsoftware.net/
the first link there is installation instructions.
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
On 08/03/2012 07:55 PM, 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
Mark, is the undo array reset when saving the script, or saving the stack, or
neither?
Bob
On Aug 1, 2012, at 8:51 PM, Mark Wieder wrote:
Alejandro-
Wednesday, August 1, 2012, 4:04:47 PM, you wrote:
glx2 is one of the most extraordinary examples of smart coding
using the best features
Bob-
Thursday, August 2, 2012, 10:40:51 AM, you wrote:
Mark, is the undo array reset when saving the script, or saving the stack, or
neither?
Ah, neither. You can undo back past saves. Hmmm... is that a problem?
--
-Mark Wieder
mwie...@ahsoftware.net
Alejandro-
Wednesday, August 1, 2012, 4:04:47 PM, you wrote:
glx2 is one of the most extraordinary examples of smart coding
using the best features of this development platform.
Uh oh. I'd better release this then since I've been keeping the undo
stuff to myself so far...
GLX2 3.0.10
new
46 matches
Mail list logo
