before 0.1
+ * fix mi2mu
- * remove spurious/outdated comments in .ly, debug .ly
-
- * pushgroup, popgroup.
-
- * basic dynamics
-
- * basic syntax & parser/lexer cleanup.
+ * update 20 pt table
* decent TeX page layout
- * clean split for m2m of sources.
-
- * caching of Register_group_register hierarchies.
-
- * midi esp.: use I32 iso int where 32 bits are needed (or assumed...)
+ * per-pstaff item-widths
+
+ * remove unnecessary or confusing constructs from .ly
This is an assorted collection of stuff that will be done, might be
done, or is an idea that I want to think about
-STUFF
- * generate all (.hh) files into out dirs
+PARSER
+ * Duration-> Musical_duration, typedef Rational Duration?
- * sort out headers, see m2m
+MAKE-STUFF
- * do platform stuff: configure, header(s), targets, build (out?)
+ * flower config: separate optiflags.
- * make install.
+ * do platform stuff: configure, header(s), targets, build (out?)
BUGS
- * barf if no score_wde_music
-
- * plet bugs: scales.ly
-
* key at clef change.
* key undo
* [c8. c32 c32]
- * $cis ( | ) cis$
+ * cis ( | ) cis
- * Group_feature at start of music.
+ * parser error handling (can you say Segfault?)
SEVERELY LACKING:
* grace notes
- * dynamics (hairpins)
+FURTHER FOR ORCHESTRAL SCORE:
+
+ * multibar rests
+
+ * barnumbers, markers
+
+ * abbreviations c4=16
INPUTLANGUAGE
- * lose the $ and @ ?
+ * unix style paths for LILYINCLUDE ENV
+
+ * configure pitch_byte
+
+ * special key.
* figured bass?
* rest name configurable
- * < .. > vs. { .. } syntax? !
+ * Raw request syntax
+
+ * uniformate: \clef\violin, \clef"violin", \geometric 1.4,
+ \meter{ 2/4 }, etc.
- * '*' vs. '/'
+ * subtime with Subtle_reqs
SMALLISH PROJECTS
- * fix Staff_elem::width() derivs to use offset_
+ * bugreport to doc++ devel: struct not in class hier; public
+ virtual baseclasses
- * parshape
+ * rpm package buildroot
+
+ * indentable stream for TeX stream, lily stream, Dstream.
- * a pure parser.
+ * key transposition
+
+ * caching breakpoints / saving them.
+
+ * key { C }
+
+ * use dstream feature in mi2mu
+
+ * qtor, btor, mtor-> tor( QUIET_ver ), tor( DEBUG_ver ), etc.
+
+ * 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
- * bar numbers/repetition marks
+ * 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: study yy_scan_buffer
+ * read from mmap directly: bugreport to flex developers->
+ yy_scan_buffer in C++..
- * binsearch/hash for notenames, id. for identifiers
+ * binsearch/hash for identifiers
* stafftypes: voice names/ instrument names.
* Brackets
- * space rest.
+ * caching of Register_group_register hierarchies.
* use (char *) iso. String for communication between lexer and
parser.
* collision Request_register.
- * make install (gnu dir names)
+ * add (good guess of) width to lyric items
+
+ * midi output: eat-up dynamic, key/meter/tempo changes, and write them neatly
- * LilyPond .rpm and .deb
+ * LilyPond .deb
DOC
FUTURE
- * Register_container baseclass
+ * slur parts as a script
+
+ * multiple scripst.
+
+ * mixed fontsizes
* put scripts on bars
* guitar chord
- * better beamslope calculation
+ * Junk Staff_column, and find the requests while walking the Voices.?
+
+ * better beamslope calculation: QLP for beams?
* implement better breaking algorithm
- * Implement all requests
+ * Text_crescendo
- * merge key{item} & localkey{item}?
+ * clean solution for staffsize in items.
- * QLP for beams?
+ * merge key{item} & localkey{item}?
* revise calcideal
* eentje/tweetje
* piano staff
-
- * abbreviations a4*8
IDEAS
* integrate Register/Midi stuff
- * create libmudela, or liblily_frontend
+ * create libmudela, or liblily_frontend
* Horizontal_align_item, Vertical_align_item.
* move MIDI io to a ANSI C libmidi library.
- * fold indentifiers and notenames?
-
- * enter Requests directly
-
* itemcolumns: Use dummy items.
- * use an embedded language: scheme, lisp, S-lang, Perl, ?
+ * use an embedded language: scheme, lisp, S-lang, Perl, GUILE, ?
* y -dims in internote?