AngularJS directives for the Google Maps Javascript API
CoffeeScript HTML JavaScript Other
Permalink
Failed to load latest commit information.
.travis different key Feb 1, 2016
dist rebuild to sync master with PR's Oct 12, 2016
example Merge remote-tracking branch 'origin/master' into ricinoMaster Sep 20, 2016
grunt example of using the project with webpack and commonJS, this should n… Oct 6, 2016
scripts fix(google's foobar): forked many repos and incuding them as npm and May 13, 2016
spec Fixed error in map control, caused by calling multiple times Oct 10, 2016
src Fixed error in map control, caused by calling multiple times Oct 10, 2016
website_libs fixing travis Feb 25, 2015
.eslintrc - bumped to grunt-contrib-coffee to latest coffeescript to support be… Jan 31, 2016
.gitignore fix(google's foobar): forked many repos and incuding them as npm and May 13, 2016
.npmignore ignores to npm and bower Oct 23, 2015
.travis.yml fixing branch check Feb 1, 2016
CHANGELOG.md Release 2.4.0 Sep 20, 2016
Gruntfile.coffee example of using the project with webpack and commonJS, this should n… Oct 6, 2016
ISSUE_TEMPLATE.md Deleting old README with old extension. Formatting ISSUE_TEMPLATE May 26, 2016
README.md typo in readme Sep 20, 2016
bower.json Release 2.4.0 Sep 20, 2016
coffeelint.json specific specs lodash Jan 24, 2016
curl.json revert issue #1676 Jan 10, 2016
karma.acceptance.conf.coffee example of using the project with webpack and commonJS, this should n… Oct 6, 2016
karma.conf.coffee re-bundled the google-maps-utility-library-v3 due to async loading of May 13, 2016
package.js made dependency to 3.0.0 instead Sep 21, 2015
package.json example of using the project with webpack and commonJS, this should n… Oct 6, 2016

README.md

Project No longer actively maintained

With angular 2 and other competing projects we have decided to announce that this project is no longer activley maintained. If someone desires to take over the project please contact any of the admins.

As a warning this project is not activley watched by the admins and is checked here and there to fix any major issues. Therefore if something is major, contact someone directly via mentioning a users name/alias (will notify the user/admin).

Alternatives:

angular-google-maps

AngularJS directives for Google Maps Dependencies  Dependencies 

Builds:

  • Master (2.3.X): Build Status

  • 2.2.X: Build Status

  • 2.1.X: Build Status

  • 2.0.X: Build Status

task board: Stories in Ready

Gitter chat

 

NPM


Getting started

This is a set of directives and services for AngularJS ~1.0.7+, ^1.2.2+.

Dependencies

Please always be checking the package.json and bower.json. They are the spoken word and will usually be more up to date than this readme.

Tip use some library which will always pull in your dependencies (no matter what the changes are) to your vendor.js. IE: main-bower-files

Current Dependencies:

Development and or Running the Build

If you plan to hack on the directives or want to run the example, first thing to do is to install NPM dependencies:

npm install && bower install
  • Installing for Meteor application:
meteor add angularui:angular-google-maps
meteor npm install --save angular-google-maps

Building

To build the library after you made changes, simply run grunt:

grunt

If you get errors from jshint or specs, just add the --force argument.

Generating SourceMap(s)

grunt buildAll

This will generate source maps for development (angular-google-maps_dev_mapped.js) (non minified) and source maps to minified (angular-google-maps_dev_mapped.min.js) files. They each have their own corresponding map files. To get the coinciding source files you will need to copy the generated /tmp directory (currently not under scc).

Running the example

To run the example page, just run

grunt example

and open your browser on http://localhost:3000/example.html.

Documentation

The various directives are documented at official site.

Contributing

Filing issues: Prior to submitting an issue:

  • Search open/closed issues, src examples (./examples), gitter, and then google plus community! Again please search!
  • issues w/ plnkrs get attention quicker

Pull Requests (PR) more than welcome! If you're adding new features, it would be appreciated if you would provide some docs about the feature. This can be done either by adding a card to our Waffle.io board, forking the website branch and issuing a PR with the updated documentation page, or by opening an issue for us to add the documentation to the site.

PR's should follow angular git commit conventions.

Branching Scheme

PRS to master are for 2.3.X only.

If you want it rolled into a older release then target your PR to that respective branching name like 2.1.X.

Note: many fixes relevant to 2.0.X can be rolled up into 2.1.X, 2.2.X and 2.3.X

  • master: points to the active targeted next release branch (2.3.X)
  • 2.2.X: latest of 2.2.X
  • 2.1.X: ""
  • 2.0.X: "" ... etc