bazzitetech

juliomrqz

nativescript-vibrate

A vibrate NativeScript module for Android and iOS

anarchicknight

  "description": "A vibrate NativeScript module for Android and iOS",

    "url": "https://github.com/anarchicknight/nativescript-vibrate.git"

  "author": "Anarchic Knight <anarchicknight@gmail.com> (http://www.anarchicknight.co.uk)",

    "url": "https://github.com/anarchicknight/nativescript-vibrate/blob/master/LICENSE"

    "url": "https://github.com/anarchicknight/nativescript-vibrate/issues"

  "homepage": "https://github.com/anarchicknight/nativescript-vibrate"

Run `npm install nativescript-vibrate --save` from your project's inner `app` directory:

│   ├── app <------------------------------ run npm install from here

│   │   │   └── nativescript-vibrate <-- The install will place the module's code here

│   │   └── package.json <----------------- The install will register “nativescript-vibrate” as a dependency here

As is, using npm within NativeScript is still experimental, so it's possible that you'll run into some issues. A more complete solution is in the works, and you can check out [this issue](https://github.com/NativeScript/nativescript-cli/issues/362) for an update on its progress and to offer feedback.

If npm doesn't end up working for you, you can just copy and paste this repo's vibrate.android.js and vibrate.ios.js files into your app and reference them directly.

To use the vibrate functionality on Android your app must request permission access the vibrator. To do so, add the following line to your project's AndroidManifest.xml

<uses-permission android:name="android.permission.VIBRATE" />

There is no API to vibrate for a specific amount of time, so it will vibrate for the default no matter what (the duration is ignored).

To use the vibrate module you must first `require()` it from your project's `node_modules` directory:

var vibrator = require( "./node_modules/nativescript-vibrate/vibrate" );

After you have a reference to the module you can then call its `vibration(milliseconds)` methods. For example, the code below turns your device's flashlight on:

var vibrator = require( "/path/to/node_modules/nativescript-vibrate/vibrate" );

A sample barebones project is included with the repo (does not include the nativescript platforms folder). To use perform the following:

* Switch to the VibrateDemo folder on your command line

* Add the platforms that you wish to use (tns platform add {android or ios})

* If you added Android as a platform add the appropriate permission to AndroidManifest.xml

* You should now be able to run the sample as usual (tns run {android or ios})

		{
		"name": "nativescript-vibrate",
		"version": "0.1.2",
		"version": "1.0.0",
		"description": "A vibrate NativeScript module for Android and iOS",
		@@ -5,0 +5,0 @@ "main": "vibrate.js",

		@@ -33,2 +33,5 @@ # NativeScript Vibrate


		## Permissions

		### Android
		@@ -42,4 +45,30 @@

		## Notes

		### iOS

		There is no API to vibrate for a specific amount of time, so it will vibrate for the default no matter what (the duration is ignored).
		There is no API to vibrate for a specific amount of time, so it will vibrate for the default no matter what (the duration is ignored).

		## Usage

		To use the vibrate module you must first `require()` it from your project's `node_modules` directory:

		```js
		var vibrator = require( "./node_modules/nativescript-vibrate/vibrate" );
		```

		After you have a reference to the module you can then call its `vibration(milliseconds)` methods. For example, the code below turns your device's flashlight on:

		```js
		// my-page.js
		var vibrator = require( "/path/to/node_modules/nativescript-vibrate/vibrate" );
		vibrator.vibration(2000);
		```

		A sample barebones project is included with the repo (does not include the nativescript platforms folder). To use perform the following:

		* Check out repo
		* Switch to the VibrateDemo folder on your command line
		* Add the platforms that you wish to use (tns platform add {android or ios})
		* If you added Android as a platform add the appropriate permission to AndroidManifest.xml
		* You should now be able to run the sample as usual (tns run {android or ios})

Fixed alerts

Improved metrics