Stephen Torri: > Let me rephrase this to see if I hear you right. Is the Chord class > really required? If [not] then can we just scrap all the classes and have > the guitar tab editor work with an Event class as the data structure?
Maybe. Or have the chord class apply structure to the Event and relate it to the actual chord database. Compare for example the key signature class in NotationTypes. Key signatures are stored basically just as an event with a string property that holds the name of the key. For any real work, we create a proper class from the same data. > > In almost all cases, given a choice of a representation that is simple > > to play in MIDI and one that is simple to edit in notation, we go for > > the former. > > I don't understand this. Well, for example, beamed groups are stored just as a beamed group id property in the events - there is no group "container" in the segment for the events to live in. That's partly so that you can just read the events straight out of the segment during playback. Similarly, tuplets are stored with their performed durations, rather than their notated ones. > Q: What is a performed not[e] event? Any Event of type Note::EventType. Chris ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ Rosegarden-devel mailing list [email protected] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
