Ok, I see. Then do you consider the splash screen for OS to setup xwalk. Like usually on Android, achieved by setting android:windowBackground.
Thanks, Shiliu. From: Li, Guangzhen Sent: Monday, December 23, 2013 11:26 AM To: Wang, Shiliu; Zhu, Junmin; crosswalk-dev@lists.crosswalk-project.org Subject: RE: [Crosswalk-dev] Intent to implement - SplashScreen API for xwalk based application. Hi Shiliu, Our current planning is to display the splash screen when application startup, So the two parts will be both included. From: Crosswalk-dev [mailto:crosswalk-dev-boun...@lists.crosswalk-project.org] On Behalf Of Wang, Shiliu Sent: Monday, December 23, 2013 10:55 AM To: Zhu, Junmin; crosswalk-dev@lists.crosswalk-project.org<mailto:crosswalk-dev@lists.crosswalk-project.org> Subject: Re: [Crosswalk-dev] Intent to implement - SplashScreen API for xwalk based application. The implementation details are only for the second part of startup time you mentioned right? What about the first part? Is it short enough for xwalk to ignore? Thanks, Shiliu. From: Crosswalk-dev [mailto:crosswalk-dev-boun...@lists.crosswalk-project.org] On Behalf Of Zhu, Junmin Sent: Friday, December 20, 2013 10:37 AM To: crosswalk-dev@lists.crosswalk-project.org<mailto:crosswalk-dev@lists.crosswalk-project.org> Subject: [Crosswalk-dev] Intent to implement - SplashScreen API for xwalk based application. Description: Xwalk based application takes too long times to show the web page at the startup. It only shows the blank screen during this time currently. It's not user friendly. I want to supply the unified SplashScreen API in manifest, which allows developer to provide screen image for application during the startup. Note that, the application startup time is composited by two parts. First is the Xwalk's startup time, including loading native library and Xwalk's resource file etc. Second is the application start up time, including the loading application's resource and rendering the page etc. Affected component: 1. Android port. 2. Tizen port. 3. Manifest API spec. Related feature: (Jira ID) https://crosswalk-project.org/jira/browse/XWALK-637 Target Release: (Crosswalk N) Crosswalk 4 Implementation details: To achieve this, two parts of implementation is needed. 1. For preparing step, we need to get SplashScreen image from manifest, and show it when it is set in the manifest. Android port: a. Add parser support for this new API in the packaging tool (make_apk.py). b. Add mechanism to show/hide the SplashScreen image (xwalk_app_template). Tizen port: (call for help from Tizen expert) .... 2. For finish step, we need to know the time when page is rendered, and remove the splash screen. a. Common: invoke the client's native callback (such as: OnFirstRenderingReady() ) when the content is updated in the ViewRender first time. b. Android port: 1) provide client's Java callback API; 2) Add JNI mapping between Java callback API and native callback API. c. Tizen port: (call for help from Tizen expert).... Thanks, Junmin.
_______________________________________________ Crosswalk-dev mailing list Crosswalk-dev@lists.crosswalk-project.org https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev
