Re: convert-ly rule

[David Kastrup]

"address@hidden" <address@hidden> writes:

> On 13 mars 2013, at 11:00, David Kastrup <address@hidden> wrote:
>
>> It might also be possible to let a callback check for the existing
>> grob interfaces in possible cases of contention and only use the
>> respective value if the grob had the proper interface.
>> 
>> So you'd have a callback that only looked at staff-padding in the
>> tuplet-bracking-interface manner if the grob had that interface, and
>> would look at it in the side-position-interface manner only if the
>> grob had _that_ interface.
>> 
>> That would require giving grobs a set of interfaces that interpret
>> any given property only in one manner.
>
> Then that would mean that the tuplet bracket could never use side
> position interface and vice versa.

Yes.  The set of interfaces is not user-changeable as far as I know.  So
this would hamper the system programmers regarding the possible
interface choices rather than the users.

Not fabulous, but I have a hard time at the current point of time coming
up with something that does not either have significant naming
redundancy and awkwardness, or is lacking flexibility.  At least when it
is supposed to fit more or less with the current scheme of things.

-- 
David Kastrup