On Fri, Dec 13, 2024 at 4:30 PM David Kastrup <d...@gnu.org> wrote:
> Trevor Bača <trevorb...@gmail.com> writes: > > > On Fri, Dec 13, 2024 at 3:46 PM David Kastrup <d...@gnu.org> wrote: > >> > >> Why would you want to list a property that has no effect on a grob? > >> > > > > David, please go look at the IR 3.1 entry for TupletBracket ... > > > > https://lilypond.org/doc/v2.24/Documentation/internals/tupletbracket > > > > ... and tell me where on that page users learn that they have the ability > > to override the color of a tuplet bracket to red. > > > > Go ahead. Where is that information provided? > > This is the last answer I will provide to this thread since I am sick of > the insinuation that the documentation of LilyPond is intended to annoy > people. > > Can you please try not to switch the topic around with every post? > First you complain that not every property of a grob is listed. Then > you complain that not every property having an effect is listed. > > Then you post dares in order to show that I am talking BS. > > So let us take the path here: the bottom of that page says > > This object supports the following interface(s): grob-interface, > line-interface, outside-staff-interface, spanner-interface and > tuplet-bracket-interface. > > If you click on grob-interface, you get a long explanation of what > constitutes a grob, followed by a list of user-settable properties > including > > color (color) > > The color of this grob. > > That an interface has properties does not mean that all of the > properties will be effective on all grobs having the interface. You > think you can come up with a better way of autogenerating LilyPond's > documentation, but all you come up with is essentially "someone™ should > write and maintain a better version of all the internal documentation > manually". > > The way to achieve this is to volunteer, not to complain. But even then > it would be a maintainability nightmare. We autogenerate the internals > documentation for a reason. It is at least accurate. > I'm sorry, I may be misunderstanding, but I don't see an answer to the question I asked you. I asked **where on the page** in the API entry for TupletBracket does a user learn that she or he can change the color of a tuplet bracket? The answer to that question is: nowhere on the TupletBracket page. Finding that information involves clicking, in a frustrating way, through interface links at the bottom of the page, hoping to maybe find what you need. Please calm down enough to read this: it is entirely reasonable for users to come to an API entry -- for any piece of software whatever -- that details a class, object or component and ask "what are all the properties that I can change here?" The way that IR 3.1 details all 163 grobs in LilyPond fails to do this. This isn't your fault. This isn't anyone's fault. But it is definitely a huge insufficiency in LilyPond's documentation. You do see that, yes? -- Trevor Bača www.trevorbaca.com soundcloud.com/trevorbaca
