You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@royale.apache.org by an...@apache.org on 2019/12/21 12:51:17 UTC
[royale-docs] branch master updated: Update flex-equivalents.md
This is an automated email from the ASF dual-hosted git repository.
andreww pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/royale-docs.git
The following commit(s) were added to refs/heads/master by this push:
new 960da5d Update flex-equivalents.md
960da5d is described below
commit 960da5dbf3affeaedefdd07f377c5d931adc7b3e
Author: Andrew Wetmore <an...@cottage14.com>
AuthorDate: Sat Dec 21 08:51:12 2019 -0400
Update flex-equivalents.md
added subtitle
---
user-interface/flex-equivalents.md | 3 +++
1 file changed, 3 insertions(+)
diff --git a/user-interface/flex-equivalents.md b/user-interface/flex-equivalents.md
index 832dcf6..433c89f 100644
--- a/user-interface/flex-equivalents.md
+++ b/user-interface/flex-equivalents.md
@@ -7,6 +7,9 @@
layout: docpage
title: Flex equivalents in Royale
---
+
+Moving from Flex to Royale
+
# Flex equivalents in Royale
Royale is not a one-for-one migration of Flex, for several reasons. A lot of Flex code presumes, and takes advantage of, features available in the Adobe AIR environment or the Flash Player plugin. Other Flex elements are more bulky than they could best be to cover a wide range of possible events and situations, so a great deal of the code in an application may be there "just in case" and never actually used.