-----Original Message-----
From: Crosswalk-dev
[mailto:crosswalk-dev-boun...@lists.crosswalk-project.org]
On Behalf Of Ming, Bai
Sent: Tuesday, December 24, 2013 9:42 AM
To: crosswalk-dev@lists.crosswalk-project.org
Subject: Re: [Crosswalk-dev] Intent to implement - SplashScreen API
for xwalk based application.
I've a done a test several months before for my shared process mode
patch, by loading a simple html hello world page:
current: about 1.5s
shared mode: about <1s
it's on Tizen/PR3
- Ming, Bai
On 12/24/2013 09:26 AM, Wang, Shiliu wrote:
Creating splashscreen using JS can't cover the period of time that
xwalk spend
to load native library and resources. Guangzheng/Junmin, could you
provide the data that how long it cost normally?
Thus, splash screen isn't that user unfriendly, at least it's better
than a black
screen/white screen at application's startup time. As long as it
keeps for a reasonable time.
Thanks,
Shiliu.
-----Original Message-----
From: Crosswalk-dev
[mailto:crosswalk-dev-boun...@lists.crosswalk-project.org] On Behalf
Of Kenneth Rohde Christiansen
Sent: Monday, December 23, 2013 7:34 PM
To: Waterman, Max
Cc: <crosswalk-dev@lists.crosswalk-project.org>
Subject: Re: [Crosswalk-dev] Intent to implement - SplashScreen API
for xwalk
based application.
I think that is why there should be some max time before initial
layout finished,
like say 300ms. If the app didn't finish initial layout at that time
the window will show anyway. That way you should have time to show a
simplified UI of your app, or a splashscreen (done with JS + some
background picture etc), and badly behaved apps will still show up
quickly, though their use experience won't be that good.
Also when creating a splashscreen you most often want it to fade
nicely into your read UI. That is what happens on iOS and is
possible to do with creating the splashscreen manually using JS and
HTML/CSS
On Mon, Dec 23, 2013 at 12:11 PM, Max Waterman
<max.water...@intel.com>
wrote:
On 23/12/13 17:50, Kenneth Rohde Christiansen wrote:
A combination of those two methods might be a better solution, or
could at least be researched.
IMO, that sounds like a much better solution.
Splashscreens always seemed like a bit of a cludge to me - just
covering up slowness that should be made faster or removed completely.
I do wonder how it would look to a user though - if the app is
particularly slow to start, then it will look as if the user hasn't
tapped the app icon properly and result in him/her tapping multiple times?
Worth looking into, though, for sure.
I hope someone is looking into how to minimise the time from the
first tap on the app's icon to the app actually starting - imo,
that's the real
issue.
Max.
_______________________________________________
Crosswalk-dev mailing list
Crosswalk-dev@lists.crosswalk-project.org
https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev
--
Kenneth Rohde Christiansen
Web Platform Architect, Intel Corporation.
Phone +45 4294 9458 ﹆﹆﹆
_______________________________________________
Crosswalk-dev mailing list
Crosswalk-dev@lists.crosswalk-project.org
https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev
_______________________________________________
Crosswalk-dev mailing list
Crosswalk-dev@lists.crosswalk-project.org
https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev
_______________________________________________
Crosswalk-dev mailing list
Crosswalk-dev@lists.crosswalk-project.org
https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev
