|
@@ -73,7 +73,7 @@ This is the recommended internal structure:
|
|
=== Clean, Build and Run Cycle
|
|
=== Clean, Build and Run Cycle
|
|
|
|
|
|
|
|
|
|
-image::sdk/jmonkeyplatform-docu-5.png[jmonkeyplatform-docu-5.png,width="421",height="298",align="center"]
|
|
|
|
|
|
+image::jmonkeyplatform-docu-5.png[jmonkeyplatform-docu-5.png,width="421",height="298",align="center"]
|
|
|
|
|
|
|
|
|
|
[IMPORTANT]
|
|
[IMPORTANT]
|
|
@@ -101,9 +101,9 @@ ant clean; ant jar; ant run;
|
|
== Development Process
|
|
== Development Process
|
|
|
|
|
|
* *Creating new files and packages:* Select the Source Packages node (or any of its subnodes), and press kbd:[Ctrl]+kbd:[N] (`menu:File[New File]`): Use the `New File` wizard to create new Java classes, Java packages, Java beans, Swing forms, JUnit files, j3m Materials, j3o scenes, j3f filters, and many more.
|
|
* *Creating new files and packages:* Select the Source Packages node (or any of its subnodes), and press kbd:[Ctrl]+kbd:[N] (`menu:File[New File]`): Use the `New File` wizard to create new Java classes, Java packages, Java beans, Swing forms, JUnit files, j3m Materials, j3o scenes, j3f filters, and many more.
|
|
-* *Editing files:* Open the Projects Explorer and double-click a Java file from the Source Packages to open it in the Editor. The <<sdk/code_editor#,jMonkeyEngine SDK Code Editor>> assists you in many ways, including syntactic and semantic code coloring, code completion, and javadoc.
|
|
|
|
|
|
+* *Editing files:* Open the Projects Explorer and double-click a Java file from the Source Packages to open it in the Editor. The xref:code_editor.adoc[jMonkeyEngine SDK Code Editor] assists you in many ways, including syntactic and semantic code coloring, code completion, and javadoc.
|
|
* *Adding Assets:*
|
|
* *Adding Assets:*
|
|
-** You can <<sdk/model_loader_and_viewer#,import models, scenes, and materials>> as assets into your project.
|
|
|
|
|
|
+** You can xref:model_loader_and_viewer.adoc[import models, scenes, and materials] as assets into your project.
|
|
** To add sound files and images, use your operating system's file explorer and copy the files into your project's asset directory.
|
|
** To add sound files and images, use your operating system's file explorer and copy the files into your project's asset directory.
|
|
|
|
|
|
* *ToDo List:* The tasks window automatically lists all lines containing errors and warnings, and all lines that you have marked with the comment keywords
|
|
* *ToDo List:* The tasks window automatically lists all lines containing errors and warnings, and all lines that you have marked with the comment keywords
|
|
@@ -114,7 +114,7 @@ FIXME
|
|
----
|
|
----
|
|
, @todo, or TODO.
|
|
, @todo, or TODO.
|
|
|
|
|
|
-* *Integrated tools:* <<sdk/debugging_profiling_testing#,Debugging, Testing, Profiling>>.
|
|
|
|
|
|
+* *Integrated tools:* xref:debugging_profiling_testing.adoc[Debugging, Testing, Profiling].
|
|
|
|
|
|
|
|
|
|
=== Adding external jar libraries
|
|
=== Adding external jar libraries
|
|
@@ -141,12 +141,12 @@ That's it, your project can now use the external library. If you also linked the
|
|
|
|
|
|
=== Application Deployment
|
|
=== Application Deployment
|
|
|
|
|
|
-* You can <<sdk/application_deployment#,deploy>> your game as desktop application (JAR), browser applet, WebStart (JNLP), or on the Android platform.
|
|
|
|
|
|
+* You can xref:application_deploymen.adoc[deploy] your game as desktop application (JAR), browser applet, WebStart (JNLP), or on the Android platform.
|
|
|
|
|
|
|
|
|
|
== Running Sample Projects
|
|
== Running Sample Projects
|
|
|
|
|
|
-The SDK contains <<sdk/sample_code#,Sample Code>> (read more).
|
|
|
|
|
|
+The SDK contains xref:sample_code.adoc[Sample Code] (read more).
|
|
|
|
|
|
Open the Source Packages node of the JmeTests project.
|
|
Open the Source Packages node of the JmeTests project.
|
|
|
|
|