royale-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From aha...@apache.org
Subject [royale-asjs.wiki] branch master updated: Updated Emulation Components (markdown)
Date Mon, 09 Apr 2018 17:39:23 GMT
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 80250d1  Updated Emulation Components (markdown)
80250d1 is described below

commit 80250d1ba9d19938bb16b4cc54d6eab807f6cf9c
Author: aharui <aharui@apache.org>
AuthorDate: Mon Apr 9 10:39:21 2018 -0700

    Updated Emulation Components (markdown)
---
 Emulation-Components.md | 16 +++++++++-------
 1 file changed, 9 insertions(+), 7 deletions(-)

diff --git a/Emulation-Components.md b/Emulation-Components.md
index 6fdea73..f5986fa 100644
--- a/Emulation-Components.md
+++ b/Emulation-Components.md
@@ -12,12 +12,14 @@ So, I am currently doing the following process:
 
 2) Copy file from flex-sdk to the proper folder in the frameworks/projects/MXRoyale folders.
 UIComponent is in frameworks/projects/MXRoyale/src/main/royale/mx/core/UIComponent, for example.
 
-2) Comment out all import statements and "use namespace mx_internal".
+3) Comment out all import statements and "use namespace mx_internal".
 
-3) Search the API list report:  Delete everything not mentioned.  Sometimes a subclass will
be using that API in which case it should be kept.  Events should be in the report so delete
unmentioned events.
+4) Comment out all [Style] metadata.  The few styles folks need we will implement as properties.
 At least, that's the plan for now.  This is because Flex CSS is not browser CSS compliant.
+
+5) Search the API list report:  Delete everything not mentioned.  Sometimes a subclass will
be using that API in which case it should be kept.  Events should be in the report so delete
unmentioned events.
 If APIs are not in list, delete them unless you know they are needed to implement something
that is used.
 
-4) If the current implementation won't work, replace with:
+6) If the current implementation won't work, replace with:
 
 ```
   //To Do
@@ -25,13 +27,13 @@ If APIs are not in list, delete them unless you know they are needed to
implemen
      trace("<name of api> is not implemented");
 ```
 
-5) If you need to return a value, just pick a reasonable value for now.
+7) If you need to return a value, just pick a reasonable value for now.
 
-6) If the component is used in MXML, add it to src/main/resources/mx-royale-manifest.xml.
 If not (an Event or helper class), add it to src/main/royale/MXRoyaleClasses.as
+8) If the component is used in MXML, add it to src/main/resources/mx-royale-manifest.xml.
 If not (an Event or helper class), add it to src/main/royale/MXRoyaleClasses.as
 
-7) Make sure it compiles without warnings.  You can use @royalesuppresspublicvarwarning in
an ASDoc comment to suppress public var warnings for public vars that are not used in handling
server data.  See ListEvent.as for an example.
+9) Make sure it compiles without warnings.  You can use @royalesuppresspublicvarwarning in
an ASDoc comment to suppress public var warnings for public vars that are not used in handling
server data.  See ListEvent.as for an example.
 
-8) References to `flash.events.Event` in API surfaces like parameters and return types should
be replaced by `org.apache.flex.events.Event`.  Also:
+10) References to `flash.events.Event` in API surfaces like parameters and return types should
be replaced by `org.apache.flex.events.Event`.  Also:
 
 `flash.events.MouseEvent` should be replaced by `org.apache.flex.events.MouseEvent`.  
 `flash.events.IEventDispatcher` should be replaced by `org.apache.flex.events.IEventDispatcher`.
 

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

Mime
View raw message