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 175e11b  Update migrate-from-flex.md
175e11b is described below

commit 175e11b1beec30106bb4e52c08d1315152820e6b
Author: Andrew Wetmore <and...@cottage14.com>
AuthorDate: Tue Feb 6 20:44:40 2018 -0400

    Update migrate-from-flex.md
    
    Added commentary and a link about Royale equivalent for Flex components.
---
 .../migrate-an-existing-app/migrate-from-flex.md                  | 8 +++++---
 1 file changed, 5 insertions(+), 3 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 25a55fd..e3f33c3 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
@@ -18,7 +18,6 @@ layout: docpage
 title: Migrate from Flex
 ---
 <!-- This is from material created by Peter Ent and modified by Tom Chiverton: 
https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=34013930 -->
-<!-- I have not added links to other pages, or to other sites, yet -->
 # Migrate from Flex
 If you have developed applications using <a href="http://flex.apache.org"; 
target="_blank">Apache Flex</a>, or Adobe Flex before it, your applications 
probably combine MXML and ActionScript files along with resources like images 
and audio files, and some of the MXML files have <fx:Script> tags with 
ActionScript snippets inside them. If that is the case, you will find yourself 
at home working with Apache Royale. The big difference is not so much the code 
you use, but the output and what it [...]
 
@@ -30,6 +29,9 @@ Components and their functions that do not rely on Apache 
Flex or Adobe Flash fe
 
 Where the changes need to happen is in the MXML files. You built your user 
interface using Spark and MX components--containers, controls, and so on. All 
those components will need to migrate to their Royale equivalents. You will 
find some differences between the components you used and the ones you now have 
available, and not all Flex components have equivalents in Royale yet.
 
-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 [...]
+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 [...]
 
-*link to Development tools page goes here...*
+## 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, since they include code built up over many iterations and 
designed to cover a wide range of possible events and situations.
+
+The goal of the Royale project is to provide the convenience and speed of 
developing in the Flex world while producing a lighter-weight application that 
plays well in the HTML-JavaScript-CSS environment. To reach that goal requires 
putting off, or finding alternatives for, certain standard Flex components and 
functions. The page [Flex equivalents in 
Royale](User-interface/Flex-equivalents.html) can help you find what you need 
as you work through your migration.

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

Reply via email to