ofcourse in the end everything is the page But what to do for example with the component that is in both places? (the component that is removed from the parent but still kept in the page for later attachement)
would be very hard to decide where it belongs and at what place to cut it loose. johan On 2/3/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
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
