ashatora/openlayers
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

More documentation improvements

Browse Source
This commit is contained in:
Andreas Hocevar
2015-04-02 14:33:29 +02:00
parent 4cce0f4936
commit 95c127d235
1 changed files with 7 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files
examples_src/readme.md
+7 -13
View File
@@ -1,16 +1,10 @@
# Code examples # Code examples
Although the main purpose of these examples is to demonstrate how to use the API, they also serve other purposes in the development cycle, and so are not exactly as they would be in normal application code: The `.html` files in this folder are built by applying the templates in the `config/examples/` folder. Examples have [YAML front-matter](http://www.metalsmith.io) headers with the following properties:
* every time the library changes, they are compiled together with the library as a basic check that they remain in sync with the library * template: The template from the `config/examples/` directory to use for this example
* they use a special loader script to enable defining at run time which build mode (raw/debug/advanced) to use * title: The title of the example
* shortdesc: A short description for the example index
To enable this, examples have the following, not needed in application code: * docs: Documentation of the example. Can be markdown.
* tags: Tags for the example index
* each html file loads `loader.js`; application code would not need this, but would instead load the appropriate library build file, either a hosted version or a custom build * resources: Additional js or css resources required by the example. This is a comma separated list of URLs.
* each js file starts with `goog.require` functions, used by the compiler; application code would only have these if the code is to be compiled together with the library and/or Closure library
* some js files use type definitions (comments with @type tags); these are also used by the compiler, and are only needed if the code is to be compiled together with the library
* html files load `example-behaviour.js` and some js files define the Map renderer option as `exampleNS.getRendererFromQueryString()`; application code would not need these
* in addition, examples use Twitter Bootstrap and jQuery; this is of course not a requirement - you may use whichever presentation/helper libraries you wish
See [Quick Start tutorial](http://openlayers.org/en/master/doc/quickstart.html) for a simple example of how application code would use the library.