Add 2 Extension APIs for handwriting: experimental.input.sendHandritingStroke and cancelHandWriting

chrome/common/extensions/api/extension_api.json

 [
   {
     "namespace": "extension",
     "unprivileged": true,
     "types": [
       {
         "id": "MessageSender",
         "type": "object",
         "description": "An object containing information about the script context that sent a message or request.",
         "properties": {
@@ skipping 2400 matching lines @@
             },
             "description": "The keyboard event to be sent."
           },
           { "type": "function",
             "name": "callback",
             "optional": true,
             "description": "This function is called when the event processing is completed.",
             "parameters": []
           }
         ]
+      },
+      {

[Peng, 2011/04/27 15:13:44]

I am thinking it is better to have a namespace chrome.input.focusedcontext or
chrome.ime.focusedcontext. and then we may put some functions for interacting
with current focused context in it.
We could put those two function in it, maybe sendKeykeyboardEvent too.

[Yusuke Sato, 2011/04/28 10:57:07]

Are we planning to have an API which allows extension developers to send a key
event to a specific input context? If not, I prefer chrome.input. I guess the
sub namespace "focused context" looks too complicated for most VK extension
developers.

How about just rewriting the description to something like "Send a handwriting
event to the focused input context in Chrome"?

On 2011/04/27 15:13:44, Peng wrote:

[Peng, 2011/04/28 15:00:30]

We don't have a plan to allow the VK interact with any input contexts. The VK is
different with physical keyboard. It can only interact with the focused context
(focused input control view). I think probably we will add more APIs, like get
context input type (email, address, number and etc), sending key events, or
inserting text, receiving some notifications from the context, and etc.

I think have a namespace focusedcontext could make those APIs very clear. VK
developers know they are playing with the focused context. If we put all APIs in
chrome.input, it will hide the concept of context from developers, and the APIs
meaning may be a little fuzzy? Or we have to put the detail in API document.

Peng

+        "name": "sendHandwritingStrokes",
+        "type": "function",
+        "description": "Send a handwriting event to Chrome.",
+        "parameters": [
+          {
+            "name": "strokes",
+            "type": "array",
+            "items": {
+              "type": "object",
+              "properties": {
+                "x": {"type": "number", "minimum": 0, "maximum": 1},
+                "y": {"type": "number", "minimum": 0, "maximum": 1}
+              }
+            }
+          }
+        ]
+      },
+      {
+        "name": "cancelHandwriting",
+        "type": "function",
+        "description": "Clear last N handwriting strokes.",
+        "parameters": [
+          {
+            "name": "n_strokes",
+            "optional": true,
+            "type": "integer"
+          }
+        ]
       }
     ],
     "events": []
   },
   {
     "namespace": "experimental.bookmarkManager",
     "nodoc": true,
     "types": [
       {
         "id": "BookmarkNodeDataElement",
@@ skipping 2904 matching lines @@
           {
             "type": "integer",
             "name": "tabId",
             "description": "The id of the tab that was detached."
           }
         ]
       }
     ]
   }
 ]