When scrolling through the pages of a ScrollableView composed out of several 'heavy' views, a noticeable lag occurs halfway scrolling to the next page.
Me and Timan Rebel tracked down the problem and manageCache seems to be the problem. When the nextPage changes half-way, manageCache renders all views within range, instead of just the new view getting into the range. It must be possible to make this more efficient. But even if it's just 1 or 2 views that need to be rendered, if they are heavy, the lag still occurs.
We investigated if the rendering could possibly be delayed until after fully having slide to the next page, but then the lag occurs 1 or 2 pixels before reaching the next page and if you scroll through the pages fast, the rendering won't be triggerd at all. We didn't manage to find a satisfying solution, but I'm sure the Appcelerator iOS experts can