GLFW VS OpenSceneGraph

Why would any software developer use an API? Well, it's not to get rid of that shirt stain you had for the last three days that's for sure. Instead, we crazy bunch use APIs to progress our software development at a faster rate. I don't really want to work with the Windows API nor do I care to open the rotten can of sardines that is the X11 API. But, thankfully, I don't have to. There are plenty of APIs that handle that for me. And they handle it very nicely too. GLFW is one of these APIs. Easy to use, fast to set up, and overall doesn't have any overhead. Handles window creation, input, and any operating system-specific stuff. It solves a clear and appropriate problem. Left pad, however, is the complete opposite. Does it solve a problem? Sure it does... if you were hit on the head with a baseball bat 17 times. Can't I at least add padding to any direction? No? Does it just have to be the left? Even though we C++ folks can say that the JavaScript weirdos are the only ones who would do such a heinous thing, that wouldn't be the entire story. It would be hypocritical even to assume that all of the useless APIs exist only in the JS ecosystem. Although being hypocritical is my strong point, even I would stop you right there. If there is an ecosystem that would be perfect for breeding unnecessarily complex, widely inefficient, and completely useless libraries, it would be C++... Rust would come at a close second but C++ is the mother of all useless and complex libraries.

Minecraft runs on various Javas.

And there's a known issue with an interaction between minecraft, Java, and the video drivers that crashes out and it can be traced back all the way to here: https://github.com/glfw/glfw/issues/1997

It's not fixed.

Window context manager - glfw, sdl

Types of tools for creating a gui (and how those tools approximately work): 1. Utilize the native _graphical interface API_, and depending on the platform, they have specific layers to interface: * Wayland, X11, for Linux * [GDI](https://learn.microsoft.com/en-us/windows/win32/gdi/windows-gdi) for windows * [Quartz](https://en.wikipedia.org/wiki/Quartz\_(graphics\_layer)) for macOS Example - GTK uses [wayland](https://gitlab.gnome.org/GNOME/gtk/-/blob/main/docs/reference/gdk/wayland.md) ([source code](https://gitlab.gnome.org/GNOME/gtk/-/tree/main/gdk/win32)) [X11](https://gitlab.gnome.org/GNOME/gtk/-/blob/main/docs/reference/gdk/x11.md) ([source code](https://gitlab.gnome.org/GNOME/gtk/-/tree/main/gdk/x11)) GDI ([source code](https://gitlab.gnome.org/GNOME/gtk/-/tree/main/gdk/win32)) Quartz ([source code](https://gitlab.gnome.org/GNOME/gtk/-/tree/main/gdk/macos)) [How to use wayland display server](https://bugaevc.gitbooks.io/writing-wayland-clients/content/black-square/the-wayland-client-library.html) (TODO missing "animation" section) 2. Utilize opengl _or other low level graphics api's_ with window context, use GPU to render widgets * Window context manager - [glfw](https://github.com/glfw/glfw), [sdl](https://www.libsdl.org/) * contexts and surfaces, reading input, handling events Example: ImGui, NanoVG, Nuklear, raylib Why? Mainly used for game development, but also good for gui's. _(i haven't seen any examples that uses this method that are used for developing general-use graphical user interfaces.)_

GLFW: A library for window creation and managing user input.

Not SDL2, but GLFW has something like that under the tests/ directory:

https://github.com/glfw/glfw/blob/master/tests/triangle-vulk...

I'm not familiar with LWJGL, my 5 seconds on their website makes me think you might be looking for something like GLFW https://www.glfw.org/ to handle I/O and window creation/management.

Consider GLFW3 for windowing and GLAD for function loading. I've used this combination myself successfully. Granted, that is "two things" you need, but OTOH it'll work well.

There is a pattern to it which is usable with every GitHub repository. For example, GLFW v3.3.8 can be fetched from: https://github.com/glfw/glfw/archive/refs/tags/3.3.8.tar.gz

I started in 2001 with OpenSceneGraph which made extensive use of intrusive pointers. This was 10 years before C++11 note. That codebase continues to be relevant and as performing as ever.

browse github and try to contribute. I started with OpenSceneGraph

I have been using OpenSceneGraph for over 20 years. It is used in the military a lot and I myself have seen it used to simulate war scenarios with realtime data aboard of a command-and-control center of a battleship.

Does http://www.openscenegraph.org/ fit?

Speed Dreams: It is a fork of TORCS, and was born as the need to include many more functions to the latter. In Speed Dreams the menus would be completely redesigned, adding many more options and making them much more intuitive; the game acquired dynamic time, improvements in reflections, career mode, a new simulation mode and multi threading. Over time many more options were implemented, such as local multiplayer mode, Force Feedback, and of course more and better cars and tracks, a new and more powerfull graphic engine (OpenSceneGraph) among other things, making it a much more complete game than its predecessor. They recently they have presented version 2.2.3. You can also install it in AppImage and Flatpak format.

Here is an example: https://github.com/openscenegraph/OpenSceneGraph/blob/master/examples/osgsimplegl3/osgsimplegl3.cpp

openscenegraph (mainly focuses on graphics, used by openmw for example)

Is not little, is very complex open source racing simulator. There are a lot of cars, categories, tracks. The physics has a lot of work . About the graphics, the devs are working on change the graphic engine to OpenSceneGraph, that actually works, but needs much more polishing. You can see his quality on this video: https://youtu.be/4daTgcxEWRg

I love Godot for a complete game engine. For just the renderer you could consider http://www.openscenegraph.org