There are two ways to dismiss SplashScreen in Cordova 1) App developers can decide when close splash screen by js : navigator.splashscreen.hide() 2) By timeout Why we need the timeout, I think it’s the final chance to dismiss the splash screen, when there are some errors occurred on Runtime or Web app.
Similar solution for Crosswalk runtime, I think we need to provide two ways 1) When first visible page occurred, dismiss the SplashScreen (By some mechanism in runtime) 2) By timeout Or the timeout can't be configured by the users, Can we make it build-in (few seconds)? -----Original Message----- From: He, Xinchao Sent: Friday, December 27, 2013 4:37 PM To: Li, Guangzhen Cc: Zhu, Yongsheng; Wang, Shiliu; [email protected] Subject: Re: [Crosswalk-dev] Intent to implement - SplashScreen API for xwalk based application. For Crosswalk runtime model side, I don't think we need a "timeout" property here, the WRT should decide how long will the splash screen displaying, and for different device, the timeout value should be also different, given a fixed splash screen timeout value is not an acceptable solution I think. "Li, Guangzhen" <[email protected]> writes: > Thanks for your review for Tizen side. > Below is just my draft proposal, need to get more feedback and discussion > from both sides. > The images for xhdpi/hdpi/mdpi/ldpi are both optional in Android. > Agree with you, we can provide only land/port firstly. > > The proposal changed to: > > “splashscreen”: { > “landscape”: “splashscreen_land.png”, > “portrait”: “splashscreen_port.png”, > "timeout": "3000" > } > > I have add another item "timeout" > > Any comments? > > -----Original Message----- > From: He, Xinchao > Sent: Friday, December 27, 2013 3:40 PM > To: Li, Guangzhen > Cc: Wang, Shiliu; [email protected] > Subject: Re: [Crosswalk-dev] Intent to implement - SplashScreen API for xwalk > based application. > > Hi Guangzhen, > Your splashscreen proposal in manifest.json looks like an Android > style, what's about Tizen and other platforms? IMO, only have one or > at most two (port/land) images defined in splashscreen field should be > more reasonable, and in Crosswalk Android port, such kinds of images > (xhdpi/hdpi/mdpi/ldpi) should be generated by make_apk.py at application > package build time. WDYT? > > "Li, Guangzhen" <[email protected]> writes: > >> Hi Shiliu, >> >> Below is my plan: >> >> There should be a configuration in manifest.json >> >> Such as >> >> …. >> >> “splashscreen”: { >> >> “land-xhdpi”: “splashscreen_land_xhdpi.png”, >> >> “port-xhdpi”: “splashscreen_port_xhdpi.png”, >> >> “land-hdpi”: “****.png”, >> >> “land-ldpi”: “****.png”, >> >> “land-mdpi”: “****.png”, >> >> “port-hdpi”: “****.png”, >> >> “port -ldpi”: “****.png”, >> >> “port -mdpi”: “****.png” >> >> } >> >> …. >> >> We can copy these png files to each drawable folder such as >> [drawable-land-xhdpi] with same file name splashscreen.png. >> >> In the template project code, we use the same resources like >> R.drawable.splashscreen, System will automatically switch the resources when >> orientation changed. >> >> If no “splashscreen” provided in configuration, we need to change the >> code by script. >> >> There are currently some source code in XWalk_app_template will be modified >> by make_apk.py at build time, So I think it’s workable. _______________________________________________ Crosswalk-dev mailing list [email protected] https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev
