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.
11-12-2009 12:39 PM
Within the widgets, if I navigate to a page running on an external server, but running in the widget... is it possible to link back to a local widget page from the remote page?
If I use a local:/// tag will this work?
11-12-2009 02:26 PM
OK I just answered this myself... it works perfectly!
Lets say I have a link in a widget page to a remote page, example:
Once I'm on the remote page, all I need to do to get back to the local page is:
<a href="local:///localpage.html">Link back to local</a>
Good job RIM
11-12-2009 11:31 PM
so you can do something like:
<img src="local:///img/myimg.png" />
In the page you are serving up from your website
It gives you lots of deployment possibilities
11-12-2009 11:35 PM
Yes! I already discovered that and tested it... haha it works very well...
The only thing I wish was better right now is that page loading is quicker in the browser than the widget... for example:
Browser load time: 4~5 seconds
Widget load time: 12~14 seconds
Is this all because of caching not enabled in the browser yet? Or is there more to it?
11-13-2009 12:13 AM
There are a couple of reasons for this..
1) When you launch a widget for the first time it needs to initialize the browser engine. Much like the first time you load Firefox on your desktop. Then when you load subsequent pages it is fast. Our BlackBerry Browser cheats a little in the fact that it has started in the background when the device boots
2) The lack of caching means that any remote resources are going to always be pulled from the network. We are currently working on the caching capability so it is on the way
Once you have your widget open, pulling in an external page that hasn't been cached should be comparable to loading it in the browser.
We also demonstrated some Loading screens at the Developer Conference where we even demonstrated screen transitions between loading states. So there's lots to come
11-13-2009 12:19 AM
Yeah the non cached pages seem to load about the same, but from there the browser wins with the caching...
I really hope you guys get it soon, I feel the aching is the only real slight problem I see now...
And there ya go teasing me with the tranisions and such... haha wish I could have made it out to Dev Con