Ha! that could work
Still, remember people are coming from the SDK : right click/new project /jme basic game/ click on the green arrow.
Many of them don’t even know command line… so we have to start cool… with commands with max 2 params
idk really… of couse savvy devs will get this sorted out anyway… but what about the others?
I actually don’t like any current approaches to assets. It’s a pain and yes, I think for gradle it may be best to put them in resources. Leaving them separate let me make -assets.jars pretty easily, though.
Anyway, this thread is good because there are a lot of things to work out before we even really standardize a template.
For example, some prebuilt plugins for application bundles that actually work, etc… I really miss a launch4j exe generator as the new SDK never produced workable bundles for me on any platform and I had to go back to manual launch4j execution.
well intellij can open a project from github, but it clones the project and use it directly, It’s not using it as a template.
My problem with this is also that a basic in a template project like this you have plenty of hardcoded stuff like the name of the app and the group…
We’ll have plenty of games called project_template in the my.app group…
People not knwoing how gradle works will never know they have to change it…
EDIT: actually the default name of the app is the current directory…so it could work…
getdown is used as launcher, bootstrap and work as standalone, without need to setup a http server. I used it to distribute app for LudumDare and itch.io.
Anyway… IMO we’ll never beat the right click new project in term of UX…
Let’s pick the approach that is not too painful for users and not too demanding for us