max
/
amber
forked from amber/amber


			
				
					
						
						
							123456789101112131415161718192021222324252627282930313233343536373839404142434445464748
							<!DOCTYPE html>
<html>

<head>
    <title>{%= title %}</title>
    <meta http-equiv="content-type" content="text/html; charset=utf-8"/>
    <meta name="author" content="{%= author_name %}"/>
    <script type='text/javascript' src='the.js'></script>
</head>

<body>
<!-- EXAMPLE APP START -->
<p>This is a sample app. It contains some
    <a href="parts.html">batteries included</a>
    and should be
    <a href="uninstall.html">cleaned up</a>
    once you start developing your own app / lib.</p>
<button id="amber-with">Hello from TagBrush >> with:</button>
<button id="silk-tag">Hello from Silk >> TAG:</button>
<button id="jquery-append">Hello from jQuery append</button>
<button id="console-log">Log into JS console</button>
<button id="timeout-alert">Remind me in five seconds</button>
<button id="lambda-status">Inspect status of backend</button>
<ol id="output-list"></ol>
<!-- EXAMPLE APP END -->
<script type='text/javascript'>
    var global = typeof global === "undefined" ? window : global || window;
    require(['app'], function (amberPromise) {
        amberPromise.then(function (amber) {
            amber.initialize({
                //used for all new packages in IDE
                'transport.defaultAmdNamespace': "{%= namespace %}"
            }).then(function () {
                // This shows IDE dialog in development mode (module is present).
                // This silently fails in deploy mode (module is missing).
                // Thus, no need to have different page for deploy, leading to less bugs.
                require(["amber-ide-starter-dialog"], function (dlg) {
                    dlg.start();
                });
                // Start the app itself.
                amber.globals.{%= name %}._start();
            });
        });
    });
</script>
</body>

</html>