Closed jjceresa closed 3 years ago
Consulting Player API, we got this display:
Lifecycle Functions for MIDI Player_linebr@{
Hm, the API docs are messed up. The sub grouping is completely wrong.
@derselbst Has something changed in the way we build the API docs?
Has something changed in the way we build the API docs?
Not that I knew of. But it's obviously completely broken :(
I think now it's time to figure out how to get that GitHub Actions artifact downloaded with a shell script, so that we can provide it to Josh.
The output from the latest API doc build action looks fine: https://github.com/FluidSynth/fluidsynth/actions/runs/389192187
So maybe the doxygen version has changed on Joshs server?
I think now it's time to figure out how to get that GitHub Actions artifact downloaded with a shell script, so that we can provide it to Josh.
Good idea. I've written a small Python tool to help with the download: https://github.com/mawe42/github-artifact-download
Better than shell and some extra dependencies, I think. Only Python 3 is required, nothing else.
The sub grouping is completely wrong
No, a lot of sub groups are well placed.
The API reference
tree is really efficient. It help me to find the player API quickly.
I've written a small Python tool to help with the download
Oh, you are already done. Very nice! I'll contact Josh.
Using recent XML API documentation. I suggest following change.
On menu API reference. 1)
Effect-Reverb, Effect-Chorus
sub group seem misplaced. They should be placed in sub group ofSynthesizer
, at the same level thatEffect - LADSPA
.2)
MIDI Player
sub group should be moved at the same level thatMIDI sequencer
and should be namedMIDI file player
.Again, many thanks to Marcus for this new efficient documentation.