| 12345678910 |
- <!DOCTYPE html><html lang="en"><head><meta charset="UTF-8"><!--[if IE]><meta http-equiv="X-UA-Compatible" content="IE=edge"><![endif]--><meta name="viewport" content="width=device-width, initial-scale=1.0"><meta name="generator" content="Asciidoctor 1.5.4"><title>managers</title><link rel="stylesheet" href="./asciidoctor.css">
- <link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/font-awesome/4.5.0/css/font-awesome.min.css">
- <link rel="stylesheet" href="./coderay-asciidoctor.css"></head><body class="article toc2 toc-left"><div id="header"><h1>managers</h1><div class="details"><span class="author" id="author"></span><br><span id="revnumber">version ,</span> <span id="revdate">2016/03/17 20:48</span></div><div id="toc" class="toc2"><div id="toolbar"><a href="https://github.com/jMonkeyEngine/wiki/edit/master/src/docs/asciidoc/jme3/advanced/atom_framework/docs/managers.adoc"><i class="fa fa-pencil-square" aria-hidden="true"></i></a><a href="https://github.com/jMonkeyEngine/wiki/new/master/src/docs/asciidoc/jme3/advanced/atom_framework/docs/"><i class="fa fa-plus-square" aria-hidden="true"></i></a></div><div id="toctitle">Table of Contents</div><ul class="sectlevel1"><li><a href="#atom-framework-s-managers">Atom framework’s Managers</a></li></ul></div></div><div id="content"><div class="sect1"><h2 id="atom-framework-s-managers">Atom framework’s Managers</h2><div class="sectionbody"><div class="paragraph"><p>Read about the Manager idea here <a href="../../../../jme3/advanced/atom_framework/atomcore.html">atomcore</a></p></div>
- <div class="paragraph"><p>Atom also have a lot of Managers. <strong>Here suggestion for implemented one!</strong>, you can call it a convention because it’s not forced on you to gain more flexibility.</p></div>
- <div class="paragraph"><p>Manager can has SubManagers, as a List or a Map (Hierarchy or not is not forced)</p></div>
- <div class="paragraph"><p>Manager can be extended or Singleton or DefaultInstance (can be getDefault() but not a singleton) here and there. Manager all “attend” in a “cycle” but not “obey”. They can implement ICycle to mark they executor as Obey stricly to the Cycle.</p></div>
- <div class="paragraph"><p>you can do Main.getManager(Class) if your Main support it, or doing the long reference getManager().getSubManager().</p></div>
- <div class="paragraph"><p>You can see it as a hybrid or “no contract yet” – “not stricted to” way of implementing to get “best of both world” out of:</p></div>
- <div class="olist arabic"><ol class="arabic"><li><p>singleton vs default vs linked instance</p></li><li><p>hierarchy vs flatten component base</p></li><li><p>cycle attend vs a random routine.</p></li></ol></div>
- <div class="paragraph"><p>In this implementation, I also try to have a good balance between flexibility and usefulness, clearance and performance. In the near future, when my framework is proved to be statable and useful, I will release it fully.</p></div></div></div></div><div id="footer"><div id="footer-text">Version <br>Last updated 2016-06-26 06:16:49 UTC</div></div></body></html>
|
