Optimise scrolling with PostLayoutListener by using object pools

[Kisty]

Love this lib! It's brilliant!

Every time a scroll occurs, ItemTransformation objects are created per view per scroll. This use of creating many ItemTransformation objects a lot of the time, it makes the GC fire off many times and therefore, you see jank. If an object pool is used, it would mean that the GC won't be fired constantly.

This would look something like adding a method to ItemTransformation.obtain(scaleX,scaleY,translationX,translationY) and using an object pool internally to get objects. Then once it's been used, just call release method on object and that tells the system it can be recycled.

Colt McAnlis explains the concept here: https://www.youtube.com/watch?v=bSOREVMEFnM

What do you think? Is it something worth exploring?

[mig35]

Hi @Kisty, again :). As I told before I'll try to find some free time to solve this issue, but I'm not sure when.
Best wishes, Mike.