Go to file

ahocevar 77a8e91a2e Merge pull request #1337 from ahocevar/no-foo

Proper namespace and sub-parser management in OGC parsers

2013-12-06 00:47:59 -08:00

apidoc

Move apidoc CSS style out of layout.css

2013-11-21 10:51:59 +01:00

bin

Merge pull request #1118 from twpayne/build-examples-together

2013-10-15 03:48:34 -07:00

buildcfg

Activate more compiler checks

2013-11-19 21:19:22 +01:00

css

add Terms of Service to the Bing attribution

2013-10-31 16:49:46 +01:00

doc

Link to API docs

2013-09-24 15:14:50 +02:00

examples

add missing requires

2013-12-02 09:48:59 +01:00

externs

Rename externs/html5.js to externs/closure-compiler.js

2013-09-08 16:53:28 +02:00

licenses

move the licenses dir to the root of the repo

2012-03-29 21:59:58 +02:00

resources

Move apidoc CSS style out of layout.css

2013-11-21 10:51:59 +01:00

src

Proper namespace and sub-parser management

2013-12-06 01:08:45 +01:00

tasks

Making use of the closure-util package

2013-09-14 18:10:12 -06:00

test

Merge pull request #1336 from ahocevar/fix-writers-typo

2013-12-05 16:00:13 -08:00

.gitignore

Making use of the closure-util package

2013-09-14 18:10:12 -06:00

.travis.yml

Use a released version of jsdoc

2013-11-06 19:11:21 +01:00

AUTHORS.md

Converted AUTHORS and LICENSE files to Markdown

2013-03-09 19:00:25 +01:00

build.cmd

Add build.cmd for Windows developers

2013-02-12 15:47:55 +01:00

build.py

Don't build ol.css in check target

2013-12-05 13:12:39 +01:00

CONTRIBUTING.md

Update README and CONTRIBUTING

2013-03-22 10:59:09 +01:00

LICENSE.md

LICENSE: Fixed reference to AUTHORS file

2013-03-09 19:02:05 +01:00

package.json

Making use of the closure-util package

2013-09-14 18:10:12 -06:00

pake.py

Update to latest version of pake

2013-04-03 13:04:37 +02:00

README.md

Correct links to hosted examples (and docs)

2013-06-27 15:59:52 -06:00

requirements.txt

Add gjslint to requirements.txt

2013-10-02 13:30:19 +02:00

README.md

OpenLayers 3

Welcome to OpenLayers 3!

Check out the hosted examples or poke around the evolving API docs.

Please see our guide on contributing if you're interested in getting involved.