ImageCapture: move mojom from WebKit/public to media/

ImageCapture: move mojom from WebKit/public to media/

This CL moves image_capture.mojom from
{third_party/WebKit/public/platform/modules => media/mojo/interfaces}
so the generated data types (e.g. PhotoCapabilities{Ptr})
can be used from both Blink and media/capture locations.

Also capture.gypi is trivially relocated to capture/ folder.

Note that gyp files are -yay!- close to being finally
removed.

BUG=518807
CQ_INCLUDE_TRYBOTS=tryserver.blink:linux_blink_rel,mac_blink_rel,win_blink_rel

Committed: https://crrev.com/64aec45d94682ae3b38c0f1c18ff74cd937ff9b5
Cr-Commit-Position: refs/heads/master@{#397644}

[mcasas, 2016-06-01 00:00:24]

Description was changed from

==========
ImageCapture: move mojom from WebKit/public to media/capture

BUG=518807
==========

to

==========
ImageCapture: move mojom from WebKit/public to media/capture

{third_party/WebKit/public/platform/modules => media/capture}

BUG=518807
==========

[mcasas, 2016-06-01 00:16:29]

Patchset #1 (id:1) has been deleted

[mcasas, 2016-06-01 01:10:11]

Description was changed from

==========
ImageCapture: move mojom from WebKit/public to media/capture

{third_party/WebKit/public/platform/modules => media/capture}

BUG=518807
==========

to

==========
ImageCapture: move mojom from WebKit/public to media/capture

This CL moves image_capture.mojom from
{third_party/WebKit/public/platform/modules => media/capture}
so the generated data types (e.g. PhotoCapabilities{Ptr})
can be used from both Blink and media/capture 
locations.

Also capture.gypi is superfluously relocated to
capture/ folder. Note that gyp files are -yay!-
close to being finally removed.

BUG=518807
==========

[mcasas, 2016-06-01 01:28:09]

Description was changed from

==========
ImageCapture: move mojom from WebKit/public to media/capture

This CL moves image_capture.mojom from
{third_party/WebKit/public/platform/modules => media/capture}
so the generated data types (e.g. PhotoCapabilities{Ptr})
can be used from both Blink and media/capture 
locations.

Also capture.gypi is superfluously relocated to
capture/ folder. Note that gyp files are -yay!-
close to being finally removed.

BUG=518807
==========

to

==========
ImageCapture: move mojom from WebKit/public to media/capture

This CL moves image_capture.mojom from
{third_party/WebKit/public/platform/modules => media/capture}
so the generated data types (e.g. PhotoCapabilities{Ptr})
can be used from both Blink and media/capture locations.

Also capture.gypi is trivially relocated to capture/ folder. 

Note that gyp files are -yay!- close to being finally 
removed.

BUG=518807
==========

[mcasas, 2016-06-01 01:31:43]

Description was changed from

==========
ImageCapture: move mojom from WebKit/public to media/capture

This CL moves image_capture.mojom from
{third_party/WebKit/public/platform/modules => media/capture}
so the generated data types (e.g. PhotoCapabilities{Ptr})
can be used from both Blink and media/capture locations.

Also capture.gypi is trivially relocated to capture/ folder. 

Note that gyp files are -yay!- close to being finally 
removed.

BUG=518807
==========

to

==========
ImageCapture: move mojom from WebKit/public to media/capture

This CL moves image_capture.mojom from
{third_party/WebKit/public/platform/modules => media/capture}
so the generated data types (e.g. PhotoCapabilities{Ptr})
can be used from both Blink and media/capture locations.

Also capture.gypi is trivially relocated to capture/ folder. 

Note that gyp files are -yay!- close to being finally 
removed.

BUG=518807
CQ_INCLUDE_TRYBOTS=tryserver.blink:linux_blink_rel,mac_blink_rel,win_blink_rel
==========

[mcasas, 2016-06-01 02:00:11]

Patchset #1 (id:20001) has been deleted

[mcasas, 2016-06-01 17:37:34]

mcasas@chromium.org changed reviewers:
+ rockot@chromium.org

[mcasas, 2016-06-01 17:37:35]

rockot@ PTAL at the concept

(I'll collect the LGTMs for namespace
updates separately).

[mcasas, 2016-06-01 18:37:36]

Patchset #1 (id:40001) has been deleted

[Ken Rockot(use gerrit already), 2016-06-01 19:13:08]

https://codereview.chromium.org/2027023002/diff/60001/media/capture/imagecapt...
File media/capture/imagecapture/image_capture.mojom (right):

https://codereview.chromium.org/2027023002/diff/60001/media/capture/imagecapt...
media/capture/imagecapture/image_capture.mojom:2: // Use of this source code is
governed by a BSD-style license that can be
I think you should just put this in media/mojo/interfaces (or
media/public/interfaces, which is where everything in media/mojo/interfaces
should be moved eventually).

[mcasas, 2016-06-01 19:57:45]

rockot@ PTAL

(I still kept image_capture.mojom separate from
the other mojoms that are selectively compiled)

https://codereview.chromium.org/2027023002/diff/60001/media/capture/imagecapt...
File media/capture/imagecapture/image_capture.mojom (right):

https://codereview.chromium.org/2027023002/diff/60001/media/capture/imagecapt...
media/capture/imagecapture/image_capture.mojom:2: // Use of this source code is
governed by a BSD-style license that can be
On 2016/06/01 19:13:08, Ken Rockot wrote:
> I think you should just put this in media/mojo/interfaces (or
> media/public/interfaces, which is where everything in media/mojo/interfaces
> should be moved eventually).

Done.

[Ken Rockot(use gerrit already), 2016-06-01 20:02:36]

lgtm

On 2016/06/01 at 19:57:45, mcasas wrote:
> rockot@ PTAL
> 
> (I still kept image_capture.mojom separate from
> the other mojoms that are selectively compiled)

I'm not sure there's much value in making a separate target here. A little less
work for the build in some cases, but one more target name to think about... In
any case, I'll defer to OWNERS on that call.

> 
>
https://codereview.chromium.org/2027023002/diff/60001/media/capture/imagecapt...
> File media/capture/imagecapture/image_capture.mojom (right):
> 
>
https://codereview.chromium.org/2027023002/diff/60001/media/capture/imagecapt...
> media/capture/imagecapture/image_capture.mojom:2: // Use of this source code
is governed by a BSD-style license that can be
> On 2016/06/01 19:13:08, Ken Rockot wrote:
> > I think you should just put this in media/mojo/interfaces (or
> > media/public/interfaces, which is where everything in media/mojo/interfaces
> > should be moved eventually).
> 
> Done.

[mcasas, 2016-06-01 20:46:31]

Description was changed from

==========
ImageCapture: move mojom from WebKit/public to media/capture

This CL moves image_capture.mojom from
{third_party/WebKit/public/platform/modules => media/capture}
so the generated data types (e.g. PhotoCapabilities{Ptr})
can be used from both Blink and media/capture locations.

Also capture.gypi is trivially relocated to capture/ folder. 

Note that gyp files are -yay!- close to being finally 
removed.

BUG=518807
CQ_INCLUDE_TRYBOTS=tryserver.blink:linux_blink_rel,mac_blink_rel,win_blink_rel
==========

to

==========
ImageCapture: move mojom from WebKit/public to media/

This CL moves image_capture.mojom from
{third_party/WebKit/public/platform/modules => media/mojo/interfaces}
so the generated data types (e.g. PhotoCapabilities{Ptr})
can be used from both Blink and media/capture locations.

Also capture.gypi is trivially relocated to capture/ folder. 

Note that gyp files are -yay!- close to being finally 
removed.

BUG=518807
CQ_INCLUDE_TRYBOTS=tryserver.blink:linux_blink_rel,mac_blink_rel,win_blink_rel
==========

[mcasas, 2016-06-01 20:55:33]

mcasas@chromium.org changed reviewers:
+ avi@chromium.org, dcheng@chromium.org, haraken@chromium.org,
xhwang@chromium.org

[mcasas, 2016-06-01 20:55:34]

avi@ RS plz content/ changes

xhwang@ RS plz media/ changes

dcheng@ RS added file to media/mojo/interfaces

haraken@ RS plz third_party/WebKit changes

changes are: 
- trivial namespace updates
- gn/gyp dependency update (to media/../imagecapture bindings)

[mcasas, 2016-06-01 20:57:12]

Patchset #2 (id:80001) has been deleted

[dcheng, 2016-06-01 20:59:31]

rs lgtm for mojom move

[Avi (use Gerrit), 2016-06-01 21:08:20]

lgtm

content stamp

[xhwang, 2016-06-01 22:15:03]

+haraken the Blink owner.

hmm, I don't think blink should depend on media, which is kinda of a fundamental
rule that we follow. Even though with this CL blink is still not depending on
the "media" target, but the new DEPS makes me nervous.

In a previous similar discussion
(https://codereview.chromium.org/1838903007/#msg11), we decided that the
(permission) mojom targets shared by chromium and blink should go into
components/. Shall we do the same for image capture? We could have
components/image_capture there holding this mojom interface.

[Ken Rockot(use gerrit already), 2016-06-01 22:32:41]

On 2016/06/01 at 22:15:03, xhwang wrote:
> +haraken the Blink owner.
> 
> hmm, I don't think blink should depend on media, which is kinda of a
fundamental rule that we follow. Even though with this CL blink is still not
depending on the "media" target, but the new DEPS makes me nervous.
> 
> In a previous similar discussion
(https://codereview.chromium.org/1838903007/#msg11), we decided that the
(permission) mojom targets shared by chromium and blink should go into
components/. Shall we do the same for image capture? We could have
components/image_capture there holding this mojom interface.

Complicated issue :)

We have some precedent for top-level dirs exposing new mojom dependencies to
blink (see: //device/usb/public/interfaces used by WebUSB). I'm pretty sure it's
fine, and preferable rather than introducing a new component just for mojom.
That solution would really only make a superficial difference which seems like a
waste of time.

If you're also proposing to move the image_capture implementation code into the
component then it's a stronger case, but I'd argue that the same should be done
for all interfaces exported by media (not necessarily a 1:1 component-per-mojom
file, but some meaningful decomposition into components), leaving media as just
static/component library code, as it probably should be. The same could be said
for the stuff in //device, for what it's worth.

In any case, less work is probably better for now IMHO, so I'd suggest making an
exception for mojom dependencies. This would be even easier to justify if the
mojom lived in a conventional interface subpath like media/public/interfaces
(hint hint ;)) because that sort of carries with it the implication that targets
like blink should feel free to depend on it.

[haraken, 2016-06-01 23:21:29]

WebKit LGTM

[xhwang, 2016-06-01 23:22:02]

xhwang@chromium.org changed reviewers:
+ dalecurtis@chromium.org

[xhwang, 2016-06-01 23:22:04]

+dalecurtis, FYI

I agree that having to have a single mojom file living in components/ for this
is ugly. And in the future (especially in the gn world) we'll have to break our
media folder/target into more logical pieces (e.g. interfaces, public, base,
etc). With that, LGTM for this change from media's perspective.

https://chromiumcodereview.appspot.com/2027023002/diff/100001/media/mojo/inte...
File media/mojo/interfaces/image_capture.mojom (right):

https://chromiumcodereview.appspot.com/2027023002/diff/100001/media/mojo/inte...
media/mojo/interfaces/image_capture.mojom:22: GetCapabilities(string source_id)
Can you provide more context about what is a |source_id| and how to get one to
make this call?

https://chromiumcodereview.appspot.com/2027023002/diff/100001/media/mojo/inte...
media/mojo/interfaces/image_capture.mojom:26: => (string mime_type, array<uint8>
data);
What is the returned |data|?

[haraken, 2016-06-01 23:25:03]

Sorry, I LGed without noticing xhwang's comment. xhwang's makes sense. Looking.

[mcasas, 2016-06-01 23:31:02]

Note that WebKit/modules already pulls mojom-generated
data types from other top-level folders, i.e.:

$ grep -rn device `find third_party/WebKit/ | grep DEPS`
[...]
third_party/WebKit/Source/modules/device_light/DEPS:9:   
"+modules/device_light",
third_party/WebKit/Source/modules/device_orientation/DEPS:9:   
"+modules/device_orientation",
third_party/WebKit/Source/modules/vibration/DEPS:4:   
"+device/vibration/vibration_manager.mojom-blink.h",
third_party/WebKit/Source/modules/battery/DEPS:4:   
"+device/battery/battery_monitor.mojom-blink.h",
third_party/WebKit/Source/modules/webusb/DEPS:2: 
"+device/usb/public/interfaces",

https://codereview.chromium.org/2027023002/diff/100001/media/mojo/interfaces/...
File media/mojo/interfaces/image_capture.mojom (right):

https://codereview.chromium.org/2027023002/diff/100001/media/mojo/interfaces/...
media/mojo/interfaces/image_capture.mojom:22: GetCapabilities(string source_id)
On 2016/06/01 23:22:03, xhwang wrote:
> Can you provide more context about what is a |source_id| and how to get one to
> make this call?

|source_id| is the render-side identifier (UUID) of
the video capture device (webcam).
(Note that there was already a security review with
dcheng@ - also in the review list).

https://codereview.chromium.org/2027023002/diff/100001/media/mojo/interfaces/...
media/mojo/interfaces/image_capture.mojom:26: => (string mime_type, array<uint8>
data);
On 2016/06/01 23:22:03, xhwang wrote:
> What is the returned |data|?

|data| is the Photo encoded in the format
specified in |mime_type|.

[haraken, 2016-06-01 23:35:44]

haraken@chromium.org changed reviewers:
+ esprehn@chromium.org

[haraken, 2016-06-01 23:35:45]

+Elliott: The question is if it's ok to add a DEPS from modules/imagecapture/ to
src/media/mojo/interfaces/.

I think it's okay to make modules/ depend on mojom interfaces defined in
content/ as long as the dependency is limited to mojom files. If modules/ starts
depending on C++ classes in content/, that's clearly a bug.

I think this boils down to the question about where we should put mojom files.

Elliott, do you have any idea?

[xhwang, 2016-06-01 23:37:57]

On 2016/06/01 23:31:02, mcasas wrote:
> Note that WebKit/modules already pulls mojom-generated
> data types from other top-level folders, i.e.:
> 
> $ grep -rn device `find third_party/WebKit/ | grep DEPS`
> [...]
> third_party/WebKit/Source/modules/device_light/DEPS:9:   
> "+modules/device_light",
> third_party/WebKit/Source/modules/device_orientation/DEPS:9:   
> "+modules/device_orientation",
> third_party/WebKit/Source/modules/vibration/DEPS:4:   
> "+device/vibration/vibration_manager.mojom-blink.h",
> third_party/WebKit/Source/modules/battery/DEPS:4:   
> "+device/battery/battery_monitor.mojom-blink.h",
> third_party/WebKit/Source/modules/webusb/DEPS:2: 
> "+device/usb/public/interfaces",
> 
>
https://codereview.chromium.org/2027023002/diff/100001/media/mojo/interfaces/...
> File media/mojo/interfaces/image_capture.mojom (right):
> 
>
https://codereview.chromium.org/2027023002/diff/100001/media/mojo/interfaces/...
> media/mojo/interfaces/image_capture.mojom:22: GetCapabilities(string
source_id)
> On 2016/06/01 23:22:03, xhwang wrote:
> > Can you provide more context about what is a |source_id| and how to get one
to
> > make this call?
> 
> |source_id| is the render-side identifier (UUID) of
> the video capture device (webcam).
> (Note that there was already a security review with
> dcheng@ - also in the review list).
> 
>
https://codereview.chromium.org/2027023002/diff/100001/media/mojo/interfaces/...
> media/mojo/interfaces/image_capture.mojom:26: => (string mime_type,
array<uint8>
> data);
> On 2016/06/01 23:22:03, xhwang wrote:
> > What is the returned |data|?
> 
> |data| is the Photo encoded in the format
> specified in |mime_type|.

Can you put these in the comments in the mojom file for better readability?

[xhwang, 2016-06-01 23:38:01]

On 2016/06/01 23:31:02, mcasas wrote:
> Note that WebKit/modules already pulls mojom-generated
> data types from other top-level folders, i.e.:
> 
> $ grep -rn device `find third_party/WebKit/ | grep DEPS`
> [...]
> third_party/WebKit/Source/modules/device_light/DEPS:9:   
> "+modules/device_light",
> third_party/WebKit/Source/modules/device_orientation/DEPS:9:   
> "+modules/device_orientation",
> third_party/WebKit/Source/modules/vibration/DEPS:4:   
> "+device/vibration/vibration_manager.mojom-blink.h",
> third_party/WebKit/Source/modules/battery/DEPS:4:   
> "+device/battery/battery_monitor.mojom-blink.h",
> third_party/WebKit/Source/modules/webusb/DEPS:2: 
> "+device/usb/public/interfaces",
> 
>
https://codereview.chromium.org/2027023002/diff/100001/media/mojo/interfaces/...
> File media/mojo/interfaces/image_capture.mojom (right):
> 
>
https://codereview.chromium.org/2027023002/diff/100001/media/mojo/interfaces/...
> media/mojo/interfaces/image_capture.mojom:22: GetCapabilities(string
source_id)
> On 2016/06/01 23:22:03, xhwang wrote:
> > Can you provide more context about what is a |source_id| and how to get one
to
> > make this call?
> 
> |source_id| is the render-side identifier (UUID) of
> the video capture device (webcam).
> (Note that there was already a security review with
> dcheng@ - also in the review list).
> 
>
https://codereview.chromium.org/2027023002/diff/100001/media/mojo/interfaces/...
> media/mojo/interfaces/image_capture.mojom:26: => (string mime_type,
array<uint8>
> data);
> On 2016/06/01 23:22:03, xhwang wrote:
> > What is the returned |data|?
> 
> |data| is the Photo encoded in the format
> specified in |mime_type|.

Can you put these in the comments in the mojom file for better readability?

[haraken, 2016-06-01 23:39:15]

On 2016/06/01 23:31:02, mcasas wrote:
> Note that WebKit/modules already pulls mojom-generated
> data types from other top-level folders, i.e.:
> 
> $ grep -rn device `find third_party/WebKit/ | grep DEPS`
> [...]
> third_party/WebKit/Source/modules/device_light/DEPS:9:   
> "+modules/device_light",
> third_party/WebKit/Source/modules/device_orientation/DEPS:9:   
> "+modules/device_orientation",

^^^ These are different things. They just depend on WebKit/Source/modules/.

> third_party/WebKit/Source/modules/vibration/DEPS:4:   
> "+device/vibration/vibration_manager.mojom-blink.h",
> third_party/WebKit/Source/modules/battery/DEPS:4:   
> "+device/battery/battery_monitor.mojom-blink.h",

^^^ Can we follow this pattern? I agree with xhwang that it's concerning to add
a dependency from modules/ to Chromium's directory in general, but it would be
okay if the dependency is limited to mojom files.

> third_party/WebKit/Source/modules/webusb/DEPS:2: 
> "+device/usb/public/interfaces",

^^^ This is concerning for the same reason to me.

[mcasas, 2016-06-01 23:48:39]

On 2016/06/01 23:35:45, haraken wrote:
> +Elliott: The question is if it's ok to add a DEPS from modules/imagecapture/
to
> src/media/mojo/interfaces/.
> 
> I think it's okay to make modules/ depend on mojom interfaces defined in
> content/ as long as the dependency is limited to mojom files. If modules/
starts
> depending on C++ classes in content/, that's clearly a bug.
> 

Make sense. For starters, restricted the DEPS 
to the mojom-blink.h file.

> I think this boils down to the question about where we should put mojom files.
> 
> Elliott, do you have any idea?

[mcasas, 2016-06-01 23:49:27]

On 2016/06/01 23:38:01, xhwang wrote:
> On 2016/06/01 23:31:02, mcasas wrote:
> > Note that WebKit/modules already pulls mojom-generated
> > data types from other top-level folders, i.e.:
> > 
> > $ grep -rn device `find third_party/WebKit/ | grep DEPS`
> > [...]
> > third_party/WebKit/Source/modules/device_light/DEPS:9:   
> > "+modules/device_light",
> > third_party/WebKit/Source/modules/device_orientation/DEPS:9:   
> > "+modules/device_orientation",
> > third_party/WebKit/Source/modules/vibration/DEPS:4:   
> > "+device/vibration/vibration_manager.mojom-blink.h",
> > third_party/WebKit/Source/modules/battery/DEPS:4:   
> > "+device/battery/battery_monitor.mojom-blink.h",
> > third_party/WebKit/Source/modules/webusb/DEPS:2: 
> > "+device/usb/public/interfaces",
> > 
> >
>
https://codereview.chromium.org/2027023002/diff/100001/media/mojo/interfaces/...
> > File media/mojo/interfaces/image_capture.mojom (right):
> > 
> >
>
https://codereview.chromium.org/2027023002/diff/100001/media/mojo/interfaces/...
> > media/mojo/interfaces/image_capture.mojom:22: GetCapabilities(string
> source_id)
> > On 2016/06/01 23:22:03, xhwang wrote:
> > > Can you provide more context about what is a |source_id| and how to get
one
> to
> > > make this call?
> > 
> > |source_id| is the render-side identifier (UUID) of
> > the video capture device (webcam).
> > (Note that there was already a security review with
> > dcheng@ - also in the review list).
> > 
> >
>
https://codereview.chromium.org/2027023002/diff/100001/media/mojo/interfaces/...
> > media/mojo/interfaces/image_capture.mojom:26: => (string mime_type,
> array<uint8>
> > data);
> > On 2016/06/01 23:22:03, xhwang wrote:
> > > What is the returned |data|?
> > 
> > |data| is the Photo encoded in the format
> > specified in |mime_type|.
> 
> Can you put these in the comments in the mojom file for better readability?

Done in #PS4, including links to the Spec.

[haraken, 2016-06-01 23:51:50]

LGTM on my side, but I'd like to have Elliott confirm.

[mcasas, 2016-06-02 23:56:49]

On 2016/06/01 23:51:50, haraken wrote:
> LGTM on my side, but I'd like to have Elliott confirm.

I'll land this as-is since it reuses an existing DEPS 
pattern, and address esprehn@ comments, if any,
in a follow-up.

[mcasas, 2016-06-02 23:57:00]

The CQ bit was checked by mcasas@chromium.org

[mcasas, 2016-06-02 23:57:01]

The patchset sent to the CQ was uploaded after l-g-t-m from rockot@chromium.org,
avi@chromium.org, dcheng@chromium.org, xhwang@chromium.org
Link to the patchset: https://codereview.chromium.org/2027023002/#ps60002
(title: "Restricted DEPS, added .mojom comments")

[commit-bot: I haz the power, 2016-06-02 23:57:55]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/2027023002/60002
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/2027023002/60002

[commit-bot: I haz the power, 2016-06-03 00:31:04]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-06-03 00:31:06]

Try jobs failed on following builders:
  android_clang_dbg_recipe on tryserver.chromium.android (JOB_FAILED,
https://build.chromium.org/p/tryserver.chromium.android/builders/android_clan...)
  chromeos_daisy_chromium_compile_only_ng on tryserver.chromium.linux
(JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/chromeos_daisy_...)
  chromeos_x86-generic_chromium_compile_only_ng on tryserver.chromium.linux
(JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/chromeos_x86-ge...)

[mcasas, 2016-06-03 00:32:04]

The CQ bit was checked by mcasas@chromium.org

[commit-bot: I haz the power, 2016-06-03 00:34:07]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/2027023002/60002
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/2027023002/60002

[commit-bot: I haz the power, 2016-06-03 03:03:14]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-06-03 03:03:15]

Try jobs failed on following builders:
  win_chromium_rel_ng on tryserver.chromium.win (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel_...)

[mcasas, 2016-06-03 04:02:48]

The CQ bit was checked by mcasas@chromium.org

[commit-bot: I haz the power, 2016-06-03 04:03:12]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/2027023002/60002
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/2027023002/60002

[commit-bot: I haz the power, 2016-06-03 05:57:00]

Description was changed from

==========
ImageCapture: move mojom from WebKit/public to media/

This CL moves image_capture.mojom from
{third_party/WebKit/public/platform/modules => media/mojo/interfaces}
so the generated data types (e.g. PhotoCapabilities{Ptr})
can be used from both Blink and media/capture locations.

Also capture.gypi is trivially relocated to capture/ folder. 

Note that gyp files are -yay!- close to being finally 
removed.

BUG=518807
CQ_INCLUDE_TRYBOTS=tryserver.blink:linux_blink_rel,mac_blink_rel,win_blink_rel
==========

to

==========
ImageCapture: move mojom from WebKit/public to media/

This CL moves image_capture.mojom from
{third_party/WebKit/public/platform/modules => media/mojo/interfaces}
so the generated data types (e.g. PhotoCapabilities{Ptr})
can be used from both Blink and media/capture locations.

Also capture.gypi is trivially relocated to capture/ folder. 

Note that gyp files are -yay!- close to being finally 
removed.

BUG=518807
CQ_INCLUDE_TRYBOTS=tryserver.blink:linux_blink_rel,mac_blink_rel,win_blink_rel
==========

[commit-bot: I haz the power, 2016-06-03 05:57:02]

Committed patchset #4 (id:60002)

[commit-bot: I haz the power, 2016-06-03 05:58:53]

Description was changed from

==========
ImageCapture: move mojom from WebKit/public to media/

This CL moves image_capture.mojom from
{third_party/WebKit/public/platform/modules => media/mojo/interfaces}
so the generated data types (e.g. PhotoCapabilities{Ptr})
can be used from both Blink and media/capture locations.

Also capture.gypi is trivially relocated to capture/ folder. 

Note that gyp files are -yay!- close to being finally 
removed.

BUG=518807
CQ_INCLUDE_TRYBOTS=tryserver.blink:linux_blink_rel,mac_blink_rel,win_blink_rel
==========

to

==========
ImageCapture: move mojom from WebKit/public to media/

This CL moves image_capture.mojom from
{third_party/WebKit/public/platform/modules => media/mojo/interfaces}
so the generated data types (e.g. PhotoCapabilities{Ptr})
can be used from both Blink and media/capture locations.

Also capture.gypi is trivially relocated to capture/ folder.

Note that gyp files are -yay!- close to being finally
removed.

BUG=518807
CQ_INCLUDE_TRYBOTS=tryserver.blink:linux_blink_rel,mac_blink_rel,win_blink_rel

Committed: https://crrev.com/64aec45d94682ae3b38c0f1c18ff74cd937ff9b5
Cr-Commit-Position: refs/heads/master@{#397644}
==========

[commit-bot: I haz the power, 2016-06-03 05:58:55]

Patchset 4 (id:??) landed as
https://crrev.com/64aec45d94682ae3b38c0f1c18ff74cd937ff9b5
Cr-Commit-Position: refs/heads/master@{#397644}

[fs, 2016-06-03 08:21:30]

A revert of this CL (patchset #4 id:60002) has been created in
https://codereview.chromium.org/2034003002/ by fs@opera.com.

The reason for reverting is: Appears to cause:

imagecapture/getphotocapabilities.html
imagecapture/takephoto.html

to timeout.

(https://storage.googleapis.com/chromium-layout-test-archives/WebKit_Win7/4297...).