fljot
PanGesture miss computed velocity property
Well it doesn't really "miss". It would be an overhead to always calculate velocity, so I had in plan to have this kind of utility class that calculates velocities (using low-pass mathematical filter or weighted average) so you could use whenever you actually need. And gestures themselves should stay as quick and light as possible.
It make total sense , I agree. Do you have any plan to add this utility class or other features ?
My usecase is to build a scrollable container with throw effect / bounce (mimic the iOS UIScrollView basically) and because I would like to use Gestouch for my app, I thought that having velocity in PanGesture was making sense. I think it is kind-of essential to have this utility class to calculate velocities etc. Hope it make sense and definitely hope that you'll add this soon :)
At the moment I don't have time to work on that, but I call you up to put your efforts in here https://github.com/fljot/TouchScrolling/tree/features/decoupled-architecture
Is TouchScrolling in this branch is flex independent ? I'm not using Flex on my current project. I didn't deeply check your code but i can see MXML files and spark classes.
There are some examples, interface is done with mxml. But scrolling itself is basically Flex independent. Might have some dependencies on some standalone spark classes, but it doesn't pull the rest of Flex.