evince-gesture: support flick gestures

[Duncan McGreggor]

The use-case mapper for evince with gestures defines the following use cases that aren't currently supported:
 * User flicks between pages - http://use-case-mapper.canonical.com/specifications/0AU5sFuLRpCpBZGZra2pqY2pfMTU3MmhwbXczcWQ1/use_cases/4_3
 * User flicks through document - http://use-case-mapper.canonical.com/specifications/0AU5sFuLRpCpBZGZra2pqY2pfMTU3MmhwbXczcWQ1/use_cases/4_4

Let's get this added to evince-gesture.

[Duncan McGreggor (oubiwann)]

It's my understanding from Chase and Henrik that they don't see flicks as a gesture primitive. In which case, we either need to start adding another layer to GEIS to support special-cased gestures that aren't primitives, or we need to put flick logic in the toolkits. If this needs to go in GEIS, I'll open a separate ticket for that.

[Duncan McGreggor (oubiwann)]

Okay, it looks like there consensus that the flick definitions belong in GEIS somewhere. This ticket, then is currently blocked on that. As soon as flick support is in GEIS, we can move forward with support in evince-gesture. I've created a GEIS ticket for this (bug #674682).

[Duncan McGreggor (oubiwann)]

Update from yesterday: Stephen is going to add flick support to GEIS.

[Duncan McGreggor (oubiwann)]

Current support is to flick a single page.

[Duncan McGreggor (oubiwann)]

Stephen will get a FFE exception for the new flick (he's got a patch for supporting it). I will assign this ticket to him.

Stephen, when flick support lands, assign back to me (Cody will be gone).

[Chase Douglas (chasedouglas)]

This is a known deficiency in the implementation of the touch specifications, but it is not being actively worked on. Rather than leave this open as in active bug, I am marking it was won't fix for now. We don't really use bug tasks for normal feature development anymore.