CVSROOT: /cvsroot/lilypond
Module name: lilypond
Branch:
Changes by: Graham Percival <[EMAIL PROTECTED]> 05/04/26 08:50:09
Modified files:
. : ChangeLog
Documentation/user: advanced-notation.itely
Log message:
Compile fix and x11 docs from Bernard.
CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/lilypond/lilypond/ChangeLog.diff?tr1=1.3506&tr2=1.3507&r1=text&r2=text
http://savannah.gnu.org/cgi-bin/viewcvs/lilypond/lilypond/Documentation/user/advanced-notation.itely.diff?tr1=1.11&tr2=1.12&r1=text&r2=text
Patches:
Index: lilypond/ChangeLog
diff -u lilypond/ChangeLog:1.3506 lilypond/ChangeLog:1.3507
--- lilypond/ChangeLog:1.3506 Tue Apr 26 05:28:46 2005
+++ lilypond/ChangeLog Tue Apr 26 08:50:09 2005
@@ -5,6 +5,9 @@
changing-defaults.itely: minor fixes. Added docs
for colors to advanced-notation.itely.
+ * Documentation/user/advanced-notation.itely: fixed compile
+ problem and added Bernard's x11-color doc patch.
+
2005-04-25 Jan Nieuwenhuizen <[EMAIL PROTECTED]>
* scm/output-ps.scm (grob-cause): Yet another fix, hope it's
Index: lilypond/Documentation/user/advanced-notation.itely
diff -u lilypond/Documentation/user/advanced-notation.itely:1.11
lilypond/Documentation/user/advanced-notation.itely:1.12
--- lilypond/Documentation/user/advanced-notation.itely:1.11 Tue Apr 26
05:28:46 2005
+++ lilypond/Documentation/user/advanced-notation.itely Tue Apr 26 08:50:09 2005
@@ -1715,11 +1715,11 @@
@node Coloring objects
[EMAIL PROTECTED] Coloring objects
[EMAIL PROTECTED] Coloring objects
@c FIXME: need link to missing list of colors
Individual objects may be assigned colors. You may use color names
-listed HERE or the x11 color names listed THERE.
+listed HERE
@lilypond[quote,raggedright,verbatim,fragment]
\override NoteHead #'color = #red
@@ -1730,6 +1730,62 @@
e
@end lilypond
+The full range of colors defined for X11 can be accessed by using the
+scheme function x11-color. The function takes one argument that can be a
+symbol
+
[EMAIL PROTECTED]
+\override Beam #'color = #(x11-color 'MediumTurquoise)
[EMAIL PROTECTED] example
+
+or a string
+
[EMAIL PROTECTED]
+\override Beam #'color = #(x11-color "MediumTurquoise")
[EMAIL PROTECTED] example
+
+The first form is quicker to write and is more efficient. However, using
+the second form it is possible to access X11 colors by the multi-word
+form of its name
+
[EMAIL PROTECTED]
+\override Beam #'color = #(x11-color "medium turquoise")
[EMAIL PROTECTED] example
+
+If x11-color cannot make sense of the parameter then the color returned
+defaults to black. It should be obvious from the final score that
+something is wrong.
+
+This example, illustrates the use of x11-color. Notice that the stem
+color remains black after being set to (x11-color 'Boggle), which is
+deliberate nonsense.
+
[EMAIL PROTECTED],raggedright,verbatim]
+{
+ \override Staff.StaffSymbol #'color = #(x11-color 'SlateBlue2)
+ \set Staff.instrument = \markup {
+ \with-color #(x11-color 'navy) "Clarinet"
+ }
+ \time 2/4
+ gis''8 a''
+ \override Beam #'color = #(x11-color "medium turquoise")
+ gis'' a''
+ \override NoteHead #'color = #(x11-color "LimeGreen")
+ gis'' a''
+ \override Stem #'color = #(x11-color 'Boggle)
+ gis'' a''
+}
[EMAIL PROTECTED] lilypond
+
+
[EMAIL PROTECTED]
+Not all x11 colors are distinguishable in a web browser. For web use
+normal colors are recommended.
+
+An x11 color is not necessarily exactly the same shade as a similarly
+named normal color.
+
+
@seealso
COLORLIST
_______________________________________________
Lilypond-cvs mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/lilypond-cvs
