On 2/2/07, Johan Compagner <[EMAIL PROTECTED]> wrote:
No really forget it to really separate the undo changes from the page.
This is really impossible to guarantee. Anon classes, models pointing to the
page or component
parents that keep the child as a reference so that they can do attach() (to
parent) again.
there are sooo many things that connect the 2 things

Well, ultimately you would have a finite set of possible parents, with
the ultimate parent being the page (or else you would have a problem,
in which case it would actually be an advantage if we could detect
that). I'm just wondering whether if we take the serialization in our
own hands, we can keep track of the parents and resolve them from the
other versions up to the serialized page when we need it.

Eelco

Reply via email to