components/autofill/README - Issue 16879006: In components/autofill, move common/ to core/common/

Side by Side Diff

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Side by Side Diff: components/autofill/README

Issue 16879006: In components/autofill, move common/ to core/common/ (Closed) Base URL: svn://svn.chromium.org/chrome/trunk/src

Patch Set: Rebase to fix conflict Created 7 years, 6 months 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

« no previous file with comments | « components/autofill/DEPS ('k') | components/autofill/browser/DEPS » ('j') | no next file with comments »

OLD	NEW
1 Autofill is in the process of becoming a layered component	1 Autofill is in the process of becoming a layered component

2 (https://sites.google.com/a/chromium.org/dev/developers/design-documents/layered -components-design)	2 (https://sites.google.com/a/chromium.org/dev/developers/design-documents/layered -components-design)

3 to enable it to be shared cleanly on iOS.	3 to enable it to be shared cleanly on iOS.

4	4

5 When this process is complete, this component will have the following structure:	5 When this process is complete, this component will have the following structure:

6	6

7 - Top-level shared code that does not depend on src/content/ or src/ios/	7 - core/: shared code that does not depend on src/content/ or src/ios/

	8 - browser/: Browser process code

	9 - common/: Code shared by the browser and the renderer

8 - content/: Driver for the shared code based on the content layer.	10 - content/: Driver for the shared code based on the content layer.

9 - browser/: Browser process code.	11 - browser/: Browser process code.

10 - renderer/: Renderer process code.	12 - renderer/: Renderer process code.

11 - common/: Code shared by the browser and the renderer.	13 - common/: Code shared by the browser and the renderer.

12 - ios/: Driver for the shared code based on src/ios.	14 - ios/: Driver for the shared code based on src/ios.

13	15

14 See	16 See

15 https://sites.google.com/a/chromium.org/dev/developers/design-documents/layered- components-technical-approach/making-autofill-into-a-layered-component	17 https://sites.google.com/a/chromium.org/dev/developers/design-documents/layered- components-technical-approach/making-autofill-into-a-layered-component

16 for an outline of the project.	18 for an outline of the project.

17	19

18 For pointers on how to continue getting your work done as the component moves	20 For pointers on how to continue getting your work done as the component moves

19 into its new structure, see	21 into its new structure, see

20 https://sites.google.com/a/chromium.org/dev/developers/design-documents/layered- components-technical-approach/making-autofill-into-a-layered-component#TOC-Help- How-Do-I-Get-My-Autofill-Related-Work-Done-	22 https://sites.google.com/a/chromium.org/dev/developers/design-documents/layered- components-technical-approach/making-autofill-into-a-layered-component#TOC-Help- How-Do-I-Get-My-Autofill-Related-Work-Done-

21	23

OLD	NEW