cherry-pick from CL: https://android-review.googlesource.com/148241
This CL replaces the Doxygen generated documentation by one that's created
by our internal tool found in framework/rs/api. The big advantages:
- Can handle overloaded functions. Doxygen could not and RenderScript has many.
- Can have version information.
- Can match the look of the Java documentation.
- Cleaner look and no leaking of internal paths.
This CL also include changes introduced by the L release which was missing
previously.
Change-Id: Icade41d04d35e45c445ad952bb8ce14389f9f59f
* commit '62eaad7200e172404db587ecec9940670946e92a':
cherrypick from lmp-docs Docs: Correcting how to escape quotes. Original Change-Id: I417546a473f0ebe76a6e4102b87883a85365ac26
Original Change-Id: I417546a473f0ebe76a6e4102b87883a85365ac26
The behavior for single and double-quotes is different--I expanded
this section to note how they differ.
bug: 19959941
Change-Id: I9be9c066c416e9403a3ac164af0b1ce35f7ab1dd
This updates the documentation of the application element of
AndroidManifest.xml to mention the new android:usesCleartextTraffic
attribute.
This also updates the Javadoc of
android.security.NetworkSecurityPolicy and ApplicationInfo to match.
Bug: 19215516
Change-Id: I5c221b56addae8988b4db51994d18ae379d0fbe3
The behavior for single and double-quotes is different--I expanded
this section to note how they differ.
(New version of a Gerrit CL I abandoned because of a commit mess-up.)
See first comment for doc stage location.
bug: 19959941
Change-Id: I417546a473f0ebe76a6e4102b87883a85365ac26
Also fixed the line breaks in android:configChanges so the syntax
code box doesn't need a horizontal scroll bar.
See first comment for doc stage location.
bug: 19935160
Change-Id: I1ec34473e743a9f0c921f771cfb47129c47f9014
While I had gridview open (per the bug), I also checked the other
files in that directory for broken image links (in case this stemmed
from a doc reorg). I didn't find any broken images, but I did find
a couple of code samples that unnecessarily had horizontal scroll
bars, so I fixed those.
See first comment for doc stage location.
bug: 19611361
Change-Id: I983a09aaee5e2b1747376748c1aa46341c31a3c2
* commit '83b96e02a4bc8b0e9f5308b441609411ee347baf':
docs: Remove deprecated Fitness information from this doc. Guides have been moved to developers.google.com/fit
* commit 'd9eb3881f452ecb4b77062eb6505a3d7601d0a8c':
docs: Remove deprecated Fitness information from this doc. Guides have been moved to developers.google.com/fit
* commit '217a435665880076abb71085e9d76aec4ff83b6d':
docs: Remove deprecated Fitness information from this doc. Guides have been moved to developers.google.com/fit
The guide documentation for the manifest data element contains a
grammar that implies leading slashes are not required for the path
part of a URI string. Also the path documentation does not mention
the need for a leading slash.
Grammar from documentation:
<scheme>://<host>:<port>/[<path>|<pathPrefix>|<pathPattern>]
^
|
Included "/" -----------+
All internal usages of path, pathPrefix, and pathPattern, have a /
starting out the string and these attributes don't work without that
/.
This change updates the grammar and the documentation for the path
attributes.
Fixes bug 19540035
Change-Id: I931a25fd1c10c01eaa32a7cfa82cca256b129efb
The guide documentation for the manifest data element contains a
grammar that implies leading slashes are not required for the path
part of a URI string. Also the path documentation does not mention
the need for a leading slash.
Grammar from documentation:
<scheme>://<host>:<port>/[<path>|<pathPrefix>|<pathPattern>]
^
|
Included "/" -----------+
All internal usages of path, pathPrefix, and pathPattern, have a /
starting out the string and these attributes don't work without that
/.
This change updates the grammar and the documentation for the path
attributes.
Fixes bug 19540035
Change-Id: I931a25fd1c10c01eaa32a7cfa82cca256b129efb
