1. A method for application interfacing a native physics engine, comprising: embedding access to the native physics engine within a WebCore of a browser engine by providing JavaScript bindings within the WebCore for supporting a plurality of application classes from the browser engine to the native physics engine and to a JavaScript engine; triggering, by the JavaScript engine, a function that calls into a corresponding JavaScript binding function of the WebCore through a table, the corresponding JavaScript binding function calling a wrapper layer function in the JavaScript binding that calls a native function from the native physics engine; and providing, by the WebCore of the browser engine, transparent access from at least one web application to the native physics engine through the JavaScript bindings.
1. A method for application interfacing a native physics engine, comprising: embedding access to the native physics engine within a WebCore of a browser engine by providing JavaScript bindings within the WebCore for supporting a plurality of application classes from the browser engine to the native physics engine and to a JavaScript engine; triggering, by the JavaScript engine, a function that calls into a corresponding JavaScript binding function of the WebCore through a table, the corresponding JavaScript binding function calling a wrapper layer function in the JavaScript binding that calls a native function from the native physics engine; and providing, by the WebCore of the browser engine, transparent access from at least one web application to the native physics engine through the JavaScript bindings. 8. The method of claim 1 , wherein the JavaScript bindings are communicated from the WebCore of the browser engine using Box2D application programming interface (API) calls to a Box2D native engine and using Box2D callbacks from the Box2D native engine, and the table includes a key that is mapped to the JavaScript binding function.