ashatora/openlayers

Fork 0

Go to file

Andreas Hocevar 88ab1ac61a Doc changes suggested by @probins

2014-07-08 22:06:21 +02:00

apidoc

Use goog.dom.fullscreen

2014-07-06 16:03:09 -06:00

bin

Remove bin/closure

2014-07-05 23:46:03 +02:00

buildcfg

Use @observable annotation instead of @todo observable

2014-07-05 16:16:44 -04:00

css

Add base control class, to simplify stylesheet

2014-05-02 14:12:31 +02:00

doc

Introduction tutorial

2014-07-03 05:14:25 -04:00

examples

Doc changes suggested by @probins

2014-07-08 22:06:21 +02:00

externs

Doc changes suggested by @probins

2014-07-08 22:06:21 +02:00

licenses

move the licenses dir to the root of the repo

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

resources

Add an exampleNS.strToBase64 function

2014-06-25 15:58:56 +02:00

src

Doc changes suggested by @probins

2014-07-08 22:06:21 +02:00

tasks

Add mocha and mocha-phantomjs as dev dependencies

2014-07-06 11:40:08 -06:00

test

Use proj4.defs instead of proj4.Proj, to conform with the proj4js API

2014-07-08 22:06:21 +02:00

.gitignore

Making use of the closure-util package

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

.jshintrc

Add .jshintrc

2014-03-23 19:59:49 +01:00

.travis.yml

Add a task to run the tests once with PhantomJS

2014-07-05 19:42:30 -04:00

AUTHORS.md

Add @tschw to AUTHORS.md

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

build.cmd

Add build.cmd for Windows developers

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

build.py

Download and use new proj4js

2014-07-08 22:06:20 +02:00

closure-util.json

Fix the closure-library version

2014-07-02 10:22:27 +02:00

CONTRIBUTING.md

Update README and CONTRIBUTING

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

LICENSE.md

Update year in LICENSE

2014-05-31 11:35:37 +01:00

package.json

Remove transient jsdoc dependencies

2014-07-08 21:38:16 +02:00

pake.py

Update to the latest version of pake

2014-02-25 22:02:35 +01:00

README.md

Mention the workshop in the readme

2014-03-31 20:55:58 +02:00

requirements.txt

Don't use the regex module

2014-03-11 21:41:36 +01:00

README.md

OpenLayers 3

Welcome to OpenLayers 3!

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

Please don't ask questions in the github issue tracker but use the mailing list instead.

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