These files are used by devsite only, so are maintained in piper.
bug: 79155333
test: make ds-docs (human review)
Change-Id: I5d5662a2a401872a669dba0916b20a79bcfca7ae
(cherry picked from commit 9e64abe7d79ef6abdd9c2d65e5f3bead9138cdb4)
Fixes: 76462084
Test: make doc-comment-check-docs, open $ANDROID_BUILD_TOP/out/target/common/docs/doc-comment-check/reference/android/view/WindowManager.LayoutParams.html, navigate to LAYOUT_IN_DISPLAY_CUTOUT_MODE_SHORT_EDGES
Change-Id: I8a9df979cbb062896fa874a163414a4f8a095b21
- Move camera reference doc images to /reference/images
- Minor formatting changes due to merging SDK/NDK metadata definitions
- Minor wording changes for the same
Bug: 69175492
Bug: 29102963
Bug: 33262893
Test: Build and manual inspection of generated docs diff
Change-Id: Ieaf0c1943eba378cc94a22d184734602c40e25e7
Previously deleted almost all the docs (with CL http://ag/1970807),
since those docs are now managed and staged/published from Piper.
However, reference docs are still generated in Gerrit, so it's useful
to be able to stage those docs from a Gerrit client--and that was
broken by my change, since the staging tool expects to see
_book.yaml and _project.yaml in the reference doc directory. So,
restoring those files to re-enable staging of reference docs from
Gerrit.
The publish process is *not* changed: we still grab a good build
from the appropriate Gerrit branch and migrate those files into
Piper, then publish the Piper files.
Test: make ds-docs ; devsite stage --site=android en/reference
Change-Id: I392f1699dc68767d1ac9b7113a149062e5e48ef7
It tooks 10 years, but better late than never!
Bug: 32984164
Test: Compiled documentation and checked in Chrome
Change-Id: I6dfd7fba6d3077f8c774b203589083bdbc15f9d2
Original Change-Id: I5331cdc968be817ff70ba32dd03fce76493a6ab8
Test: make ds-docs
Android developer docs are now maintained in Piper, go/dac-source
Removing all files from Gerrit, since these files can cause build
errors if they refer to classes that are later removed (whence
bug b/35849713 ).
Gerrit already has readme files in these directories telling people
docs are not maintained here; these readmes will be a lot easier to
spot now.
Ran a doc build with these files deleted, and it seems to work fine,
so submitting this CL *shouldn't* break anything.
Bug: 35849713
Change-Id: Ic74c3f97f9620daf23543930a8b7ed1386f4d172
This configuration uses 64 bits per pixel. Heach component is stored as a
half precision float value (16 bits). Half floats can be decoded/encoded
using android.util.Half.
RGBA_F16 bitmaps are used to decode wide-gamut images stored in 16 bit
formats (PNG 16 bit for instance). aapt is currently not aware of PNG
16 bits so such files must be placed in raw/ resource directories.
This first pass provides only partial drawing support with hardware
acceleration. RGBA_F16 bitmaps are stored in linear space and need
to be encoded to gamma space with the appropriate OETF to be rendered
properly on Android's current surfaces. They are however suitable for
linear blending. Full rendering support will be provided in a future
CL (BitmapShaders might be a bit tricky to handle properly during
shader generation).
Bug: 32984164
Test: bit CtsGraphicsTestCases:android.graphics.cts.BitmapRGBAF16Test
Change-Id: I328e6b567441a1b9d152a3e7be944a2cf63193bd
ColorSpace.createRenderer() returns a ColorSpace.Renderer which
can be used to visualize multiple color spaces and colors (each
associated with a specific color space) in the same CIE 1931 xyY
chromaticity diagram. This API was used to generate all the
diagrams shown in the documentation.
Bug: 32984164
Test: ColorSpaceTest in CTS
Change-Id: Ic94d939d5cfd563d826701f5e876b67b47ed56ec
Bug: 21721463
Training module and related API-reference documentation. This is new
material for Android Wear D(iamond) release.
Change-Id: I9959bca50fd96812abd7cfb693139986bc59b133
* commit '7af3566912b0e014cfd1704acdeb31a0a7cca0d3':
docs: Added Javadocs for Testing Support Library v0.3 and updated the corresponding setup instructions. bug: 21442922
