MeFisto94
commented
4 years ago See https://github.com/jMonkeyEngine/sdk/issues/117 for the reasoning
Open MeFisto94 opened 4 years ago
MeFisto94
commented
4 years ago See https://github.com/jMonkeyEngine/sdk/issues/117 for the reasoning
nickidebruyn
commented
4 years ago Yes I was on an old SDK. I however did get a good process working to build android without using jME sdk. I am now using Android SDK to build my project by using gradle to pull in jME files and my game files. I would however like to keep seeing android build option in jME sdk even if it just creates a skeleton android project that will be able to be opened in android studio.
MeFisto94
commented
4 years ago I think what needs to be done for this is enabling an easy android version with the gradle template that is part of https://github.com/jMonkeyEngine/sdk/tree/master/jme3-templates
neph1
commented
2 years ago I'm also building the core game in the SDK, then using Android Studio (+ gradle) for android specific things. You just get so much for free in AS.
Sounds harsh but we get a lot of hate lately regarding Android Support.
The Problems are:
Our support was incomplete anyway
Users needed NBAndroid anyway
Our support won't work anymore
We had some code to select the SDK Version which invoked the sdkmanager.bat from android, but they completely changed the command line making it more interactive, so updating our code is relatively hard for no gain.
NBAndroidV2 can also manage SDK Versions and AVD's and you need NBAndroidV2 anyway. Personally I could also see someone having a shared project: Using the SDK for Modelling (and Desktop) and using Android Studio for Android, because Android Studio has by far the most professional Android IDE Experience, which we cannot reach.
@nickidebruyn You are probably the one most affected by that, so what are your thoughts? Weren't you on an old SDK anyway, because of something with NBAndroid?