Add initial support for NV_path_rendering extension to gpu command buffer

gpu/GLES2/extensions/CHROMIUM/CHROMIUM_NV_path_rendering.txt

Index: gpu/GLES2/extensions/CHROMIUM/CHROMIUM_NV_path_rendering.txt
diff --git a/gpu/GLES2/extensions/CHROMIUM/CHROMIUM_NV_path_rendering.txt b/gpu/GLES2/extensions/CHROMIUM/CHROMIUM_NV_path_rendering.txt
new file mode 100644
index 0000000000000000000000000000000000000000..5f3a23a0a96e1ddabb7ad96c92c2af524ed236ca
--- /dev/null
+++ b/gpu/GLES2/extensions/CHROMIUM/CHROMIUM_NV_path_rendering.txt
@@ -0,0 +1,72 @@
+Name
+
+    CHROMIUM_NV_path_rendering

[piman, 2014/04/11 22:19:27]

nit: s/CHROMIUM_NV/CHROMIUM/

[Kimmo Kinnunen, 2014/04/15 16:16:58]

Done.

+
+Name Strings
+
+    GL_CHROMIUM_NV_path_rendering
+
+Version
+
+    Last Modifed Date: March 26, 2014
+
+Dependencies
+
+    OpenGL ES 2.0 is required.
+
+Overview
+
+    This extensions is pretty much the same as NV_path_rendering

[piman, 2014/04/11 22:19:27]

Can we document the extension independently of the existing other extension?

[piman, 2014/04/11 22:19:27]

Also, I don't see any path rendering in this extension...

Should we have 2 extensions?
e.g.
GL_CHROMIUM_transform_matrix
GL_CHROMIUM_path_rendering

[Kimmo Kinnunen, 2014/04/14 12:56:30]

Well, the path-rendering part is rather elaborate to document or
cut-and-paste-and-maintain.

[Kimmo Kinnunen, 2014/04/14 12:56:30]

This is augmented in the next patch:
https://chromiumcodereview.appspot.com/169403005/
Well, personally I'd rather not split them. The transform_matrix extension would
be pointless in isolation, as only thing it can affect is the path rendering.

If split is a requirement, then I could of course cut-paste-and-maintain a
partial version of  direct_state_access extension?

http://www.opengl.org/registry/specs/EXT/direct_state_access.txt 

[Kimmo Kinnunen, 2014/04/15 16:16:58]

Done.

+    except it also includes minimal set of functionality from OpenGL
+    4.4 Compatibility Profile to enable fixed-function vertex
+    processing.
+
+New Tokens
+
+    Accepted by the <mode> parameter of MatrixMode:
+    MODELVIEW                                         0x1700
+    PROJECTION                                        0x1701

[vmiura, 2014/04/11 21:54:48]

Should add GL_MATRIX_MODE?

[Kimmo Kinnunen, 2014/04/15 16:16:58]

Removed.

+
+New Procedures and Functions
+
+    void MatrixMode(enum mode);
+
+    Selects current matrix mode, eg. which matrix is affected by the
+    matrix operations. Takes one of the pre-defined constants
+    MODELVIEW or PROJECTION as the argument value.
+
+    Otherwise functions as specified in The OpenGL Graphics System: A
+    Specification (Version 4.4 (Compatibility Profile) - October 18,
+    2013) Section 12.1.1.
+
+    void LoadMatrixf(const float* m);
+
+    Takes a pointer to a 4x4 matrix stored in column-major order as 16
+    consecutive floating-point values.
+
+    Functions as specified in The OpenGL Graphics System: A
+    Specification (Version 4.4 (Compatibility Profile) - October 18,
+    2013) Section 12.1.1.
+
+    void LoadIdentity(void);
+
+    Effectively calls LoadMatrix with the identity matrix.
+
+    Functions as specified in The OpenGL Graphics System: A
+    Specification (Version 4.4 (Compatibility Profile) - October 18,
+    2013) Section 12.1.1.
+
+
+Errors
+
+    None.
+
+New State
+
+    Get Value    Type   Get Command  Initial Value   Description
+    ------------ -----  ------------ --------------  -------------------
+    MATRIX_MODE  enum   GetInteger   MODELVIEW       Current matrix mode
+
+Revision History
+
+    26/3/2014    Documented the extension