ashatora/openlayers

Go to file

Tom Payne 26fa8d9d53 Track current program in context, rather than renderers

2013-11-20 11:31:20 +01:00

Remove '(Optional)' from Description

2013-11-14 10:21:23 +01:00

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

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

Activate more compiler checks

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

add Terms of Service to the Bing attribution

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

Link to API docs

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

Default projection does not need to be provided

2013-11-14 17:29:11 +01:00

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

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

move the licenses dir to the root of the repo

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

Add jsdoc plugin that maps @todo tags to @stability and @observable tags.

2013-10-28 15:17:59 -04:00

Track current program in context, rather than renderers

2013-11-20 11:31:20 +01:00

Making use of the closure-util package

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

add an optional argument to getAttributes so we can get a feature's attributes except for the geometry ones

2013-11-19 15:39:22 +01: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

Use -server -XX:+TieredCompilation to double compilation speeds

2013-11-19 15:51:03 +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.