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
+grep for TODO and ugh/ug
0.2:
- * latex quirk?
+ * ly2dvi seams to eat accents as in \'el\'egant
+
+ * libtoolize flowerlib
+
+ * shared lib
+
+ * bf: abbrevbeam?
+
+ * add full coriolan to website.
+
+ * robustify Beam (in case of no stems, 32nd notes)
+
+ * fix [c8 c16 c16] (mustn't slope)
+
+ * fix silly " "2*12 a4 (=4*12) sticky plet
* check for groff / troff/ nroff et
+ * latex quirk?
+
* use kpsepath to find all TeX dirs
- configure.in
- clean-fonts.sh
- * fix MIDI
-
* mudela-convert.
* nicen examples:
- remove all \multi
- break-up heavily-nested score blocks
- * --metafont
-
* disable spaces in TeX stuff
-
- * height of dyns.
* handle ^C for tmp/file creation.
* versioning for Feta
- * bf: abbrevs over whole note
-
* the warning about the negative slur/tie length appears twice
which is irritating.
* better hshift (dots, distance, head dependent)
- * tie/slur dir & curvature
-
* stem len adjustable
- * mindist for spanners
+STUFF
+ * clefs: The names I'd like are of the form
-
+ [FGC]n{[_^]8} F, G or C clef, on nth line, subscripted
+ or superscripted with an 8.
+ So:
+ G, G2, treble, (== current `violin') G clef on second line.
+ F, F4, bass (== current `bass' ) F clef on fourth line
+ G_8, G2_8 G clef on 2nd line, with 8 subscript
+ G^8 G clef on 2nd line with 8 superscript
+ C1, soprano (==current `soprano') C clef on first line.
+ C2, (==current `mezzosoprano') C clef on second line
+ C3, alto (==current `alto') C clef on third line
+ C4, tenor (==current `tenor') C clef on fourth line
+ C5 (==current `baritone') C clef on fifth line)
-STUFF
* give Items/Spanners access to unbroken originals
- staff title
* page handling:
- - papersizes
- PS output
- optimal pagebreaking.
* AFM for font input?
+
3RD PARTY BUGS:
- * gdb on RedHat 5
+ * tried egcs 1.0.2: failed on lily/stem.cc -> flower/include/interval.hh
+ should narrow down and send bug report
* xdvi: PS in magnifying glass.
* Makefile stuff:
- shared lib on Solaris too.
- - check libtool
* Add mudela-output to Rosegarden.
* a musical dictionary. See Documentation/vocabulary-*, other
languages:
+ - explanation
- italian
- german
- dutch
* add to MIDI output:
- tempo change
+ - ornaments (and trills?)
- repeat
- slurs
- - dynamics etc.
+ - accents
+ - dynamics
+ - account for rhythmic position in measure
+ - etc.
* grace notes
- make separate class for Grace_*_engravers
(which is at Voice_gravs level)
- make encapsulated spacing problems.
- * On-demand loading of simple-engravers?
-
* accidentals per Voice_group
- * Convert all ref/bib stuff into BibTeX.
-
* Output class, handles : (smallish)
- help text /(c) notice?
- version line
make ofi2 TeX, MusiXTex, Display PostScript, PostScript,
Ascii... interpreters. (difficult)
- - poor man's ascii output possible?
- - MusiXTeX output possible? (would have to be done before break calc.)
- NIFF ?
- Common Music Notation
- PostScript output (esp. Beams, Slurs, etc)
* TeX spanners , use texbeam.cc as an example (smallish)
- Glissando
- trill
- - bracket
* Rewrite Stem, Beam and Rhythmic_grouping (hairy)
- [c8. c32 c32]
* breaking:
- caching breakpoints
- saving them
- - allowing users to set them.
- penalties
- specify number of lines
* Rhythmic staff.
- * Baroque superstaff
-
-SEVERELY LACKING:
-
- * SPEED!
-
* multibar rests
* markers
* adaptive accidental spacing.
* handle EOF graciously in error messages.
-
+oo
* caching Item/spanner dimensions.
* centered whole rest
IDEAS
- * Output abstract data structures associated with
-Mudela.
+ * Output data structures of Mudela in XML/SGML.
* create libmudela, or liblily_frontend
if ( t <= get_type( q ))
..
- * naming of Voice_group/Voice
-
* versioning stuff (cvt mudela, mudela, etc.)
* a real convert-mudela
* lyrics in chords still fuck up.
- * rewire acknowledge_element() logic with a process_acknowledged()
-
* pushgroup/popgroup
- * multi threading?
- - 1 thread per element/ 1 thread per line
- - 1 thread per Translator
-
* Use hooks/dependency graphs for properties