5 * create libmudela, libmidi, or liblily_frontend
7 * Register_groups as a baseclass.
13 * decent TeX page layout
15 * < .. > vs. { .. } syntax? !
17 This is an assorted collection of stuff that will be done, might be
18 done, or is an idea that I want to think about
25 * key print if clef change.
29 * Group_feature at start of music.
47 * rest name configurable
55 * bar numbers/repetition marks
57 * read from mmap directly: study yy_scan_buffer
59 * binsearch/hash for notenames
61 * stafftypes: voice names/ instrument names.
63 * Lookup::tex_glissando, Lookup::tex_bracket, (use texbeam.cc as an
66 * Decent TeX titledefs (\tempo, \metron, etc. )
68 * command priority into enum
72 * textspanner: center position
80 * use (char *) iso. String for communication between lexer and
83 * configure idealspacing: arithmetic spacing
85 * fix linking: `Warning: size of symbol'
87 * collision Request_register.
89 * LilyPond .rpm and .deb
103 * Register_container baseclass
105 * put scripts on bars
111 * better beamslope calculation
113 * implement better breaking algorithm
115 * Implement all requests
117 * merge key{item} & localkey{item}?
131 * enter Requests directly
133 * itemcolumns: Use dummy items.
135 * use an embedded language: scheme, lisp, S-lang, Perl, ?
137 * y -dims in internote?
139 * hack up mf sources for decent spacing info (and then maybe
142 * merge Atom and Symbol?
144 * merge common code of Item, Atom/Molecule
146 * Spacing_request for manually adjusting spacing
148 * Staff_group, Score_request_register.
150 * SHIT: meters/bars should be aligned, which is difficult if
151 we get different keychanges in different staffs.
153 * Integrating (objectiveC) MusicKit with LilyPond
155 * MusixTeX output possible?
157 * PostScript output (esp. Beams, Slurs, etc)
159 * caching breakpoints