Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [platform-swt-dev] SWT Browser - Chromium vs Safari [Was: Browser WEBKIT style]

Hi Scott,

I don't know of a current plan to pursue this in SWT.  If CEF was committed to maintaining API stability then implementing support for it should be possible.  They were not planning to do this when I last contacted them, but that was a few years ago, so this could have changed.

Note that there is a project that apparently has done an implementation that works on Windows, see http://www.genuitec.com/about/labs-webkit-for-swt/WebKit%20For%20SWT%20Developer%20Guide.html .  It doesn't list CEF as a requirement, but is based on it, so I'm assuming that it ships CEF.  Perhaps they will look to move up to a newer CEF release and add support for the non-Windows platforms now that the native support is there.

Grant




From:        Scott Elcomb <psema4@xxxxxxxxx>
To:        platform-swt-dev@xxxxxxxxxxx
Date:        09/12/2012 02:38 PM
Subject:        [platform-swt-dev] SWT Browser - Chromium vs Safari [Was: Browser        WEBKIT style]
Sent by:        platform-swt-dev-bounces@xxxxxxxxxxx




Hi all.  I'd like to follow up on an old post (Jan '11) - specifically:

<
http://dev.eclipse.org/mhonarc/lists/platform-swt-dev/msg07195.html>

"The cross-platform API exposed by WebKit is much more core than the
one from Gecko, so each platform requires its own WebKit port
(basically a layer)  that bridges the gap between this core
functionality and embedding apps like SWT.  There isn't a
cross-platform WebKit api that would actually be useful to expose to
SWT clients, so consequently there isn't something comparable to
JavaXPCOM available.  As an example of this cross-platform difference,
SWT has a completely different implementation of WebKit.java for each
supported window system, whereas its Mozilla.java class is shared
across them.

Chrome also uses WebKit, but it implements its own port on top which
is different from the win32 port provided by Apple (even when running
on Windows).  So SWT's Browser implementation cannot embed WebKit from
a Chrome installation.  To do so would require Chrome's WebKit port to
commit to providing a stable API for embedders, and SWT would then
have to do another implementation from scratch.  This work is not
currently planned."

It appears that the ChromiumEmbedded project is making good progress
(now with Windows, Mac OS-X and Linux support*) and I'm wondering if
SWT will be able to leverage those gains?


Best,
- Scott.


* See "Notable Changes" at <
http://code.google.com/p/chromiumembedded/>

--
 Scott Elcomb
 @psema4 on Twitter / Identi.ca / Github & more

 Atomic OS: Self Contained Microsystems
 
http://code.google.com/p/atomos/

 Member of the Pirate Party of Canada
 
http://www.pirateparty.ca/
_______________________________________________
platform-swt-dev mailing list
platform-swt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-swt-dev



Back to the top