Use chrome_html structure for shared_resources and options2 page.

tools/gritsettings/resource_ids

Index: tools/gritsettings/resource_ids
diff --git a/tools/gritsettings/resource_ids b/tools/gritsettings/resource_ids
index 301530b229f6f99433c428e8019b9918d96ea114..f9bc35e827709e328024622e83f9e2711912b723 100644
--- a/tools/gritsettings/resource_ids
+++ b/tools/gritsettings/resource_ids
@@ -27,6 +27,7 @@
   },
   "chrome/browser/resources/shared_resources.grd": {
     "includes": [2000],
+    "structures": [2200],
   },
   "chrome/common/common_resources.grd": {
     "includes": [2500],
@@ -165,7 +166,7 @@
     "includes": [22000],
   },
   "chrome/browser/resources/options2_resources.grd": {
-    "includes": [22200],
+    "structures": [22200],

[James Hawkins, 2012/06/01 23:05:57]

Why are these called structures?

[flackr, 2012/06/04 12:11:50]

Joi has informed me that when we are doing modification of the source (even
things like flatten_html) we should be using structure nodes and add a gatherer
type, includes should be strictly included files. As such, chrome_html is
implemented as a gatherer for a structure which performs the functions include
does and adds high dpi images.

   },
   "cloud_print/virtual_driver/win/install/virtual_driver_setup_resources.grd": {
     "messages": [22500],