[royale-docs] branch develop updated: Update migrate-from-flex.md

[andreww]

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 
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, 
https://cwiki.apache.org/confluence/display/FLEX/Circular+Dependencies; 
target="_blank">this entry on circular dependencies, written while the 
project was still known as FlexJS, will be useful.
 - **Renaming of properties** - this material will be available soon. For now, 
https://cwiki.apache.org/confluence/display/FLEX/Renaming+Variables; 
target="_blank">this entry on compiler renaming of properties, 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.

[royale-docs] branch develop updated: Update migrate-from-flex.md

[andreww]

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 
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, 
https://cwiki.apache.org/confluence/display/FLEX/Circular+Dependencies; 
target="_blank">this entry on circular dependencies, written while the 
project was still known as FlexJS, will be useful.
+- **Renaming of properties** - this material will be available soon. For now, 
https://cwiki.apache.org/confluence/display/FLEX/Renaming+Variables; 
target="_blank">this entry on compiler renaming of properties, 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.

[royale-docs] branch develop updated: Update migrate-from-flex.md

[andreww]

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

commit ad265cb6f60dbdf9a21522c137296bb2f6b36e50
Author: Andrew Wetmore 
AuthorDate: Fri Feb 16 16:39:06 2018 -0400

Update migrate-from-flex.md

Slight text update.
---
 .../migrate-an-existing-app/migrate-from-flex.md   | 10 +-
 1 file changed, 5 insertions(+), 5 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 7172ee3..9c98d85 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
@@ -23,15 +23,15 @@ If you have developed applications using http://flex.apache.org; target
 
 It is not yet possible to just import an existing Flex application into Apache 
Royale and then produce output in JavaScript that will run almost anywhere. 
However, you may need to do less hands-on conversion than you think to get to 
where you can produce your application, transpiled to JavaScript, through 
Royale.
 
-ActionScript syntax is the same for Royale as it was in Flex. Functions, 
loops, classes, and properties will work as they worked before.
-Your "business logic", which you built all or mainly in ActionScript, probably 
does not need to change. 
-Components and their functions that do not rely on Apache Flex or Adobe Flash 
features will probably work with minor tweaks.
+- ActionScript syntax is the same for Royale as it was in Flex. Functions, 
loops, classes, and properties will work as they worked before.
+- Your "business logic", which you built all or mainly in ActionScript, 
probably does not need to change. 
+- Components and their functions that do not rely on Apache Flex or Adobe 
Flash features will probably work with minor tweaks.
 
-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.
+Where most of 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 [...]
 
 ## 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.
 
-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.
+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. Combine that focus with the small size of the development team, and 
it is clear why there are a lot of Flex features not yet available in Royale. 
Visit [Flex equivalents  [...]

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

[royale-docs] branch develop updated: Update migrate-from-flex.md

[andreww]

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 
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.

[royale-docs] branch develop updated: Update migrate-from-flex.md

[andreww]

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 
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
 ---
 
-
 # Migrate from Flex
 If you have developed applications using http://flex.apache.org; 
target="_blank">Apache Flex, 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  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.

[royale-docs] branch develop updated: Update migrate-from-flex.md

[andreww]

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

commit 089fe39d9959882ee293d6358aad6d695dfefe46
Author: Andrew Wetmore 
AuthorDate: Fri Jan 26 09:51:35 2018 -0400

Update migrate-from-flex.md

Added a link to another doc page.
---
 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 98fee4b..25a55fd 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
@@ -30,6 +30,6 @@ 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...*

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

[royale-docs] branch develop updated: Update migrate-from-flex.md

[andreww]

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

commit 68eb64ea70fea8057c6fdc69f1f82f22fcab71ea
Author: Andrew Wetmore 
AuthorDate: Fri Jan 26 09:36:48 2018 -0400

Update migrate-from-flex.md

Added "http://; to my test link.
---
 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 d7177d6..98fee4b 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
@@ -20,7 +20,7 @@ title: Migrate from Flex
 
 
 # Migrate from Flex
-If you have developed applications using Apache Flex, 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  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 needs  [...]
+If you have developed applications using http://flex.apache.org; 
target="_blank">Apache Flex, 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  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 [...]
 
 It is not yet possible to just import an existing Flex application into Apache 
Royale and then produce output in JavaScript that will run almost anywhere. 
However, you may need to do less hands-on conversion than you think to get to 
where you can produce your application, transpiled to JavaScript, through 
Royale.
 

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

[royale-docs] branch develop updated: Update migrate-from-flex.md

[andreww]

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

commit 4c47648f77a1a6e1c706dfced46565147a24008d
Author: Andrew Wetmore 
AuthorDate: Fri Jan 26 08:33:21 2018 -0400

Update migrate-from-flex.md

Testing making a link that pops a new browser tab.
---
 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 e81f5c6..d7177d6 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
@@ -20,7 +20,7 @@ title: Migrate from Flex
 
 
 # Migrate from Flex
-If you have developed applications using Apache Flex, 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 
 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 needs to run 
properly.
+If you have developed applications using Apache Flex, 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  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 needs  [...]
 
 It is not yet possible to just import an existing Flex application into Apache 
Royale and then produce output in JavaScript that will run almost anywhere. 
However, you may need to do less hands-on conversion than you think to get to 
where you can produce your application, transpiled to JavaScript, through 
Royale.
 

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

[royale-docs] branch develop updated: Update migrate-from-flex.md

[andreww]

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

commit 560b01ecbbba1941ec5f08fb3eeea2ffb5a908a1
Author: Andrew Wetmore 
AuthorDate: Wed Jan 24 16:11:38 2018 -0400

Update migrate-from-flex.md

Removed hyphens and inserted capital letters in the front-matter box.
---
 .../create-an-application/migrate-an-existing-app/migrate-from-flex.md  | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git 
a/Welcome/create-an-application/migrate-an-existing-app/migrate-from-flex.md 
b/Welcome/create-an-application/migrate-an-existing-app/migrate-from-flex.md
index ed7888e..d890458 100644
--- a/Welcome/create-an-application/migrate-an-existing-app/migrate-from-flex.md
+++ b/Welcome/create-an-application/migrate-an-existing-app/migrate-from-flex.md
@@ -1,6 +1,6 @@
 ---
 layout: docpage
-title: migrate-from-flex
+title: Migrate from Flex
 ---
 
 

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