List view

• Write DOM to File

  As soon as Chorus allows modifications on the loaded DOM, the user should be allowed to write the modified DOM back to a file.

  No due date
  0% complete0 open0 closed

• DOM fires ChangeEvents on changes

  At the moment the DOM is treated as static: after the DOM is read in from a XML file it is parsed once, to create the MIDI-events and render the layout. Every modification beyond that is ignored. To allow changes on the DOM, the DOM nodes should fire change events on modifications. With a ChangeEvent-firing DOM the different modules of the application (MIDI- and Layout-render) may be changed to recreate there output for the modified nodes only, instead of re-rendering the complete DOM again. We need custom ChangeEvents, for ValueChanges as well as for changes in collections (node inserted/removed/reordered), for which java.beans.PropertyChangeEvent are not sufficient - they only cover value changes.

  No due date
  0% complete0 open0 closed