<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<link rel="stylesheet" href="./doc/style.css" type="text/css" media="screen">
<link rel="stylesheet" href="./doc/print.css" type="text/css" media="print">
<link rel="stylesheet" href="./doc/override.css" type="text/css">
<title>Temple</title>
<style type="text/css">
.example {
padding-top: 14px;
}
</style>
</head>
<body>
<div id="fb-root"></div>
<script>(function(d, s, id) {
var js, fjs = d.getElementsByTagName(s)[0];
if (d.getElementById(id)) return;
js = d.createElement(s); js.id = id;
js.src = "//connect.facebook.net/nl_NL/all.js#xfbml=1&appId=235069249947120";
fjs.parentNode.insertBefore(js, fjs);
}(document, 'script', 'facebook-jssdk'));</script>
<table class="titleTable" id="titleTable" style="" cellpadding="0" cellspacing="0">
<tbody>
<tr>
<td class="titleTableTitle" align="left">Temple Library for ActionScript 3.0 by MediaMonks</td>
<td class="titleTableTopNav" align="right">
<a href="http://code.google.com/p/templelibrary/">Project Home</a> |
<a href="./doc/index.html">API Documentation</a> |
<a href="http://code.google.com/p/templelibrary/source/checkout">Source</a>
</td>
<td class="titleTableLogo" align="right" rowspan="3">
<img class="logoImage" title=" Temple Logo " alt=" Temple Library " src="./doc/images/logo.jpg" />
</td>
</tr>
<tr class="titleTableRow2">
<td class="titleTableSubTitle" id="subTitle" align="left" colspan="2">Temple</td>
</tr>
<tr class="titleTableRow3">
<td colspan="2"> </td>
</tr>
</tbody>
</table>
<div class="MainContent">
<h1>Temple Library for ActionScript 3 by MediaMonks</h1>
<p>ActionScript 3 toolkit for stable, high performance and maintainable Flash applications. Special designed for general everyday development.</p>
<p>This is version <!-- VERSION -->3.7.1<!-- /VERSION --> of the <!-- NAME -->Temple<!-- /NAME -->, build on
<!-- DATE -->2014-11-05<!-- /DATE -->. Get the latest version from:
<a href="http://code.google.com/p/templelibrary/">http://code.google.com/p/templelibrary/</a>. You can get the files from
<a href="http://code.google.com/p/templelibrary/source/checkout">SVN</a>.</p>
<p>The Temple consists of classes we use on a regular basis. They are designed for re-usability and optimized
for performance and memory usage. The Temple is specially designed to work with other frameworks like
<a href="http://www.gaiaflashframework.com/" target="_blank">Gaia</a>, <a href="http://www.robotlegs.org/" target="_blank">Robotlegs</a>
or <a href="http://www.greensock.com/tweenlite/" target="_blank">TweenLite</a>.</p>
<p>The Temple focuses on:</p>
<ul>
<li><a href="./doc/temple/core/debug/Memory.html">Memory Management</a></li>
<li><a href="./doc/temple/core/destruction/package-detail.html">Destruction</a></li>
<li><a href="./doc/temple/core/debug/package-detail.html">Debugging</a></li>
<li><a href="./modules/utils/readme.html">Utilities</a></li>
<li><a href="./modules/ui/readme.html">UI Components</a></li>
<li><a href="./doc/temple/ui/form/Form.html">Forms</a></li>
<li><a href="./modules/data/readme.html">Data loading, parsing and handling</a></li>
<li><a href="./doc/temple/ui/layout/liquid/LiquidBehavior.html">Layout</a></li>
<li><a href="./doc/temple/data/cache/CacheLoader.html">Caching</a></li>
<li><a href="./modules/facebook/readme.html">Facebook Communication</a></li>
</ul>
<p>But the Temple contains many other classes which can help you in work as a Flash Developer. The Temple can also be
useful for Flash Animators for creating easy, fast and stable interactive UI Components.</p>
<p>The Temple is specially designed to work with Flash in the Flash IDE, but can also be used in combination with Flex.</p>
<p>The Temple is build by <a href="http://www.mediamonks.com/" target="_blank">MediaMonks</a> and is partly based and
inspired on other frameworks and libraries.
<h1>Modules</h1>
<p>The Temple consists of several <a href="./modules/index.html">modules</a> which all have there own functionality and
can be used together. The most common modules are grouped together in the root <a href="./source">/source</a> folder of
the Temple Library.</p>
<h3>Most common modules:</h3>
<ul>
<li><a href="./modules/core/readme.html">Core</a></li>
<li><a href="./modules/common/readme.html">Common</a></li>
<li><a href="./modules/utils/readme.html">Utils</a></li>
<li><a href="./modules/data/readme.html">Data</a></li>
<li><a href="./modules/control/readme.html">Control</a></li>
<li><a href="./modules/ui/readme.html">UI</a></li>
<li><a href="./modules/yalog/readme.html">Yalog</a></li>
<li><a href="./modules/tweenlite/readme.html">TweenLite</a></li>
</ul>
<h3>Other modules:</h3>
<ul>
<li><a href="./modules/camera/readme.html">Camera</a></li>
<li><a href="./modules/codecomponents/readme.html">CodeComponents</a></li>
<li><a href="./modules/facebook/readme.html">Facebook</a></li>
<li><a href="./modules/liveinspector/readme.html">Live Inspector</a></li>
<li><a href="./modules/mediaplayers/readme.html">MediaPlayers</a></li>
<li><a href="./modules/microphone/readme.html">Microphone</a></li>
<li>Multi-Language*</li>
<li><a href="./modules/reflection/readme.html">Reflection</a></li>
<li>Sound*</li>
<li><a href="./modules/speech/readme.html">Speech</a></li>
</ul>
<p><i>*coming soon!</i></p>
<h1>Content</h1>
<dl>
<dt><a href="./bin">/bin</a></dt>
<dd>Contains the SWC files of the Temple.</dd>
<dt><a href="./doc">/doc</a></dt>
<dd>Contains the <a href="./doc/index.html">documentation of the Temple</a>.</dd>
<dt><a href="./examples">/examples</a></dt>
<dd>Contains <a href="./examples/index.html">examples of the Temple</a>.</dd>
<dt><a href="./lib">/lib</a></dt>
<dd>Contains SWC files needed for the Temple.</dd>
<dt><a href="./source">/source</a></dt>
<dd>Contains the source (.as) files of the Temple. These are the source files of the most common modules of the
Temple. These files are set as SVN external, so they are directly
linked to the original source files in the corresponding module.</dd>
<dt><a href="./extended">/extended</a></dt>
<dd>Contains additional source (.as) files of the Temple, from the most common Temple modules. These files are set
as SVN external, so they are directly linked to the original source files in the corresponding module.</dd>
<dt><a href="./modules">/modules</a></dt>
<dd>Contains all <a href="./modules/index.html">Temple modules</a>. The most common modules are also linked in the <code>source</code> folder of the
Temple. The <code>modules</code> folder also contains some more additional modules, like <code>Facebook</code> or
<code>CodeComponents</code>.<em><br/>
(This folder is not available in the zip file.)</em></dd>
<dt><a href="./tools">/tools</a></dt>
<dd>Contains ANT scripts which are used to generate docs, examples, swc etc... <br/>
<em>(This folder is not available in the zip file.)</em></dd>
</dl>
<h1>Getting started</h1>
<p></p>
<h3>Adding the Temple to your project</h3>
<p>To add the Temple to your project you could use the SWC file or the AS files. The SWC file can be found in the
<code><a href="./bin/">bin</a></code> folder. If you want to use the SWC file you need to add the SWC file to the class
path of your project.</p>
<p>If you want to use the AS files you just need to copy the content of the <code><a href="./source/">/source</a></code>
folder to the source folder of your project. Or you could add the <code><a href="./source/">/source</a></code> folder to
the class path of your project.<br/><strong>NOTE:</strong> don't copy folders from an SVN check out, since this can
cause SVN problems. It would be better to do an SVN export to your own folder.
</p>
<h3>Use the Temple in your project</h3>
<p>To get more information about the usage of the classes in the Temple you could check out the
<a href="./doc/index.html">AS Documentation</a>, the <a href="./examples/index.html">examples</a> or the
<code>readme.html</code> in every <a href="./modules/index.html">module</a> you want to use.</p>
<h1>Examples</h1>
<p>Check out the <a href="./examples">/examples</a> folder for all examples. This folder also contains a
<a href="./examples/index.html">list of all available examples</a>.</p>
<p>Note: every example has an XML file which is an <a href="http://ant.apache.org/" target="_blank">ANT</a> build file
which can be used to build the example.</p>
<h1>Contact</h1>
<p>Follow us on <a href="http://twitter.com/templelibrary" target="_blank">Twitter</a>
or <a href="http://www.facebook.com/TempleLibrary" target="_blank">Facebook</a> to get the lastest updates and tips
about the library. If you have a question you can start a discussion at
<a href="http://groups.google.com/group/templelibrary" target="_blank">Google Groups</a>. Bugs and feature requests
can be posted in the <a href="http://code.google.com/p/templelibrary/issues" target="_blank">Issue Tacker</a> at
GoogleCode.</p>
<div class="fb-like" data-href="http://code.google.com/p/templelibrary/" data-send="true" data-width="450" data-show-faces="true"></div>
<h1>Version</h1>
<p>This is version <!-- VERSION -->3.7.1<!-- /VERSION --> of the Temple. This version number consists of 3 numbers which
has the following meaning:</p>
<ol>
<li>The first number incremented when the Temple is completely refactored and will not be backwards compatible with the
previous version of the Temple.</li>
<li>The second number is incremented when something has change in the API of the Temple of when classes are added to the Temple.
These updates are not intended to be backwards compatible, but should be interchangeable with some minor changes.</li>
<li>The third number is incremented when there were updated in classes which has no effect on the API of the Temple.
These updates should be backwards compatible, although backwards compatibility is not supported in the Temple.</li>
</ol>
<p>When the first or second number is incremented, the following numbers will be reset to zero. For maintainability all
modules have the same version number, even when nothing has changed in the module. Modules with the same version number
can always be used together.</p>
<h1>License</h1>
<p>Temple Library for ActionScript 3.0<br />
Copyright © MediaMonks B.V.<br />
All rights reserved.</p>
<p>Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:</p>
<ol>
<li>Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.</li>
<li>Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.</li>
<li>All advertising materials mentioning features or use of this software
must display the following acknowledgement:
This product includes software developed by MediaMonks B.V.</li>
<li>Neither the name of MediaMonks B.V. nor the
names of its contributors may be used to endorse or promote products
derived from this software without specific prior written permission.</li>
</ol>
<p>THIS SOFTWARE IS PROVIDED BY MEDIAMONKS B.V. ''AS IS'' AND ANY
EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL MEDIAMONKS B.V. BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.</p>
<h3>Note</h3>
<p>This license does not apply to 3rd party classes inside the Temple
repository with their own license!</p>
<p><strong>We make use of (and recommend) GreenSock’s Tweening Platform
(<a href="http://www.tweenlite.com" target="_blank">TweenLite</a> / <a href="http://www.tweenlite.com" target="_blank">TweenMax</a>)
which is licensed separately. Please see <a href="http://www.greensock.com" target="_blank">GreenSock.com</a> for details.</strong></p>
<center class="copyright">
<footer>by MediaMonks | http://www.mediamonks.com</footer>
<br/>
</center>
</div>
</body>
</html><!--by MediaMonks | http://www.mediamonks.com<br/> -->