Changes between Version 12 and Version 13 of Modules


Ignore:
Timestamp:
Feb 27, 2012 7:17:27 PM (9 years ago)
Author:
abarth@webkit.org
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Modules

    v12 v13  
    1111The code for a module belongs in a subdirectory of the [http://trac.webkit.org/browser/trunk/Source/WebCore/Modules/ Modules] directory and in a subdirectory of [http://trac.webkit.org/browser/trunk/Source/WebCore/platform/ WebCore/platform].  For example, the MediaStream module is contained in http://trac.webkit.org/browser/trunk/Source/WebCore/Modules/mediastream and http://trac.webkit.org/browser/trunk/Source/WebCore/platform/mediastream.
    1212
    13 Keeping the code for your feature in a single directory reduces the burden that your feature places on other WebKit contributors as they develop other modules and core functionality of the engine.  This [https://docs.google.com/drawings/d/10WlCj2J3arxf4cDGRKteNinaP755iFnmYtYtnNSCQOY/edit?authkey=CP6plYAI dependency diagram] shows how the WebAudio, MediaStream, and IndexedDB modules fit into the WebKit's dependency diagram.  Notice, in particular, that WebCore proper ''should not'' have dependencies on your module.
     13Keeping the code for your feature in a single directory reduces the burden that your feature places on other WebKit contributors as they develop other modules and core functionality of the engine.  This [https://docs.google.com/drawings/d/10WlCj2J3arxf4cDGRKteNinaP755iFnmYtYtnNSCQOY/edit?authkey=CP6plYAI dependency diagram] shows how the WebAudio, MediaStream, and IndexedDB modules fit into the WebKit's dependency diagram.  Notice, in particular, that WebCore proper should not have dependencies on your module.
    1414
    1515== Associating JavaScript APIs with "core" objects ==