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/urg
- * use streambufs to provide IO handling for TeX stream, mudela stream,
-data-file.
+BUGS:
+ * c4 \! \> c4
- * seriously buffer TeX output (do profile of writing .5 mb TeX file.)
+ * tremolo stuff
- * strip EXEs before installing
+ * gallina barlines.
- * zip target for binary windows dist (JBR)
+ * fix height of / collisions with lyrics (chords),
+ see input/test/vertical-text.ly
- * repeat bars: need distance after ":|" and before "|:"
+ * repeat/volta:
+ - one volta spanner per score
+ - repeat bars span staffs
+ - placement alternative number
- * doco should not depend on a4
+ * who is trying to print too (small/big) piano braces all the time?
+ warning: piano brace too small (16.000pt)
- * text continuationss
+ * latex bla.tex broken (titles / \lilyfooter stuff?)
- * fix plain tex footer line.
+ * msgfmt -o check?
- * install TeX stuff into tex/generic directory.
+ * \breathmark TeX macro
- * preformatted .info stuff.
+ * configure error if GUILE 1.3 not found
- * percussion note heads
+ * configure error if no rtti (gcc 2.8 or egcs-1.1)
- * mi2mu empty staffs.
+ * catch GUILE errors?
+
+ * add new glyphs to font.ly
+
+ * formatting of input stuff.
+
+ * \notes{ a \< b \cr } vs \notes{ a \< b \! }
+
+ * if possible, it might be nice for a warning to appear if someone does
+ \translator with no name and without assigning it to an
+ identifier.
- * include MIDI list
+ * space after bars?
- * make separate translation property list.
+ * \type Voice \times 2/3 { [c8 c16 c16 c16 c16] }
- * make GNU style webpages.
+ * fix singleStaffBracket
+
+ * repeat bars: need distance after ":|" and before "|:"
+
+ * The time signature warnings still remain, will be fixed later.
+
+ Summary of minor spelling irregularities:
+ - capitalization/use of underscores in property names
+
+ * fix SkipBars -> skipBars
+
+ * \shape 1st dim skipped?
+
+ * fix marks/barnumbers/marginal notes
+
+ * broken scripts:
+ lbheel = \script { "bheel" 0 0 -1 0 0 }
+ rbheel = \script { "bheel" 0 0 1 0 0 }
+ lbtoe = \script { "btoe" 0 0 -1 0 0 }
+ rbtoe = \script { "btoe" 0 0 1 0 0 }
+ lfheel = \script { "fheel" 0 0 -1 0 0 }
+ rfheel = \script { "fheel" 0 0 1 0 0 }
+ lftoe = \script { "ftoe" 0 0 -1 0 0 }
+ rftoe = \script { "ftoe" 0 0 1 0 0 }
+
+ and also
+
+ portato= \script { "portato" 0 -1 0 1 0 }
- * There seems to be an install error in lilypond-1.0.0. Most of the
- files in the "init" directory don't get installed in the
- /usr/local/share/lilypond directory. The files installed are of
- the form feta*.ly. In particular init.ly doesn't get installed.
- I installed the files by hand and then the system seems to work.
+STUFF
+ * uniformise recent feta contributions.
+
+ * check out legal/(c) matters for scores.
+
+ * check out GCC signatures?
+
+ * Align_element::padding ?
+
+ * uniformise property names.
+
+ * ydirection <-> yDirection
+
+ * typo checks on property names?
+
+ * use streambufs and iostream
+ to provide IO handling for TeX stream, mudela stream, data-file.
+
+ * seriously buffer TeX output (do profile of writing .5 mb TeX file.)
+
+ * strip EXEs before installing
+
+ * zip target for binary windows dist (JBR)
+
+ * junking \skip req in lyrics
+
+ * Language:
+ - \type -> \context ?
+ - \translator -> ?
+ - fix \partial
+ - \bla {} vs \bla ;
+ - mix engraver hacking with music ?
+ - \once\property KEY = VAL
+ - \addtranslator, \removetranslator
+ - junk ^ and _ for scripts
+ - junk _ for lyrics.
+ - abstract grammar.
+
+ * percussion note heads
+
+ * mi2mu empty staffs.
* midi_instrument -> midiInstrument
* stable make/config stuff
- * stemup/stemdown; see test/updown.fly
- - check examples; add \type Staff hither and thether
-
* $DEPENDENCIES_OUTPUT support
- * use a fake-yodl.sh to mimick yodl when yodl is not installed
-
* fix BUGs
- * fix weird behaviour when .AFMs not found.
+ * fix weird behaviour when .AFMs/.SCMs not found.
- * Xdvi zooming ?!
+ * Xdvi zooming ?! Try to understand GS garbage collection.
gs: Error: /undefined in draw_beam
gs: Operand stack:
* fix vertical alignment and stafflines
- *GrandStaff needs more work -- I want a single word `harpsichord' to the
- left of the grandstaff, not one on each stave.
- (Organ staff -- with separate pedal -- but common properties may be
- something to think about. Of course for organ you want to be able
- to give stop indications on the way through, so the \property
- Voice.Instrument would be a stop, and \property
- GrandStaff.instrument would be PipeOrgan...)
-
+ * GrandStaff needs more work -- I want a single word
+ `harpsichord' to the left of the grandstaff, not one on each
+ stave. (Organ staff -- with separate pedal -- but common
+ properties may be something to think about. Of course for
+ organ you want to be able to give stop indications on the way
+ through, so the \property Voice.Instrument would be a stop,
+ and \property GrandStaff.instrument would be PipeOrgan...)
* make Tie_req a "command" { <c g> ~ <c g> }
- * bib ep1988
-
- * mix engraver hacking with music ?
-
* revise the Score_priority_align_engraver concept. It sucks.
- * ly2xdvi
-
* make new VoiceOne, VoiceTwo, VoiceThree contexts with
ydirection and hshift preset
* \cadenza , \meter, \grouping should all be \properties
* rename
- - plet -> tuplet
- measure -> bar
+ - abbrev -> tremolo
- abbreviation-beam -> (measured/unmeasured) tremolo
- partial -> anacrouse
- * libtoolize flowerlib
-
* shared lib
* robustify Beam (in case of no stems, 32nd notes)
* check for groff / troff/ nroff et
* more intelligent file searching
- - use kpsepath
- - make LilyPond fully relocatable
-
- * use kpsepath to find all TeX dirs
- - configure.in
- - clean-fonts.sh
+ - make LilyPond RPM fully relocatable
* nicen examples:
- break-up heavily-nested score blocks
* handle ^C for tmp/file creation.
+
* dots & rest collisions.
* documentation
* clefs (AG): The "8" should appear closer to the actual clef,
touching it.
- * scoping for properties?
-
- { c4
- \multi 2 < { \stemup .. } { \stemdown .. } >
- c2
- }
-
- this modifies \stem for the c2
-
* put errorlevel in Input class
* junk nesting slurs
* integrate midi-elts from mi2mu and lily?
- * cautionary accidental
-
* score-bar-scripts
FMR: Free memory read:
* This is occurring while in:
3RD PARTY BUGS:
- * redhat (v?) graphical install bomb-out?
-
- * egcs-1.03 ice: stem.cc:327; should localize bug (mine's still 10K)
-
- * gcc 2.8.1: see ice and RESIZE_ICE
+ * make GCC warn about ctor that leaves member vars uninitialised.
- * xdvi: PS in magnifying glass.
-
- * GNU patch 2.1: hardcoded limit of 1024 to the linelength
+ * redhat (v?) graphical install bomb-out?
* GNU diff 2.7: diff -rN does not see a new directory with empty file
* GNU indent: handle C++
- * GNU make: move hardcoded builtin rules to runtime ?
-
* GNU patch
- - rewrite ? -> check out GNU patch 2.5
- 'double-fix' mode: ignore identical fix, rather than suggest
to revert patch direction when (more or less? exactly) the same
thing is fixed
- indentation
- notenames?
- fontlock: \melodic \melodic
-
* use properties for:
- - Text_style
- - default_octave
- plet?
- Staff_sym size
- default tempo.
- font size
- bartypes (get rid of derived Span_bar_engravers)
- cadenza mode?
- - MIDI instrument
- - staff title
* page handling:
- PS output
* Spring_spacer:
- write a faster Spring_spacer (without matrices if possible)
- - use straight LP to find minimal "fitting force"
- relate energybound to linelen unitspace fontsize etc.
- - used fixed point fp
+ - used fixed point fp?
* \header
- output header info to MIDI too.
- * Add mudela-output to Rosegarden. (contact Derek Wyatt)
-
* a musical dictionary. See Documentation/vocabulary-*, other
languages:
- - explanation
+ - explanations
- italian
- german
- dutch
.. ?
* chords
- - guitar chords
- - chord names
+ - jazz style inversions C/E => <e g c>
+ - guitar chords (fret diagrams)
+ - other chord name styles (american(?) style)
- basso continuo
- - Syntax/parser
- MIDI output?
- - typesetting
* Debug logs:
- derive lily_stream, Dstream, texstream from ostream?
* add to MIDI output:
- tempo change
- ornaments (and trills?)
- - repeat
+ - repeat/volta
- slurs
- accents
- dynamics
- Move all Score_elems, into libmutype.a
- SGML
-
* Documentation
- Doc (C) stuff of sheet music
- a better format? SGML? TeX? Info?
- - a tutorial
+ - a better tutorial
* more spanners (smallish)
- Glissando
- use plet grouping
- separate visual from rhythmic info even more
- beams over bars
- - endbeam req should be *after* the duration, so you can do
- < { [c4] }
- { c8. c16 } >
-
* lines:
- Ledger lines, should be separate item: Ledger_lines, Ledger_lines
* Keys:
- merge key{item} & localkey{item}?
- - Major/Minor
- spacing, national styles?
* Support for TAB
* relative mode for pitch entering
- * bracket: volta 1,2
-
* configure pitch_byte
* rest name configurable
* write Dynamic_line (to group dynamics horizontally)
* use Real for all y positions.
- - use translate_axis( .. ,Y_AXIS)
+ - use translate_axis( .. ,Y_AXIS) iso separate variables.
* half-sharps, half-flats
* centered whole rest
- * qtor, btor, mtor-> tor( QUIET_ver ), tor( DEBUG_ver ), etc.
- - use tors feature in lily (?)
-
* declare notenametab?
* midi esp.: use I32 iso int where 32 bits are needed (or assumed...)
* Flower types:
- A decent scalar type
- - String hash
- - Pointer hash
-
- * binsearch/hash for identifiers
* stafftypes: voice names/ instrument names.
* textspanner: center position
- * Brackets
-
-
- % toe to bheel four to five
+ * % toe to bheel four to five
% ^_u 4_5
% -
% --|x-- --|x--
* revise calcideal
- * volta
-
IDEAS
-
* Output data structures of Mudela in XML/SGML.
* create libmudela, or liblily_frontend
* move MIDI stuff (including Quantization) to a ANSI C libmidi library.
* use an embedded language: Python, Scheme
- for:
+ for:
- Score_elems
- Translators
* caching breakpoints
- * breath marks
-
* used fixedpoint arithmetic for min. energy.
* move towards incremental algorithms.
* versioning stuff (cvt mudela, mudela, etc.)
- * padded vertical alignment (rods for vertical placement)
-
- * use String iso Text_def for lyrics.
-
* Klavarskribo?
- * lyrics in chords still fuck up.
-
- * Use hooks/dependency graphs for properties
+ * dynamic loading of engravers?
+
+SMOBS:
+
+****************************************
+Han-Wen Nienhuys <hanwen@cs.uu.nl> writes:
+
+> mcmanus@IDT.NET writes:
+> > > I want different C++ objects (with scheme embedded) to be linked by
+> > > C++ pointers. I want to access these other objects from the Scheme
+> > > code, and I want access to these pointers from C++.
+> >
+> > You can do this with a combination of smob's and primitive functions,
+> > though it may not be be exactly what you wanted. You would have one
+> > smob for each class in your application, and then you would write a
+> > primitive function that would return the objects that are linked to a
+> > base object.
+>
+> And the smob and the C++ class are interlinked? Like
+>
+> class Foo_class {
+> Foo_smob *smob_ptr_;
+> }
+>
+> struct Foo_smob {
+> Foo_class *class_ptr_
+> }
+
+Usually you can get away without having this interlinked structure.
+One piece of information you need when exporting objects to scheme is
+the smob tag for your class. You might store this value (a long) into
+a class static variable, or a file static variable. I'll use a class
+static variable in this example.
+
+I typically use code that works like this (untested code ahead):
+
+class Foo_class {
+ static long *Foo_smob_tag;
+ SCM obj; // representation as a scheme object, description comes later
+}
+
+// call this once on startup
+void init_Foo_class {
+ static scm_smobfuns type_rec;
+
+ type_rec.mark = foo_mark;
+ type_rec.free = foo_free;
+ type_rec.print = foo_display;
+ type_rec.equalp = 0;
+ Foo_class::Foo_smob_tag = new int(scm_new_smob(type_rec));
+}
+
+When you want to export an object to scheme, you put a pointer to the
+object itself in the cdr of the cell, and the tag in the car of the
+cell. The code looks like this:
+
+// Is this a Foo?
+static int
+foo_p(SCM obj)
+{
+ return(SCM_NIMP(obj) && SCM_CAR(obj) == Foo_class::Foo_smob_tag);
+}
+
+// given a Scheme representation, return, a C++ representation
+static Foo_class *
+foo_unbox(SCM obj)
+{
+ return((Foo_class*)SCM_CDR(obj));
+}
+
+// the SCM representation of the object is stored inside itself
+// this will become useful when destructor gets called
+static SCM
+foo_box(Foo_class *foo)
+{
+ SCM_DEFER_INTS;
+ SCM_NEWCELL(foo->obj);
+ SCM_SETCAR(foo->obj, Foo_class::Foo_smob_tag);
+ SCM_SETCDR(foo->obj, (SCM)foo);
+ SCM_ALLOW_INTS;
+ return foo->obj;
+}
+
+> C++ determines life time, so what is the strategy?
+
+What happens now when the destructor gets called? Lets set the cdr to
+NULL, and then check for that in all of the primitive functions that
+use your smob. We'll call this notion 'live'; a scheme object is
+'live' if the C++ representation still exists, it's dead if the C++
+object is gone. You can still have references to dead objects in
+scheme code; it's just an error to use them. This idea is stolen from
+Emacs's handling of buffers ('buffer-live-p' and friends).
+
+Add another function, foo_live_p:
+
+static int
+foo_live_p(SCM obj)
+{
+ return(foo_p(obj) && SCM_CDR(obj) != NULL);
+}
+
+In you destructor, you need to do:
+
+~Foo_class()
+{
+ SCM_CDR(this->obj, NULL);
+}
+
+When writing new primitives, now just check foo_live_p().
+
+I hope the above helps,
+
+-russ
+
+
+--
+"Even if you are on the right track, you'll get run over
+if you just sit there."
+ --Will Rogers (1879-1935)
+
+***************************
projects / lilypond.git / blobdiff