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 07a8bb7 Update migrate-from-flex.md 07a8bb7 is described below commit 07a8bb73ada025f869df746bd2cee4da45c2f757 Author: Andrew Wetmore <and...@cottage14.com> AuthorDate: Tue Feb 20 13:55:09 2018 -0400 Update migrate-from-flex.md Added a stub on public Vars. --- create-an-application/migrate-an-existing-app/migrate-from-flex.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) 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 4b2d101..bd58701 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 @@ -32,10 +32,11 @@ Where most of the changes need to happen is in the MXML files. You built your us One big change you will notice right away is that the default Royale UI components come with a basic set of functions, but not with the full range of behaviors that was loaded into every single Flex UI component whether it needed it or not. To get exactly the behavior your application needs from a data display or an input field, you may need to add "beads" to the basic Royale component. For example, to provide a field where the user can enter a password, you need to take the basic Royale [...] ## Standard runtime problems -*This section will address some issues that may arise for applications migrated from Flex.* +There are some issues that you may run into when you migrate a Flex-built application to Royale. Here are some significant ones: - **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. +- **Public variables** - *information on this coming soon.* ## 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.