Kieren MacMillan:
> > 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. â
Using git isn't needed.
Having makefiles is just sound engineering, saves a lot clicking and
typeing.
Command line, why are people afraid of that, I just don't understand.
And we are talking about lilypond which is basically a command line
type of a program.
> is what I would hope a great framework would avoid. (And some of those
> mentioned in this thread attempt to do exactly that.)
Why do you want to avoid time saving tools. Generally easy things are
easy and hard things are hard, why make it harder.
> 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)
> %%%
>
> and have a beautiful SATB score pop out.
Since \makeScore isn't available I wrote the program mentioned above
which basically does what you want \makeScore to do. But since mknew.pl
is tailored to my needs and infrastructure, I guess it wouldn't be
very useful for someone else. Though, if some brave soul would like to
try it I'm here to help.
Regards,
/Karl Hammar
