petabyt
commented
6 days ago If libui-ng gets any changes (it hasn't in 6 months, I think it won't get any for a while longer) then I'll merge it here.
I'm not gonna merge any of this into libui-ng myself. The owner seems to only login every few months, and a handful of PRs have been waiting years to be merged. That seems like a dead end so I'm working on my own fork.
I'm also willing to change the API a little bit (as long as the changes are well documented) in ways that libui-ng may find unacceptable
Yes definitely the readme should be improved. A lot of stuff should be written up, including better documentation.
To anybody reading this, if anybody who wants to help out I can give you write access to this repo.
Hey there petabyt,
Great to see enthusiasm for the libui-family here.
You are currently providing an overview of changes made via libui-dev here at the main README:
https://github.com/petabyt/libui-dev
such as:
"Tooltips (266)"
Having an overview is great and very useful, because people can refer to what is different quickly.
Right now it is a tiny bit confusing in that it seems not ordered or sorted in a specific manner. For instance:
Tooltips (266) Placeholders (224) Fix uiWindowSetContentSize (https://github.com/libui-ng/libui-ng/pull/261)
This has issues 266, then 224 and then 261. It is also not sorted alphabetically either, e. g. first there is T, then P, then F.
Of course it is up to you if you would like to keep that sorted in any way, but perhaps it could be sorted in some way? Be it alphabetically, or by #issue number.
Irrespective of this, perhaps the main README could also briefly explain which changes may be applicable for libui-dev and which ones won't? I assume not all issues may be applicable or contain code that can be integrated, so perhaps a recommendation on the main README what people should do in this case (e. g. send pull requests to libui-ng and then you decide if this is applicable to libui-dev; by the way I think many right now don't know about libui-dev, I only found it indirectly via kojix2, and of course now I wonder whether the changes made to libui-dev are also taken up by kojix2' ruby bindings, but that's naturally a question for kojix2 rather than you).
Please feel free to close this issue here at any moment in time.