From 193cb7a76b5dd0c8fe236a9b95cd6ef11f044328 Mon Sep 17 00:00:00 2001 From: Graham Percival Date: Sun, 4 Oct 2009 14:33:54 +0100 Subject: [PATCH] Docs: move Programming interfaces into Extending. --- Documentation/extending.tely | 2 ++ .../programming-interface.itely | 4 ++-- Documentation/notation.tely | 2 -- Documentation/notation/changing-defaults.itely | 12 +++++++----- Documentation/notation/expressive.itely | 7 +++++-- Documentation/notation/text.itely | 4 +++- 6 files changed, 19 insertions(+), 12 deletions(-) rename Documentation/{notation => extending}/programming-interface.itely (99%) diff --git a/Documentation/extending.tely b/Documentation/extending.tely index 5f374fc465..bb985e2c36 100644 --- a/Documentation/extending.tely +++ b/Documentation/extending.tely @@ -45,6 +45,7 @@ by the authors. @menu * Scheme tutorial:: Programming inside LilyPond. +* Interfaces for programmers:: How to interface with scheme. Appendices @@ -60,6 +61,7 @@ Appendices @include extending/scheme-tutorial.itely +@include extending/programming-interface.itely @include fdl.itexi diff --git a/Documentation/notation/programming-interface.itely b/Documentation/extending/programming-interface.itely similarity index 99% rename from Documentation/notation/programming-interface.itely rename to Documentation/extending/programming-interface.itely index dc11ee1a6e..471276f0b4 100644 --- a/Documentation/notation/programming-interface.itely +++ b/Documentation/extending/programming-interface.itely @@ -669,7 +669,7 @@ doubleSlur = #(define-music-function (parser location note) (ly:music?) The easy way to add articulation to notes is to merge two music expressions into one context, as explained in -@ref{Creating contexts}. However, suppose that we want to write +@ruser{Creating contexts}. However, suppose that we want to write a music function that does this. A @code{$variable} inside the @code{#@{...#@}} notation is like @@ -1109,7 +1109,7 @@ to the @code{interpret-markup} function, with the @code{layout} and Note: there is now an internal command @code{\smallCaps} which can be used to set text in small caps. See -@ref{Text markup commands}, for details. +@ruser{Text markup commands}, for details. @knownissues diff --git a/Documentation/notation.tely b/Documentation/notation.tely index 76bcaa95b9..39933622fc 100644 --- a/Documentation/notation.tely +++ b/Documentation/notation.tely @@ -90,7 +90,6 @@ Distributions will want to install lilypond.info in postinstall, doing: LilyPond input and output. * Spacing issues:: Display of output on paper. * Changing defaults:: Tuning output. -* Interfaces for programmers:: How to interface with scheme. Appendices @@ -115,7 +114,6 @@ Appendices @include notation/spacing.itely @include notation/changing-defaults.itely -@include notation/programming-interface.itely @include notation/notation-appendices.itely diff --git a/Documentation/notation/changing-defaults.itely b/Documentation/notation/changing-defaults.itely index 5ea8a2ebb5..ef8e5f737c 100644 --- a/Documentation/notation/changing-defaults.itely +++ b/Documentation/notation/changing-defaults.itely @@ -391,7 +391,7 @@ any context of type @var{type}, regardless of its given name. This variant is used with music expressions that can be interpreted at several levels. For example, the @code{\applyOutput} command (see -@ref{Running a function on all layout objects}). Without an explicit +@rextend{Running a function on all layout objects}). Without an explicit @code{\context}, it is usually applied to @code{Voice} @example @@ -1729,7 +1729,7 @@ f' The music stream which is generated from a section of an input file, including any automatically inserted elements, may be examined, -see @ref{Displaying music expressions}. This may be helpful in +see @rextend{Displaying music expressions}. This may be helpful in determining what may be modified by a @code{\tweak} command. @@ -1737,8 +1737,8 @@ determining what may be modified by a @code{\tweak} command. Learning Manual: @rlearning{Tweaking methods}. -Notation Reference: -@ref{Displaying music expressions}. +Extending: +@rextend{Displaying music expressions}. @knownissues @@ -2914,7 +2914,6 @@ Learning Manual: Notation Reference: @ref{Explaining the Internals Reference}, @ref{Modifying properties}, -@ref{Interfaces for programmers}. Installed Files: @file{scm/@/define@/-grobs@/.scm}. @@ -2922,6 +2921,9 @@ Installed Files: Snippets: @rlsr{Tweaks and overrides}. +Extending: +@rextend{Interfaces for programmers}. + Internals Reference: @rinternals{All layout objects}. diff --git a/Documentation/notation/expressive.itely b/Documentation/notation/expressive.itely index 942dbd7bdf..223bab244f 100644 --- a/Documentation/notation/expressive.itely +++ b/Documentation/notation/expressive.itely @@ -461,7 +461,7 @@ mfEspressDynamic = #(make-dynamic-script mfEspress) @end lilypond The Scheme form of markup mode may be used instead. Its syntax is -explained in @ref{Markup construction in Scheme}. +explained in @rextend{Markup construction in Scheme}. @lilypond[verbatim,quote] moltoF = #(make-dynamic-script @@ -481,13 +481,16 @@ Font settings in markup mode are described in Notation Reference: @ref{Formatting text}, @ref{Selecting font and font size}, -@ref{Markup construction in Scheme}, @ref{What goes into the MIDI output?}, @ref{Controlling MIDI dynamics}. Snippets: @rlsr{Expressive marks}. +Extend: +@rextend{Markup construction in Scheme}, + + @node Curves @subsection Curves diff --git a/Documentation/notation/text.itely b/Documentation/notation/text.itely index cab401bb16..81e6ed5d16 100644 --- a/Documentation/notation/text.itely +++ b/Documentation/notation/text.itely @@ -1296,11 +1296,13 @@ An exhaustive list of markup list commands can be found in @seealso Notation Reference: @ref{Text markup list commands}, -@ref{New markup list command definition}. Snippets: @rlsr{Text}. +Extending: +@rextend{New markup list command definition}. + Internals Reference: @rinternals{TextScript}. -- 2.39.5