From: fred Date: Sun, 24 Mar 2002 19:43:02 +0000 (+0000) Subject: lilypond-0.0.62 X-Git-Tag: release/1.5.59~4745 X-Git-Url: https://git.donarmstrong.com/?a=commitdiff_plain;h=c6a8bd08e78f843c4e402c091e22f0269aeb1549;p=lilypond.git lilypond-0.0.62 --- diff --git a/TODO b/TODO index e4b56d2381..75162b7604 100644 --- a/TODO +++ b/TODO @@ -1,4 +1,3 @@ - This is an assorted collection of stuff that will be done, might be done, or is an idea that I want to think about @@ -8,11 +7,14 @@ grep for TODO and ugh/ugr IMPORTANT + * faq about mi2mu midi t1. + * update 20 pt table * use Hungarian throughout code * rename mf fonts to avoid conflicts with musixtex + check (c) issues * decent TeX page layout @@ -26,8 +28,9 @@ IMPORTANT PROJECTS - * Output class, handles + * Output class, handles : (smallish) - help text /(c) notice? + - version line - warning /errors/progress - abort on error/warning; exit status - quiet/ignore-version options @@ -39,25 +42,32 @@ PROJECTS - slur start/end * Output an output format independent (ofi) typeset file; and - make ofi2 TeX, MusixTex, PostScript, Ascii... interpreters. + make ofi2 TeX, MusixTex, PostScript, Ascii... interpreters. (difficult) - poor man's ascii output possible? - MusixTeX output possible? (would have to be done before break calc.) - NIFF ? - PostScript output (esp. Beams, Slurs, etc) - * TeX spanners , use texbeam.cc as an example + * TeX spanners , use texbeam.cc as an example (smallish) - Glissando - trill - bracket - * Rewrite Beam and Rhythmic_grouping + * Rewrite Beam and Rhythmic_grouping (hairy) - [c8. c32 c32] - - interbeam height + - interbeam height - general shaving - use plet grouping - abbreviations [c2 c2]1/2 - separate visual from rhythmic info + * Redo MIDI output to use Registers: (Difficult) + - remember more horizontal info than melodics: + - tempo change + - repeat + - slurs + - dynamics etc. + PARSER * Duration -> Musical_duration, typedef Rational Duration? @@ -69,10 +79,6 @@ ruimte van een hele maat erachter (bij unmatching staffs) Hele rusten ook in andere maatsoort dan 4/4 (en centreren in de maat) -------------------------\ -barcheck failed in lyric mode -> assert (zie barcheck.ly) (0.0.57) -------------------------/ - noten staan vaak te dicht aan de rechterkant van de maatstreep. optie om nummers/markers boven maatstrepen te zetten @@ -88,10 +94,6 @@ verplichte regels implementeren versieringen door duration *0 ofzo? (geeft nu assertion, zie duration0.ly) -midi: instrumenten definieren? -midi: tempo halverwege het stuk wijzigen? -midi: gebonden noten niet herhalen? - Triolen enzo: het zou handig zijn als je het cijfer "3" ook _tussen_ twee noten kon plaatsen. Dat is bijvoorbeeld nodig in c4*2/3 c8*2/3 @@ -103,8 +105,6 @@ gedrukt. BUGS - * detect -pipe - * staccato dot positions. * stacked scripts. @@ -122,7 +122,6 @@ BUGS * standchen triool beam up/down - SEVERELY LACKING: * SPEED! @@ -145,7 +144,6 @@ INPUTLANGUAGE * \duration 8; e*2/3 - * configure pitch_byte * special key. @@ -160,6 +158,8 @@ INPUTLANGUAGE SMALLISH PROJECTS + * --fast/--draft: leave out constraints + * write Dynamic_line (to group dynamics horizontally) * write Rest_collision @@ -177,7 +177,7 @@ SMALLISH PROJECTS * key undo - * unix style paths for LILYINCLUDE EN + * unix style paths for LILYINCLUDE env * indentable stream as baseclass for TeX stream, lily stream, Dstream. @@ -191,7 +191,7 @@ SMALLISH PROJECTS * qtor, btor, mtor-> tor( QUIET_ver ), tor( DEBUG_ver ), etc. - - declare notenametab? + * declare notenametab? * use tors feature in lily @@ -228,10 +228,11 @@ SMALLISH PROJECTS * configure idealspacing: arithmetic spacing - * midi output: eat-up dynamic, key/meter/tempo changes, and -write them neatly - * LilyPond .deb + * LilyPond .deb. Other packaging methods? + + * detect -pipe + DOC @@ -243,6 +244,8 @@ DOC FUTURE + * auxilliary file for caching info. + * Reg_configure_request * bring Collision::do_pre_processing to haircutter @@ -257,8 +260,6 @@ FUTURE * 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 @@ -283,22 +284,20 @@ IDEAS ID '=' EXPR; - * integrate Register/Midi stuff - * create libmudela, or liblily_frontend * move MIDI stuff (including Quantization) to a ANSI C libmidi library. - * use an embedded language: Python, Scheme? + * use an embedded language: Python for : - Items/Spanners - Registers - - Complex mudela + - Complex mudela? * y -dims in internote? * hack up mf sources for decent spacing info (and then - read TFM directly, for text too) + read AFM/TFM directly, for text too) * merge Atom and Symbol?