|
|
@@ -1,10 +1,6 @@
|
|
|
= Projects and Assets
|
|
|
-:author:
|
|
|
-:revnumber:
|
|
|
-:revdate: 2016/03/17 20:48
|
|
|
-:relfileprefix: ../../
|
|
|
-:imagesdir: ../..
|
|
|
-ifdef::env-github,env-browser[:outfilesuffix: .adoc]
|
|
|
+:revnumber: 2.0
|
|
|
+:revdate: 2020/07/10
|
|
|
|
|
|
|
|
|
The SDK heavily uses the systems provided by the base platform for the handling of assets and projects and extends the system with jME3 specific features.
|
|
|
@@ -29,7 +25,7 @@ The ProjectAssetManager is basically a normal DesktopAssetManager for each proje
|
|
|
|
|
|
== AssetDataObject
|
|
|
|
|
|
-Most “files that you encounter in the SDK come in the form of AssetDataObjects. All Nodes that you encounter contain the AssetDataObject they were loaded from. It provides not just access to the FileObject of the specific file but also an AssetData object that allows access to jME specific properties and data. The AssetData object also allows loading the object via the jME3 assetManager. It is accessible via the lookup of the Node or AssetDataObject:
|
|
|
+Most "`files`" that you encounter in the SDK come in the form of AssetDataObjects. All Nodes that you encounter contain the AssetDataObject they were loaded from. It provides not just access to the FileObject of the specific file but also an AssetData object that allows access to jME specific properties and data. The AssetData object also allows loading the object via the jME3 assetManager. It is accessible via the lookup of the Node or AssetDataObject:
|
|
|
|
|
|
[source,java]
|
|
|
----
|
mitm001