+0.1:
+ * versioning stuff (cvt mudela, mudela, etc.)
+
+Features you cannot find in the doco as working, should be mentioned here.
+
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
+ * dots into separate item.
-IMPORTANT
+ * lyrics in chords still fuck up.
- * update 20 pt table
+ * add to MIDI output:
+ - tempo change
+ - repeat
+ - slurs
+ - dynamics etc.
+
+ * rewire acknowledge_element() logic with a process_acknowledged()
- * use Hungarian throughout code
+ * pushgroup/popgroup
- * rename mf fonts to avoid conflicts with musixtex
+ * whole head on ledger line
+
+ * piano staff
+
+ * implement better breaking algorithm
+
+ * update 20 pt table
* decent TeX page layout
- * per-pstaff item-widths [JCN]
+ * enter script priority
- * script priority
+ * a hands on tutorial
- * use own fonts/update musixtex fonts
+PROJECTS
- * a Hands on tutorial [HKN]
+ * grace notes
+ - adapt for multiple font sizes.
+ - make separate class for Grace_*_engravers
+ (which is at Voice_gravs level)
+ - move stem, beam, slur into baseclass to adapt for (fixed
+ size) grace notes.
+ * accidentals per Voice_group
-PROJECT:
+ * Convert all ref/bib stuff into BibTeX.
- * Output class, handles
+ * 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
+ - scripts
+ - text
+ - slur start/end
* Output an output format independent (ofi) typeset file; and
- make ofi2 TeX, MusixTex, PostScript, Ascii... interpreters.
+ make ofi2 TeX, MusixTex, PostScript, Ascii... interpreters. (difficult)
- poor man's ascii output possible?
- - MusixTeX output possible?
+ - MusixTeX output possible? (would have to be done before break calc.)
+ - NIFF ?
+ - Common Music Notation
- PostScript output (esp. Beams, Slurs, etc)
+ - Move PScore, Items, Spanners etc. into libmutype.a
+
+ * separate Score_elem settings in user-settable (properties
+ .. ) and non-user-settable part. Maybe use something like X-resources:
+ "Staff=oboe*dir: 0", "Staff=*.Voice_group=solo*dir: 1"
+
+ * TeX spanners , use texbeam.cc as an example (smallish)
+ - Glissando
+ - trill
+ - bracket
+
+ * Rewrite Stem, Beam and Rhythmic_grouping (hairy)
+ - [c8. c32 c32]
+ - interbeam height
+ - doc on Rhythmic_grouping
+ - general shaving on Beam and Stem
+ - use plet grouping
+ - abbreviations [c2 c2]1/2
+ - separate visual from rhythmic info even more
+ - beams over bars
+
+
+ * Redo font support
+ - rename mf fonts to avoid conflicts with musixtex
+ - 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)
+ - use MF to generate rules.
+ - rewrite : make a metafont iso font
+
+ * lines:
+ - Ledger lines, should be separate item: Ledger_lines, Ledger_lines
+ - set different line sizes / thicknesses
+ - stem down too far right
+ - beam stem showthrough, inter beam sizes (french vs german style)
+
+ * Collisions
+ - bring Collision::do_pre_processing to haircutter
+ - left/right note balls should be handled by Collision:
+ < \multi 2; { \stem 1; <b c> } { <f as b> } >
+
+ * Keys:
+ - merge key{item} & localkey{item}?
+ - do conventional keys (C G A, F B E, a e fis, d as des, etc ),
+ besides lists of flats/sharps, possibly via declaration
+ - key transposition.
+ - key undo: \key bes; .. . \key; should print natural
+ - special key: \key 'b bes bis';
+ - spacing, national styles?
PARSER
- * Duration-> Musical_duration, typedef Rational Duration?
-
-HKN buglist:
+ * Duration -> Musical_duration, typedef Rational Duration?
-\bar || ook dunne streepjes? Sluit de balk niet af! (soms met de
-ruimte van een hele maat erachter (bij unmatching staffs)
-
-Hele rusten ook in andere maatsoort dan 4/4 (en centreren in de maat)
-
-------------------------\
-barcheck failed in lyric mode -> assert (zie barcheck.ly) (0.0.57)
-------------------------/
-
-optie om te stoppen na eerste barcheck fail? (en wellicht in eerder
-stadium van preprocessing)
-
-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
+BUGS
-barcheck her-synchroniseren? (evt met optie)
+ * fix mysterious Flex malloc bug
-script ^"3" onder ondanks boven?
+ * should adjust stemlength for flag number.
-symbolen voor triller? (dus "tr---")
+ * lilypond - -> crash
-waarom geen ; achter dingen in \paper? (\textwidth 180\mm)
-(sowieso: wanneer wel en geen ; ?)
+ * standchen triool beam up/down
+
+ * (where are the) gcc compile warnings on linux
+
+SEVERELY LACKING:
-Onduidelijk wanneer wel en geen \ voor een woord. Maak liever
-verplichte regels
+ * SPEED!
-implementeren versieringen door duration *0 ofzo? (geeft nu assertion,
-zie duration0.ly)
+ * multibar rests
-midi: instrumenten definieren?
-midi: tempo halverwege het stuk wijzigen?
-midi: gebonden noten niet herhalen?
+ * barnumbers, markers
---------/\
-De beam van de triool klopt niet.
- <[d8. b8.> \duration 32; <e'32*2/3 cis'32*2/3> <d'32*2/3 b32*2/3>
- <cis'32*2/3 a32*2/3> \duration 16; <b gis> <d' fis> <cis' e>
-<b d]> |
-(zie ook ergens in lacidarem-pianoI.ly)
---------/
-scales.ly compileert niet meer (vanwege transpose?)
+ * abbreviations c4=16
-Lengte van de stokken klopt vaak niet, zie bijv. de eerste maat van
-langestok.ly.
+INPUTLANGUAGE
-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
+ * c4 4 4 4 for c4 c4 c4 c4?
----------------\
-\bar "||" \meter 6/8; op het eind van de regel staat door elkaar
-gedrukt.
+ * neatly (and readably) expressing concurrent
+ voices
+ * <c f a>4 ?
-BUGS
+ * should have \require{package.ly} to read req'd packages.
- * detect -pipe
-
- * redo timing stuff <-> pulk to allow \meter 2/4; e2. to work
- out correctly
+ * Viola mode?
- * key transposition.
+ @c c g e g
+ for
+ c g es g,
- * hairpin width
+ @A c g e g
+ for
+ cis gis e gis
- * help-lines for rests
+ * relative mode for pitch entering
- * [c8. c32 c32]
+ * bracket (bracketplets)
* \duration 8; e*2/3
- * cis ( | ) cis
-
- * lilypond - -> crash
-
- * chlapik balk ruimte
-
- * standchen triool beam up/down
-
-
-SEVERELY LACKING:
-
- * SPEED!
-
- * grace notes
-
-FURTHER FOR ORCHESTRAL SCORE:
+ * configure pitch_byte
- * multibar rests
+ * figured bass?
- * barnumbers, markers
+ * rest name configurable
- * abbreviations c4=16
+ * Raw request syntax
- * doublebar "||", finishbar "|||" (or "||." ?)
+ * subtime with Subtle_reqs
-INPUTLANGUAGE
+PROJECTS
- * relative mode for pitch entering
+ * Do RTTI i.s.o. static_name(), name() and request-junk.
- * configure pitch_byte
+SMALLISH PROJECTS
- * special key.
+ * A range for context errors (eg. mark both { and }. )
- * figured bass?
+ * lyric in staff (sharpsharp in staff, text below)
- * rest name configurable
+ * fix Egler definitions ( see tex/eglerdefs.tex )
- * Raw request syntax
+ * replace Score_elem member access by get()/set() methods, to enable
+ future embedded code.
- * subtime with Subtle_reqs
+ * --fast/--draft: leave out constraints
-SMALLISH PROJECTS
+ * write Dynamic_line (to group dynamics horizontally)
* write Rest_collision
* bugreport to doc++ devel: struct not in class hier; public
virtual baseclasses
+ * get rid of init_end;
+
* cleanup lily-proto.hh and proto.hh
* half-sharps, half-flats
-
- * key undo
- * unix style paths for LILYINCLUDE EN
+ * adaptive accidental spacing.
+
+ * 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?
-
- * 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
+ * declare symtab
- * update for T70 fonts or newer
+ * declare notenametab?
* midi esp.: use I32 iso int where 32 bits are needed (or assumed...)
* stafftypes: voice names/ instrument names.
- * Lookup::tex_glissando, Lookup::tex_bracket, (use texbeam.cc as an
- example.)
-
* Decent TeX titledefs (\tempo, \metron, etc. )
- * C meter iso 4/4
+ * lily \tempo
+
+ * C meter iso 4/4, idem for alla breve, etc.
* 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 spacing
- * midi output: eat-up dynamic, key/meter/tempo changes, and
-write them neatly
+ * LilyPond .deb. Other packaging methods?
- * LilyPond .deb
+ * detect -pipe
DOC
-
- * beam generation.
+ * Score_elem structure.
* all errors
+
+ * config of TeX macros
* a test suite
+ * hacking-HOWTO
+
FUTURE
- * Reg_configure_request
+ * auxilliary file for caching info.
- * bring Collision::do_pre_processing to haircutter
+ * Reg_configure_request
* slur parts as a script
* put scripts on bars
- * glissando
-
* guitar chord
- * Junk Staff_column, and find the requests while walking the Voices.?
-
- * MIDI repeat: make lily understand repeats
-
* 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
-
- * vertical spanner
-
IDEAS
+ * check out CORBA for Score_elems?
+
+ * derive PCol from Score_elem? More in Score_elems? Spacing?
* scoping in Lexer: do general id- assignments in mudela.
ID '=' EXPR;
- * integrate Register/Midi stuff
-
* create libmudela, or liblily_frontend
* move MIDI stuff (including Quantization) to a ANSI C libmidi library.
- * use an embedded language: scheme, lisp, S-lang, Perl, GUILE, ?
- for :
- - Items/Spanners
- - Registers
+ * use an embedded language: Python
+ for:
+ - Score_elems
+ - Engraver
+ - Translators
+ - Complex mudela?
* y -dims in internote?
- * hack up mf sources for decent spacing info (and then
- read TFM directly, for text too)
-
* 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.
+ * Spacing_request for manually adjusting spacing
* caching breakpoints
* 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 >
% --|--- --|---
(where "to" is a tiny bow)
+ * move towards incremental algorithms.
+
+ * design meta-language like TeX and Metafont
projects / lilypond.git / blobdiff