Cool_Tools/imgui
1
0
Fork 0
mirror of https://github.com/ocornut/imgui.git synced 2025-02-26 06:48:26 +01:00
Code Releases Wiki Activity

Updated Funding (markdown)

omar 2024-03-17 20:33:52 +09:00
parent 95840f0a1e
commit f0aa503319
1 changed files with 8 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
Funding.md

@ -7,10 +7,14 @@ Dear ImGui has first been conceptualized and prototyped in 2012, first released
Dear ImGui in 2024 is incredibly more powerful and versatile than Dear ImGui was 2017. We are committed to keep improving the software while keeping it sane, optimal, flexible. Every engineering teams will benefit from it.
We are consistently doing R&D and sitting on unfinished features needing work.
We are answering [many community questions/issues](https://github.com/ocornut/imgui/issues?q=) in the open and in one centralized place in order to create a database of knowledge.
We have created a [test engine & test suite](https://github.com/ocornut/imgui_test_engine).
We are ensuring at every moment that the library is the most efficient it can be (with strict standards such as: 0 allocation on most frames).
We are designing easy and well-documented transition to updated APIs when changes are necessary.
We have answered [thousands of community questions/issues](https://github.com/ocornut/imgui/issues?q=) in the open and in one centralized place in order to create a database of knowledge.
We have created a [test engine & test suite](https://github.com/ocornut/imgui_test_engine) to test the library, minimize regressions, facilitate contributions and effectively contributes to documenting the code (pro-tip: if you are unsure what some code is for, disable it and run the test suite!).
We are ensuring at every moment that the library is the most efficient it can be (with strict standards aligning with the needs of game developers, such as: 0 allocation on most frames).
We are designing easy and well-documented transitions to updated APIs when changes are necessary, because code written by users often lives for years or decades.
But we can only keep doing that and move forward with continued support.