[Protux-devel] So, may the UNDO discussion begin ...

[Luciano Giordana]

Hi all,
this is to talk about some initial ideas I have about the UNDO stuff.

First of all, I was told that there are two basic approachs on implementing 
UNDO engine.

1 - the memory snapshot approach
2 - the action pipeing approach

the memory snapshot , or MS for shot, refers to the ability of saving / 
serializing all objects in a given moment, save it someway
and then, in case of a undo, retrieve the last saved object images

the action pipeing approach, or AP, refers to the concept that EACH action has 
a anti-action, and the program has the abilty of pushing all 
undoable actions into a pipe, and in case of undo, to perform the anti-action 
in a reverse order

Ok, so to put a initial fire on this matter, I think I preferen the AP 
approach, since it fits more in the JMB philosophy. Also, the MS apprach 
requires
lots of RAM, and usually leads to memory leaks, or even crashes.

RFC (surely) ...

-- 
Best Regards
--
Luciano Giordana - Musician - Certified Java/GNU C++ Developer - Free Software 
Evangelist
Project Mustux - http://www.freesoftware.fsf.org/mustux
-- GNU/Linux adoption grew 65% only this yer. Smile : we're winning. --