No subject

platform specific ones, because they are very different pieces of
software.

So in the future if it will be packaged we will currently have
GtkWebkit, QtWebkit and V8/Cromium Webkit, possibly Maemo/S60 Webkits
as well. Which as far as I can see will be build out of different
branches from respective publishers. They are converging at different
levels for test-suites and core functionalities but ports still use
very different sets of dependencies and provide various degrees of
API/functionalities.

"WebKit is not a bundle of maximally general and reusable code."
"WebKit is not the solution to every problem." [1]

You really need to do a separate port / fork of it to make a library
for your needs.

And as for releases it's waterfall / rolling model with webkit
constantly targetting latest HTML / SVG / and other standards with
ports ship under their schedules.

This is very general overview and I might be wrong on a few things but
webkit is not a stable library with bindings it's more like LLVM which
you can use to build something you need.

[1] http://webkit.org/projects/goals.html

--
With best regards


Dmitrijs Ledkovs (for short Dima),
=D0=9B=D0=B5=D0=B4=D0=BA=D0=BE=D0=B2 =D0=94=D0=BC=D0=B8=D1=82=D1=80=D0=B8=
=D0=B9 =D0=AE=D1=80=D1=8C=D0=B5=D0=B2=D0=B8=D1=87

() =C2=A0ascii ribbon campaign - against html e-mail
/\ =C2=A0www.asciiribbon.org =C2=A0 - against proprietary attachments