This is an automated email from the ASF dual-hosted git repository.

aharui pushed a commit to branch develop
in repository https://gitbox.apache.org/repos/asf/royale-docs.git

commit 2ccdbe5ac1064a75cf5e902ed1dd92e090cc5737
Author: Alex Harui <aha...@apache.org>
AuthorDate: Thu Jan 25 10:26:02 2018 -0800

    fill in Create An Application
---
 Create An Application.md | 22 ++++++++++++++++++++++
 1 file changed, 22 insertions(+)

diff --git a/Create An Application.md b/Create An Application.md
new file mode 100644
index 0000000..5e3dd61
--- /dev/null
+++ b/Create An Application.md  
@@ -0,0 +1,22 @@
+---
+layout: docpage
+title: Create an Application
+---
+
+# Create an Application
+
+The easiest way to create a Royale application is to start with an existing 
one and modify it.  In the examples folder are several examples you can use as 
a starting point.  But if you want to know more about the underlying 
principles, read on.
+
+This document is divided into several sections:
+
+[Application Lifecycle](create-an-application/application-lifecycle.html) 
explains how a Royale application starts up and presents the initial UI.
+
+[Structure](create-an-application/application-structure.html) explains the 
important files that typically comprise and application and what they do.
+
+[Migrate an Existing App](create-an-application/migrate-an-existing-app.html) 
provides strategies and techniques when migrating existing Flex apps to Royale, 
and how to switch to Royale if you already have a Javascript application.
+
+[Security](create-an-application/security.html) provides more information 
about making sure hackers can't use your app to be malicous and about dealing 
with common security restrictions when your app wants to access external 
resources.
+
+[Modules](create-an-application/modules.html) discusses how to break your 
application into pieces so it doesn't have to all get downloaded at once.  Or 
have the whole thing compiled at once.
+
+[Royale code conventions](create-an-application/royale-code-conventions.html) 
explains the typical ways Royale developers name files, classes, function, 
variables and more.

-- 
To stop receiving notification emails like this one, please contact
aha...@apache.org.

Reply via email to