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 04:42:32 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 333139e  Updated Emulation Components (markdown)
333139e is described below

commit 333139e6055d7cf25447cf08445dc0005e433a78
Author: aharui <aharui@apache.org>
AuthorDate: Sun Apr 8 21:42:30 2018 -0700

    Updated Emulation Components (markdown)
---
 Emulation-Components.md | 10 +++++++++-
 1 file changed, 9 insertions(+), 1 deletion(-)

diff --git a/Emulation-Components.md b/Emulation-Components.md
index 79de42f..7caf0cf 100644
--- a/Emulation-Components.md
+++ b/Emulation-Components.md
@@ -31,7 +31,15 @@ If APIs are not in list, delete them unless you know they are needed to
implemen
 
 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.
 
-###Things to keep in mind:
+8) 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.
 
+flash.events.EventDispatcher should be replaced by org.apache.flex.events.EventDispatcher.
   
+
+The internal implementation can still use flash.*.* if it is in COMPILE::SWF blocks.
+
+### Things to keep in mind:
 
 Infrastructure (commitProperties, measure, updateDisplayList, etc should not be preserved.
 Remove it.  We expect the underlying Basic or Express component and beads will effectively
result in the same visuals.  We keep invalidateProperties, invalidateSize and invalidateDisplayList
because it is called from app code.  I think it can just do nothing.  We'll figure that out
later.
 

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

Mime
View raw message