Searched full:guidelines (Results 1 – 25 of 293) sorted by relevance
12345678910>>...12
| /external/chromium-trace/catapult/third_party/flot/ |
| D | CONTRIBUTING.md | 3 We welcome all contributions, but following these guidelines results in less 38 4. Format your code according to the style guidelines below. 40 ### Flot Style Guidelines ### 42 Flot follows the [jQuery Core Style Guidelines](http://docs.jquery.com/JQuery_Core_Style_Guidelines…
|
| /external/chromium-trace/catapult/third_party/Paste/docs/ |
| D | DeveloperGuidelines.txt | 86 * Try to keep to the `Style Guidelines`_. But if you are bringing in 88 have a choice, follow that. Those guidelines are meant to represent 92 .. _Style Guidelines: StyleGuide.html
|
| /external/libxml2/doc/ |
| D | guidelines.html | 16 <title>XML resources publication guidelines</title> 20 <h1 align="center">XML resources publication guidelines</h1> 24 <p>The goal of this document is to provide a set of guidelines and tips 36 These guidelines hope to improve the matter and provide a better overview of 42 <li><a href="#Design">Design guidelines</a></li> 48 <h2><a name="Design">Design guidelines</a></h2> 364 <p>Following the set of guidelines and tips provided in this document should
|
| D | ChangeLog.xsl | 38 <li><a href="{$href_base}guidelines.html">XML Guidelines</a></li>
|
| /external/mesa3d/src/gallium/ |
| D | README.portability | 1 CROSS-PLATFORM PORTABILITY GUIDELINES FOR GALLIUM3D 9 headers in general, should strictly follow these guidelines to ensure
|
| /external/libxml2/test/valid/ |
| D | xhtml1.xhtml | 129 agents is possible by following a small set of guidelines.</p> 254 <li class="tocline"><a href="#guidelines">Appendix C. HTML Compatibility Guidelines</a></li> 276 simple <a href="#guidelines">guidelines</a> are followed, 906 href="#guidelines">HTML Compatibility Guidelines</a> for information on ways to 997 See the <a href="#guidelines">HTML Compatibility 998 Guidelines</a> for information on ensuring such anchors are backwards 1010 accomplish. Guidelines for creating compatible documents can be 1011 found in <a href="#guidelines">Appendix C</a>.</p> 1018 <p>However, XHTML Documents which follow the guidelines set forth 1019 in <a href="#guidelines">Appendix C</a>, "HTML Compatibility Guidelines" may be [all …]
|
| /external/libxml2/result/valid/ |
| D | xhtml1.xhtml | 114 agents is possible by following a small set of guidelines.</p> 230 <li class="tocline"><a href="#guidelines">Appendix C. HTML Compatibility Guidelines</a></li> 252 simple <a href="#guidelines">guidelines</a> are followed, 864 …e> or <code><hr></hr></code>. See <a href="#guidelines">HTML Compatibility Guidelines<… 953 See the <a href="#guidelines">HTML Compatibility 954 Guidelines</a> for information on ensuring such anchors are backwards 966 accomplish. Guidelines for creating compatible documents can be 967 found in <a href="#guidelines">Appendix C</a>.</p> 974 <p>However, XHTML Documents which follow the guidelines set forth 975 in <a href="#guidelines">Appendix C</a>, "HTML Compatibility Guidelines" may be [all …]
|
| /external/dbus/ |
| D | HACKING | 1 The guidelines in this file are the ideals; it's better to send a 2 not-fully-following-guidelines patch than no patch at all, though. We 14 Most of D-Bus is security sensitive. Guidelines related to that: 328 style guidelines
|
| /external/libgdx/ |
| D | CONTRIBUTING.md | 6 Following these guidelines helps to communicate that you respect the time of 31 Guidelines for bug reports: 111 A couple of guidelines:
|
| /external/skia/ |
| D | CONTRIBUTING | 1 Please see the guidelines for contributing code at https://skia.org/dev/contrib/
|
| /external/okhttp/okio/ |
| D | BUG-BOUNTY.md | 9 guidelines at https://hackerone.com/square-open-source
|
| /external/okhttp/ |
| D | BUG-BOUNTY.md | 9 guidelines at https://hackerone.com/square-open-source
|
| /external/libweave/include/weave/provider/ |
| D | http_server.h | 30 // same guidelines as implementation of AddHttpRequestHandler(...) with the 38 // Implementation of GetHttpsPort() should follow the same guidelines as
|
| /external/skia/site/user/quick/ |
| D | index.md | 4 System-specific guidelines:
|
| /external/chromium-trace/catapult/telemetry/ |
| D | OWNERS | 2 # http://dev.chromium.org/developers/telemetry/telemetry-feature-guidelines
|
| D | README.md | 116 * [Feature guidelines](https://sites.google.com/a/chromium.org/dev/developers/telemetry/telemetry…
|
| /external/chromium-trace/catapult/third_party/closure_linter/ |
| D | README.chromium | 10 The Closure Linter enforces the guidelines set by the Google JavaScript Style
|
| /external/llvm/utils/vim/ |
| D | vimrc | 1 " LLVM coding guidelines conformance for VIM 68 " Useful macros for cleaning up code to conform to LLVM coding guidelines
|
| /external/androidplot/Examples/DemoApp/res/values/ |
| D | dimens.xml | 5 <!-- Default screen margins, per the Android Design guidelines. -->
|
| /external/opencv3/ |
| D | README.md | 16 Summary of guidelines:
|
| /external/llvm/utils/emacs/ |
| D | emacs.el | 1 ;; LLVM coding style guidelines in emacs
|
| /external/libvncserver/ |
| D | TODO | 12 style fixes: use Linux' coding guidelines & ANSIfy tightvnc-filetransfer:
|
| /external/chromium-trace/catapult/third_party/gsutil/third_party/boto/ |
| D | README.rst | 24 To port a module to Python 3.3+, please view our `Contributing Guidelines`_ 199 .. _Contributing Guidelines: https://github.com/boto/boto/blob/develop/CONTRIBUTING
|
| /external/chromium-trace/catapult/telemetry/third_party/webpagereplay/ |
| D | README.md | 28 guidelines](documentation/Contributing.md).
|
| /external/boringssl/src/ |
| D | README.md | 28 * [STYLE.md](/STYLE.md): rules and guidelines for coding style.
|
12345678910>>...12