@ -21,15 +21,11 @@ This is a draft of a feature that is work in progress. If you have questions or
</li>
<li><div> Install jMonkeyEngine <acronymtitle="Software Development Kit">SDK</acronym></div>
</li>
<li><div> Install Android Project support in the jMonkeyEngine <acronymtitle="Software Development Kit">SDK</acronym>:</div>
<li><div>(Optional) Install NBAndroid in the jMonkeyEngine <acronymtitle="Software Development Kit">SDK</acronym>:</div>
<ol>
<li><div> Open Tools→Plugins→Settings</div>
</li>
<li><div> Activate the nightly build.</div>
</li>
<li><div> Go to Tools→Plugins→Available Plugins.</div>
</li>
<li><div> Install the Android Support plugin.</div>
<li><div> Install the "Android" plugin.</div>
</li>
</ol>
</li>
@ -136,24 +132,7 @@ It lets you edit the MainActivitity.java, the AndroidManifest.xml, and build.pro
</p>
<p>
The Android deployment option creates a separate sub-project for android and makes the main project and associated libraries available to the sub-project as libraries. The sub-project can be edited using NBAndroid (see below) or using Eclipse or any other IDE that supports standard android projects. Normally you do not need to edit the android project files. Exceptions are described further below.
</p>
<p>
Activating the nbandroid plugin in the jMonkeyEngine <acronymtitle="Software Development Kit">SDK</acronym> is optional, but recommended. You do not need the nbandroid plugin for Android support to work, however nbandroid will not interfere and will in fact allow you to edit the android source files and project more conveniently. To be able to edit, extend and code android-specific code in Android projects, install NBAndroid from the update center:
</p>
<ol>
<li><div> Open Tools→Plugins→Settings</div>
</li>
<li><div> Go to Tools→Plugins→Available Plugins.</div>
</li>
<li><div> Install the NbAndroid plugin. (Will show up as Android)</div>
</li>
</ol>
<p>
Restart the jMonkeyEngine <acronymtitle="Software Development Kit">SDK</acronym>.
The Android deployment option creates a separate sub-project for android and makes the main project and associated libraries available to the sub-project as libraries. The sub-project can be edited using NBAndroid (see below) or using Eclipse or any other IDE that supports standard android projects. Normally you do not need to edit the android project files. Exceptions are described further below. <em>The libraries are first added to the android sub-project when the main project is built for the first time.</em>
</p>
</div>
@ -165,25 +144,61 @@ Restart the jMonkeyEngine <acronym title="Software Development Kit">SDK</acronym
Open your game project in the jMonkeyEngine <acronymtitle="Software Development Kit">SDK</acronym>.
</p>
<p>
<strong>Building</strong>
</p>
<ol>
<li><div> Right-click the project node and choose Set Main Project.</div>
</li>
<li><div> Right-click the project node to build your project. <br/>
An APK file is created in the "dist" folder.</div>
</li>
<li><div> (Right-click and run the project. The default run target uses the default device set in the Android configuration utility. If you set that to a phone you can run the application directly on your phone!)</div>
</ol>
<p>
<strong>Running</strong>
</p>
<ol>
<li><div> Select the project</div>
</li>
<li><div> Alternatively, select the "Android Device" build configuration next to the Run toolbar button. You can run the project on the emulator (in theory – the emulator doesn’t support OpenGL 2.0 yet?)</div>
<li><div> Select the "Android Device" build configuration next to the Run toolbar button.</div>
</li>
<li><div> Make sure "Compile on Save" is disabled in your project preferences.</div>
</li>
<li><div> Run the application on a connected phone by right-clicking it and selecting "Run" or press the "Play" button in the toolbar.</div>
</li>
</ol>
<p>
The default android run target uses the default device set in the Android configuration utility. If you set that to a phone you can run the application directly on your phone, the emulator does not support OpenGLES 2.0 and cannot run the engine.
Activating the nbandroid plugin in the jMonkeyEngine <acronymtitle="Software Development Kit">SDK</acronym> is optional, but recommended. You do not need the nbandroid plugin for Android support to work, however nbandroid will not interfere and will in fact allow you to edit the android source files and project more conveniently. To be able to edit, extend and code android-specific code in Android projects, install NBAndroid from the update center:
</p>
<ol>
<li><div> Open Tools→Plugins→Settings</div>
</li>
<li><div> Go to Tools→Plugins→Available Plugins.</div>
</li>
<li><div> Install the NbAndroid plugin. (Will show up as Android)</div>
<form><div><inputtype="hidden"name="do"value="login"/><inputtype="hidden"name="sectok"value="6f139d65a3f955caf3492f84be10ab4e"/><inputtype="submit"value="Login"class="button"title="Login"/></div></form><form><div><inputtype="hidden"name="do"value="index"/><inputtype="submit"value="Sitemap"class="button"accesskey="x"title="Sitemap [X]"/></div></form><a><inputtype="button"class="button"value="Back to top"onclick="window.scrollTo(0, 0)"title="Back to top"/></a>
<form><div><inputtype="hidden"name="do"value="login"/><inputtype="hidden"name="sectok"value="d53e8f44804daa7c4f329d03722a8f2c"/><inputtype="submit"value="Login"class="button"title="Login"/></div></form><form><div><inputtype="hidden"name="do"value="index"/><inputtype="submit"value="Sitemap"class="button"accesskey="x"title="Sitemap [X]"/></div></form><a><inputtype="button"class="button"value="Back to top"onclick="window.scrollTo(0, 0)"title="Back to top"/></a>
</div>
<div></div>
</div-->
@ -351,7 +351,7 @@ You've followed a link to a topic that doesn't exist yet. If permissio
The build script is a non-proprietary Apache Ant script. It will work out-of-the-box, but if necessary, you can extend and customize it.
</p>
@ -89,15 +89,11 @@ Read the comments in <code>build.xml</code>, they explain how to override target
</p>
<p>
Additionally, you can manually edit the <code>*-build-impl.xml</code> files that are created when you change the deployment settings: linuxlauncher-impl.xml, macapp-impl.xml, mobile-impl.xml, jnlp-impl.xml, etc. Note that if you deactivate and reactivate a deployment setting, these files are reset, so keep a copy of your changes.
</p>
<p>
Don't edit the base <code>build-impl.xml</code>.
Additionally, you can manually override the targets in the <code>*-impl.xml</code> files that are created when you change the deployment settings: linuxlauncher-impl.xml, macapp-impl.xml, mobile-impl.xml, jnlp-impl.xml, etc. Simply copy&paste a target from these files into the main build.xml and that will be run instead with all modifications.
Don't edit the base <code>*-impl.xml</code> files directly, if you deactivate and reactivate a deployment setting, these files are reset, so you have to copy the whole target and its dependencies, else your build script will become invalid when you disable the deployment option.
nor..om
13 years ago