Changes between Version 5 and Version 6 of QtWebKitAPI


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

--

Legend:

Unmodified
Added
Removed
Modified
  • QtWebKitAPI

    v5 v6  
    66
    77== The process ==
     8
     9Make sure you've read QtWebKitContrib
    810
    911   1. Create a new bugreport in Bugzilla describing your enhancement. Please use the following template for creating the bug: [http://webkit.org/new-qtwebkit-bug http://webkit.org/new-qtwebkit-bug]
     
    1618== API Style, Conventions and Principles ==
    1719
    18 For QtWebKit we follow the same guidelines that are used for the Qt API. You can review the entire the style guide at [http://qt.gitorious.org/qt/pages/ApiDesignPrinciples http://qt.gitorious.org/qt/pages/ApiDesignPrinciples]
     20For QtWebKit we follow the same guidelines that are used for the Qt API. You can review the entire the style guide at [http://qt.gitorious.org/qt/pages/ApiDesignPrinciples http://qt.gitorious.org/qt/pages/ApiDesignPrinciples]. Notice that although we follow the same API guidelines, the [http://webkit.org/coding/coding-style.html webkit coding style] is different from the one commonly used in Qt and should be respected.
    1921
    2022To the users of QtWebKit we promise to maintain binary and source compatibility between minor releases. We share the same policies with KDE and Qt, which are summarized on the KDE website at [http://techbase.kde.org/Policies/Library_Code_Policy http://techbase.kde.org/Policies/Library_Code_Policy]. Another recommended read is the guide about what kind of API changes are binary compatible and what can be done to work around the imposed limitations: [http://techbase.kde.org/Policies/Binary_Compatibility_Issues_With_C%2B%2B http://techbase.kde.org/Policies/Binary_Compatibility_Issues_With_C++]