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.
03-13-2012 08:34 PM
I'm a bit stumped with my latest problem. My WebWorks App uses JQuery 1-6.1 and JQuery UI 1.8.13 for UI features, DOM manipulation, and AJAX querying. The situation is when the user requests data via an AJAX call to a web service my application then takes a stored HTML string and updates the string with the returned data. Then using JQuery it adds this HTML to the DOM by using $("table#mainTable").prepend(html).hide().fadeIn(1
I thought maybe there were hung AJAX calls so I overrode the close logic to call the .abort() function call on all possible queries if they weren't already set to null. This still didn't seem to work. Does anyone have any insight or ideas?
03-13-2012 09:23 PM
It has to do with the garbage clean-up that occurs with webworks. It used to happen when memory usage changed more than 5 or 10% but that caused apps to delay on start-up and random points during execution. To deal with that it now runs on close. So it is out of your control at the moment, but I belive there are more improvements coming with WW 2.4.
The delay probably gets longer as you load more data into the app.
03-13-2012 09:44 PM
That would make sense, my app does use a lot of data. Has there been any word on the street as to when WW 2.4 might be coming out? The problem has been severe enough I've considered redoing the phone version of my app with Java.
03-13-2012 10:08 PM
03-13-2012 10:22 PM
03-14-2012 01:22 AM