Provide skeleton for ChromeVox next.

chrome/browser/resources/chromeos/chromevox_next/chromevox.gyp

+# Copyright 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.
+
+{
+  'conditions': [
+    ['chromeos==1 and disable_nacl==0 and disable_nacl_untrusted==0', {
+      'targets': [
+        {
+          'target_name': 'chromevox_resources',

[Peter Lundblad, 2014/05/12 18:37:32]

Please pick a unique target name so it is easier to build this separately on the
command line.

[David Tseng, 2014/05/12 20:33:38]

Done.

+          'type': 'none',
+          'copies': [
+            {
+              'destination': '<(PRODUCT_DIR)/resources/chromeos/chromevox/chromevox2/background',

[Peter Lundblad, 2014/05/12 18:37:32]

Why don't you create chromevox_next under chromeos and get rid of 'chromevox2'?
It seems confusing to sometimes call this chromevox2 and sometimes
chromevox_next.

[David Tseng, 2014/05/12 20:33:38]

I created chromeos/chromevox2/chromevox2/*

This reflects the directory structure of the output files.
(i.e.
chromevox2: (the first one) is the target
chromevox2/chromevox2: is the root of all files under the cvox2 namespace.

Does that make sense?

+              'files': [
+                'chromevox2/background/background.html',

[Peter Lundblad, 2014/05/12 18:37:32]

Why do we need both a html file and js file for the background page?

[David Tseng, 2014/05/12 20:33:38]

The html file includes all other dependencies (e.g. ChromeVox classic's
background page).

+                'chromevox2/background/background.js',
+              ],
+            },
+            {
+              'destination': '<(PRODUCT_DIR)/resources/chromeos/chromevox/chromevox2/injected',
+              'files': [
+                'chromevox2/injected/injected.js',
+              ],
+            },
+          ],
+        },
+      ],
+    }],
+  ],
+}