anchor.diff:  a|.j3m file syntax
   
   a| Float
  -a| (basic Java type) 
  -a| a float (e.g. 0.72) , no comma or parentheses 
  +a| (basic Java type)
  +a| a float (e.g. 0.72) , no comma or parentheses
   
   a| Vector2
   a| `com.jme3.math.Vector2f`
  -a| Two floats, no comma or parentheses 
  -
  -a| Vector3 
  -a| `com.jme3.math.Vector3f` 
  -a| Three floats, no comma or parentheses 
  +a| Two floats, no comma or parentheses
  +
  +a| Vector3
  +a| `com.jme3.math.Vector3f`
  +a| Three floats, no comma or parentheses
   
   a| Vector4
  -a| `com.jme3.math.Vector4f` 
  -a| Four floats, no comma or parentheses 
  -
  -a| Texture2D 
  -a| `com.jme3.texture.Texture2D` 
  -a| Path to texture in `assets` directory, no quotation marks 
  +a| `com.jme3.math.Vector4f`
  +a| Four floats, no comma or parentheses
  +
  +a| Texture2D
  +a| `com.jme3.texture.Texture2D`
  +a| Path to texture in `assets` directory, no quotation marks
   
   a| Texture3D
  -a| `com.jme3.texture.Texture3D` 
  -a| Same as texture 2D except it is interpreted as a 3D texture 
  +a| `com.jme3.texture.Texture3D`
  +a| Same as texture 2D except it is interpreted as a 3D texture
   
   a| TextureCubeMap
  -a| `com.jme3.texture.TextureCubeMap` 
  -a| Same as texture 2D except it is interpreted as a cubemap texture 
  +a| `com.jme3.texture.TextureCubeMap`
  +a| Same as texture 2D except it is interpreted as a cubemap texture
   
   a| Boolean
  -a| (basic Java type) 
  -a| `true` or `false` 
  +a| (basic Java type)
  +a| `true` or `false`
   
   a| Int
  -a| (basic Java type) 
  -a| Integer number, no comma or parentheses 
  -
  -a| Color 
  -a| `com.jme3.math.ColorRGBA` 
  -a| Four floats, no comma or parentheses 
  +a| (basic Java type)
  +a| Integer number, no comma or parentheses
  +
  +a| Color
  +a| `com.jme3.math.ColorRGBA`
  +a| Four floats, no comma or parentheses
   
   a| FloatArray
  -a| 
  -a| (Currently not supported in J3M) 
  +a|
  +a| (Currently not supported in J3M)
   
   a| Vector2Array
  -a| 
  -a| (Currently not supported in J3M) 
  +a|
  +a| (Currently not supported in J3M)
   
   a| Vector3Array
  -a| 
  -a| (Currently not supported in J3M) 
  +a|
  +a| (Currently not supported in J3M)
   
   a| Vector4Array
  -a| 
  -a| (Currently not supported in J3M) 
  +a|
  +a| (Currently not supported in J3M)
   
   a| Matrix3
  -a| 
  -a| (Currently not supported in J3M) 
  +a|
  +a| (Currently not supported in J3M)
   
   a| Matrix4
  -a| 
  -a| (Currently not supported in J3M) 
  +a|
  +a| (Currently not supported in J3M)
   
   a| Matrix3Array
  -a| 
  -a| (Currently not supported in J3M) 
  +a|
  +a| (Currently not supported in J3M)
   
   a| Matrix4Array
  -a| 
  -a| (Currently not supported in J3M) 
  +a|
  +a| (Currently not supported in J3M)
   
   a| TextureBuffer
  -a| 
  -a| (Currently not supported in J3M) 
  +a|
  +a| (Currently not supported in J3M)
   
   a| TextureArray
  -a| 
  -a| (Currently not supported in J3M) 
  +a|
  +a| (Currently not supported in J3M)
   
   |===
   
  
positive.code: 
  In the <<jme3/advanced/material_definitions#,Material Definitions>> article you learned how to configure <<jme3/advanced/materials_overview#,Materials>>  programmatically in Java code. If you have certain commonly used Materials that never change, you can clean up the amount of Java code that clutters your init method, by moving material settings into .j3m files. Then later in your code, you only need to call one setter instead of several to apply the material.
  
  If you want to colorize simple shapes (one texture all around), then .j3m are the most easily customizable solution. J3m files can contain texture mapped materials, but as usual you have to create the textures in an external editor, especially if you use UV-mapped textures. 
  
  
  == Writing the .j3m File
  
negative.code: = Saving and Loading Materials with .j3m Files
  :author:
  :revnumber:
  :revdate: 2016/03/17 20:48
  :keywords: material, texture, file, sdk, wireframe, documentation
  :relfileprefix: ../../
  