{"id":264,"date":"2014-12-04T11:00:00","date_gmt":"2014-12-04T11:00:00","guid":{"rendered":"http:\/\/localhost\/?p=264"},"modified":"2017-01-09T07:04:59","modified_gmt":"2017-01-09T07:04:59","slug":"moving-forward-with-ngcordova","status":"publish","type":"post","link":"https:\/\/ionic.io\/blog\/moving-forward-with-ngcordova","title":{"rendered":"Moving Forward with ngCordova"},"content":{"rendered":"

This is a guest post by Paolo Bernasconi<\/a>, lead developer on ngCordova<\/a>.<\/em><\/p>\n

To watch ngCordova<\/a> grow from a small idea to a popular open source project with over 1250 stars on GitHub has been a great pleasure for me. Since its inception in July 2014, I’ve had the opportunity to learn about creating and maintaining a GitHub repository, and I’ve come to realize the true power of the open source community and individual contributors. With the community’s troubleshooting help and submissions, we’ve been able to improve ngCordova more rapidly and effectively than one person, or even a small team, ever could.<\/p>\n

When we first built ngCordova, it covered 14 basic Cordova plugins. Now it has 47<\/strong> and counting, ranging from Push Notifications to Facebook support. We have since released 8 versions, received 230 pull requests from 49 contributors, and resolved over 170 issues.<\/p>\n

<\/p>\n

So, what’s next?<\/h3>\n

The first new feature in ngCordova’s future is an automatic deviceready<\/code> check to determine whether a device is ready to use plugins. Currently, the only way to ensure this is to manually insert plugin calls inside the event-listener:<\/p>\n

document.addEventListener("deviceready", function () {\n  $cordovaPlugin.someFunction().then(success, error);\n}, false);\n\n\/\/ OR with Ionic\n\n$ionicPlatform.ready(function() {\n  $cordovaPlugin.someFunction().then(success, error);\n});\n<\/code><\/pre>\n
This “event check”<\/em> needs to be done for each plugin method, which becomes a bit tedious and over-bloats code in the controller. Soon, ngCordova will call the deviceready<\/code> event in the background, making it easier and simpler to use plugins.<\/p>\n
Another important feature on the roadmap is an improved demo app. Cordova plugins can often be very hard to use, and there are times when you might have no idea why your app isn’t working or what error is being produced. While the current demo<\/a> does include quite a few plugins, we plan to support all<\/em> plugins in ngCordova, with very detailed examples and unit-tests.<\/p>\n
Finally, we understand the need for great documentation, so we are improving the docs with more comprehensive methods for each plugin API (see the Facebook plugin for an example<\/a>), so you’ll have all the information you need readily available.<\/p>\n
What about testing in the browser?<\/h3>\n
One of the biggest issues with app development using Cordova plugins is the fact that it can sometimes break an app when testing in the browser, giving us the “white screen of death”. ngCordova does have a mocks module<\/a>, but it requires a lot of extra code in your controller to simulate the phone environment and isn’t well documented at the moment.<\/p>\n
That’s why I created a Google Chrome extension called Cordova Mocks<\/a> (Github<\/a>), which generates mock-data and automatically injects it into your browser. It follows the same API that Cordova plugins use, so the only thing you have to do is install the extension and start using your app as if you were testing on your phone.<\/p>\n
It currently supports the following plugins, with many more to come:<\/p>\n