I have been making the time to continue working on this, and I have been pushing my changes to my GitHub fork as I go, so anyone interested can check out my work.
I now have unrecognized chords transposing and rendering reasonably. So far, there is no way to customize how they are rendered, but I've set things up to make that a pretty straightforward extension. First, though, I'm getting ready to hook this up to Harmony Properties and MusicXML. I could use some feedback on a few issues: 1. The data structures currently built via Harmony Properties and MusicXML import seem to be pretty nice as a way of capturing the actual structure of a chord. I'd like to tie into this - shoring up the generation of chord names from this data, and generating this data from the parsed form of chords typed by the user. With that in place, my plan is to not store this info in the score file but instead simply store the name (as is already going to be the case for chords typed by the user, as per my changes) and then regenerate these data structures from the stored name when scores are loaded. Objections? 2. Right now there is no way to control the loading of chords.xml. I want to create a new chord description file "wysiwyg.xml" that would have no predefined chord id's whatsoever, so all chords would be unrecognized and therefore would be rendered on the fly directly from the parsed form of the name (and similarly would have voicing and MusicXML info generated on the fly). But a chord id list is always being loaded from chords.xml right now, and this happens before the chord description file is ever loaded. A quick-and-dirty fix would be to add a tag to the chord description file that, if encountered, would cause MuseScore to throw away the already-loaded chords.xml info. But that's pretty kludgy. I'd prefer to have a style parameter to either choose a different chords.xml or else suppress it entirely. Thoughts? 3. I notice that the chordname text style setting has disappeared, and a couple of text-style-like parameters are now found in the chordname *general* style. I assume this change was deliberate and for a reason. Most text styling for chordnames has come from the chord description files, so the settings in the text style were being largely ignored anyhow. But with the changes I am trying to make, unrecognized chords will be displayed using a default font, and it seems reasonable to want direct control over what that font is. The new wysiwyg.xml chord description file would have alll chords unrecognized, and therefore rendered on the fly using this default font. Sure would be nice to just be able to set it as text style, now that this would actually have an effect. Thoughts? -- View this message in context: http://dev-list.musescore.org/integrating-the-chord-parser-into-the-class-structure-tp7578067p7578088.html Sent from the MuseScore Developer mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Learn Graph Databases - Download FREE O'Reilly Book "Graph Databases" is the definitive new guide to graph databases and their applications. This 200-page book is written by three acclaimed leaders in the field. The early access version is available now. Download your free book today! http://p.sf.net/sfu/neotech_d2d_may _______________________________________________ Mscore-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mscore-developer
