Implement an infrastructure of Blink-in-JS

Source/core/core.gypi

Index: Source/core/core.gypi
diff --git a/Source/core/core.gypi b/Source/core/core.gypi
index 81b9d726ec434cb1c3e1673badb0942d346d45c9..3e0397ad3fe84c512b4434ce83a59a1f82afe75c 100644
--- a/Source/core/core.gypi
+++ b/Source/core/core.gypi
@@ -449,6 +449,7 @@
             'xml/XPathNSResolver.idl',
             'xml/XPathResult.idl',
             'xml/XSLTProcessor.idl',
+            '../bindings/v8/PrivateScriptTest.idl',

[Nils Barth (inactive), 2014/06/23 03:14:30]

1. Alphabetical order please (.. is at start)

2. Testing files should go in 'webcore_testing_idl_files' instead

3. 'private_source_idl_files' variable instead?

This is creating a dependency of core on bindings
(later core_bindings_v8);
I assume this is ok, but it's a bit icky-looking.
Assuming we'll have more of these, better would be a variable
like 'private_source_idl_files',
which you could include from bindings.gypi
(later: bindings_core_v8.gypi)
and then have listed at the top via: <(private_source_idl_files)

[haraken, 2014/06/23 06:01:46]

This is my question as well --- where the IDL files for PrivateScripts should be
listed.

- The IDL files for PrivateScripts (including PrivateScriptTest.idl) are not a
part of testing IDL files. They are a part of normal core/modules IDL files that
should be aggregated into aggregated binding files. Thus we cannot put them into
webcore_testing_idl_files.

- Almost all IDL files for PrivateScripts that will be added in the future will
be placed in core/ or modules/ (in order to replace the implementation of core/
and modules/ with JavaScript). PrivateScriptTest.idl will be the only IDL file
placed in bindings/.

Given the situation, where do you think I should list up the IDL files?

[Nils Barth (inactive), 2014/06/23 06:21:25]

Probably best would be a separate list, say core_private_idl_files?
Putting them in the same core list is saying that they're part of
the web interface, but these are fundamentally implementation details,
and I think we'll want to treat these pretty differently
(we're already having special cases).

Also it's weird to put 1 test file with real files;
presumably we shouldn't be *shipping* test interfaces,
which is exactly why there's separate treatment for existing
test interfaces.

Cleanest would be another category,
core_private_testing_idl_files
...but if it's only going to be one file,
and it's not going to be treated differently,
that seems a bit silly.

Safer would be to make it runtime enabled, say
[RuntimeEnabled=PrivateScript] or something

Anyway, for the test file itself:
* Ok to put in core, I think.
* Otherwise make a separate bindings_idl_files list in bindings or
bindings/core/idl.gypi and then add that to the main core list in
bindings/core/idl.gypi.

[haraken, 2014/06/23 08:15:38]

Done. I kept PrivateScriptTest.idl in bindings/v8/ and added 'binding_idl_files'
to bindings/core/v8/idl.gypi.

[Nils Barth (inactive), 2014/06/23 08:54:11]

Thanks, that's a good way to do it!

         ],
         # 'partial interface', target (right side of) 'implements', and
         # interfaces with static bindings (in bindings/v8/)