=head1 NAME
-CodingStyle - standards while programming for LilyPond
+CodingStyle - standards while programming for GNU LilyPond
=head1 DESCRIPTION
-Please use these standards while doing programming for LilyPond
+Please use these standards while doing programming for GNU LilyPond
Functions and methods do not return errorcodes, but use assert for
checking status.
=head2 CLASSNAMES (2)
-A lot of classes in LilyPond start with 'P', this is to distinguish
-certain parts of LilyPond: the P stands for Printer, and the P-classes
+A lot of classes in GNU LilyPond start with 'P', this is to distinguish
+certain parts of GNU LilyPond: the P stands for Printer, and the P-classes
are supposed to be more lowlevel than the others. Example:
Staff uses PStaff, PScore and PCol to do the typesetting of
=head1 NAME
-INSTALL - installing LilyPond
+INSTALL - installing GNU LilyPond
=head1 DESCRIPTION
-This page documents installation and compilation of LilyPond
+This page documents installation and compilation of GNU LilyPond
=head1 IMPORTANT
=over 5
=item *
-Unix. LilyPond is known to run on Linux, AIX, Digital Unix and
+Unix. GNU LilyPond is known to run on Linux, AIX, Digital Unix and
Solaris
If you have the Cygnus WIN32 port of the GNU utils, it will
=head1 CONFIGURING and COMPILING
-to install LilyPond, simply type:
+to install GNU LilyPond, simply type:
configure
make install
configure --prefix=/home/me_myself_and_I/
-Since LilyPond currently is beta, You are advised to also use
+Since GNU LilyPond currently is beta, You are advised to also use
--enable-debug
--enable-checking
=head1 RUNNING
-LilyPond does use a lot of resources. For operation you need the following:
+GNU LilyPond does use a lot of resources. For operation you need the following:
=over 5
you need the cygnus win32 gnu port development stuff; have a look
at http://www.cygnus.com/gnu-win32.
-to make LilyPond under, brr, aargh, well, simply type:
+to make GNU LilyPond under, brr, aargh, well, simply type:
bash configure
make win32
=head1 PLATFORMS
-LilyPond (pl 0.0.39) is known to compile on the following platforms:
+GNU LilyPond (pl 0.0.39) is known to compile on the following platforms:
* linux 2.0.28, g++ 2.7.2[.1]
* aix 4.1, g++ 2.7.2
=head1 NAME
-FAQ - LilyPond FAQs
+FAQ - GNU LilyPond FAQs
=head1 DESCRIPTION
Some questions that have been answered before.
-=head2 language
+=head2 Language: mudela
+
+Q: Why can't you type C<#c> in stead of C<cis> ?
+
+A: We think that C<#c> looks as if you are entering the symbols to
+print (which you are not; remember, you're entering the musical
+content in Mudela)
+
+We're not sure on leaving out this feature. If you think this is a
+good idea, please let us know.
+
+Be warned we will I<not> allow you to leave out the C<#> if the note
+already has an accidental. We won't allow
+
+ c# c % no way!
+
+in stead of:
+
+ cis cis
+ #c #c
+
Q: I can type
Q: Why do I need g++ >= 2.7?
-A: By using g++ LilyPond is portable to all platforms which support
+A: By using g++, GNU LilyPond is portable to all platforms which support
g++ (there are quite a few). Not having to support other compilers
-saves us a I<lot> of trouble. LilyPond and FlowerLib use:
+saves us a I<lot> of trouble. GNU LilyPond and FlowerLib use:
=over 4
A.0: Reconsider. Try Linux. It's fun!
-A.1: Currently (patchlevel 27), LilyPond (and flowerLib) compiles, links
+A.1: Currently (patchlevel 27), GNU LilyPond (and flowerLib) compiles, links
and runs on windhoos-nt, using the cygnus gnu port (release b17.1).
I (JCN) only had to make a minor workaround for missing library calls.
-Have a look at http://www.cygnus.com/gnu-win32. To make LilyPond type
+Have a look at http://www.cygnus.com/gnu-win32. To make GNU LilyPond type
C<make $OSTYPE>. (I am not promising to maintain this platform, it is just
that when having to use doze, i-m sometimes too lazy to reboot.)
+pl 51
+ - transposition bugfix + doco
+ - LilyPond -> GNU LilyPond
+ - bugfixes for Staff_side and Note_column*
+ - wohltemperirt: 12 more bars
+
+******
+april 11
pl 50
- merge rest / notehead.
- Staff_side as a base class for most "staff-side" symbols.
- version check
- Note_column_register, Note_column
- multiple scripts
+
********
april 8
pl 49.jcn1
* decent TeX page layout
* per-pstaff item-widths
-
- * remove unnecessary or confusing constructs from .ly
- * key undo
+ * script priority
This is an assorted collection of stuff that will be done, might be
done, or is an idea that I want to think about
PARSER
* Duration-> Musical_duration, typedef Rational Duration?
-MAKE-STUFF
-
- * do platform stuff: configure, header(s), targets, build (out?)
-
BUGS
+ * hairpin width
+
+ * problems with empty staff.
+
* help-lines
* help-lines for rests
* lilypond - -> crash
+ * \stem -1 < chord > rest
+
SEVERELY LACKING:
+ * SPEED!
+
* grace notes
FURTHER FOR ORCHESTRAL SCORE:
* half-sharps, half-flats
+ * key undo
+
* unix style paths for LILYINCLUDE EN
* rpm package buildroot
* C meter iso 4/4
* textspanner: center position
-
* script-spacing
* Brackets
* add (good guess of) width to lyric items
- * midi output: eat-up dynamic, key/meter/tempo changes, and write them neatly
+ * midi output: eat-up dynamic, key/meter/tempo changes, and
+write them neatly
* LilyPond .deb
* Junk Staff_column, and find the requests while walking the Voices.?
+ * MIDI repeat: make lily understand repeats
+
+
* better beamslope calculation: QLP for beams?
* implement better breaking algorithm
* piano staff
+ * vertical spanner
IDEAS
* integrate Register/Midi stuff
* #c <-> cis
* breath marks
+
+ * used fixedpoint arithmetic for min. energy.
projects / lilypond.git / commitdiff