-*-outline-layout:(2 (-1 -1 0 :) 0);outline-stylish-prefixes:nil -*-
+
* GNU LilyPond TODO
Features you cannot find in the documentation as working, should be
mentioned here. This is an assorted collection of stuff that will be
done, might be done, or is an idea that we want to think about.
-m
Most of the items are marked in the code as well
Grep -i for TODO, FIXME and ugh/ugr/urg.
.* TODO
. * use hash tabs iso. alist_ for elt property?
-. * agressive type-checking for SCM stuff.
-. * use "staff-space" and "half-space" iso interline,
- staff_line_leading () etc.
-. * why does Voice.beamQuantisation = #'none not work?
- overriding in ly/params.ly works fine
-
+. * control paper-size/-file from commandline ?
+ lilypond --paper=paper16 foo.ly
+ lilypond --paper=paper20 foo.ly
+ lilypond --paper=paper-as9 foo.ly
+. * entangle ly/* paper-params papersize stuff
+. * fix tremolos.
+. * change ) c4 to c4-)
+. * internationalize GUILE msgs.
+. * unbroken marks.
+. * write smobifying howto.
+. * put property test files in refman.
+. * alignment within @itemize
+. * interstaff stems
+. * junk dstream output.
+. * Change website to be index to documentation.
+. * \grace { c d } c1 in midi
+. * \prop slurdir in grace notes
+. * Make fingering and playing instructions Music_wrappers?
+. * \eltproperty "=Context" "Elt_name" "prop-name" #value
+. * script columns
+. * Must stop before this music ends:
+verse=\lyrics {
+. * input/test/grace.sly: wierd big spacing on grace notes
. * TODO^2:
. * make a TODO.texi, like http://www.gnu.org/software/guile/ideas.html
. * make this file understandable for 3rd parties.
. * \accepts -> \acceptedby
. * context in embedded SCM errors.
-. * eradicate all VIRTUAL_COPY_CONS () macros ; use indexed creation,
- eg.
-
- ctor_dict["Score_element"]->clone_func (orig);
- ctor_dict["Score_element"]->create_func ();
. * acc at tied note after linebreak.
+. * fontSize for time sigs and beams.
. * fix font-naming and selecting
-. * sparse ties.
+. * add context information to warnings
+Paper:
+waarschuwing: Kan niet beide uiteinden van bindingsboog vinden
+MIDI:
+pa.ly:33:23: waarschuwing: Schroot verzoek: `Span_req':
+ g' a4 bes8 \grace f8(
+ )es16 d es8 r c |
. * chord tonic: placement of accidental C#, Cb (from scm and C++)
. * note head on stem err msg in dutch.
. * why need to run -C mf twice?
. * hara kiri _8 clef.
. * junk -M ?
. * mudela-book doco
-. * fix or replace feta-accordion.mf
-. * script engraver
. * bracket pdf hack
+. * Added StaffContents and RhythmicStaffContents context, they are
+between Staff (which groups the elements), and generates the Staff
+level elements (key, clef, meter, etc). This construction makes
+\consistsend redundant
+
. * Mondrup:
- if I change the property minVerticalAlign in a multi staff score with
lyrics the change affects the lyrics too. I would like the change to
- I would like to be able to influence the sloping of xtuplet brackets
-- for one of my test scores containing a modern edition of an early
-17'th century composition I have a leading measure containing the
-orginal clefs and note values of the original composition. I use the
-a"harmonic" and "diamond" note head styles for that measure and would
-like to have the stems of these notes _centered_ on the notehead as in
-the mensural music notation.
-
- after the leading measure in the above mentioned score I want a double
bar line fully drawn across the staves and after that keep to the
ChoirStaff bar line types in the rest of the scores
-
-. * make all Feta (including dynamics) available to the user in
- textual scripts. Examples: "D.S. al \coda", "\mf espress.".
. * Write script that uses --find-old-relative to do auto relativization.
-. * Junk shared cruft (duration, moment) in lib/
.* Cleanups needed
. * \$ and $ identifier syntax in examples.
-. * Junk ghost positioning objects eg, Script leans on Staffside
- leans on Staff.
. * Key_engraver, Local_key_item
. * Think of comprehensive solution for "if (grace_b == self_grace_b_)"
. * String[String.length] doesn't trap.
. * Rhythmic_column and interaction stem/rhythmic_column/note_head/dots.
-. * Duration
. * clef engraver
. * parser
. * Lookup::text -> needs to be TeX independent.
. * junk Music_iterator::first_b_
-. * Bezier
.* ACCIDENTALS
. * half-sharps, half-flats
. * accidentals closer to note head
-.* Beams
+.* BEAMS
. * [c8. c16 c16 c16] in 6/8 timesig.
. * Rewrite Stem, Beam (hairy)
-. * general shaving on Beam and Stem
-. * use plet grouping
-. * beams over bars
+. * beams over barlines
. * Rests and beams don't work too well together. Example:
[ r8 g''16 des'] [r8 c16 a]
. * autoBeamMelisma: if I explicitly beam notes in a staff with auto
. * staffside spanner (crescendo!) along with staffswitch.
. * * auto melismaBusy for beams.
-. *
-> \context Staff <
+. * \context Staff <
> {\voiceone''4. r8}
> \voicetwo c,4 r4}
> >
-. * sort out breve shapes.
. * \time forces keysig?
.* STUFF
. * 4. Lyrics and grace sections don't go too well together.
The words are aligned with the main note, not the start of the
grace note. This is usually wrong, but is sometimes right.
-. * tie-direction
-. * repeats and partial measures.
. * rhythmic staff & accidentals.
. * use melismaBusy in Lyric context to typeset melismata correctly.
. * ly2dvi/lilypond logfile.
. * msgfmt -o check?
. * collision of lyrics with span_bars. See star-spangled.
. * It is impossible to typeset two textual scripts that are stacked
- on top of eachother and avoids note collisions and at the same
+ on top of each other and avoids note collisions and at the same
time are typeset with different textStyle. I tried to move around
the text_engraver and other engravers between Voice and Thread
but the granularity is not fine enough, the scripts have to
. * don't shorten stems/staffs closer to each other.
. * to space the staffs/staffgroups contained in the score.
. * heavier beams?
-
-. * tuplets that are written as "number : note", for example
- "3 : [image of a half note here]". possible?
-. * a note with a circle after it, meaning:
-
- note + circle = note + 1/4 of its length
-
- the circle is like a dot that's not filled in. for example, on
- page three, the c-sharp on the second line should be a quarter with
- a circle, not a quarter tied to a sixteenth. is this at all
- possible with lily?
-. * make dependencies () a virtual function.
-. * deprecate hangOnClef.
. * Abstraction for engravers:
. * make "in-between" engraver (Tie)
. * make wide_spanner_engraver (line_group_spanner, staff_symbol)
. * store req -> element, element -> element causes for warnings
-. * compulsory hshift
. * My wish list for lyrics. I dream of a time when I will have enough time to
become familiar enough with the source code to be able to implement some of
these myself, but I don't know when that will be, so I thought I'd "publish"
. * --prefix option?
. * -I option per filetype?
. * kpathsea?
-. * fix vertical alignment and stafflines
. * declaring Performers
. * text-items clash with stems/beams
. * --include, -I option for ly2dvi (pass on to lily)
* { a4 a16 } c <-- duration of c?
* < a4 b8 > c <-- duration of c?
. * \tempo 4. = 90;
-. * make sure all ex's have a mudela-version
. * do rest-collisions for Multi_measure_rests as well.
. * split error/warning in error/warning/non_fatal_error
-. * add a Duration_convert member to Duration_iter to set parameters.
- Junk global duration settings.
. * discourage breaking of slurs
. * fix variable define/lookup parser global<->paper
. * fix title/instrument placements; see input/test/title.ly
. * patch: don't touch timestamp if all patches fail.
. * MetaPost: should not generate setgray for unfill
-
-. * mf-to-table -> add space 'before ; in AFM output. (-> check AFM
-spec. Is this a bug in afm2tfm?)
. * check out GCC signatures?
. * glibc 2.0:
f = fopen ("/dev/null", "r")
. * slurs
. * accents
. * dynamics
-> Would it be hard to add support for proper dynamics in MIDI output? I
-> would really like to have this feature...
-
-Concretely spoken, for dynamics you have to write a performer
-(Dynamics_performer), that will take the input requests. If I
-understand correctly, every MIDI note played must have its dynamic
-strength set separately. That means the the Dynamics_performer must
-set the strength of every Audio_note it finds. This means that one
-has to modify existing Audio items. The best way of doing this is
-with a broadcast/acknowledge process.
-
-So the best way of handling this, is
-
- 1 supporting dynamic settings in Audio_note
-
- 2 Write a Dynamics_performer that will modify
- any notes it finds to set appropriate strengths.
-
-I'd say that the work involved is not hard, but you have to be fluent
-with C++ and need some insight into the working of Notation Contexts
-and friends. I guess I could do it in a day or so, but if you are not
-so fluent with the inner workings of LilyPond, it could take you some
-more time (A few more days?).
-
-Please note, that I am *not* going to code this myself: my days are
-valuable, and I think I have more interesting things to do than fixing
-the MIDI output (I don't even have a soundcard). But I *do* want to help
-you or other people with implementing this, so if you need help, don't
-hesitate to ask.
. * account for rhythmic position in measure
. * etc.
. * Glissando
. * trill
-. * Collisions
-. * left/right note balls should be handled by Collision:
- < \multi 2; { \stem 1; <b c> } { <f as b> } >
-
. * Keys:
. * merge key{item} & localkey{item}?
. * spacing
. * write Dynamic_line (to group dynamics horizontally)
-
. * handle EOF graciously in error messages.
. * midi esp.: use I32 iso int where 32 bits are needed (or assumed...)
% --|--- --|---
(where "to" is a tiny bow)
-. * auxilliary file for caching info.
-
. * Text_crescendo
.* IDEAS
projects / lilypond.git / blobdiff