HomeSort by relevance Sort by last modified time
    Searched defs:WebViewCore (Results 1 - 4 of 4) sorted by null

  /external/webkit/WebKit/android/jni/
WebViewCore.h 93 // one instance of WebViewCore per page for calling into Java's WebViewCore
94 class WebViewCore : public WebCoreRefObject {
97 * Initialize the native WebViewCore with a JNI environment, a Java
98 * WebViewCore object and the main frame.
100 WebViewCore(JNIEnv* env, jobject javaView, WebCore::Frame* mainframe);
101 ~WebViewCore();
104 static WebViewCore* getWebViewCore(const WebCore::FrameView* view);
105 static WebViewCore* getWebViewCore(const WebCore::ScrollView* view);
357 // WebViewCore
    [all...]
WebViewCore.cpp 29 #include "WebViewCore.h"
153 static SkTDArray<WebViewCore*> gInstanceList;
155 void WebViewCore::addInstance(WebViewCore* inst) {
159 void WebViewCore::removeInstance(WebViewCore* inst) {
167 bool WebViewCore::isInstance(WebViewCore* inst) {
171 jobject WebViewCore::getApplicationContext() {
173 // check to see if there is a valid webviewcore objec
    [all...]
  /frameworks/base/core/java/android/webkit/
WebViewCore.java 53 final class WebViewCore {
65 * WebViewCore always executes in the same thread as the native webkit.
68 // The WebView that corresponds to this WebViewCore.
132 public WebViewCore(Context context, WebView w, CallbackProxy proxy,
138 // This context object is used to initialize the WebViewCore during
146 synchronized (WebViewCore.class) {
153 WebViewCore.class.wait();
173 // Send a message to initialize the WebViewCore.
211 /* Handle the initialization of WebViewCore during subwindow creation. This
595 // Message id for initializing a new WebViewCore
    [all...]
WebView.java 74 import android.webkit.WebViewCore.EventHub;
75 import android.webkit.WebViewCore.TouchEventData;
385 // A final CallbackProxy shared by WebViewCore and BrowserFrame.
398 private WebViewCore mWebViewCore;
406 // Used by WebViewCore to create child views.
424 * Time of the last time sending touch event to WebViewCore
430 * WebViewCore. This really should be tuned for each type of the devices.
432 * 150ms to do a full cycle in the WebViewCore by processing a touch event,
436 * to WebViewCore queue and the real layout and draw events will be pushed
552 private int mContentWidth; // cache of value from WebViewCore
    [all...]

Completed in 34 milliseconds