-Features you cannot find in the doco as working, should be mentioned here.
+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
+
+ * decimal point in \paper {}
+
+ > I have changed Mark_engraver to use the G_... classes.
+ > My implementation has the following shortcomings at the
+ > moment.
+ >
+ > - markScriptPadding is not supported, since G_staff_side_item does not
+ > support padding.
+ >
+ > - markBreakPriority is not supported.
+ >
+ > - Mostly, you want the marks aligned with the bar lines. I don't
+ > really understand how to implement that feature.
+ >
+ > - You get lots of warnings about missing 'number' and 'Large'
+
+
+ *{ \voiceone <a'4.*2/3 d''4.*2/3 fis''4.*2/3> [g''8 fis'' e''] d''4 |}
+ and=20
+ { \voicetwo d'4 d'2.*2/3 } spacing
+
+ * tied notes for MIDI
+
+ * sharp /flat on trills (in MIDI ??)
+
+ * scm-ify \property values.
+- The direction of textual scripts ('^' or '_') is ignored.
+ * move class Lookup {} into scm
+
+ * read tfms too.
+
+ * update mi2mu for lilypond 1.1
+
BUGS:
+ * collisions/voices \voiceone \voicetwo are broken; see
+ input/praeludium-fuga-E.ly
+ mutopia/J.S.Bach/wtk1-fugue2.ly
+
+ * fix: standchen.
+
+ * fix: cello suites
+
+ * fix: text on rests: rediculous dims
+
+ * fix extender
+
+ * fix fingering 'a-5': font direction broken *again*
+
+ * fix braces
+
+ * multibar rests: SkipBars=0
+
+ * ly2dvi barfs on linewidth = -1.
+
+ * fix midi output.
+
+ * turn slope-damping on/off
+
+ * c4 \! \> c4
+
+ * tremolo stuff
+
* gallina barlines.
* fix height of / collisions with lyrics (chords),
- see input/test/vertical-text.ly
+ see input/test/vertical-text.ly; input/test/repeat.ly
* repeat/volta:
- one volta spanner per score
- repeat bars span staffs
- placement alternative number
- * who is trying to print too (small/big) piano braces all the time?
- warning: piano brace too small (16.000pt)
-
* latex bla.tex broken (titles / \lilyfooter stuff?)
+ * check/set minimum slur/tie length
+
* msgfmt -o check?
* \breathmark TeX macro
- * configure error if GUILE 1.3 not found
-
- * configure error if no rtti (gcc 2.8 or egcs-1.1)
-
* catch GUILE errors?
* add new glyphs to font.ly
* space after bars?
+ * 'hinterfleisch' before bar (e.g. wtk1-fugue2)?
+
* \type Voice \times 2/3 { [c8 c16 c16 c16 c16] }
* 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
* check out legal/(c) matters for scores.
- * move option processing out of gh_enter
-
* check out GCC signatures?
* Align_element::padding ?
* typo checks on property names?
- * --safe: disallow backslashes
-
* use streambufs and iostream
to provide IO handling for TeX stream, mudela stream, data-file.
* zip target for binary windows dist (JBR)
- * revise documentation
-
* junking \skip req in lyrics
* Language:
* mi2mu empty staffs.
- * include MIDI list
-
* midi_instrument -> midiInstrument
* horizontal centering of dynamics
* 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 ?! Try to understand GS garbage collection.
gs: Error: /undefined in draw_beam
gs: Operand stack:
- * run texhash after installing .tex
-
* fix vertical alignment and stafflines
* GrandStaff needs more work -- I want a single word
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
-
* revise the Score_priority_align_engraver concept. It sucks.
- * ly2xdvi, ly2ps
-
* make new VoiceOne, VoiceTwo, VoiceThree contexts with
ydirection and hshift preset
* fix audio-items (don't use (input) requests, but copy data)
- * junk My_lily_parser::abbrev_beam_type_i_
-
* make sure all ex's have a mudela-version
* do rest-collisions for Multi_measure_rests as well.
* deps for ly2dvi
- * clean up abbrev/plet/beam/abbrevbeam/duration mess in parser.
-
* minimum length second part broken tie
* en-,discouraged linebreaking:
* \cadenza , \meter, \grouping should all be \properties
* rename
- - plet -> tuplet
- measure -> bar
- abbrev -> tremolo
- abbreviation-beam -> (measured/unmeasured) tremolo
* handle ^C for tmp/file creation.
+
* dots & rest collisions.
* documentation
.. ?
* chords
- - jazz style inversions C/E => <e g c>
- guitar chords (fret diagrams)
- other chord name styles (american(?) style)
- basso continuo
- 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
* handle EOF graciously in error messages.
- * centered whole rest
-
* declare notenametab?
* midi esp.: use I32 iso int where 32 bits are needed (or assumed...)
- * Flower types:
- - A decent scalar type
-
- * binsearch/hash for identifiers
-
* stafftypes: voice names/ instrument names.
* lily \tempo
* 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