Split EventTargetFactory.in and auto-generate modules-related files.

Source/modules/InitModules.cpp

Index: Source/modules/InitModules.cpp
diff --git a/Source/modules/InitModules.cpp b/Source/modules/InitModules.cpp
new file mode 100644
index 0000000000000000000000000000000000000000..f8d0ed8b03f569e3ff10ea15254005c57de4daba
--- /dev/null
+++ b/Source/modules/InitModules.cpp
@@ -0,0 +1,27 @@
+// Copyright (c) 2014 The Chromium Authors. All rights reserved.
+// Use of this source code is governed by a BSD-style license that can be
+// found in the LICENSE file.
+
+#include "config.h"
+#include "InitModules.h"
+
+#include "EventTargetModulesNames.h"
+#include "core/Init.h"
+
+namespace WebCore {
+
+void initModules()

[Nils Barth (inactive), 2014/05/12 01:41:56]

abarth:
Do we have a naming preference about initModules() vs. modulesInit()?

Ditto EventTargetModules vs. ModulesEventTarget etc.

(No preference personally, but consistency with existing practices
worthwhile...)

+{
+    static bool isInited;
+    if (isInited)
+        return;
+    isInited = true;
+
+    init();
+
+//    EventNames::init(); TODO: split core and modules names under bindings

[Nils Barth (inactive), 2014/05/12 01:31:41]

Could you link to a bug number? http://crbug.com/358074 is fine as the tracking
bug, unless you want to open a separate one.

+    EventTargetNames::initModules();
+//    EventTypeNames::init(); TODO: split core and modules type names under bindings
+}
+
+} // namespace WebCore