Opened 21 months ago
Last modified 20 months ago
#18312 new task
api docs: BGradient doc missing
Reported by: | nephele | Owned by: | nielx |
---|---|---|---|
Priority: | normal | Milestone: | Unscheduled |
Component: | Documentation | Version: | |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Platform: | All |
Description
This seems to already have doxygen files backing it, but they don't seem to correspond to any page for BGradient.
Change History (3)
comment:1 by , 21 months ago
comment:2 by , 20 months ago
Generally, I mark any APIs as private when they are in the BPrivate namespace. For BGradient, this is not the case, but the comment at the top of the file seemed to indicate that this is internal.
There is no rule against documenting it, so feel free to provide patches. We can also discuss whether it should be stabilized, but that goes beyond this documentation ticket.
comment:3 by , 20 months ago
If we document it, a warning should be added in the documentation that it is not part of the stable API. As with many of the "private" classes, this gets some use in 3rd party applications and it is difficult, or at least annoying, to write code that does not use it when you want a gradient.
Ideally the code would be shipped in a static library, but in the case of BGradient, the tight coupling with BView makes it difficult to do so. So indeed, people should be even more careful here than they should be with private classes that are in separate libraries.
Replying to nephele:
Those are marked as INTERNAL, so not generated by default. And then they are basically placeholders with "Undocumented", so despite having the files, they still have no content.