This is an automated email from the ASF dual-hosted git repository.

aharui pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/royale-asjs.wiki.git


The following commit(s) were added to refs/heads/master by this push:
     new 806864b  Updated Emulation Components (markdown)
806864b is described below

commit 806864bd946132bfef036a2f350ad89b4fef8f21
Author: aharui <aha...@apache.org>
AuthorDate: Sat Apr 7 23:47:01 2018 -0700

    Updated Emulation Components (markdown)
---
 Emulation-Components.md | 8 ++++++--
 1 file changed, 6 insertions(+), 2 deletions(-)

diff --git a/Emulation-Components.md b/Emulation-Components.md
index 34458e5..29ccfdc 100644
--- a/Emulation-Components.md
+++ b/Emulation-Components.md
@@ -4,11 +4,13 @@ The plan is to quickly create classes with stubs for APIs we 
know our migrating
 
 But first, we want to try to get the migrating user's app to compile.  So the 
process is to quickly create a class of the same package name and class name as 
the Flex component and either copy in Royale APIs (renaming if necessary), 
copying in the API from the flex-sdk repo (if it will work as is) or copying in 
the API from the flex-sdk repo and removing all of the code and leaving a TODO.
 
-We have created an emulation of UIComponent already.  Emulation components 
don't have to retain their Flex class hierarchy if the intermediate ancestor 
classes are not directly used in user code.  For example, mx:Application 
currently just subclasses UIComponent instead of LayoutContainer.  Really, the 
goal is to toss out as much Flex code as we possibly can and use Royale beads 
instead to implement the API.  But we are copying APIs from flex-sdk in order 
to retain the ASDoc on the APIs  [...]
+We have created an emulation of UIComponent and several components already.  
Emulation components don't have to retain their Flex class hierarchy if the 
intermediate ancestor classes are not directly used in user code.  For example, 
mx:Application currently just subclasses Container instead of LayoutContainer.  
Really, the goal is to toss out as much Flex code as we possibly can and use 
Royale beads instead to implement the API.  But we are copying APIs from 
flex-sdk in order to retain t [...]
 
 So, I am currently doing the following process:
 
-1) Copy file from flex-sdk.
+1) Visit this GitHub issue and place a check in the checkbox next to the 
components you are going to work on.  You may have to hit the "Edit" button 
first.  I think there is no "Save" button.  Clicking a checkbox seems to save 
it.
+
+2) Copy file from flex-sdk.
 
 2) Comment out all import statements and "use namespace mx_internal".
 
@@ -35,6 +37,8 @@ Flash APIs are not being emulated at this time.  Replace 
DisplayObject, DisplayO
 
 You may need to add an API for a Flash API to UIComponent or some other 
low-level ancestor class like Button.
 
+It should be rare to need to emulate an mx_internal method, but mx_internal 
should be ok to use.
+
 ### API List
 
 This is the list of APIs we know users are using.  Bold lines have been 
implemented.  Strike-through means that there is currently no plans to emulate. 
 The number after each API is a relative number of how often it was used in the 
applications that we have data on.

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

Reply via email to