[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH] Porrectus: second try

From: Han-Wen Nienhuys
Subject: Re: [PATCH] Porrectus: second try
Date: Thu, 20 Sep 2001 17:00:09 +0200

address@hidden writes:
> > address@hidden writes:
> > > * New porrectus properties: porrectus-width, line-thickness.
> > 
> > Please use simply "width" and "thickness" we want to keep the number
> > of variables down.

oops, misread that one. line-thickness is ok. porrectus-width not.

> I had a look at grob-property-description.scm.  It already contains both,
> thickness and line-thickness.  Semantically, line-thickness matches
> exactly:
> (grob-property-description 'line-thickness number? "the
> thickness[stafflinethickness] of the line.")
> More important, it might be provident to reserve property name thickness
> for the thickness of the porrectus shape.
> Regarding use of the term width, grob-property-descriptions.scm contains
> arch-width, beam-width, bracket-thick for system start bracket width,
> flag-width-function, minimum-width reserved for use in context of rests
> only, note-width. But, currently, there is no property width defined in
> grob-property-descriptions.scm.

The system start bracket is a special case, in that it is a bug,
awaiting rewriting.

> > note that prefix syntax is not necessary per se, since you can parse
> > the first note and the following \~ as a single syntactical construct
> > and internally switch the order of the two.
> > 
> Theoretically, of course.  But, in practice, I guess this would mean to
> restructure quite a lot of the parser, since there may be yet other
> syntactical constructs between the first note and the following \~ that
> also would have to be regarded.

No, it is not really complex. ( (slur start) also follows the
note, but happens at the same time as the note. 


Han-Wen Nienhuys   |   address@hidden    |

reply via email to

[Prev in Thread] Current Thread [Next in Thread]