Webkit
This is an article to describe what I found in the process of studying Webkit.
WebKit is a layout engine designed to allow web browsers to render web pages. The WebKit engine provides a set of classes to display web content in windows, and implements browser features such as following links when clicked by the user, managing a back-forward list, and managing a history of pages recently visited.
WebKit has 2 components: WebCore and JavaScriptCore. WebCore is a layout, rendering, and Document Object Model (DOM) library for HTML and SVG, JavaScriptCore is a framework that provides a JavaScript engine for WebKit implementations.
The WebKit framework wraps WebCore and JavaScriptCore, providing an Objective-C application programming interface to the C++-based WebCore rendering engine and JavaScriptCore script engine, allowing it to be easily referenced by applications based on the Cocoa API; later versions also include a cross-platform C++ platform abstraction, and various ports provide additional APIs.
Origyn Web Browser(OWB)
OWB is a WebKit®-based web browser designed for consumer electronic devices.
There are many samples implementations.
• The best one is GTK-based, which provides full option WebKit.
• There is also a sample implementation for SDL which allows you to test the browser (under optimized, clearly), on many platforms.
OWBAL (Origyn Web Browser Abstraction Layer) is the core re-factoring of webkit, allowing separate dependencies at the library level instead of the platform-wide level.
OWB graphics reference implementation is based on SDL.
The OwBal architecture, while looking complicated, is actually very straightforward; additionally, the CCMake architecture makes it easy to select which components need to be ported or not.
CMake
CMake generates native makefiles and workspaces that can be used in the compiler environment of your choice.
CMake is controlled by writing instructions in CMakeLists.txt files. Each directory in your project should have a CMakeLists.txt file.
To convert your CMakeLists.txt description into a traditional make build system automatically, change into your build directory and run cmake pointing it to the directory of the top-level CMakeLists.txt.
If all goes well, cmake will process your CMakeLists.txt files, find the location of all libraries and include paths and spew a bunch of configuration information including a traditional Makefile in your build directory. (this cmake process is similar to ./configure). You are now ready to build your code using the traditional make system. Run make in your build directory to compile and link everything.
To build OWB
# mkdir build
# cd build
# cmake ../
WebKit is a layout engine designed to allow web browsers to render web pages. The WebKit engine provides a set of classes to display web content in windows, and implements browser features such as following links when clicked by the user, managing a back-forward list, and managing a history of pages recently visited.
WebKit has 2 components: WebCore and JavaScriptCore. WebCore is a layout, rendering, and Document Object Model (DOM) library for HTML and SVG, JavaScriptCore is a framework that provides a JavaScript engine for WebKit implementations.
The WebKit framework wraps WebCore and JavaScriptCore, providing an Objective-C application programming interface to the C++-based WebCore rendering engine and JavaScriptCore script engine, allowing it to be easily referenced by applications based on the Cocoa API; later versions also include a cross-platform C++ platform abstraction, and various ports provide additional APIs.
Origyn Web Browser(OWB)
OWB is a WebKit®-based web browser designed for consumer electronic devices.
There are many samples implementations.
• The best one is GTK-based, which provides full option WebKit.
• There is also a sample implementation for SDL which allows you to test the browser (under optimized, clearly), on many platforms.
OWBAL (Origyn Web Browser Abstraction Layer) is the core re-factoring of webkit, allowing separate dependencies at the library level instead of the platform-wide level.
OWB graphics reference implementation is based on SDL.
The OwBal architecture, while looking complicated, is actually very straightforward; additionally, the CCMake architecture makes it easy to select which components need to be ported or not.
CMake
CMake generates native makefiles and workspaces that can be used in the compiler environment of your choice.
CMake is controlled by writing instructions in CMakeLists.txt files. Each directory in your project should have a CMakeLists.txt file.
To convert your CMakeLists.txt description into a traditional make build system automatically, change into your build directory and run cmake pointing it to the directory of the top-level CMakeLists.txt.
If all goes well, cmake will process your CMakeLists.txt files, find the location of all libraries and include paths and spew a bunch of configuration information including a traditional Makefile in your build directory. (this cmake process is similar to ./configure). You are now ready to build your code using the traditional make system. Run make in your build directory to compile and link everything.
To build OWB
# mkdir build
# cd build
# cmake ../
留言