On Tue, Feb 10, 2026, 8:04 AM Carl Sorensen <[email protected]> wrote:
> > > On Tue, Feb 10, 2026, 7:40 AM Kieren MacMillan < > [email protected]> wrote: > >> Hi Karl, >> >> > Instead of using templates, I create skeleton files with mknew.pl [1]. >> >> To be clear, the complexity and technicality of what you’ve described — >> using git, having makefiles, touching the command line, etc. — is what I >> would hope a great framework would avoid. (And some of those mentioned in >> this thread attempt to do exactly that.) >> >> In my experience (including trying to mentor very intelligent composer >> colleagues on Lilypond, and teaching Lilypond workshops to college >> students), the basic Lilypond user wants to say something like: >> >> %%% >> \include “SATB_framework.ily” >> >> soprano = { blah } >> alto = { blah } >> tenor = { blah } >> bass = { blah } >> >> \makeScore #’(soprano, alto, tenor, bass) >> %%% >> > > I use a Frescobaldi input template for SATB. That template could be > easily modified to be SATB_framework.ily and it would work exactly as you > propose. > > I'll put a sample up in the next few days. > As I started thinking about the sample, it seems to me that the Frescobaldi template.is exactly what you want. It allows the choice of all your desired parts, and has appropriately named variables for all the music and lyrics. Kieren, have you ever tried the frescobaldi choral templates? If not, please give them a look. If so, what do you dislike about them for your use case? Thanks, Carl
