[Webkit-unassigned] [Bug 69048] Separate compositor platform support from webkit's platform support

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=69048





--- Comment #15 from James Robinson <jamesr at chromium.org>  2011-09-29 18:58:55 PST ---
(In reply to comment #14)
> (In reply to comment #11)
> > This might be better:
> > 
> >   struct WebKitInitializationOptions {
> >       bool initializeV8;
> >       bool initializeCompositor;
> >       // ... default ctor sets them to true ...
> >   };
> >   WEBKIT_EXPORT void initializeWithOptions(WebKitPlatformSupport*, const WebKitInitializationOptions&);
> > 
> 
> The initialization for v8 and for the compositor isn't really initializing anything - it's more binding gloop together so that it'll work together.  We use V8 in the browser process but still call initializeWithoutV8() cos we don't bind V8 and WebKit together in the browser.
>

I guess that's not entirely true - for V8 the call actually does initialize V8, but also does binding gloop.  For compositor it'll only do binding gloop, it won't actually initialize anything.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.