Added about:flags entries for --enable-accelerated-drawing flag.

chrome/app/generated_resources.grd

 <?xml version="1.0" encoding="UTF-8"?>
 
 <!--
 This file contains definitions of resources that will be translated for each
 locale.  The variables is_win, is_macosx, is_linux, and is_posix are available
 for making strings OS specific.  Other platform defines such as use_titlecase
 are declared in build/common.gypi.
 -->
 
 <grit base_dir="." latest_public_release="0" current_release="1"
@@ skipping 4139 matching lines @@
       </message>
       <message name="IDS_FLAGS_ACCELERATED_COMPOSITING_DESCRIPTION" desc="Description of the 'GPU Accelerated Compositing' lab.">
         Enables 3D CSS and higher performance compositing of webpages using Graphics Processor Unit (GPU) hardware.
       </message>
       <message name="IDS_FLAGS_COMPOSITED_LAYER_BORDERS" desc="Name of the 'Composited layer borders' lab.">
         Composited render layer borders
       </message>
       <message name="IDS_FLAGS_COMPOSITED_LAYER_BORDERS_DESCRIPTION" desc="Description of the 'Composited layer borders' lab.">
         Renders a border around composited Render Layers to help debug and study layer compositing.
       </message>
+      <message name="IDS_FLAGS_ACCELERATED_DRAWING_NAME" desc="Title for the flag to enable accelerated drawing">
+        GPU Accelerated Drawing
+      </message>
+      <message name="IDS_FLAGS_ACCELERATED_DRAWING_DESCRIPTION" desc="Description for the flag to enable accelerated drawing">
+        Enable GPU accelerated drawing of composited render layers.

[vangelis, 2011/06/20 18:06:51]

Since essentially all rendering in the page (including the root layer) will be
going through the GPU should the be phrased as:

"Enable GPU accelerated drawing of page contents"

or something like that?  Also, what happens if accelerated drawing is enabled
without force compositing mode?  Should one trigger the other? If not, we should
probably put a brief blurb here that it also requires the force compositing flag
to be enabled.

[alokp, 2011/06/20 19:01:18]

Isn't root layer a composited render layer? I think "composited render layers"
is more appropriate than "page contents" because it only comes into effect when
compositing is active.
DONE.

[vangelis, 2011/06/20 19:27:47]

The root is currently a special case and not treated like the rest of the
content layers.  In any case though, since this is a user facing message that
distinction would be lost.

You are right that we need to somehow indicate that this only affects pages that
go through the compositor. I think it could be clearer if we say that this does
accelerated drawing for the contents of the layer (as opposed to an accelerated
compositing operation).

"Enable GPU accelerated drawing of page contents when compositing is enabled."

?

[alokp, 2011/06/20 19:33:38]

perfect! DONE.

+      </message>
       <message name="IDS_FLAGS_SHOW_FPS_COUNTER" desc="Name of the 'Show FPS counter' lab.">
         FPS counter
       </message>
       <message name="IDS_FLAGS_SHOW_FPS_COUNTER_DESCRIPTION" desc="Description of the 'Show FPS counter' lab.">
         Shows a page's actual frame rate, in frames per second, when hardware acceleration is active.
       </message>
       <message name="IDS_FLAGS_COMPOSITE_TO_TEXTURE_NAME" desc="Name of the 'Offscreen Compositing' lab.">
         Composite to Texture
       </message>
       <message name="IDS_FLAGS_COMPOSITE_TO_TEXTURE_DESCRIPTION" desc="Description of the 'Offscreen Compositing' lab.">
@@ skipping 8527 matching lines @@
     </includes>
     <structures fallback_to_english="true">
       <structure name="IDD_CHROME_FRAME_FIND_DIALOG" file="cf_resources.rc" type="dialog" >
       </structure>
       <structure name="IDD_CHROME_FRAME_READY_PROMPT" file="cf_resources.rc" type="dialog" >
       </structure>
     </structures>
 
   </release>
 </grit>