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 0b7d4af Update emulation.md
0b7d4af is described below
commit 0b7d4af34be743c6040cd49cf20957bab8feb718
Author: Andrew Wetmore <[email protected]>
AuthorDate: Thu Jan 9 10:23:53 2020 -0400
Update emulation.md
Lined to component sets page
---
migrate-an-existing-app/emulation.md | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/migrate-an-existing-app/emulation.md
b/migrate-an-existing-app/emulation.md
index a28ae58..b40d240 100644
--- a/migrate-an-existing-app/emulation.md
+++ b/migrate-an-existing-app/emulation.md
@@ -19,7 +19,10 @@ Apache Royale offers a growing list of components that let
you build your applic
Royale is creating a set of **emulation** components to replace the Flex
components that depended on Flash features. These components do not promise
100% backward compatibility and may not use the same class hierarchy as Flex.
But they do approximate what the equivalent components in Flex did.
-There are two sets of emulation components: _MXRoyale_ contains emulations of
UIComponent and other MX components. _SparkRoyale_ will contain emulation of
Spark components.
+There are two emulation [component sets](/component-sets):
+
+* **MXRoyale** contains emulations of UIComponent and other MX components.
+* **SparkRoyale** contains emulations of Spark components.
The Royale team typically discovers the need to emulate a component when a
project or company starts to migrate an existing Flex application. We have
developed guides to help developers create emulations that they need for their
own applications, and that they can share with the community.
