> > I agree introducing a new ChordEvent (or whatever the name will be) is a > > better idea. And more elaborated, but that won't stop me :-). I'm > > volunteering to have a look at this. And as Micheal already suggest, this > > could be done in another branch.
In the meantime I have created this new branch, NewChord. > > This might ease some other ideas I have > > regarding chords, like "generating" the chord. We already have the > > ChordNameRuler so it is possible. > It seems to me we could disable the legacy text chord in the GUI, so it > is no longer possible to create new ones. Existing ones would continue > to work as they always did. > > For new chords, I'm seeing a new tool whose icon sits next to the guitar > fretboard diagram tool. It inserts a new kind of entity that displays > itself as text in the notation editor, the way the old chord type text > events did, but this entity has super powers. > > My biggest concern about this is making the new entity a reality. I'm volunteering to take this task. My plan is to combine the GuitarChord and the Text::Chord into new ChordLabel. Step 1 will be get this new class/event working, including the exporters. Next step will be add new magic > I think we should concentrate on that project first, and once there's > something to hang the superpowers off of, power the thing up. I agree. Best regards, Niek ------------------------------------------------------------------------------ Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58041391&iu=/4140/ostg.clktrk _______________________________________________ Rosegarden-devel mailing list [email protected] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
