I know that it says on the README that documentation isn't ready yet, but I really want to use this tool as it is right now. Can you please please please provide at least some documentation on the most essential parts of LibUI so we don't have to fish through a C header file for a function?
hanyuone
All 3 comments
@andlabs If down the line you have documentation drafts that you feel need looking over (or polishing), I'd gladly offer my help. Unfortunately, I currently don't know enough about the innards of libui to write items from scratch.
I really like the idea behind this project.
adrian5
on 25 Dec 2017
I've started adding API reference documentation into ui.h
in my docs branch.
I've been pulling comments over from the equivalent godoc comments in the golang bindings, adding C-specific info where relevant.
@andlabs: let me know if this is useful - if so I'll push on and do the rest of the calls.
bcampbell
on 7 Jan 2018
Merged with #317.
andlabs
on 25 Mar 2018
Related issues
flying-sheep
路
16Comments
andlabs
路
9Comments
amar-laksh
路
4Comments
parro-it
路
15Comments
ctoth
路
9Comments
Most helpful comment
I've started adding API reference documentation into ui.h
in my docs branch.
I've been pulling comments over from the equivalent godoc comments in the golang bindings, adding C-specific info where relevant.
@andlabs: let me know if this is useful - if so I'll push on and do the rest of the calls.