1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
|
before 0.1
* update 20 pt table
* decent TeX page layout
* per-pstaff item-widths
* remove unnecessary or confusing constructs from .ly
* key undo
This is an assorted collection of stuff that will be done, might be
done, or is an idea that I want to think about
PARSER
* Duration-> Musical_duration, typedef Rational Duration?
MAKE-STUFF
* do platform stuff: configure, header(s), targets, build (out?)
BUGS
* help-lines
* help-lines for rests
* [c8. c32 c32]
* cis ( | ) cis
* lilypond - -> crash
SEVERELY LACKING:
* grace notes
FURTHER FOR ORCHESTRAL SCORE:
* multibar rests
* barnumbers, markers
* abbreviations c4=16
INPUTLANGUAGE
* relative mode for pitch entering
* configure pitch_byte
* special key.
* figured bass?
* transposition
* rest name configurable
* Raw request syntax
* subtime with Subtle_reqs
SMALLISH PROJECTS
* bugreport to doc++ devel: struct not in class hier; public
virtual baseclasses
* half-sharps, half-flats
* unix style paths for LILYINCLUDE EN
* rpm package buildroot
* indentable stream as baseclass for TeX stream, lily stream, Dstream.
* caching Item/spanner dimensions.
* key transposition
* caching breakpoints / saving them.
* use dstream feature in mi2mu
* qtor, btor, mtor-> tor( QUIET_ver ), tor( DEBUG_ver ), etc.
- declare notenametab?
* use tors feature in lily
* 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...)
* fix Staff_elem::width() derivs to use offset_
* parshape
* read from mmap directly: bugreport to flex developers->
yy_scan_buffer in C++..
* binsearch/hash for identifiers
* stafftypes: voice names/ instrument names.
* Lookup::tex_glissando, Lookup::tex_bracket, (use texbeam.cc as an
example.)
* Decent TeX titledefs (\tempo, \metron, etc. )
* command priority into enum
* don't broadcast Staff_sym
* C meter iso 4/4
* textspanner: center position
* script-spacing
* Brackets
* caching of Register_group_register hierarchies.
* use (char *) iso. String for communication between lexer and
parser.
* configure idealspacing: arithmetic
* collision Request_register.
* add (good guess of) width to lyric items
* midi output: eat-up dynamic, key/meter/tempo changes, and write them neatly
* LilyPond .deb
DOC
* beam generation.
* all errors
* a test suite
FUTURE
* Reg_configure_request
* slurs per voicegroup.
* slur parts as a script
* multiple scripst.
* mixed fontsizes
* put scripts on bars
* glissando
* guitar chord
* Junk Staff_column, and find the requests while walking the Voices.?
* better beamslope calculation: QLP for beams?
* implement better breaking algorithm
* Text_crescendo
* clean solution for staffsize in items.
* merge key{item} & localkey{item}?
* revise calcideal
* volta
* piano staff
IDEAS
* integrate Register/Midi stuff
* create libmudela, or liblily_frontend
* Horizontal_align_item, Vertical_align_item.
* move MIDI io to a ANSI C libmidi library.
* use an embedded language: scheme, lisp, S-lang, Perl, GUILE, ?
- Items/Spanners
- Registers
* y -dims in internote?
* hack up mf sources for decent spacing info (and then maybe
read TFM directly)
* merge Atom and Symbol?
* merge common code of Item, Atom/Molecule
* Spacing_request for manually adjusting spacing
* Staff_group, Score_request_register.
* SHIT: meters/bars should be aligned, which is difficult if
we get different keychanges in different staffs.
* Integrating (objectiveC) MusicKit with LilyPond
* MusixTeX output possible?
* PostScript output (esp. Beams, Slurs, etc)
* caching breakpoints
* use exceptions iso assert?
* #c <-> cis
* breath marks
|
