anchor.diff:  
   [TIP]
   ====
  -Writing and reusing (extending) your own base framework saves you time. When you update your generic base classes, all your games that extend them benefit from improvements to the base (just as all jME-based games benefit of improvements to the jME framework). +Also, your own framework gives all your games a common look and feel.
  +Writing and reusing (extending) your own base framework saves you time. When you update your generic base classes, all your games that extend them benefit from improvements to the base (just as all jME-based games benefit of improvements to the jME framework). +
  +Also, your own framework gives all your games a common look and feel.
   ====
   
   
  
positive.code: a|Pros
  a|Cons
  
  a|Desktop Launcher +(.EXE, .app, .jar+.sh)
  a|This is the standard way of distributing desktop applications. The jMonkeyEngine SDK can be configured to automatically create zipped launchers for each operating system. 
  a|You need to offer three separate, platform-dependent downloads.
  
  a|Desktop Application +(.JAR)
  a|Platform independent desktop application. 
  a|User must have Java configured to run JARs when they are opened; or user must know how to run JARs from command line; or you must provide a custom JAR wrapper.
  
  a|Web Start +(.JNLP)
  a|The user accesses a +++<abbr title="Uniform Resource Locator">URL</abbr>+++, saves the game as one executable file. Easy process, no installer required. You can allow the game to be played offline.
  a|Users need network connection to install the game. Downloading bigger games takes a while as opposed to running them from a CD. 
  
  a|Browser Applet +(.+++<abbr title="HyperText Markup Language">HTML</abbr>++++.JAR)
  a|Easy to access and play game via most web browsers. Userfriendly solution for quick small games.
  a|Game only runs in the browser. Game or settings cannot be saved to disk. Some restrictions in default camera navigation (jME cannot capture mouse.)
  
  a|Android +(.APK)
  a|Game runs on Android devices.
  a|Android devices do not support post-procesor effects.
  
  
negative.code: *  link:http://cowboyprogramming.com/2007/01/05/evolve-your-heirachy/[http://cowboyprogramming.com/2007/01/05/evolve-your-heirachy/] 
  *  link:http://www.gamasutra.com/blogs/MeganFox/20101208/88590/Game_Engines_101_The_EntityComponent_Model.php[http://www.gamasutra.com/blogs/MeganFox/20101208/88590/Game_Engines_101_The_EntityComponent_Model.php]
  *  link:http://gamedev.stackexchange.com/questions/28695/variants-of-entity-component-systems[http://gamedev.stackexchange.com/questions/28695/variants-of-entity-component-systems]
  *  link:http://t-machine.org/index.php/2012/03/16/entity-systems-what-makes-good-components-good-entities/[http://t-machine.org/index.php/2012/03/16/entity-systems-what-makes-good-components-good-entities/]
  *  link:http://entity-systems.wikidot.com/[http://entity-systems.wikidot.com/]
  
  