Changes between Version 3 and Version 4 of HighLevelOverview


Ignore:
Timestamp:
May 13, 2011 9:40:17 AM (9 years ago)
Author:
levin@chromium.org
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • HighLevelOverview

    v3 v4  
     1Directory structure
    12
    2 WebKit is basically made up of the following:
     3 * Examples
    34
    4 1. '''JavaScriptCore''': The JavaScript engine. This also includes the WTF 
    5 library, which contains various utilities. This is completely cross-platform
    6 (though there are various platform-specific JIT backends). This can be used
    7 as a separate entity from the rest of WebKit.
     5 * [wiki:"SourceDirectory" Source] The code needed to build WebKit and nothing else.
    86
    9 2. '''WebCore:''' this is where most of the magic lives. All of the rendering 
    10 logic, SVG support, transforms, network support, etc. is here.
     7 * Tests -- Moves in progress shortly to make this directory happen -- Only the tests themselves.
     8     * Layout (Better name pending).
     9     * Manual
     10     * Performance
     11     * Unit -- The directory structure under here should be the same as Source.
     12         * gtest -- This built as part of the unit tests so it fits better here rather than the Tools directory.
    1113
    12 Each platform has specific logic here. Look in WebCore platform for 
    13 the OS-specific and rendering (Skia, CG, Cairo) backends.
     14 * Tools -- Includes many tools and utilities for WebKit development including build scripts, test harnesses, the sheriffbot, etc.
     15     * DumpRenderTree
     16     * Scripts
     17     * WebKitTestRunner
    1418
    15 3. '''WebKit''': the front-end layer used by applications. Each GUI platform 
    16 (windows, Cocoa, Gtk+, Qt) provides a different implementation of 
    17 this. Generally, the goal is to make this a client to the WebCore 
    18 layer, basically just 'shimming' WebCore to the specific Os/Platform 
    19 that will be using WebKit.
    20 
    21 The remaining projects are autogenerated bindings to the DOM, etc.
    22 
    23 (Taken from [https://lists.webkit.org/pipermail/webkit-help/2009-July/000010.html Brent's email] to webkit-help)
    24 
    25 The WebKit source tree also contains the following project:
    26 
    27 1. '''JavaScriptGlue:''' this is a legacy component needed for compatibility
    28 with some older Mac OS X software. It will eventually be retired and should
    29 not receive any new development.
    30 
    31 (Information taken from [https://bugs.webkit.org/show_bug.cgi?id=31618#c2 a Bugzilla comment by Darin])
     19 * Websites -- the code and pages for various webkit web site with the directory names reflecting the sites.
     20