Yes :) Thanks for your better explanation & correction. On 19 February 2013 00:04, Martin Robinson <mrobin...@webkit.org> wrote:
> On Mon, Feb 18, 2013 at 9:57 AM, Arunprasad Rajkumar > <ararunpra...@gmail.com> wrote: > > yes :). WebKit is not a library, so it don't have defined form of API > > exposed. The one who _uses_ WebCore(WebCore+WTF+JSC/V8) called as > Embedders > > have some form of API, but again it is up-to them to expose the level of > > control to outside. Embedders call their work by different names like > > QtWebKit, GTK WebKit, EFL WebKit,... & they may provide as libraries. All > > have some level of documented Public API for its users. > > A small clarification: The ports are not embedders. > > It's true that WebKit, the project, is not a library. It is a code > base and a community. Certain "ports" of WebKit are libraries or > "embedding APIs", such as Mac Webkit, QtWebKit, EFLWebKit and > WebKitGTK+. Because of the history of the WebKit project, the Mac port > is sometimes just called "WebKit." You can think of the ports as > WebKit implemented for a particular platform. These port libraries > expose WebKit in slightly different ways depending on the culture and > needs of the communities in which they exist. Applications that use a > WebKit library to show a WebView or otherwise access web content are > called embedders. > > Since this discussion is not about development of WebKit internals, > it's probably better to move it to webkit-help. > > --Martin > -- *Arunprasad Rajkumar* http://in.linkedin.com/in/ararunprasad
_______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev