Changes between Version 8 and Version 9 of WebKitGTK/AddingNewWebKit2API


Ignore:
Timestamp:
Mar 21, 2013 12:23:00 PM (8 years ago)
Author:
Carlos Garcia Campos
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • WebKitGTK/AddingNewWebKit2API

    v8 v9  
    11= Adding new API to WebKit2 GTK+ =
    22
    3 {{{
    4 #!comment
    5 * Patches including new public API should be approved by at least two reviewers
    6 Remove this comment when we release the first stable verion
    7 }}}
     3 * Patches including new public API should be approved by at least two reviewers
    84 * Patches should include API documentation for new methods, properties, signals, etc.
    95  * See http://developer.gnome.org/gtk-doc-manual/stable/
     
    139  * If the patch adds a new public class, add the get_type() method to file [http://trac.webkit.org/browser/trunk/Source/WebKit2/UIProcess/API/gtk/docs/webkit2gtk.types UIProcess/API/gtk/docs/webkit2gtk.types]
    1410  * If the patch adds a new section, remember to update the file [http://trac.webkit.org/browser/trunk/Source/WebKit2/UIProcess/API/gtk/docs/webkit2gtk-docs.sgml UIProcess/API/gtk/docs/webkit2gtk-docs.sgml] too
     11  * Add Since: tag using the next major release.
     12  * Check if this is the first new symbol for the next major stable release and add the index of new symbols to the file [http://trac.webkit.org/browser/trunk/Source/WebKit2/UIProcess/API/gtk/docs/webkit2gtk-docs.sgml UIProcess/API/gtk/docs/webkit2gtk-docs.sgml]
     13  {{{
     14<index id="api-index-2-2" role="2.2">
     15  <title>Index of new symbols in 2.2</title>
     16  <xi:include href="xml/api-index-2.2.xml"><xi:fallback /></xi:include>
     17</index>
     18  }}}
    1519 * Patches should always include unit tests for new API when possible
    1620 * If the patch adds a new public header