Changes between Version 70 and Version 71 of QtWebKitContrib


Ignore:
Timestamp:
Oct 20, 2010, 3:29:54 PM (14 years ago)
Author:
Ademar Reis
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • QtWebKitContrib

    v70 v71  
    5353
    5454== Hacking on QtWebKit ==
    55 
    5655Effective immediately all commits to QtWebKit should use the [http://webkit.org/coding/coding-style.html WebKit coding style] for '''all files''' in the project. That includes qwebview(.h|cpp), qwebpage(.h|.cpp) and all others. Repeat: the Qt style should not be used. Thank you.
    5756
    … …  
    5958 * [wiki:"QtWebKitAPI" Process of contribution to QtWebKit's API]
    6059
     60== Information on Git for QtWebKit developers ==
     61 * [wiki:"UsingGitWithWebKit" Using Git with WebKit]
     62 * [http://ktown.kde.org/~zrusin/git/git-cheat-sheet-medium.png A Git cheat sheet]
     63 * [http://eagain.net/articles/git-for-computer-scientists/ An excellent article on Git for computer scientists]
     64
     65== Communication ==
     66We use the regular webkit-dev mailing and IRC channels list to coordinate:
     67
     68 * [http://lists.webkit.org/mailman/listinfo.cgi/webkit-qt webkit-qt Mailing List]
     69 * [http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev webkit-dev Mailing List]
     70 * IRC: #qtwebkit at freenode
     71 * IRC: #webkit at freenode
     72
    6173=== Running the tests ===
    6274
    6375==== Dependencies ====
    64 
    6576You will need to install the following packages to run the layout tests:
    6677
    … …  
    8394
    8495==== Installing the layout test fonts/Using run-webkit-tests ====
    85 
    8696To run the tests the normal WebKit layout test infrastructure is used. In addition you need a fixed set of fonts for testing. You can download them using Git from Gitorious:
    8797
    … …  
    111121
    112122=== Building API Docs ===
    113 
    114123Before you can build the API docs you need make sure to have Qt build from sources and run {{{make docs}}} in your Qt build directory once. This will ensure that the Qt API documentation is built and can be referenced from the QtWebKit docs and it will also ensure that qdoc (the tool that generates the API docs) is built.
    115124
    116125To build the QtWebKit API docs simply run {{{make docs}}} in your build directory, i.e. {{{WebKitBuild/Release}}}. The output will be generated in HTML in the {{{doc/html}}} subdirectory.
    117126
    118 == Information on Git for QtWebKit developers ==
    119  * [wiki:"QtWebKitGitInstructions" QtWebKit Git Instructions]
    120  * [wiki:"UsingGitWithWebKit" Using Git with WebKit]
    121  * [http://ktown.kde.org/~zrusin/git/git-cheat-sheet-medium.png A Git cheat sheet]
    122  * [http://eagain.net/articles/git-for-computer-scientists/ An excellent article on Git for computer scientists]
    123 
    124 
    125 == Communication ==
    126 We use the regular webkit-dev mailing and IRC channels list to coordinate:
    127 
    128  * [http://lists.webkit.org/mailman/listinfo.cgi/webkit-qt webkit-qt Mailing List]
    129  * [http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev webkit-dev Mailing List]
    130  * IRC: #qtwebkit at freenode
    131  * IRC: #webkit at freenode
    132 
    133127== Obtaining Check-In Privileges ==
    134 
    135128Contributors with a proven track record of good patch submissions and that have demonstrated an ability to work well with the community can obtain check-in privileges to the QtWebKit git repository. 
    136129
    … …  
    142135
    143136== Attic ==
    144 
    145137 * [wiki:"QtWebKitTodo" TODO List]