How to add a splash screen in a DwCS6 PhoneGap for Android build?

Question

So I have the new Dw CS6 and want to see what great things DW can do in building Android Apps. So I follow the California Trails demo on Lynda.com. Build it in DreamWeaver, package it with Phonegap and it runs. However, there are some things I'm noticing that happen with this Phonegap that do not happen when I take the SAME files and place them in my Eclipse SDK and build the application under Eclipes.
1) There is a 5 to 9 second delay where a black screen is displayed after the app is launched and when it actually displays the index.html. How do I stop this from happening?
2) How do you add a splach screen? In Eclipes I would add the image to the drawables folders and modify my Activity.java file but we don't have these in DW.
3) How do I get an external URL to display within my Phonegap App? In Eclipes I make the call to the URL while in a WebView but there isn't anything like that in Dw or Phonegap.
4) How do I attach or reference my KeyStore file in these PhoneGap builds so I can put them on Google Play?
Maybe I'm asking too much of Dw and PhoneGap? It this release not intended to create a fully functional app or is it just suppose create a Pseudo App that in reality is a HTML5 webpage made to look like an app? I'm not judging or being critical just trying to find out how or if this Dw feature can be interated in to my workflow.

Answer 1

I assume that you want to show the splash page after every session is initiated after an authentication.
Try this:
Protect the app pages (/app1, /app2 etc) with the following authen scheme:
Level:1
Form:/login.html
Action:/dummy1
Passthrough:no
In the authentication success of this one, have an action:
Authentication success URL: /some_dummy_page.html
Now, protect this url /some_dummy_page.html with the following:
Level:2
Form:/splash_page.html
Action:/dummy2
Passthrough:no
When you access /app1 or /app2, then the first scheme will be invoked, login.html page will come. give your login and password, on successful authen, it will (try to) go to /some_dummy_page.html. but since this one is protected, it will show the splash_page.html. Click on ok, and it will POST to the /dummy2. Because the action in both the schemes are different, the obformlogin cookie will persist.
You will need to have the action in the splash page to point to /dummy2.
Hope this helps. Let us know.