I'm not a heavy user, so take my thoughts with whatever grain of salt
you want, but this is how I would naively expect these constructs to work:
<< \\ \\ \\ >>
The voices would be entered in order from top to bottom. In this way
the physical structure of the code would resemble the structure of the
music I'm entering (thanks to line breaks in the code between the voices).
\voiceOne \voiceTwo \voiceThree \voiceFour
The numbers here are confusing. They could be a top-down enumeration of
the voices or a more musical outside to inside pattern. Further, the
fact that they don't match up with the 1/2/3/4 numbers of the implicit
code above is even more confusing. If we stick with numbers, then
numbers should match. However it would probably better if we got away
from numbers altogether here. Kieren's suggestion of \voiceUp.1 and
\voiceDown.1 seems somewhat more natural, but the numbers still have the
potential for confusion. I do not know how to solve this (if it's
solvable).
Finally, as a coder I always favor a phased process for changes to the
user interface so that people have time to adapt to the change. A flag
which can flip between the new and old behavior is definitely in order
until 3.0.0 comes out. I'd default the flag to the old behavior while
the new one is being worked on and then default it to the new behavior
once a stable state has been reached.
--
✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝
Br. Samuel, OSB
St. Anselm’s Abbey
Washington, DC
(R. Padraic Springuel)
PAX ☧ ΧΡΙΣΤΟΣ
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
