Hi Ivan. Ivan Andjelkovic: > 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.
I think that is what Thomas meant by granularity. Maybe it would be excessive to store every single DOM mutation, and that grouping them in blocks of script runs would be more helpful. Maybe the interface could support both, allowing the user to jump forward/back a group of mutations or a single mutation at a time? Thomas DeWeese: > > 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? Ivan Andjelkovic: > 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 think the issue would be that if for example you inserted a new rect element into the document, it would start off with no attributes and would thus be invalid, and an error message would pop up. Pausing the document would stop processing and you could resume it once the user has written the proper attributes on the element. You can pause/resume the document with the suspendRedraw and unsuspendRedraw methods on the SVGSVGElement object. > I have also created a wiki and put some of the things there > http://wiki.apache.org/xmlgraphics-batik/IvanAndjelkovic-gsoc2007 Great! -- Cameron McCormack, http://mcc.id.au/ xmpp:[EMAIL PROTECTED] ▪ ICQ 26955922 ▪ MSN [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
