lilypond-user
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

GPD: staff first draft


From: Graham Percival
Subject: GPD: staff first draft
Date: Fri, 02 Nov 2007 23:53:36 -0700
User-agent: Thunderbird 2.0.0.6 (X11/20071022)

As always, see here:
http://web.uvic.ca/~gperciva/


Here's the TODO list for Staff. If there's anything to add, please speak up now.



QUESTIONS

System start delimiters:

The difference between GrandStaff and StaffGroup should be
explained here.  As it now stands, it seems as if the only
difference is a graphical one: brace or bracket. But according to
the prog. reference, StaffGroup can contain most/all other staff
types, whereas GrandStaff only contains FiguredBass and Staff, so
perhaps SG should come first? But this "can contain" doesn' seem
to mean nesting, because this:

\score {
 \new StaffGroup <<
    \melody
     \new GrandStaff <<
       \melody
       \melody
     >>
     \melody
     \melody
   >>

does not "contain" any GrandStaff at all, only a blank line.
Should be clarified: what does it mean to "contain", and how does
one achieve the "nested" layout?


* I've added a reference to the lsr snippet with use of
InternalStaffGroup, which is much more likely to be useful to most
people. perhaps that reference should be expanded to a full
description with an example, to make it more prominent.

* The lilypond example to the description of the
systemStartDelimiterHierarchy property, is very convoluted.
I don't understand the scheme syntax of this property, which is
said to be a pair, but according to the "definition" of a pair in
the tutorial, pairs have the form (x . y).  This should be
explained.  What do the letters a, b, and d do, why is there no c?

* the systemStartSquare should be mentioned, incl. a bit of
code to show how to use it.

* should we make a new @unnumberedsubsubsec Nesting staff groups ?


Staff symbol

* rename to Staff appearance ?

* make new @unnumberedsubsubsec Ossia ?

Hiding staves

* if new Ossia, then change ref to Ossia.


Quoting other voices

- general rewrite

Formatting cue notes

- maybe rewrite


CLARIFY
http://code.google.com/p/lilypond/issues/detail?id=365



Cheers,
- Graham




reply via email to

[Prev in Thread] Current Thread [Next in Thread]