diff options
Diffstat (limited to 'ChangeLog')
| -rw-r--r-- | ChangeLog | 65 |
1 files changed, 65 insertions, 0 deletions
@@ -1,3 +1,68 @@ +2012-11-23 Krzysztof Czech <k.czech@samsung.com> + + [EFL] Platform support for Accessibility feature. + https://bugs.webkit.org/show_bug.cgi?id=100848 + + Reviewed by Gyuyoung Kim. + + Add support for ATK library. + + * Source/cmake/FindATK.cmake: Added. + * Source/cmake/OptionsEfl.cmake: + +2012-09-26 Gustavo Noronha Silva <gns@gnome.org> + + [GTK] Split SVG from WebCore to work-around make limitation + https://bugs.webkit.org/show_bug.cgi?id=97735 + + Reviewed by Carlos Garcia Campos. + + Add a new libtool convenience library, libWebCoreSVG.la, to work-around + make limitation when linking libWebCore. + + * GNUmakefile.am: variables for the new library. + +2012-11-22 Simon Hausmann <simon.hausmann@digia.com>, Pierre Rossi <pierre.rossi@digia.com> + + [Qt] Separate QWidget dependant code into separate WebKitWidgets static library + https://bugs.webkit.org/show_bug.cgi?id=102800 + + Reviewed by Tor Arne Vestbø. + + This patch separates code that needs to use QWidget related APIs in + WebKit/qt/WebCoreSupport and Api from code that doesn't. This means for + example FrameLoaderClientQt.cpp remains in the WebKit1 static library, + while qwebpage.cpp and qwebframe.cpp become part of the WebKitWidgets + static library. WebKit1 is compiled without QT += widgets and therefore + any widget related dependency has been moved "up" and out of WebKit1 into + the WebKitWidgets library. + + Between the code in WebKit.a and WebKitWidgets.a new adapters and + interfaces have been introduced, such as QWebPageAdapter and + QWebFrameAdapter. QWebPageAdapter, when used from WebKit1, is a way to + call out into the API layer, implemented by QWebPage (QWebPagePrivate). + The other way around if QWebPage wants to access WebCore or + WebCoreSupport related functionality, it will go through + QWebPageAdapater (as base class). The separation in the direction up + into the API layer is complete with this patch, no code in WebKit1 + depends on QtWidgets. The separation the other way around, code in the + API layer not using any WebCore types, is not complete yet. + + Some classes such as QWebSettings, QWebElement or + DumpRenderTreeSupportQt remain in WebKit1. While they are API layer, + they do not depend on widget related Qt APIs and they make much more + use of WebCore internal APIs and therefore are easier to keep in + WebKit1. + + In the future we plan to place a real shared library boundary between + WebKit1 and WebKitWidgets, by keeping the WebKit1 static library as + part of the QtWebKit shared library and by turning the WebKitWidgets + static library into a shared one. + + + * Source/api.pri: + * WebKit.pro: + 2012-11-21 Ryuan Choi <ryuan.choi@gmail.com> [EFL] Remove unnecessary definition, -DENABLE_SPELLCHECK=1 |