Update readme

Signed-off-by: falkTX <[email protected]>

.editorconfig

@@ -6,3 +6,6 @@ indent_size = 4
 indent_style = space
 insert_final_newline = 1
 trim_trailing_whitespace = 1
+
+[README.md]
+trim_trailing_whitespace = 0

README.md

@@ -1,15 +1,69 @@
-# DPF Widgets 
-## Official and Community made reusable GUI widgets for DPF
+# DPF Widgets
+## Official and Community made reusable GUI widgets for [DPF](https://github.com/DISTRHO/DPF/)
 
-This is a repository for shared GUI widgets targetting DPF.
-Very much work in progress! Do not use right now unless you plan to contribute some yourself.
+This is a repository for shared GUI widgets targetting [DPF](https://github.com/DISTRHO/DPF/).
 
-Since DPF allows multiple backends (cairo, opengl or vulkan), we need to split them as such.
-Each folder provides widgets for its dedicated backend type.
-It is not mandatory that a widget is usable for more than 1 backend.
+Since [DPF](https://github.com/DISTRHO/DPF/) allows multiple backends (cairo, opengl or vulkan), we need to split them as such.  
+Each folder provides widgets for its dedicated backend type.  
+It is not mandatory that a widget is usable for more than 1 backend.  
 Generic widgets (those based on DPF core classes like Color, Rectangle, etc) are placed under the "generic" directory.
 
-### Rules and Layout
+## Status
+
+**generic / ResizeHandle**
+
+Resize handle for DPF windows, will sit on bottom-right.
+
+Works in both Cairo and OpenGL modes (classic/legacy OpenGL only, does not support OpenGL3 mode).
+
+Used very often and in many plugins.
+
+** opengl/Blendish **
+
+Blendish widgets for DPF.
+Work in progress, but mostly usable.
+
+Used in:
+
+- [AIDA-X](https://github.com/AidaDSP/AIDA-X/) (standalone options)
+
+** opengl/DearImGui **
+
+Exposes the [Dear ImGui](https://github.com/ocornut/imgui/) drawing API inside a DGL Widget.  
+The drawing function onDisplay() is implemented internally but a new onImGuiDisplay() needs to be overridden instead.  
+This class will take care of setting up ImGui for drawing, and also also user input, resizes and everything in between.
+
+Used in:
+
+- [dear-plugins](https://github.com/DISTRHO/dear-plugins)
+- [Ildaeil](https://github.com/DISTRHO/Ildaeil)
+- [master_me](https://github.com/trummerschlunk/master_me/) (histogram display)
+
+See [imgui-template-plugin](https://github.com/DISTRHO/imgui-template-plugin/) for a CMake-based template plugin project around ImGui,
+or [imgui-template-app](https://github.com/DISTRHO/imgui-template-app/) for a standalone application template.
+
+** opengl/DearImGuiColorTextEditor **
+
+Text Editor Widget class, based on [ImGuiColorTextEdit](https://github.com/BalazsJako/ImGuiColorTextEdit/).
+
+Used in:
+
+- [dear-plugins](https://github.com/DISTRHO/dear-plugins)
+
+** opengl/LVGL **
+
+Exposes the [LVGL](https://github.com/lvgl/lvgl) drawing API inside a DGL Widget.  
+This class will take care of setting up LVGL for drawing, and also also user input, resizes and everything in between.
+
+See [lvgl-template-plugin](https://github.com/DISTRHO/lvgl-template-plugin/) for a CMake-based template plugin project around LVGL.
+
+** opengl/Quantum **
+
+[Quanta](https://forum.cockos.com/showthread.php?t=269437)-inspired widgets for DPF.
+
+In use for [master_me](https://github.com/trummerschlunk/master_me/) project.
+
+## Rules and Layout
 
 Each widget MUST follow these rules:
 
@@ -21,7 +75,7 @@ Each widget MUST follow these rules:
  6. contain 0 or 1 implementation files, with cpp extension and same basename as the matching hpp file
  7. optionally contain extra files, directly included from the cpp file
  8. place any extra files under a directory with the same basename as the cpp file, minus the file extension
- 9. be self-contained, not needing externally installed dependencies (besides the locally available extra files defined in the previous point)
+ 9. try to be self-contained, not needing externally installed dependencies (besides the locally available extra files defined in the previous point)
 10. be contained within DGL_NAMESPACE
 11. have clear documentation specifying its use
 12. be cross-platform (win32 and posix)