Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(223)

Side by Side Diff: components/README

Issue 11648012: Establish src/components/ directory. (Closed) Base URL: svn://svn.chromium.org/chrome/trunk/src
Patch Set: Created 8 years ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View unified diff | Download patch | Annotate | Revision Log
« components/DEPS ('K') | « components/OWNERS ('k') | no next file » | no next file with comments »
Toggle Intra-line Diffs ('i') | Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
OLDNEW
(Empty)
1 This directory is for components that have the Content Module as the
2 uppermost layer they depend on. They may depend only on the Content
3 API (content/public) and on lower layers (e.g. base/, net/, ipc/
4 etc.).
5
6 Components that have bits of code that need to live in different
7 processes (e.g. some code in the browser process, some in the renderer
8 process, etc.) should separate the code into different subdirectories.
9 Hence for a component named 'foo' you might end up with a structure
10 like the following:
11
12 components/foo - DEPS, OWNERS, foo.gypi
13 components/foo/browser - code that needs the browser process
14 components/foo/common - for e.g. IPC constants and such
15 components/foo/renderer - code that needs renderer process
16
17 These subdirectories should have DEPS files with the relevant
18 restrictions in place, i.e. only components/*/browser should
19 be allowed to #include from content/public/browser.
20
21 Note that there may also be an 'android' subdir, with a Java source
22 code structure underneath it where the package name is
23 org.chromium.components.foo, and with subdirs after 'foo'
24 to illustrate process, e.g. 'browser' or 'renderer':
25
26 components/foo/android/OWNERS, DEPS
27 components/foo/android/java/src/org/chromium/components/foo/browser/
28 components/foo/android/javatests/src/org/chromium/components/foo/browser/
29
30 The code in each component, or group of components, should be placed
Jói 2012/12/19 14:35:20 Note: The previous decision, when content/compone
jam 2012/12/19 17:12:58 the convention for namespaces has been that every
Jói 2012/12/20 15:16:32 OK, let's go with components:: as the namespace.
31 in a namespace named for the component, e.g. a component
32 components/foo might use the namespace foo::.
OLDNEW
« components/DEPS ('K') | « components/OWNERS ('k') | no next file » | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698