andlabs/libui

Aggregate "TODO" list - or hopeful TODO listing as-is

rubyFeedback opened this issue · 8 comments

I am not sure whether andlabs has enough time/motivation/incentive for libui, but I was thinking that perhaps one day libui may be picked up again, be it by andlabs or others or a team. So I was thinking that it may be nice to have an "aggregate TODO" list, as overview. Things that would be nice to implement and add.

I invite folks to add suggestions. My personal recommendation would be to ideally focus on things that could be easily implemented.

Feel free to use this in any way as you see fit. If you already have made a proposal years ago, and want to remind that this may still be useful, then perhaps just add it here, and a link to the discussion or issue as such, as an additional pointer (if this here can remain open for a bit longer, say, a year or two years at least?).

  • Make it possible to specify WHERE the main window is on the screen, e. g. its top-left position.

In gtk we can do so via .move(). So this can perhaps work cross-platform too (no idea how this is
done on the windows UI).

Background explanation: I often start windows in the top-left area for simplicity, that way I can
quickly find it, in particular when I have lots of windows open at the same time.

Two more todo entries (I had this from gtk but I think in most toolkits these work as-is too):

  • Tooltip on buttons: Something that briefly explains to the user
    how a button may be used, such as the main point of having this
    button or what this button does, before the user clicks on it.

  • Mnemonics on buttons: be able to use a shortcut combination such
    as "ctrl+k" to activate a button's action. This may also be called
    accelerators. I know these work on gtk, but no idea whether these work
    on windows and OSX.

I just wanted to note that there are already aggregate TODO lists noted by @andlabs in the README as "Master Issues":
https://github.com/andlabs/libui/issues?utf8=%E2%9C%93&q=master+in%3Atitle+is%3Aissue+is%3Aopen

Also, @andlabs clearly states in the README that he did not abandon the project:
"But libui is not dead; I am working on it whenever I can, and I hope to get it to a point of real quality soon!"

Also, @andlabs clearly states in the README that he did not abandon the project:
"But libui is not dead; I am working on it whenever I can, and I hope to get it to a point of real quality soon!"

If I remember correctly that sentence was written some ~4 years ago (or more) and since then ... nothing really happened.

Also, @andlabs's last commit to the new remodel branch was on Dec 31, 2020: https://github.com/andlabs/libui/commits/remodel

So, your points is that ... the project is alive?

Essentially. Atleast to the point that it hasn't been 4 years.