From eae1ceba11cf0b64e32caf00b1303f27c3e43bab Mon Sep 17 00:00:00 2001 From: Graham Percival Date: Tue, 3 May 2005 11:27:08 +0000 Subject: [PATCH] New chapter; placeholder for future expansion. --- Documentation/user/putting.itely | 61 ++++++++++++++++++++++++++++++++ 1 file changed, 61 insertions(+) create mode 100644 Documentation/user/putting.itely diff --git a/Documentation/user/putting.itely b/Documentation/user/putting.itely new file mode 100644 index 0000000000..28f3e4a8ae --- /dev/null +++ b/Documentation/user/putting.itely @@ -0,0 +1,61 @@ +@c -*- coding: latin-1; mode: texinfo; -*- +@node Putting it all together +@chapter Putting it all together + +This section will demonstrate more complicated stuff in LilyPond, probably +via annotated examples. It's currently incomplete and serves as a +placeholder so that the chapter numbering doesn't change later. + +@menu +* Suggestions for writing LilyPond files:: +@end menu + +@c explain \score{} ? Add a note to the tutorial? + +@node Suggestions for writing LilyPond files +@section Suggestions for writing LilyPond files + +Now you're ready to begin writing larger LilyPond files -- not just the +little examples in the tutorial, but whole pieces. But how should you +go about doing it? + +The best answer is ``however you want to do it.'' As long as LilyPond +can understand your files and produces the output that you want, it +doesn't matter what your files look like. That said, sometimes we +make mistakes when writing files. If LilyPond can't understand your +files, or produces output that you don't like, how do you fix the +problem? + +Here are a few suggestions that can help you to avoid or fix +problems: + +@itemize @bullet +@item Include @code{\version} numbers in every file. Note that all +templates contain a @code{\version "2.4.0"} string. We +highly recommend that you always include the @code{\version}, no matter +how small your file is. Speaking from personal experience, it's +quite frustrating to try to remember which version of LilyPond you were +using a few years ago. @code{convert-ly} requires you to declare +which version of LilyPond you used. + +@item Include checks: See @ref{Bar check} and @ref{Octave check}. If you +include checks every so often, then if you make a mistake, you can pinpoint +it quicker. How often is ``every so often''? It depends on the complexity +of the music. For very simple music, perhaps just once or twice. For +very complex music, every bar. + +@item One bar per line. If there is anything complicated, either in the music +itself or in the output you desire, it's often good to write only one bar +per line. Saving screen space by cramming eight bars per line just isn't +worth it if you have to `debug' your files. + +@item Comment your files, with either bar numbers (every so often) or +references to musical themes (``second theme in violins'', ``fourth +variation''). You may not need it when you're writing the piece for +the first time, but if you want to go back and change something two +or three years later, you won't know how your file is structured if you +don't comment the file. + +@end itemize + + -- 2.39.5