Hi everyone, > Actually, I don't think editing would have to be restricted to > then. If you have rolled back changes the document is in the state > it was in earlier. Admittedly doing that may break a lot of scripts > but heck any editing of the document without being careful is likely > to do that. > > Perhaps a better question would be if you include script > modifications (and I'm not sure it's a good idea just because of > memory consumption, certainly it needs to be a UI option to > turn of tracking history for dynamic documents) what would be > your granularity. Having undo one script change would likely > be almost useless. I was thinking that you might group all script > changes between user changes into one 'extra' undo block.
Initially I was thinking of remembering every single change on the document and putting it into the history (history size would be initially set), and offering an option to allow undo of a single change or a custom number of last changes to the document. The problem appears when the changes in the document are frequent in a short period, and some changes that are "not of interest" are remembered - each one as a separate change. For example a value of an attribute can be changed many times in a row. Grouping all these changes to a separate change would discard the changes "not of interest". If this is what you meant by granularity, then I think the issue might be finding a way to create the "groups" of changes. > Also depending on how you implement updates, you have the issue > that even when live tracking a change to the document may have made > the change you were about to apply to the document invalid. I'm > actually thinking that the Viewer may need to 'pause' the document > when it goes into 'edit' mode. There is a good question of how > best to have the user signal the move into edit mode. Should it > be a 'check box' in the UI. Should it happen automatically if you > click on a field (to start an edit) or try to create/delete elements? I meant to refresh the view in the Viewer through mutation events. If the user edits the document through the Viewer, the document changes, mutation events are fired and the view in the Viewer refreshes. Do you think I need to 'pause' the document? How do I do that? I have also created a wiki and put some of the things there http://wiki.apache.org/xmlgraphics-batik/IvanAndjelkovic-gsoc2007 Ivan -- View this message in context: http://www.nabble.com/Getting-to-know-Batik%27s-codebase-tf3673369.html#a10794127 Sent from the Batik - Dev mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
