-
This is an assorted collection of stuff that will be done, might be
done, or is an idea that I want to think about
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
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
- 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?
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
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
BUGS
- * detect -pipe
-
* staccato dot positions.
* stacked scripts.
* standchen triool beam up/down
-
SEVERELY LACKING:
* SPEED!
* \duration 8; e*2/3
-
* configure pitch_byte
* special key.
SMALLISH PROJECTS
+ * --fast/--draft: leave out constraints
+
* write Dynamic_line (to group dynamics horizontally)
* write Rest_collision
* key undo
- * unix style paths for LILYINCLUDE EN
+ * unix style paths for LILYINCLUDE env
* indentable stream as baseclass for TeX stream, lily stream, Dstream.
* qtor, btor, mtor-> tor( QUIET_ver ), tor( DEBUG_ver ), etc.
- - declare notenametab?
+ * declare notenametab?
* use tors feature in lily
* 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
FUTURE
+ * auxilliary file for caching info.
+
* Reg_configure_request
* bring Collision::do_pre_processing to haircutter
* 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
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?