A concrete example of why Apple's documentation is terrible

Re:A concrete example of why Apple's documentation is terrible by malfist on Sunday January 07, 2024 @05:11PM (#38905689)

I agree with you. Everything this person is struggling with is well documented on the parent class. A basic understanding of OOP is all that's needed to use this documentation and this dialog.

Are they mad at Java docs? Or C# docs? Or any other OOP doc that follows the same pattern of not repeating the parent's documention on the subclass unless the subclass adds to it.

[ Parent | on HN ]

Re:A concrete example of why Apple's documentation is terrible by zastrowm on Sunday January 07, 2024 @06:46PM (#38906440)

The charitable view would be that they come from language/platform that does include the base-class's methods/apis.

Your example of dotnet/C# doesn't seem to be the best - DotNet/C# repeats the base documentation - for example the SaveFileDialog class [1] lists all of the methods but indicates when the methods come from the base class.

Flutter also seems to list inherited methods - for example the TextButton [2].

[1]: https://learn.microsoft.com/en-us/dotnet/api/system.windows....

[2]: https://api.flutter.dev/flutter/material/TextButton-class.ht...

[ Parent | on HN ]