ANN: GLX2 3.0.10

[Alejandro Tejada]

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 XML is so... Readable. :-)


Mark Wieder wrote
> 
> Much easier (and faster and less memory for storage) to store an array
> whose
> keys are the property names and whose elements are the values. Then use
> Richard's merge function to find the deltas quickly.
> 

I am sure that you are correct, but I could not create the script to
demonstrate it. :-D
Suppose that I have 10000 controls in the card (remember, it's a graphic
application),
and (if I understand correctly your advice) then I had to create 10000
arrays in memory
to hold the properties of each control. Could this be the correct
interpretation of your
idea for this task?

Old computer graphics programs have a limited number of undo. The user had
to set
manually the number of undo. I remember that there was a program (FreeHand
or
Ilustrator?) with a maximum number of undos of 10 (Ten). The program was
really slow
with this "huge" number of data in memory... :-O

The first time that I tried to create an undo, some time ago, I simply
copied the
card contents to a new card in a hidden stack, before any operation that
modified,
create or delete any control.
This Undo system could not be more simple, but it failed in a spectacular
way.
After a while, as the number of controls grows, the process of copying all
controls
become, more and more slow, until the stack became unresponsive and
unusable.

Al




--
View this message in context: http://runtime-revolution.278305.n4.nabble.com/ANN-penTool-0-3-2h-with-scalable-gradients-tp4653241p4653462.html
Sent from the Revolution - User mailing list archive at Nabble.com.