What do you want to reconstruct on the client? if the back button is pressed. And we have an special ajax request for that. That calls the server and does:
Component[] alteredComponents = page.getVersionManager().rollbackAjax(-1) and then in the ajax request target we set those altered components. So that they are rerendered in the browser.. I think it is very easy to know what components are altered. We just let the version manager catch that again :) so if the version manager does this: Add.undo() (that removes a component from a parent) we just let the version manager record that change and we know which component did change again. i think that should work. or the other way around that we just ask the Add change what component it will alter when it undo's johan On 2/8/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
On 2/8/07, Matej Knopp <[EMAIL PROTECTED]> wrote: > Although there is a drawbacks for this: > The history would be lost after first page refresh (so that my example > wouldn't even work, unless you don't refresh it :)) But if we would keep ajax changes separately or with a special mark somehow, we could push the part of the ajax history we didn't rollback to the client (our ajax engine) so that we could reconstruct it again. Eelco
