Refactors gesture conversion functions to ui/events/blink

Refactors gesture conversion functions to ui/events/blink

We want to use this from html_viewer, which can't depend on content.

BUG=none
TEST=none
R=jam@chromium.org, sadrul@chromium.org, dglazkov@chromium.org

Committed: https://crrev.com/83e08f5e90e017aa7dd9daa60cce84a242e631c8
Cr-Commit-Position: refs/heads/master@{#322582}

[sky, 2015-03-25 21:34:40]

john: content/
sadrul: making sure you're ok with this in ui/events/blink
jochen: DEPS include of webkit in ui/events/DEPS

[sky, 2015-03-25 22:14:55]

Naming and where to put stuff is always tricky. I could see at least two
possibilities for directory structures for refactoring like this:

1. Create child directories that depend upon blink as I've done here. This is
nice in that the functionality is logically grouped with related functionality.
This approach is a bit confusing in that it's easy to miss the DEP on blink the
directory has.

2. Create a new top level directory that has a dep on blink with child
directories used to group related functionality. For example,
blink_no_content/events. blink_no_content isn't the name we really want, but you
get the idea. Such a directory structure is nice in that it makes it clear the
files in this directory can depend upon blink, but the grouping based on
dependency feels a bit arbitrary.

I've gone with 1, but am of course open to whatever.

[sadrul, 2015-03-25 22:19:33]

I prefer option 1 too. lgtm

https://codereview.chromium.org/1034713004/diff/50019/ui/events/blink/DEPS
File ui/events/blink/DEPS (right):

https://codereview.chromium.org/1034713004/diff/50019/ui/events/blink/DEPS#ne...
ui/events/blink/DEPS:2: "+third_party/WebKit/public/platform",
We probably don't need platform here.

[jochen (gone - plz use gerrit), 2015-03-26 15:36:52]

ui/events might end up in browser, right?

In that case, we can't blanket allow all public/web headers, but should list the
ones we need (and make sure they're just enum/POD headers, see
chrome/browser/DEPS

[jam, 2015-03-26 15:43:40]

lgtm

[sky, 2015-03-26 17:07:35]

On 2015/03/26 15:36:52, jochen wrote:
> ui/events might end up in browser, right?
> 
> In that case, we can't blanket allow all public/web headers, but should list
the
> ones we need (and make sure they're just enum/POD headers, see
> chrome/browser/DEPS

Updated. Although if you look at blink_event_util you can see that it's actually
creating WebInputEvents. But this is just a move, and we were already doing this
in the browser.

[jochen (gone - plz use gerrit), 2015-03-27 14:43:20]

lgtm

[sky, 2015-03-27 15:38:38]

The CQ bit was checked by sky@chromium.org

[sky, 2015-03-27 15:38:39]

The patchset sent to the CQ was uploaded after l-g-t-m from sadrul@chromium.org,
jam@chromium.org
Link to the patchset: https://codereview.chromium.org/1034713004/#ps100001
(title: "specific dep")

[commit-bot: I haz the power, 2015-03-27 15:39:13]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1034713004/100001

[commit-bot: I haz the power, 2015-03-27 15:42:56]

Committed patchset #7 (id:100001)

[commit-bot: I haz the power, 2015-03-27 15:43:32]

Patchset 7 (id:??) landed as
https://crrev.com/83e08f5e90e017aa7dd9daa60cce84a242e631c8
Cr-Commit-Position: refs/heads/master@{#322582}

[sky, 2015-04-02 17:29:41]

sky@chromium.org changed reviewers:
+ dglazkov@chromium.org
- jochen@chromium.org