Thank you for visiting the BlackBerry Support Community Forums.
BlackBerry will be closing the BlackBerry Support Community Forums on April 1st. 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
07-14-2011 07:40 AM
From my experiments, it appears that its not just gradients that stop hw acceleration. For example, just adding form elements to the content that is to be animated for me also stops hw acceleration. As mentioned i have got hw acceleration working fine in very simple projects (static jpg etc) but as soon as i try and apply this to "real world" content, ie. paras of text, form elements etc the choppy animations are back!
I for one would be very interested in seeing the project you mention - is it animating "real world" full page content? When might this project be available to view? Thanks.
07-14-2011 08:47 AM
We're working on getting the project out there as an open source sample on github. Hopefully within the next few weeks it will be up there. It's currently known as "Alice" as in "Alice in Wonderland"...
I have personally seen it hardware accelerate animations with form elements and a whole lot of other things
07-14-2011 10:10 AM
@tneil it SHOULD, but unfortunately at times it fails miserably. Especially when trying to animate a structure of elements rather than just one or two. There's an active bug open for this. Hope it gets fixed soon because right now as soon as the stuff you try to animate approaches real-world complexity the hardware acceleration fails.
Staff UI Prototyper (read: full-time hacker)
07-16-2011 11:43 AM
I've got "-webkit-transform: translate3d(0px, 0px, 0px);" declarations for my scrolling panes, but based on what I've read above it sounds like I've probably got content that's too complicated or has elements in it that currently breaks hardware acceleration.
I hope RIM is/will make this a priority fix, as this really would help WebWorks apps pull even in useability with the other frameworks in place for the PlayBook.
07-17-2011 07:03 AM
If you are trying to use something like iScroll to make "smooth scrolling" work it is actually getting in the way of the PlayBook's built in smooth scrolling.
Full kinetic scrolling is built into the scrolling of the main page as well as any content of a div or iframe that has scrollable areas.
07-19-2011 04:02 PM - edited 07-19-2011 04:04 PM
I have no issues with iScroll, in fact it scrolls much smoother than the native "kinect" scrolling. I am using the following:
Latest update 1.0.7 has made my application snappier!! keep it up RIM!
Q: tneil, any change you can show me an example of a scrolling div which is natively elastic? I have been trying but only the main page scrolls elasticaly, contents within div do not.
07-19-2011 04:24 PM - edited 07-19-2011 04:25 PM
anzorb, you're using jQuery Mobile + iScroll 4 for PlayCentre? That's very interesting - I just loaded your app onto my PlayBook and it is indeed a good performer. Perhaps I need to take another look at using jQuery Mobile. Can you offer any tips on getting the scrolling as smooth as you've gotten it?
07-19-2011 11:19 PM - edited 07-19-2011 11:21 PM
07-20-2011 09:46 AM