imgui VS lvgl

include(cmake/CPM.cmake) function(raylib_imgui_setup_dependencies) message(STATUS "Include Dear ImGui") FetchContent_Declare( ImGui GIT_REPOSITORY https://github.com/ocornut/imgui GIT_TAG 277ae93c41314ba5f4c7444f37c4319cdf07e8cf) # v1.90.4 FetchContent_MakeAvailable(ImGui) FetchContent_GetProperties(ImGui SOURCE_DIR IMGUI_DIR) add_library( imgui STATIC ${imgui_SOURCE_DIR}/imgui.cpp ${imgui_SOURCE_DIR}/imgui_draw.cpp ${imgui_SOURCE_DIR}/imgui_widgets.cpp ${imgui_SOURCE_DIR}/imgui_tables.cpp) target_include_directories(imgui INTERFACE ${imgui_SOURCE_DIR}) include(cmake/CPM.cmake) message(STATUS "Include dbg-macro") cpmaddpackage( "gh:sharkdp/dbg-macro#fb9976f410f8b29105818b20278cd0be0e853fe8" )# v0.5.1 message(STATUS "Include fmtlib") cpmaddpackage("gh:fmtlib/fmt#e69e5f977d458f2650bb346dadf2ad30c5320281" )# 10.x message(STATUS "Include raylib") cpmaddpackage("gh:raysan5/raylib#ae50bfa2cc569c0f8d5bc4315d39db64005b1b0" )# v5.0 message(STATUS "Include spdlog") cpmaddpackage("gh:gabime/spdlog#7c02e204c92545f869e2f04edaab1f19fe8b19fd" )# v1.13.0 message(STATUS "Include rlImGui") FetchContent_Declare( rlImGui GIT_REPOSITORY https://github.com/raylib-extras/rlImGui GIT_TAG d765c1ef3d37cf939f88aaa272a59a2713d654c9) FetchContent_MakeAvailable(rlImGui) FetchContent_GetProperties(rlImGui SOURCE_DIR RLIMGUI_DIR) add_library(rlimgui STATIC ${rlimgui_SOURCE_DIR}/rlImgui.cpp) target_link_libraries(rlimgui PRIVATE imgui raylib) target_include_directories(rlimgui INTERFACE ${rlimgui_SOURCE_DIR}) endfunction()

Immediate mode is a fuzzy concept, as witnessed by this writeup: https://github.com/ocornut/imgui/wiki/About-the-IMGUI-paradi...

It's fun to see the evolution in e.g. these examples of image loading for Dear Imgui:

https://github.com/ocornut/imgui/wiki/Image-Loading-and-Disp...

DirectX9 will even load the image for you, DirectX11 okay we get a few more structures to fill out, DirectX12 is where it goes off the rails and we are filling out a bunch of UNKNOWN DONT_CARE JUST_DO_IT. Then of course Vulkan is the one that gets the big fat "this probably won't actually work for you" warning.

I understand whats happening, but you know sometimes I just want to display a fucking image.

ImGui is engine/GPU agnostic

Themeing isn't a just a retained mode thing, you can do wonders with immediate UIs, even thought (dear)ImGui doesn't provide much, you can still do wonders: https://github.com/ocornut/imgui/issues/707#issuecomment-362...

More on that topic: https://www.youtube.com/watch?v=Z1qyvQsjK5Y

Bonus: If you want to make desktop app with UI, then this is another great C++ library and it's also simple to learn as well. https://github.com/ocornut/imgui.

AFAIK the Rust equivalent to C++'s Dear ImGui is egui.

They use a Dear ImGui, a C++ GUI library.

Aside from bugs and driver issues, Wayland has some unfortunate design limitations. For example, Dear ImGui multi-viewports don't work because "Wayland doesn't let application read or write windows positions."

https://github.com/ocornut/imgui/wiki/Multi-Viewports

This is a feature available on Windows, macOS, and of course X11. Making choices like this means desktop Linux becomes even more of a weird island that nobody wants to support.

So here is the thing: The iPod Nano 7g is from 2012. I've seen many people designing custom PCBs and releasing Kickstarter projects for custom audio players[5] or game handhelds[6]. I know Rockbox (which is great, but its lacks support for Wifi and Bluetooth AFAIK and just does not compete with the UX of iPod's audio book features in my opinion) and iPod Linux. 10 years ago someone even reverse engineered the iPod Nano 6g display[3].

Although I'm not skilled enough in PCB-Design, after some research I found the Lilygo T-Display S3 Pro[4] based on ESP32 S3, which would be the size, but lacks audio and OS. There is also the Mango PI CyberPad[7], which looked interesting, but maybe is already too clunky.

Programming wise, LVGL[8] may be a good framework to develop a modern and efficient UI - at least it looks promising.

So, why is nobody interested in recreating an iPod nano like device? It should be doable with modern tech, but Phones have completely taken over the marked...

1: https://www.reddit.com/r/audiobooks/comments/14ue4un/comment/ks1sj99/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button

2: https://github.com/advplyr/audiobookshelf-app/issues/847

3: https://www.youtube.com/watch?v=7TedIzmguP0

4: https://www.lilygo.cc/products/t-display-s3-pro

5: https://www.youtube.com/watch?v=1C597AkhGtw

6: https://www.funkey-project.com/

7: https://mangopi.org/cp1m

8: https://lvgl.io/

LVGL is a graphics library used mostly for embedded UI's. Main website: https://lvgl.io/

Popular embedded UI library

If you need something written in C and very tiny, I recommend LVGL https://lvgl.io/

The factory code uses the Lvgl graphic library. https://github.com/lvgl/lvgl

I'm trying to interface SPI LCD (ILI943) with Zynq 7020 (PYNQ-Z2 board) and LVGL embedded UI libary. And considering between two approaches: