The MVC pattern in Pivot is well implemented and it is getting me thinking about options for a musical score. My view of a score is that it is comprised of its data, a model object graph and a graphic representation of the data in the graph. There may be a way to align these aspects with the MVC pattern that Pivot uses?
Presently, the model object graph has just enough objects arranged in a tree to allow any type of score to be formed. The objects carry a lot of data that is put there by editing tools and musical analysers. Possibly the graph could be an extended Component? There are many ways to represent pure music data so having alternate skins (and styles) might be a way to do that as well? I have resolved my requirements already but there may be a benefit to refactoring to the MVC pattern Pivot uses? Thom
