Immediate-Mode-UI / Immediate-Mode-UI/Nuklear

SDL2 version of the example (or even better, backend-independent)

Open
#495 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
11.4k
Forks
686
Avg merge
4d 1h
Merged PRs (30d)
3

Description

The best screenshots at the Readme come from the demo in the "example" folder. However, that demo is not just a "demo", because it includes a complete GLFW backend, thus making that example GLFW-dependent and GLEW-dependent, which is unfortunate. I believe that example could be rewritten in a backend-independent way, just like the small demos in the source tree.

The unfortunate thing is not only making it dependent on a specific backend, but, by implementing the backend together with the example, the code is unnecessarily complex. The small demos separate the backend and the demo code, making it very easy to understand (and not because they are smaller, but because you don't mix what belongs to the backend, and what belongs to the demo).

I prefer Nuklear over ImGui because I use C, but in ImGui you can see the complete demo in all backends. In Nuklear it should be possible too. Those of us who don't use GLFW, miss the fun of the best example...

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the demo in the example folder and comparing it with the small demos in the source tree, especially how backend code is separated from demo code. Determine the scope of an SDL2 or backend-independent example and consider how the README screenshots would use it; done means the example no longer depends on GLFW or GLEW and remains understandable across backends.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
desktop
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.