+Features you cannot find in the doco as working, should be mentioned her.
+
+This is an assorted collection of stuff that will be done, might be
+done, or is an idea that I want to think about
+
+Most of the items are marked in the code as well, with full explanation.
+grep for TODO and ugh/ugr
+
+
+IMPORTANT
+
+ * faq about mi2mu midi t1.
+
+ * update 20 pt table
+
+ * use Hungarian throughout code
+
+ * decent TeX page layout
+
+ * per-pstaff item-widths [JCN]
+
+ * script priority
+
+ * a Hands on tutorial [HKN]
+
+PROJECTS
+
+ * Output class, handles : (smallish)
+ - help text /(c) notice?
+ - version line
+ - warning /errors/progress
+ - abort on error/warning; exit status
+ - quiet/ignore-version options
+ - logfile output
+
+ * elaborate Staff_side baseclass:
+ - scripts
+ - text
+ - slur start/end
+
+ * Output an output format independent (ofi) typeset file; and
+ 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 (smallish)
+ - Glissando
+ - trill
+ - bracket
+
+ * Rewrite Beam and Rhythmic_grouping (hairy)
+ - [c8. c32 c32]
+ - interbeam height
+ - doc on Rhythmic_grouping
+ - 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.
+
+ * Redo font support
+ - rename mf fonts to avoid conflicts with musixtex
+ - check (c) issues
+ - use own fonts/update musixtex fonts/find older (c)-less fonts
+ - hack up mf sources for decent spacing info (and then
+ read AFM/TFM directly, for text too)
+
+PARSER
+ * Duration -> Musical_duration, typedef Rational Duration?
+
+**********************
+HKN buglist:
+
+\bar || ook dunne streepjes? Sluit de balk niet af! (soms met de
+ruimte van een hele maat erachter (bij unmatching staffs)
+
+noten staan vaak te dicht aan de rechterkant van de maatstreep.
+
+optie om nummers/markers boven maatstrepen te zetten
+
+tekst staat erg ver van notenbalken af
+
+waarom geen ; achter dingen in \paper? (\textwidth 180\mm)
+(sowieso: wanneer wel en geen ; ?)
+
+Onduidelijk wanneer wel en geen \ voor een woord. Maak liever
+verplichte regels
+
+implementeren versieringen door duration *0 ofzo? (geeft nu assertion,
+zie duration0.ly)
+
+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
+
+---------------\
+\bar "||" \meter 6/8; op het eind van de regel staat door elkaar
+gedrukt.
+****************
+
BUGS
- * first clef
- * position of key acc's
+ * mi2mu nonexist.midi
+
+ * staccato dot positions.
+
+ * stacked scripts.
+
+ * key transposition.
+
+ * help-lines for rests
+
+ * lilypond - -> crash
+
+ * chlapik balk ruimte
+
+ * standchen triool beam up/down
SEVERELY LACKING:
+ * SPEED!
+
* grace notes
+FURTHER FOR ORCHESTRAL SCORE:
+
+ * multibar rests
+
+ * barnumbers, markers
+
+ * abbreviations c4=16
+
+ * doublebar "||", finishbar "|||" (or "||." ?)
+
INPUTLANGUAGE
- * figured bass?
+ * relative mode for pitch entering
- * transposition
+ * \duration 8; e*2/3
- * voicegroups.
+ * configure pitch_byte
+
+ * special key.
+
+ * figured bass?
* rest name configurable
+ * Raw request syntax
+
+ * subtime with Subtle_reqs
+
SMALLISH PROJECTS
- * Lookup::tex_glissando, Lookup::tex_bracket,
- Lookup::tex_cresc, Lookup::tex_decresc (use texbeam.cc as an
- example.)
+ * Help_line, Help_line_reg
- * Decent TeX titledefs (\tempo, \metron, etc. )
+ * --fast/--draft: leave out constraints
- * command priority into enum
+ * write Dynamic_line (to group dynamics horizontally)
+
+ * write Rest_collision
+
+ * use Real for y positions.
+
+ * shared lib on Solaris too.
+
+ * bugreport to doc++ devel: struct not in class hier; public
+ virtual baseclasses
+
+ * cleanup lily-proto.hh and proto.hh
+
+ * half-sharps, half-flats
+
+ * adaptive accidental spacing.
+
+ * score_elem invible_b_ flag
+
+ * key undo
+
+ * unix style paths for LILYINCLUDE env
+
+ * indentable stream as baseclass for TeX stream, lily stream, Dstream.
+
+ * handle EOF graciously in error messages.
+
+ * caching Item/spanner dimensions.
+
+ * key transposition
+ * centered whole rest
+
+ * caching breakpoints / saving them.
+
+ * use dstream feature in mi2mu
+
+ * qtor, btor, mtor-> tor( QUIET_ver ), tor( DEBUG_ver ), etc.
+ * use tors feature in lily
+
+ * declare notenametab?
+
+ * do conventional keys (C G A, F B E, a e fis, d as des, etc ),
+ besides lists of flats/sharps
+
+ * midi esp.: use I32 iso int where 32 bits are needed (or assumed...)
+
+ * parshape
+
+ * read from mmap directly: bugreport to flex developers->
+ yy_scan_buffer in C++..
+
+ * binsearch/hash for identifiers
+
+ * stafftypes: voice names/ instrument names.
+
+ * Decent TeX titledefs (\tempo, \metron, etc. )
+
* C meter iso 4/4
- * textspanner: dir of beam.
+ * textspanner: center position
* script-spacing
* Brackets
- * space rest.
-
- * use (char *) iso. String for communication between lexer and parser.
+ * caching of Register_group_register hierarchies.
- * As vs. as notename.
+ * use (char *) iso. String for communication between lexer and
+ parser.
* configure idealspacing: arithmetic spacing
- * fix symbols in parser.o: `Warning: size of symbol'
+ * LilyPond .deb. Other packaging methods?
+
+ * detect -pipe
- * Viola clef (->jan?!)
DOC
+ * all errors
+
+ * config of TeX macros
- * beam generation.
+ * a test suite
- * all errors
+ * hacking-HOWTO
FUTURE
- * Text_pstaff/Lyric_staff
+ * auxilliary file for caching info.
- * put requests on barcommands
+ * Reg_configure_request
- * glissando
+ * bring Collision::do_pre_processing to haircutter
+
+ * slur parts as a script
+
+ * mixed fontsizes
+
+ * put scripts on bars
* guitar chord
- * better beamslope calculation
+ * Junk Staff_column, and find the requests while walking the Voices.?
- * implement better breaking algorithm
+ * better beamslope calculation: QLP for beams?
- * check out linux -> go32 crosscompiler: dos port
+ * implement better breaking algorithm
- * Implement all requests
+ * Text_crescendo
- * QLP for beams?
+ * clean solution for staffsize in items.
- * stacked slurs.
+ * merge key{item} & localkey{item}?
* revise calcideal
- * eentje/tweetje
+ * volta
+
+ * piano staff
+
+ * vertical spanner
IDEAS
- * itemcolumns
+ * scoping in Lexer: do general id- assignments in mudela.
- * check out PMX
+ ID '=' EXPR;
- * dependencies: -> implement children more elegantly. Handle
- spanner with broken deps.
+ * create libmudela, or liblily_frontend
- * use an embedded language: scheme, lisp, S-lang, Perl, ?
+ * move MIDI stuff (including Quantization) to a ANSI C libmidi library.
- * Broadcasts in Walker of Request and Item.
+ * use an embedded language: Python
+ for :
+ - Items/Spanners
+ - Registers
+ - Complex mudela?
* y -dims in internote?
- * hack up mf sources for decent spacing info (and then maybe
- read TFM directly)
-
* merge Atom and Symbol?
- * merge Command/Input_command.
-
* merge common code of Item, Atom/Molecule
-
* Spacing_request for manually adjusting spacing
- * Staff_group.
+ * Staff_group, Score_request_register.
- * SHIT: meters/bars should be aligned, which is difficult if
+ * Meters/bars should be aligned, which is difficult if
we get different keychanges in different staffs.
- * Integrating (objectiveC) MusicKit with LilyPond
-
- * MusixTeX output possible?
+ * caching breakpoints
+
+ * #c <-> cis
+
+ * breath marks
+
+ * used fixedpoint arithmetic for min. energy.
+
+ * default convert mudela-file.ly -> mudela-file.tex
+ - rename {standchen,scsii-menuetto,...}.tex
+
+ * (related with above) --simple-mudela option for lily,
+ to lily input files with one-voice simple mudela
+ (no red tape)
+
+ * stack scripts in chords:
+ % fingering: footing:
+ < a-4 c-2 g-1 > < c-\ltoe e-\lheel >
+
+ * parameterised scripts for fingering and footing:
+
+ % toe to bheel four to five
+ % ^_u 4_5
+ % -
+ % --|x-- --|x--
+ % --|--- --|---
+ % --|--- --|---
+ (where "to" is a tiny bow)
- * PostScript output (esp. Beams, Slurs, etc)
+ * move towards incremental algorithms.