Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Expand new Gradle project wizard to support Android development #498

Open
tonihele opened this issue Apr 18, 2023 · 2 comments
Open

Expand new Gradle project wizard to support Android development #498

tonihele opened this issue Apr 18, 2023 · 2 comments

Comments

@tonihele
Copy link
Contributor

Expand new Gradle project wizard to support Android development. Yeah, this is something that I know nothing about. And I do not know is this sufficient or is there something else required to give Android developers a boost. But seems that the wizard should ask first that desktop or Android. Some packages can't be used on Android and the are some differences in the build.gradle. Essentially the jMonkeyInitializer can be monkeyed off for example.

Here is a related thread on the forums:
https://hub.jmonkeyengine.org/t/running-android-error-java-lang-noclassdeffounderror-sun-misc-base64encoder/46685

@peedeeboy
Copy link
Contributor

peedeeboy commented Apr 21, 2023

I like the LibGDX project layout: https://libgdx.com/wiki/start/project-generation#project-layout

Similar to the jMonkeyInitializer project layout (Core project + launcher projects for desktop, Andriod, iOS), but with the addition of a dedicated /assets project, which the Initializer doesn't have.

I think the dedicated /assets project is good because a) the Asset Manager in the SDK already has it in its classloader b) If you have published a game to Steam or similar, the assets don't/won't need to be downloaded/updated for users as part of a code only update?

I didn't go down this road, as I also have 0 experience of developing for Android / iOS, and didn't have the confidence for such a change

@MeFisto94
Copy link
Member

MeFisto94 commented Jun 11, 2023

But seems that the wizard should ask first that desktop or Android

We could also support both, probably. You could have a commons library, desktop and android specific jars and potentially also three asset jars (commons, desktop, android)

I don't know how real that usecase is, though. More often, you'd go for an app and probably in the future make the app run natively via windows 11

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants