Thank you for visiting the BlackBerry Support Community Forums.
BlackBerry will be closing the BlackBerry Support Community Forums Device Forums on April 1st (Developers, see below)
BlackBerry remains committed to providing excellent customer support to our customers. We are delighted to direct you to the CrackBerry Forums, a well-established and thorough support channel, for continued BlackBerry support. Please visit http://forums.crackberry.com or http://crackberry.com/ask. You can also continue to visit BlackBerry Support or the BlackBerry Knowledge Base for official support options available for your BlackBerry Smartphone.
"When we launched CrackBerry.com 10 years ago, we set out to make it a fun and useful destination where BlackBerry Smartphone owners could share their excitement and learn to unleash the full potential of their BlackBerry. A decade later, the CrackBerry community is as active and passionate as ever and I know our knowledgeable members and volunteers will be excited to welcome and assist more BlackBerry owners with their questions."
- Kevin Michaluk, Founder, CrackBerry.com
Developers, for more information about the BlackBerry Developer Community please review Join the Conversation on the BlackBerry Developer Community Forums found on Inside BlackBerry.
08-28-2012 12:28 AM
08-28-2012 01:26 AM
08-29-2012 01:47 AM
08-29-2012 05:33 AM
Ever tried to use the image as your splash screen image? Have a look to the config.xml documentation here: https://developer.blackberry.com/html5/documentati
08-29-2012 05:09 PM
no it needs to be part of the page. Its the background if that is the splash screen people will start clicking on it and tell me the app lags. Thats not an acceptable solution.
08-30-2012 01:20 AM
If it's the background you might want to decrease the size of that image. If it's a background people will start clicking on it, it might be possible to have the same effect in HTML+JS+CSS using a button only, maybe with a smaller image?
08-30-2012 05:04 PM
08-31-2012 01:38 AM
I think caching is only available if an app is running. If you close the app, cache will be released for other things so it things might need to be loaded next time the app is starting again.
By this it depends on your use case. I'm working on a customer project where the app/content needs to translated before user should be able to do something. This is done by presenting the first screen, add a CSS shader over it with a small loading indicator and if all things done and loaded to get started the shader and loading indicator becomes hidden.
So I do not know how your source code looks like, mainly in the header where you load all your JS + CSS and so on. Maybe you can change something to load the image first and then load all the other content.