I finally took the time to fix some nasty bugs that were infesting iScroll. This has been the most important bugs hunting session since v3.0. Hurry up, take it while is hot.
One of the most important features has been finally added to iScroll: please welcome the snap scroll. The scrolling area is subdivided into pages and you may choose to scroll to any page both programmatically and with user swipes. The code has been further optimized so that the new feature doesn’t impact on file size nor performance.
The most requested feature for iScroll was probably the ability to programmatically scroll to an element by #id. v3.5 adds this feature and much more. You can actually scroll to any element from a CSS3 query selector opening the door to hardware accelerated carousels.
Frameworks for mobile platforms are coming out quickly. What was pioneering not more than two months ago is now everybody’s land. In this scenario does it still make sense to develop stand alone scripts like iScroll? Short answer: yes.
This latest update brings even better Android compatibility. If I receive no complains I’d consider this release final, freeze the code and move to the next milestone (3.4).
Android is a bad beast but we’ll tame it. My quest to get full Android compatibility continues and this time we are getting pretty close to it. Once again I need beta testers!
You asked for it and now you have it. v3.3 (beta 1) is my first attempt to port iScroll to Android 1.5. It seems to work, but no hardware acceleration. Is it really worth the effort?
Don’t you hate your own code 3 weeks later? I do. I finally tidied up iScroll code and managed to remove some insidious bugs. Please welcome version 3.2: smaller, faster, smarter.
The Slide-in menu exits alpha stage, gets Android compatibility and it’s finally ready for production.