ashatora/openlayers

Go to file

Tim Schaub 36ea408ed2 Handle namespace provides

It looks like the convention in the Closure Library is to export either namespaces (starting with lowercase), constructors (starting with uppercase), or enums (all uppercase, one instance).  I don't see any places where the Closure Library exports a function that is not a constructor.

Following the same convention, when we export `ol.foo`, it means we are making available function properties of the `ol.foo` object that start with a lowercase letter.

2013-09-04 13:55:54 -06:00

Add export annotation @exportFunction

2013-08-19 14:01:57 +02:00

Add a temporary html5 externs file

2013-08-13 11:31:58 +02:00

Add zoom to extent control

2013-07-16 17:13:38 +02:00

Adjective -> adverb

2013-06-27 16:01:22 -06:00

Export namespaces or constructors but not functions

2013-09-04 13:55:54 -06:00

Remove handleMapPostrender extension point

2013-08-31 23:25:08 +02:00

move the licenses dir to the root of the repo

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

Upgrade Font Awesome to version 3.2.1

2013-07-15 10:16:42 +02:00

Export namespaces or constructors but not functions

2013-09-04 13:55:54 -06:00

Remove map from control options

2013-08-30 14:59:21 -06:00

.gitignore

Download Plovr into build directory

2013-04-02 16:16:45 +02:00

.travis.yml

Use regex module to work around arbitrary limitations in re

2013-07-22 18:20:39 +02: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

Handle namespace provides

2013-09-04 13:55:54 -06: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

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

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.