On 3/5/06, Michelle Donalies <[EMAIL PROTECTED]> wrote: > The string and fret notation seem to be just integer properties added to a > Note event. If so, then there's a question: does every Note get some sort of > default tab info (wasteful) or should defaults only be generated when a tab > staff is actually displayed (seems much better to me)? The second would > require an option to store the tab info when a file gets saved.
If I understand correctly, RG thinks in terms of events. Each event can have one or more named properties. So you only need to add the tab info to a note event when it is required. Presumably, if we use the built in event property mechanism, saving this info will almost code itself :) > > The next issue is the tablature staff. I see that NotationStaff is a > LinedStaff. How does the class Staff fit in here? LinedStaff inherits Rosegarden::Staff - that's how :-) > Ignoring what I don't understand (which may make my following remarks > nonsense), I'll continue to think about a tab staff, which I'll call > TabStaff. Should TabStaff just be the tablature part and somehow or other the > TabStaff gets connected to a NotationStaff? Or does TabStaff need to be an > extension of NotationStaff? This really comes down to the desired effect in the GUI. I've seen two main styles for tab: 1) As a second staff underneath a trad notation staff. In this case, all the tab shows are the frettings. Rhythm, dynamics etc are all on the trad staff. 2) As a self-sufficient staff where the rhythm and dynamics are marked on the same staff. This style looks like trad notation, but with numbers instead of blobs for the note heads. 1) Is what you typically see on magazines. 2) Is what you would tend to write yourself on a pad of paper. Suppose we go for 2). Then TabStaff could inherit NotationStaff (be a "special sort" of NotationStaff) - that seems most fitting. If we go for 1), then TabStaff isn't a NotationStaff - it would inherit LinedStaff. The main issue with (1) is that RG, afaik, doesn't have the capacity for displaying linked staves (think piano score with LH and RH staves). That makes the "just the numbers" view less useful. So personally I've prefer (2), but I'm open to persuasion. :) ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642 _______________________________________________ Rosegarden-devel mailing list [email protected] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
