Janek Warchoł <janek.lilyp...@gmail.com> writes:
> On Wed, Feb 29, 2012 at 9:22 AM, David Kastrup <d...@gnu.org> wrote:
>> Janek Warchoł <janek.lilyp...@gmail.com> writes:
>>>
>>> sure, i can do this. Nevertheless, writing these in \layout {} would
>>> be more elegant
>>
>> No. An arbitrary number of named contexts can occur in the text, and
>> some are implicitly named anyway. So you want to change _all_ contexts
>> of a given type in \layout and/or derive a new context type (aaVoice or
>> so) and then use \new aaVoice ... in the score.
>>
>>> and in my opinion easier to maintain: \layout must be placed at the
>>> end of \score block, while variables containing context modifications
>>> must be defined before they are used, i.e. before \score block. Thus,
>>> style decisions are spread over two places.
>>
>> A _style_ is something affecting _all_ contexts of a given type, not
>> just particular contexts with a particular id.
>
> Hmm. I'm not sure if i understand what you mean. Let me give an
> example case where i think that named context thingy would be useful:
> i have a piece for 3 SATB choirs; the structure is
>
> \score { <<
> \new ChoirStaff = ChoirOne <<
> \new Staff = soprano { }
> \new Staff = alto { }
> \new Staff = tenor { }
> \new Staff = bass { }
> >>
> \new ChoirStaff = ChoirTwo <<
> \new Staff = soprano { }
> \new Staff = alto { }
> \new Staff = tenor { }
> \new Staff = bass { }
> >>
> \new ChoirStaff = ChoirThree <<
> \new Staff = soprano { }
> \new Staff = alto { }
> \new Staff = tenor { }
> \new Staff = bass { }
> >>
>>>
>
> i'll print scores separately for each choir, so to save space i can
> make two choirStaves smaller in each print.
Then make a SmallStaff context definition and use it instead of Staff.
Take a look at engraver-init.ly for examples. I think that
RhythmicStaff is created from Staff, for example.
--
David Kastrup
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
