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 38d878d Updated Emulation Components (markdown)
38d878d is described below
commit 38d878d6a93179cfb26f70d7f79f444f570aeed1
Author: aharui <[email protected]>
AuthorDate: Thu Jan 9 01:16:59 2020 -0800
Updated Emulation Components (markdown)
---
Emulation-Components.md | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/Emulation-Components.md b/Emulation-Components.md
index 0ad976c..7720be4 100644
--- a/Emulation-Components.md
+++ b/Emulation-Components.md
@@ -16,7 +16,7 @@ The plan is to quickly create classes with stubs for APIs we
know our migrating
The rest of this document was written back when all we were doing is creating
emulation components that wrapped HTMLElements. Lately, more and more
components and features are being developed in a different approach. That
approach is described in [Creating A High-level Emulation
Component](creating-a-high-level-emulation-component)
-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.
+When creating a lower-level emulation component, we first 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. That way you will
hopefully discover that only a subse [...]
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 [...]
@@ -61,7 +61,7 @@ Infrastructure (commitProperties, measure, updateDisplayList,
etc should not be
Some imports can be replaced with Royale imports like org.apache.royale.geom
and org.apache.royale.events
-Flash APIs are not being emulated at this time. Replace DisplayObject,
DisplayObjectContainer, Sprite with IUIComponent or UIComponent
+Most Flash APIs are not being emulated at this time. Replace DisplayObject,
DisplayObjectContainer, Sprite with IUIComponent or UIComponent. Some Flash
APIs have mx.*.* emulations.
You may need to add an API for a Flash API to UIComponent or some other
low-level ancestor class like Button.
@@ -2244,4 +2244,3 @@ The current set of running components are not finished.
They do not appear on t
We haven't finished any component yet. As we do so and better understand good
practices for doing so, we will update this section. But first, we want to see
if we can get a migrated app to launch and put something up on the screen
without any exceptions being thrown.
-
