lilypond-devel
[Top][All Lists]
Advanced

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

Re: convert-ly rule


From: David Kastrup
Subject: Re: convert-ly rule
Date: Wed, 13 Mar 2013 12:37:11 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux)

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

> On 13 mars 2013, at 11:56, David Kastrup <address@hidden> wrote:
>
>> "address@hidden" <address@hidden> writes:
>> 
>>> 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.
>
> Makes sense.
>
> In my work with eliminating the translate_axis call, then, I'd need to
> create an:
>
> outside-staff-interface
>
> For all grobs that can be positioned outside the staff.  That way
> TupletBracket could be part of this without having bleedover from the
> side-position-interface's use of staff-padding.  It'd require adding a
> new interface to a lot of grobs, but it actually adds a lot of
> clarity, as in the documentation we can indicate that the internals
> reference shows all grobs that can be outside-staff positioned via
> this interface.

This sounds like a plan.  It would mean copying/using the callbacks from
one grob into an another might not be sufficient to get the same
interpretation of some property if the grobs don't share the same
interfaces.

I think that is likely the best we can manage right now short of a
complete redesign.  It may restrict the flexibility of some grobs and/or
their design, but where "flexibility" means "it is unpredictable, but
this might or might not be made to do x, and possibly other side effects
will ensue", it is of dubious value anyway.

And of course it is also nice to be able to write acknowledgers that
will only get to hear about grobs with an outside-staff-interface.

-- 
David Kastrup



reply via email to

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