I noticed that the master branch hasn't been updated since Dec 2, 2016. Does it mean that libui is dead / no longer maintained or did you achieve the state of the API that no longer needs any updates?
I want to use libui in one of my projects but am concerned because neither libui nor some of it's bindings to other languages have been updated since December of last year.
I hope not, because libui could be my only solution. And Gunnar just released an update of his Lua bindings https://hg.tset.de/public/lui/rev/7e6d577f160d
I am working on individual feature branches now, not master. Admittedly I haven't been very productive lately, though...
@andlabs Have you considered accepting donations through a platform such as Open Collective?
I think there is high demand for a library such as libui to exist, if it gained some traction maybe that could allow you to dedicate more time on this.
@lukechilds is also have not found any other library like libui. It has the potential to be something great maybe even a de-facto standard. If you want something big, nowadays you would chose Qt I guess, but if you want something small and simple then libui is probably the one. Am I wrong?
There is IUP which has a lovely support, so there would be an alternative for C GUIs. However, I sure do hope that libui won't die soon.
I suppose the problem is not money but time, so it would probably make more sense to contribute code instead of collecting donations.
@andlabs Is there any current work we could help with?
As far as I know IUP does not support macOS with native Cocoa but GTK instead. But libui does that, doesn't it?
That is correct, although native macOS support is on their ToDo list.
Admittedly I've been lazy and with low motivation recently. I'll try to continue tomorrow or sometime in the next few days or something... I'm almost done with the new text drawing stuff, at least.
Admittedly I've been lazy
@andlabs Always remember, with OSS you don't owe anyone anything.
I'd recommend to find someone or a couple of others to help you out. Working in a team doesn't always make things easier, but it may allow to spread the work. For example just taking someone knowledgeable of the lib to clean up the existing PR list or go through and checking the various issues.
Keep it up!
@andlabs I'm still here to help!
Right. I'll get to merging the PRs once I finish the utflib-and-attrstr branch, because it's going to be a significant, backwards-incompatible API change. That being said, I still accept peoples's contributions, though for future contributions I did start a contribution guidelines page in said branch.
@andlabs
Based on the number of outstanding pull requests I strongly encourage delegating management/merge responsibilities to someone with a proven track record so that you can focus on the the development aspects that most interest you.
i just found this library. Any update with this library?
@andlabs Is there any timeframe as to when the utflib-and-attrstr branch will be merged into master? (And then, another release?)
No. I work for a new company now, and I need copyright clearance from them before I can continue writing code (unless I want to assign copyright for the new code to them). Sorry. Of course, once I do get that, I will push out the "alpha 3.5" patch idea (which is just master + #202) and continue working on utflib-and-attrstr, which is presently having a final cleanup phase of its current feature set (which will be sufficient for a merge, but not ideal, but I want to get other stuff done too).
libui is decidedly not dead, though. I have a lot of momentum built up, and a mental roadmap for development in 2018 :)
Enjoy your new job!
Clearance obtained. Let's get busy again.
Thanks for the update on the copyright clearance!! 馃憤 It's fantastic news!
Is there a widget for like GtkTreeView both for treestore and liststore?
It is WIP. Anyway, this particular topic is resolved.
Most helpful comment
I am working on individual feature branches now, not master. Admittedly I haven't been very productive lately, though...