Since unfortunately @nehon is now retired and it doesn’t sound like that’s going to change any time soon , I’ve been thinking of “rebooting” this project with some expanded features. However, the lack of any mention of license on the repo is an issue. This is a shame because there’s some good stuff in there that’d be going to waste.
Does anyone know if nehon ever mentioned licensing, or if he gave a go-ahead for others to create derivatives? Or should I just start from ground zero if I were to work on this? (I was going to anyway, then I remembered this existed, so that’s no big deal.)
If I do go forward, some ideas/changes I’d likely look at are…
- BSD-3 license (same as JME’s)
- Similar template based approach
- Expanded feature set:
- Optional dependency selection for Gradle build config (i.e. as libgdx has, checkboxes for dependencies such as bullet, lwjgl2/3, terrain, etc. as well as 3rd party dependencies such as jme-jfx-11?)
- Possibly some optional code generation to allow for additional flexibility beyond templates?
- Tempate additions
- Standard JME Test template (in a futile attempt to standardize test PRs a bit, and encourage some best practices, in collaboration with others here)
- Template(s) for examples?
- Possibly template(s) to make creating reproducible bug-report examples less painful (just some un-vetted ideas so far, may scrap this if not helpful enough)
- New JavaFX UI (partly because I just can’t go back to Swing willingly, partly for new features like bindings and CSS)
- Name change
- “JME-like” JFX UI theme closely matching the forum/store and so on
- If there’s interest, I could try keeping the UI and project generation decoupled enough that 3rd parties such as the SDK or an IntelliJ plugin have the option of pulling functionality in some day.