Browse files

wrote some text

  • Loading branch information...
1 parent 6941ca9 commit b4b59f03f246986903463f42675a499ddc37fd91 @leafo committed Apr 9, 2012
Showing with 40 additions and 1 deletion.
  1. +39 −0 site/
  2. +1 −1 site/style.less
@@ -11,6 +11,45 @@ easy to port.
+## How It Works
+Native client files are distributed as `.nexe` binaries where are compiled for
+both 64-bit and 32-bit computers. Aroma comes as a compiled `.nexe` file that's
+ready to use after uploading to your server.
+### Reusing Your Browser
+Aroma comes with some support JavaScript that must be uploaded alongside your
+game. The JavaScript facilitiates things like loading code, loading images, and
+rendering fonts.
+In order to keep the `.nexe` binary small, things that can already be
+accomplished by your browser are handled there. Thing like rendering fonts and
+decoding images are handled by the `canvas` tag, which functions as an
+invisible buffer.
+### Asynchronous Loading
+Aroma loads all of your game code from the web. You typically will upload your
+code alongside the `.nexe` files. This enables you to quickly deploy changes
+without having to recompile anything.
+If you've ever done web programming you're probably familiar with making
+asynchronous requests to a server to fetch resources by providing some sort of
+a callback function. On the other hand, when loading code in Lua typically
+write something synchronous like:
+ ```lua
+ require "mygame.enemy"
+ ```
+Aroma translates this call into an asynchronous request to the browser,
+blocking the execution of the game until the resource has been fetched.
+Combined with the caching provided by the browser, this makes loading code from
+the web pleasant.
## Download
## Getting Started
@@ -85,7 +85,7 @@ a {
background: #E7FFF6;
padding: 12px;
- h2 {
+ h2, h3, h4 {
color: #48817D;
text-shadow: 0px 1px 0px white;

0 comments on commit b4b59f0

Please sign in to comment.