This is an automated email from the ASF dual-hosted git repository.
andreww pushed a commit to branch develop
in repository https://gitbox.apache.org/repos/asf/royale-docs.git
The following commit(s) were added to refs/heads/develop by this push:
new 5c1b7fa Update migrate-from-flex.md
5c1b7fa is described below
commit 5c1b7fa82b0fecfadff597253b8151f40d89855f
Author: Andrew Wetmore <and...@cottage14.com>
AuthorDate: Sun Feb 18 14:33:17 2018 -0400
Update migrate-from-flex.md
Add links to wiki pages for now, until we get around to migrating the
information.
---
create-an-application/migrate-an-existing-app/migrate-from-flex.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/create-an-application/migrate-an-existing-app/migrate-from-flex.md
b/create-an-application/migrate-an-existing-app/migrate-from-flex.md
index bac18e2..4b2d101 100644
--- a/create-an-application/migrate-an-existing-app/migrate-from-flex.md
+++ b/create-an-application/migrate-an-existing-app/migrate-from-flex.md
@@ -34,8 +34,8 @@ One big change you will notice right away is that the default
Royale UI componen
## Standard runtime problems
*This section will address some issues that may arise for applications
migrated from Flex.*
-- **Circular dependencies** - this material will be available soon.
-- **Renaming of properties** - this material will be available soon.
+- **Circular dependencies** - This material will be available soon. For now,
<a
href="https://cwiki.apache.org/confluence/display/FLEX/Circular+Dependencies";
target="_blank">this entry on circular dependencies</a>, written while the
project was still known as FlexJS, will be useful.
+- **Renaming of properties** - this material will be available soon. For now,
<a href="https://cwiki.apache.org/confluence/display/FLEX/Renaming+Variables";
target="_blank">this entry on compiler renaming of properties</a>, written
while the project was still known as FlexJS, will be useful.
## Royale equivalents for Flex components ##
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.
--
To stop receiving notification emails like this one, please contact
andr...@apache.org.
