Re: [Protux-devel] Mustux MUE - Mustux Undo Engine - First formal approach

[Luciano Giordana]

Serialization is a robust concept.. I dont get it...
anyway, we can see alternatives...

--------- Mensagem Original --------
De: Remon Sijrier <address@hidden>
Para: address@hidden <address@hidden>
Assunto: Re: [Protux-devel] Mustux MUE - Mustux Undo Engine - First formal
                approach
Data: 17/05/04 14:12

> On Monday 17 May 2004 14:40, Luciano Giordana wrote:
&gt; Just quick answers : details later (little time now)
&gt;
&gt; - I dont agree with the multi-stack, one for each viewport. I think you
&gt; meant one for each SONG, since view ports would only look to the
different
&gt; parts of same song. But, essentially, for a mono-view app , such
protux,
&gt; you are correct. (hey...why not multiview in protux... intersting...)

Ehm, thats what I said ;-)
Each Song (== ViewPort) has its own Stack.

&gt;
&gt; &gt; I don't get one thing here. Anti actions are (hard) linked to
Objects. In
&gt;
&gt; case
&gt; you restart a MustuxApplication, the &amp;quot;undo&amp;quot; stack is
loaded into
&gt; memory, but
&gt; how do all the actions/antiactions know on what Object they apply since
the
&gt; relation is broken to these Objects?
&gt;
&gt; - After desserialization, you link objects propertly, even if the
objects
&gt; addresses are different. Thats is the very essence of serialization.
Not
&gt; simple to code thou.

Is there no other way to do this more robustly?

I was also very interested in the &quot;Contextual Undo&quot;
Nobody else have some opinion on this?


Greetings,

Remon


_______________________________________________
Protux-devel mailing list
address@hidden
http://mail.nongnu.org/mailman/listinfo/protux-devel



________________________________________________
Horizon Serviços Digitais
Assine já! - 0300 789 70 90