API to get layout data from LilyPond

> First of all, I don't want to steer the discussion away from
> Werner's original question.

Actually, you do. :-)

> I'd just like to share a few thoughts in the hope that they might
> inspire a broader discussion.

Always start a new thread for a new topic.

> As far as I understand, formats such as MEI (and perhaps Finale
> internally) are able to preserve not only the musical semantics but
> also layout information. This made me wonder whether it would be
> useful for LilyPond to expose the final layout of each Grob after
> the layout process through a stable rendering cache or API.

I'm not a Scheme expert but I think all of this is already available.
You could, for example, extend Tina's MusicXML generator to output
such information, too.

> Perhaps Point-and-Click already computes or stores much of this
> information internally. If so, would it make sense to expose it
> through a stable interface?

Please explain how such a 'stable interface' should look like.


    Werner