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 de9df75 Update migrate-from-flex.md
de9df75 is described below
commit de9df7501527261daf6112a321b943e881ea0808
Author: Andrew Wetmore <and...@cottage14.com>
AuthorDate: Wed Feb 7 09:16:20 2018 -0400
Update migrate-from-flex.md
Slight text change.
---
create-an-application/migrate-an-existing-app/migrate-from-flex.md | 2 +-
1 file changed, 1 insertion(+), 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 e3f33c3..7172ee3 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,6 +32,6 @@ Where the changes need to happen is in the MXML files. You
built your user inter
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 [...]
## 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.
+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.
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.
