[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Lilypond-auto] Issue 4438 in lilypond: Internals Reference: add siz
From: |
lilypond |
Subject: |
Re: [Lilypond-auto] Issue 4438 in lilypond: Internals Reference: add size to the properties of Fretboards |
Date: |
Mon, 08 Jun 2015 12:21:30 +0000 |
Comment #1 on issue 4438 by address@hidden: Internals Reference: add size to
the properties of Fretboards
https://code.google.com/p/lilypond/issues/detail?id=4438
At the bottom of the manual entry you can read:
This object supports the following interface(s): chord-name-interface,
font-interface, fret-diagram-interface, grob-interface, item-interface,
outside-staff-interface and rhythmic-grob-interface.
You'll find "size" in
http://lilypond.org/doc/v2.19/Documentation/internals/fret_002ddiagram_002dinterface
Now fret-diagram-interface is only used in FretBoard. Whether or not size
should be separately documented in FretBoard depends on whether its meaning
significantly diverges from that of other properties.
The documentation for "size" states:
size (number)
Size of object, relative to standard size.
which is a fairly generic description not specific to fret boards.
Indeed, "instrument-specific-markup-interface" (which is only used
in "TextScript", huh) carries it as well.
instrument-specific-markup-interface has enough similarity with
fret-diagram-interface that one seriously has to question the overall
design and distribution of properties across interfaces here.
So I'm not sure that adding a redundant description (or default setting) of
size to FretBoard is the most reasonable remedy to the perceived
inconsistency. Maybe reorganizing interfaces, possibly adding
instrument-specific-markup-interface to Fretboard and retaining only those
properties not covered by instrument-specific-markup-interface in
fret-diagram-interface, would be the better choice.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings