-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Move gmaps.js to NPM and modularize it. #404
Comments
I think this sounds awesome. Thanks for all your hard work. |
👍 |
2 similar comments
👍 |
👍 |
Great idea! +1 |
awesome, maybe one again place into bower. |
@hpneo Will your project remain available as a |
hey hpneo there is no inside callback for geo fence ?? |
+1 |
hi, any updates on this issue ? |
I'm so sorry, I've been really busy with my daytime job I'm not sure if I can make it. There is already a bunch of gmaps modules on NPM but they're behind the gmaps master branch, so besides of finishing the split now I have to update the already created packages, and it's a lot of work I can't do right now. I hope I can make some time for this but I can't assure you. |
Found it here if anybody is looking for the npm repo: https://www.npmjs.com/package/gmaps |
Shame this project has stalled for so many years really made my life easier working with Google Maps API. Anyone thought of picking it back up? |
Why not you? |
@jeduan don't know if I have the skills for it but you got me thinking I might just do it you know! |
You probably have all the skills you need or you can learn them easily. |
I've been playing with @AmpersandJS and I must say is amazing what they accomplished in terms of simplicity, code reusability and a better approach to work with modules. I'm thinking on follow that philosophy and make gmaps.js a modular library for working with Google Maps.
That way, you can use only what you need (markers but no routes, polygons but no layers), and even make your own builds with what you need, or extend gmap.js in an easier way.
To do this, I need to use Browserify to create the bundles for using the library in the browser, since the gmaps modules should be in NPM, like https://www.npmjs.com/search?q=ampersand-
I want to know what do you think.
The text was updated successfully, but these errors were encountered: