-
Notifications
You must be signed in to change notification settings - Fork 617
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Aggregate "TODO" list - or hopeful TODO listing as-is #543
Comments
In gtk we can do so via .move(). So this can perhaps work cross-platform too (no idea how this is Background explanation: I often start windows in the top-left area for simplicity, that way I can |
Two more todo entries (I had this from gtk but I think in most toolkits these work as-is too):
|
I just wanted to note that there are already aggregate TODO lists noted by @andlabs in the README as "Master Issues": Also, @andlabs clearly states in the README that he did not abandon the project: |
If I remember correctly that sentence was written some ~4 years ago (or more) and since then ... nothing really happened. |
@andlabs 's last commit was on Jan 2, 2021: https://github.com/andlabs/libui/commits/master |
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. |
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?).
The text was updated successfully, but these errors were encountered: