chromium/src
0
Fork 0
Code Activity

Add/update printing and pdf README files.

Browse Source 
Document the relationship between the low-level directory and the higher
level components directory. Also change files to Markdown.

Change-Id: I6cdac633cda329c41a75418ebf630d977d90a2cf
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2971195
Commit-Queue: Lei Zhang <thestig@chromium.org>
Reviewed-by: Daniel Hosseinian <dhoss@chromium.org>
Cr-Commit-Position: refs/heads/master@{#893857}
This commit is contained in:
Lei Zhang
2021-06-18 17:23:11 +00:00
committed by Chromium LUCI CQ
parent 727f20ef44
commit a40fc29aff
5 changed files with 22 additions and 5 deletions
components
pdf
README.md
printing
READMEREADME.md
pdf
README.md
printing
README.md

7
components/pdf/README → components/pdf/README.md

@ -1,4 +1,7 @@
The PDF component contains code necessary for using the PDF plugin in
content-based clients. It provides an implementation for the PPB_PDF ppapi
content-based clients. It provides an implementation for the PPB\_PDF PPAPI
interface, and the necessary browser and renderer-side code for processing the
relevant IPC mesages.
relevant IPC messages. The PDF plugin code lives in `//pdf`.
TODO(crbug.com/702993): Update description when the PDF plugin no longer uses
PPAPI and is also no longer a plugin process.

3
components/printing/README

@ -1,3 +0,0 @@
Printing is a work in progress component. It is introduced to allow chrome
and webview to share the common printing-related code. When completed, it will
contain the code necessary for using basic printing in content-based clients.

4
components/printing/README.md Normal file

@ -0,0 +1,4 @@
The printing component contains code that lives above the content layer. It
allows multiple embedders, like `//chrome`, `//headless`, and
`//android_webview`, to share the code necessary to perform basic printing.
Foundational printing code lives in `//printing`.

9
pdf/README.md Normal file

@ -0,0 +1,9 @@
`//pdf` contains the PDF plugin, its Blink-based replacement, as well as PDF
utility functions that leverage PDFium. It can use low-level components that
live below the content layer, as well as other foundational code like
`//printing`. It should not use `//content` or anything in `//components` that
lives above the content layer. Code that lives above the content layer should
live in `//components/pdf`, or in the embedder. All the code here should run in
sandboxed child processes.
TODO(crbug.com/1220865): Remove existing `//content` dependencies.

4
printing/README.md Normal file

@ -0,0 +1,4 @@
`//printing` contains foundational code that is used for printing. It can depend
on other low-level directories like `//cc/paint` and `//ui`, but not higher
level code like `//components` or `//content`. Higher level printing code should
live in `//components/printing` or the embedder.