Palette hierachy with sub-palettes
The question of sub-palettes has arisen before, but I don't see any definite conclusions. I've often felt that some palettes are conflations of many disparate elements (Lines, for example; and Arpeggios & Glissandos, which itself contains useful diagonal lines; there are many examples).
With the work I've been doing on Fretboard Diagrams, I really can't picture a good useful palette implementation without some form of palette hierarchy. I think that having a single palette of 21 simple guitar chords is of limited use (though most users of this feature will be customizing their own diagrams regardless).
In my ideal world, I'd like to prepare the following sub-palettes, for nested access somehow under the Fretboard Diagrams heading:
- Blank chord grids
- Guitar chords (simple)
- Ukulele chords (simple)
- Mandolin chords (simple)
- Jazz guitar chords (major family)
- Jazz guitar chords (minor family)
- Jazz guitar chords (dominant family)
- Jazz guitar chords (altered family)
- Jazz guitar chords (Drop-2)
- Jazz guitar chords (Drop-23)
I just can't imagine providing this range of choices as separate top-level palettes, nor do I relish setting up my system with this many custom palettes in a workspace (though that's what I'm doing).
If this problem were unique to fretboard diagrams then perhaps we could look at some other way of selecting from a much larger dictionary of chord forms, analogous to the Master Palette interface.
However, as MuseScore grows in sophistication, the number of entries in each palette and the number of palettes will continue to swell. I'd think that instrument-specific palettes like Bagpipe Embellishments and Fretboard Diagrams could all be tucked away somewhere out of mainstream view; and that some of the other palettes could be simplified/consolidated/split to streamline their use.
I'm sure this has been given a lot of thought, but I don't believe we've passed the point of no return where such an interface change would be impossible.