Go to file

Éric Lemoine 78504831e6 Export ol.Observable

This is so on, un and friends appear in the api docs.

2014-01-02 16:40:43 +01:00

apidoc

external/src/types.js file no longer exists

2013-12-12 16:57:39 +01:00

bin

Remove export_as handling from generate-exports.py

2013-12-18 08:25:14 +01:00

buildcfg

File types.js no longer an input for ol.js

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

css

fix hover style on zoom buttons in examples

2013-12-18 14:28:07 +01:00

doc

Link to API docs

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

examples

Merge pull request #1395 from elemoine/exports

2013-12-18 07:17:24 -08: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

Export ol.Observable

2014-01-02 16:40:43 +01:00

tasks

Making use of the closure-util package

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

test

Merge pull request #1382 from tschaub/observable-geometry

2013-12-16 07:43:06 -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

Make build.py compatible with Python 2.6

2013-12-29 12:00:43 -05: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.