jMonkeyEngine / jMonkeyEngine/jmonkeyengine
Plan to remove default dependency from AWT Settings launcher
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 4.3k
- Forks
- 1.2k
- Avg merge
- 4d 7h
- Merged PRs (30d)
- 14
Description
Currently, jME relies by default on a small AWT launcher to configure some basic settings. In theory, it is fully optional, but in practice jME does not start with very sensible defaults, so it is effectively required, especially for examples.
AWT is still tied to X11, which means it requires the X11 compatibility layer for an engine that would otherwise be Wayland-native. The AWT event loop is also known to cause issues on macOS when used together with GLFW.
I propose changing the engine defaults to make the AWT launcher less essential.
- Frequency: 0 (auto)
- Width: 1440
- Height: 900
- Samples: 4
- Resizable: true
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue concerns the AWT settings launcher and the engine's startup defaults; no source files or tests are named. Start by tracing how examples obtain their display settings and how the AWT launcher supplies them. Done means the listed defaults are used without requiring the launcher, while AWT remains optional and existing platform startup paths still work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- desktop, game-dev
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100