3 ms·
Many people have no problem using libui. There are even many bindings available that people use some of which have documentation. I was able to start using libu
by deorder 8y ago
Many people have no problem using libui. There are even many bindings available that people use some of which have documentation. I was able to start using libui instantly, but mostly because I already have experience using other GUI libraries.
People that know C should be able to read and understand the interface file at:
https://github.com/andlabs/libui/blob/master/ui.h https://github.com/andlabs/libui/blob/master/ui.h
The function / variable names are informative enough. There are examples which should get you started at:
https://github.com/andlabs/libui/tree/master/examples https://github.com/andlabs/libui/tree/master/examples
Even if they would add comments to the interface files (that may be used to generate docs), it will not add much value if it will become as follows:
// Set window title. First argument should be the window and the second the title as a string
uiWindowSetTitle(uiWindow *w, const char *title);
What I think is more important is adding tests etc. Tests can then also serve as a kind of documentation.
- loup-vaillant 8y ago> Tests can then also serve as a kind of documentation. They would have to be written with documentation in mind, which distracts them from their primary purpose: catching bugs. Trying to understand Monocypher from just its test suite¹ for instance would be a pretty bad idea. That test suite is top notch at catching bugs, but it sucks big time at documenting Monocypher. https://github.com/LoupVaillant/Monocypher/blob/master/tests/test.c https://github.com/LoupVaillant/Monocypher/blob/master/tests...