Re: Doc: Grobs without printed output on their own

[James]

On 07/09/14 15:18, Simon Albrecht wrote:
> Hello,
> 
> as suggested by James, I come up with a suggestion on how to clarify the
> meaning of DynamicLineSpanner and similar.
> 
> 1. In
> <http://lilypond.org/doc/v2.19/Documentation/learning/objects-and-interfaces>,
> insert the following after the fourth paragraph:
> “What’s more, there are ‘abstract’ grobs which don’t print anything of
> their own, but rather collect, position and manage other grobs. Common
> examples for this are DynamicLineSpanner, BreakAlignment, NoteColumn,
> VerticalAxisGroup, NonMusicalPaperColumn and similar. We’ll see how some
> of these are used later.”

This has been added as

http://code.google.com/p/lilypond/issues/detail?id=4137

Thanks


> 
> Other than that, I have no striking ideas on where to add information,
> especially in the NR. A table in the A.x attachment part wouldn’t be the
> right thing.
> And subdividing IR 3.1 into ‘printing grobs’ and ‘abstract grobs’ would
> require major redesign, which is probably unnecessary.
> So, just another idea of mine. I hope you don’t mind if I continue to
> post some thoughts which come to my mind. I know they are eccentrical
> and far from implementation reality sometimes and do not intend but to
> propose them to your judgement :-)


Just curious why it matters, or what is gained if a grob is documented
whether it 'prints' ouput or not, if the actual behaviour of what the
grob does is documented (i.e. in the IR).

James