Thanks for the explanation. LGTM. Thanks, Shiliu.
From: Huo, Halton Sent: Wednesday, July 9, 2014 4:27 PM To: Wang, Shiliu; crosswalk-dev@lists.crosswalk-project.org Subject: RE: [Crosswalk-dev] Intent to Implement - Pluggable extensions for embedding API No, if an extension is created like new EchoExtension, the extension will be registered to the native(C++) extension service automatically, this is already done in XWalkExtensionAndroid and JNI code as well. Thanks, Halton. From: Wang, Shiliu Sent: Wednesday, July 09, 2014 3:37 PM To: Huo, Halton; crosswalk-dev@lists.crosswalk-project.org<mailto:crosswalk-dev@lists.crosswalk-project.org> Subject: RE: [Crosswalk-dev] Intent to Implement - Pluggable extensions for embedding API Is there any API to register Extension? Thanks, Shiliu. From: Crosswalk-dev [mailto:crosswalk-dev-boun...@lists.crosswalk-project.org] On Behalf Of Huo, Halton Sent: Wednesday, July 9, 2014 9:21 AM To: crosswalk-dev@lists.crosswalk-project.org<mailto:crosswalk-dev@lists.crosswalk-project.org> Subject: [Crosswalk-dev] Intent to Implement - Pluggable extensions for embedding API Description: This feature is Android only. So far, pluggable android extension[1] is supported for runtime mode(shared or embedded). After embedding API[2] supporting is added in, there is clear need to add this support pluggable extension support for embedding API as well. Affected component: XWalk embedding API XWalk embedding API document and test case Related feature: https://crosswalk-project.org/jira/browse/XWALK-1052 Target release: Crosswalk8 Implementation details: Android extension is rely on org.xwalk.core.internal.extensions.XWalkExtensionAndroid to bridge all Java instances via C++ extension instances to JS side and vice versa. XWalkExtension will be exposed in Embedding API public XWalkExtensionAndroid(String name, String jsApi) public XWalkExtensionAndroid(String name, String jsApi, String[] entryPoints) protected void destroyExtension() public void postMessage(int instanceID, String message) public void broadcastMessage(String message) public abstract void onMessage(int instanceID, String message) public abstract String onSyncMessage(int instanceID, String message) Internally, it will call org.xwalk.core.internal.extensions.XWalkExtensionAndroid. Difference with runtime extensions: * The life cycle related APIs(onPause, onResume, etc) are not provided. This is mainly because the responsibility of life cycle handling for embedding API and runtime are different For embedding API. Embedder(embedding API) own the extension instance reference and decide what to do, while runtime layer. While for runtime, extension reference is handled inside runtime, which means hidden for runtime user, so we need offer the life cycle APIs. * There will be no helper like make_apk.py for embedding API, embeedder is responsible to add extension jar to workspace. The document for that. * Despite the life cycle API, the extension code for embedding and runtime should very similar but not compatible because the based interface are different. If extension developer want to support both embedding API and runtime layer, we might offer a tooling or HOWTO. References: [1] https://crosswalk-project.org/#documentation/android_extensions [2] https://crosswalk-project.org/#documentation/embedding_crosswalk Thanks, Halton.
_______________________________________________ Crosswalk-dev mailing list Crosswalk-dev@lists.crosswalk-project.org https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev
