You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are so many instances where you'll use \editionMod ... \once \override ... so I think we should add new functions for this kind of use case. Something like
Of course the existing functions should be kept to allow arbitrary music expressions to be applied. But there could be more use cases for other specialized interface functions.
I think things like these shouldn't be hard to implement, the most complicated thing probably being the naming ;-)
However, I'm thinking if it wouldn't be a good idea not to improve the edition-engraver and then move it into a new-style library. There have now been multiple experiences with the tool, ideas for subtle and substantial improvements, and a completely new use case. Maybe it's time for a restart, collaboratively creating that new library from scratch and simply leaving the current tool as it is.
This should go along with a new ID based approach.
Maybe it's time for a restart, collaboratively creating that new library from scratch and simply leaving the current tool as it is. This should go along with a new ID based approach
I think we shouldn’t rule out a from-scratch approach.
Regardless, I’ve got a wealth of experience (several years and dozens of scores) from which I can speak to this.
Maybe you could start speaking (aside and maybe privately) to me with hints on how the edition-engraver can successfully interact with multiple bookparts?
There are so many instances where you'll use
\editionMod ... \once \override ...
so I think we should add new functions for this kind of use case. Something likewhich will internally translate to
This approach would also make it possible to automatically add a conditional coloring based on the state of, say
\getOption default.draft
.Additionally I think of things like
Of course the existing functions should be kept to allow arbitrary music expressions to be applied. But there could be more use cases for other specialized interface functions.
I think things like these shouldn't be hard to implement, the most complicated thing probably being the naming ;-)
However, I'm thinking if it wouldn't be a good idea not to improve the edition-engraver and then move it into a new-style library. There have now been multiple experiences with the tool, ideas for subtle and substantial improvements, and a completely new use case. Maybe it's time for a restart, collaboratively creating that new library from scratch and simply leaving the current tool as it is.
This should go along with a new ID based approach.
@jpvoigt @kierenmacmillan ideas? opinions?
The text was updated successfully, but these errors were encountered: