Next: , Previous: Skipping corrected music, Up: Other stuffs TODO move?


3.3.3 context list FIXME

>> > > - list of contexts: my *danger unmaintainable* >> > > alarm just went off. I'm

I knew it would... And leaving out some of them is perfectly fine with me. I do think that a list like this, with the main contexts and a brief description of what they do (perhaps also with a note about what default behaviour is associated with each of them, but this may be unmanageable), should be there, and then we could simply list the remaining ones without further explanation and with links to the IR.

The Master Of All Contexts ==========================

* Score This is the top level notation context. No other context can contain a Score context. This context handles the administration of time signatures. It also makes sure that items such as clefs, time signatures, and key-signatures are aligned across staves. You cannot explicitly instantiate a Score context (since it is not contained in any other context). It is instantiated automatically when an output definition (a \score or \layout block) is processed. (it should also be made clear somewhere what the difference is between \score and \Score).

Top-level contexts: Staff containers ==================================== * StaffGroup Groups staves while adding a bracket on the left side, grouping the staves together. The bar lines of the contained staves are connected vertically. StaffGroup only consists of a collection of staves, with a bracket in front and spanning bar lines. * ChoirStaff Identical to StaffGroup except that the contained staves are not connected vertically. * GrandStaff A group of staves, with a brace on the left side, grouping the staves together. The bar lines of the contained staves are connected vertically. * PianoStaff Just like GrandStaff but with a forced distance between the staves, so cross staff beaming and slurring can be used. * DrumStaff Handles typesetting for percussion. Can contain DrumVoice * InnerStaffGroup * InnerChoirStaff

Staff-level contexts ==================== * Staff Handles clefs, bar lines, keys, accidentals. It can contain Voice contexts. * RhythmicStaff Like Staff but for printing rhythms. Pitches are ignored; the notes are printed on one line. * TabStaff Context for generating tablature. By default lays the music expression out as a guitar tablature, printed on six lines. * VaticanaStaff Same as Staff, except that it is accommodated for typesetting a piece in gregorian style. * MensuralStaff Same as Staff, except that it is accommodated for typesetting a piece in mensural style.

Voice-level (bottom) contexts ============================= What is generated by default here? The voice-level contexts initiate certain properties and start engravers.

* Voice Corresponds to a voice on a staff. This context handles the conversion of dynamic signs, stems, beams, super- and subscripts, slurs, ties, and rests. You have to instantiate this explicitly if you want to have multiple voices on the same staff. Bottom context. * VaticanaVoice Same as Voice, except that it is accommodated for typesetting a piece in gregorian style. * MensuralVoice Same as Voice, except that it is accommodated for typesetting a piece in mensural style. * Lyrics Corresponds to a voice with lyrics. Handles the printing of a single line of lyrics. Bottom context. * DrumVoice A voice on a percussion staff. * FiguredBass

* ChordNames Typesets chord names. This context is a `bottom' context; it cannot contain other contexts.

——————————————– Then the following, which I don't know what to do with:

* TabVoice * GregorianTranscriptionVoice * GregorianTranscriptionStaff

* FretBoards Engraves fretboards from chords. Not easy... Not documented. * NoteNames

* CueVoice Not documented * Global Hard coded entry point for LilyPond. Cannot be tuned. * Devnull Silently discards all musical information given to this context.


Next: , Previous: Skipping corrected music, Up: Other stuffs TODO move?

Cette page documente LilyPond-2.11.40 (branche de développement).

Rapportez toute anomalie en français à lilypond-user-fr@gnu.org ou en anglais à http://post.gmane.org/post.php?group=gmane.comp.gnu.lilypond.bugs

Vos suggestions à propos de la documentation sont les bienvenues.