Simulating multi-touch events on a browser system

Patent metadata

Field	Value
Publication number	US-9891727-B2
Application number	US-201213415619-A
Country	US
Kind code	B2
Filing date	Mar 8, 2012
Priority date	Mar 8, 2012
Publication date	Feb 13, 2018
Grant date	Feb 13, 2018

Abstract

Technology provided here facilitates simulating multi-touch events on a browser system. In one example, a browser system receives low-level touch events from a touch-input system. The browser system generates script-callbacks from the low-level touch events. The browser system converts the script-callbacks into compliant touch events that are compliant with a multi-touch browser standard. The browser system then sends the compliant touch events to a web application. This Abstract is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims.

First claim

What is claimed is:

1. A method to facilitate simulation of multi-touch events on a browser system, the method comprising:
receiving low-level touch events from a touch-input system, the low-level touch events comprising data that describes an activity at a contact point of a touch-sensing surface of the touch-input system, the low-level touch events being converted from raw touch events generated from the touch-input system such that the low-level touch events are capable of being interpreted by the browser system;
generating script-callbacks from the low-level touch events, the script-callbacks comprising properties, the properties comprising a contact identifier, a contact position, and a contact type that describe the activity at the contact point of the touch-sensing surface of the touch-input system, the script-callbacks comprising callbacks of a scripting language, the properties being in a first format incompliant with a multi-touch browser standard;
converting the script-callbacks into compliant touch events by converting each of the properties of the script-callbacks to compliant properties in a second format compliant with the multi-touch browser standard, the compliant touch events comprising the compliant properties that describe the activity at the contact point of the touch-sensing surface of the touch-input system, wherein the converting further comprises at least one of converting, using code built into the browser system, an incompliant position into a compliant position, converting, using the code built into the browser system, an incompliant touch type into a compliant touch type, and converting, using the code built into the browser system, an incompliant identifier into a compliant identifier; and
sending the compliant touch events to a web application configured to combine the compliant touch events to perform high-level actions.

2. The method of claim 1 , wherein a multi-touch enabler is configured to convert the script-callbacks into the compliant touch events and the web application is configured to receive the compliant touch events from the multi-touch enabler and generate properly formatted content for a rendering engine of the browser system.

3. The method of claim 1 , wherein a multi-touch enabler is configured to convert the script-callbacks into the compliant touch events and the web application is configured to receive the compliant touch events from the multi-touch enabler, and generate properly formatted content for a rendering engine of the browser system, the method further comprising:
receiving the formatted content from the web application; and
instructing a browser display window to display the formatted content.

4. The method of claim 1 , wherein a Netscape Program Application Program Interface (NPAPI) plug-in device is configured to generate the script-callbacks.

5. The method of claim 1 , wherein a script library that complies with a scripting language that enables dynamic and interactive Web pages is configured to convert the script-callbacks to the compliant touch events.

6. The method of claim 1 , wherein the compliant touch events comply with a touch events specification of a World Wide Web Consortium.

7. The method of claim 1 , wherein the web application includes at least one of a video game or a mobile web application.

8. The method of claim 1 , wherein the touch-input system comprises:
a touch-input surface configured to receive multi-touch-input and generate raw touch-signals; and
a low-level converter configured to receive the raw touch-signals and generate the low-level touch events, wherein the low-level converter complies with a tangible user interface objects (TUIO) protocol, and wherein the low-level touch events include tangible user interface objects (TUIO) protocol events.

9. The method of claim 1 , wherein converting the script-callbacks includes identifying the properties of the script callbacks and converting the identified properties to the second format compliant with the multi-touch browser standard.

10. The method of claim 1 , wherein the web application is configured to interpret the compliant touch events as multi-point gestures or single-point gestures.

11. The method of claim 1 , wherein the incompliant identifier uniquely distinguishes a corresponding contact point from other contact points at the touch-sensing surface, and the compliant identifier comprises a format that complies with a touch events specification of a World Wide Web Consortium.

12. The method of claim 1 , wherein the incompliant position describes a location of a corresponding contact point at the touch-sensing surface, the incompliant touch type describes the corresponding contact point as being a start, a move, or an end of a gesture, and wherein the compliant position and the compliant touch type comprise respective formats that comply with a touch events specification of a World Wide Web Consortium.

13. The method of claim 12 , wherein the code built into the browser system comprises at least one of a script programming language library or a browser plug-in.

14. A browser system that facilitates simulation of multi-touch events, the browser system comprising:
an application programming interface (API) device configured to receive low-level touch events from a touch-input system and generate script-callbacks from the low-level touch events, the low-level touch events comprising data that describes an activity at a contact point of a touch-sensing surface of the touch-input system, the low-level touch events being converted from raw touch events generated from the touch-input system such that the low-level touch events are capable of being interpreted by the browser system, the script-callbacks comprising properties, the properties comprising a contact identifier, a contact position, and a contact type that describe the activity at the contact point of the touch-sensing surface of the touch-input system, the script-callbacks comprising callbacks of a scripting language, the properties being in a first format incompliant with a multi-touch browser standard; and
a multi-touch enabler configured to convert the script-callbacks into compliant touch events by converting each of the properties of the script-callbacks to compliant properties in a second format compliant with the multi-touch browser standard and send the compliant touch events to a web application, the compliant touch events comprising the compliant properties that describe the activity at the contact point of the touch-sensing surface of the touch-input system, wherein the multi-touch enabler is further configured to convert, using code built into the browser system, an incompliant position into a compliant position, convert, using the code built into the browser system, an incompliant touch type into a compliant touch type, and convert, using the code built into the browser system, an incompliant identifier into a compliant identifier.

15. The browser system of claim 14 , wherein the web application is configured to receive the compliant touch events from the multi-touch enabler and generate formatted content that is reliable from the low-level touch events received at the API device.

16. The browser system of claim 14 , wherein the web application is configured to receive the compliant touch events from the multi-touch enabler and generate formatted content that is reliable from the low-level touch events received at the API device, the browser system further comprising:
a rendering engine configured to receive the formatted content from the web application and instruct a browser display window to

Assignees

• Smus Boris
• Google Llc

Inventors

• Smus Boris

Classifications

• G06F17/30873

  Physics · mapped topic

• G06F2203/04104

  Multi-touch detection in digitiser, i.e. details about the simultaneous detection of a plurality of touching locations, e.g. multiple fingers or pen and finger · CPC title

• G06F3/0488

  using a touch-screen or digitiser, e.g. input of commands through traced gestures · CPC title

• G06F3/041 Primary

  Digitisers, e.g. for touch screens or touch pads, characterised by the transducing means · CPC title

• G06F2203/04808

  Several contacts: gestures triggering a specific function, e.g. scrolling, zooming, right-click, when the user establishes several contacts with the surface simultaneously; e.g. using several fingers or a combination of fingers and pen · CPC title