There is prior art in the area of splash screens; you guys shouldn't have to
reinvent this concept. In particular, there is a standard Cordova API for
splash screens. The latest version of the documentation can be found here:
http://docs.phonegap.com/en/3.3.0/cordova_splashscreen_splashscreen.md.html.
Please read this and touch base with Tony Homer in the XDK project to make sure
that Crosswalk aligns with the XDK in this area.
FYI, splash screens are not simply a kludge to cover up the fact that apps are
slow. HTML documents are rendered incrementally, so UI controls often appear
before it is really safe to use them. There are MANY web sites that behave
badly if you start entering text or operating menus before the app is ready.
Putting up a splash screen until the app is ready is a natural and reliable way
to fix bugs like that. It's a lot simpler than putting special checks all over
the place. This problem is even worse in mobile apps, because drivers may
require a warm up period before the corresponding devices can be used. All
Cordova apps are requires to wait until the "deviceready" event is fired before
any Cordova API functions can be called. This pretty much means that every
Cordova App must have a splash screen.
Getting the splash screen to appear on startup is tricky. As mentioned above,
you can't call the Cordova API to raise the splash screen,
navigator.splashscreen.show, until the deviceready event arrives, which would
seem to defeat the purpose of a splash screen. Cordova solves this problem
with a build-time configuration option that is stored in the Cordova config.xml
file. The Intel XDK API raises a splash screen by default. Again, I recommend
you touch base with Tony to make sure your implementation aligns.
Julian
_______________________________________________
Crosswalk-dev mailing list
[email protected]
https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev
