Chromium Code Reviews| Index: components/autofill/README.txt |
| diff --git a/components/autofill/README.txt b/components/autofill/README.txt |
| new file mode 100644 |
| index 0000000000000000000000000000000000000000..e1be4a313f85be5bac722b186416eae805ac34a9 |
| --- /dev/null |
| +++ b/components/autofill/README.txt |
| @@ -0,0 +1,20 @@ |
| +Autofill is in the process of becoming a layered component |
| +(https://sites.google.com/a/chromium.org/dev/developers/design-documents/layered-components-design) to enable it to be shared cleanly on iOS. |
|
Jói
2013/06/05 19:08:55
Break after the closing parenthesis?
blundell
2013/06/06 07:23:48
Done.
|
| + |
| +When this process is complete, this component will have the following structure: |
| + |
| +- Top-level shared code that does not depend on src/content/ or src/ios/ |
| +- content/: Driver for the shared code based on the content layer. |
| + - browser/: Browser process code. |
| + - renderer/: Renderer process code. |
| + - common/: Code shared by the browser and the renderer. |
| +- ios/: Driver for the shared code based on src/ios. |
| + |
| +See |
| +https://sites.google.com/a/chromium.org/dev/developers/design-documents/layered-components-technical-approach/making-autofill-into-a-layered-component |
| +for an outline of the project. |
| + |
| +For pointers on how to continue getting your work done as the component moves |
| +into its new structure, see |
| +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- |
| + |