@node Using a Virtual Machine to Compile LilyPond
@section Using a Virtual Machine to Compile LilyPond
+TODO: rewrite for lily-git.tcl !!! do before GOP! -gp
+
Since it is not possible to compile Lilypond on Windows, some
developers may find it useful to install a GNU/Linux virtual
machine. A disk image with a special remix of @strong{Ubuntu}
@item Open a @strong{terminal} session.
(@code{Applications > Accessories > Terminal})
-@c FIXME: make sure the url link below doesn't get broken -vv
-
@item Open @strong{Firefox} (there's an icon for it on the
panel at the top of the screen) and go to the online Lilypond
@uref{http://lilypond.org/doc/latest/Documentation/contributor/,
manual.
@item
-@@predefined ... @@endpredefined is for commands in ly/*-init.ly
-FIXME?
+@@predefined ... @@endpredefined is for commands in
+@file{ly/*-init.ly}
@item
Do not include any real info in second-level sections (ie 1.1
@node Introduction to contributing
@chapter Introduction to contributing
-FIXME add fluff
+This chapter presents a quick overview of ways that people can
+help LilyPond.
@menu
* Help us::
@node Iterator tutorial
@section Iterator tutorial
-FIXME -- this is a placeholder for a tutorial on iterators
+TODO -- this is a placeholder for a tutorial on iterators
Iterators are routines written in C++ that process music expressions
and sent the music events to the appropriate engravers and/or
@node Engraver tutorial
@section Engraver tutorial
-FIXME -- This is a placeholder for a tutorial on how engravers work.
+TODO -- This is a placeholder for a tutorial on how engravers work.
Engravers are C++ classes that catch music events and
create the appropriate grobs for display on the page. Though the
@node Callback tutorial
@section Callback tutorial
-FIXME -- This is a placeholder for a tutorial on callback functions.
+TODO -- This is a placeholder for a tutorial on callback functions.
@node LilyPond scoping
@section LilyPond scoping
@item @strong{Release prep phase}:
-FIXME: I don't like that name.
+TODO: I don't like that name.
A new git branch @code{stable/2.x} is created, and a major release
is made in two weeks.
@seealso
Notation Reference:
@ruser{Changing context default settings}.
-@c FIXME
-@c uncomment when backslash-node-name issue is resolved -pm
-@c @ruser{The set command}.
+@ruser{The set command}.
Internals Reference:
@rinternals{Contexts},
@subheading force-hshift property
-@c FIXME: formatting stuff (ie not important right now IMO)
-@c @a nchor Chopin finally corrected TODOgp
-
We can now see how to apply the final corrections to the Chopin
example introduced at the end of @ref{I'm hearing Voices}, which
was left looking like this:
@node The set command
-@subsection The @code{\set} command
+@subsection The @code{@bs{}set} command
@cindex properties
@funindex \set
property @code{drumStyleTable} in context @code{DrumVoice}. The
following variables have been predefined:
-@c FIXME: decide what to do about this table. (ie verbatim or not)
+@c TODO: decide what to do about this table. (ie verbatim or not)
@table @code
@item drums-style
@snippets
-FIXME: MOVE ALL THESE TO LSR! -gp
+@c TODO: MOVE ALL THESE TO LSR! -gp
Here are some examples:
>>
@end lilypond
-@c FIXME: this now links to LM -vv
+@c TODO: this now links to LM -vv
+@c umm, yeah... so what? -gp
@cindex SATB
@cindex choral score