npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2025 – Pkg Stats / Ryan Hefner

piyay-custom-keyboard

v1.0.3

Published

Unobstrive Ionic Custom Keyboard for Ionic 1

Readme

Peanut Hub - Custom Keyboard


Download RC Version | Get Started | Guide | Report Issues


Unobstrive AngularJs/Ionic Component for Ionic 1

Note: Custom Keyboard is under active development. As such, while this library is well-tested, the API may change. Consider using it in production applications only if you're comfortable following a changelog and updating your usage accordingly.

Get Started

(1) Get Custom Keyboard in one of the following ways:

(2) Include peanuthub-custom-keyboard.js (or peanuthub-custom-keyboard.min.js) in your index.html

(3) Include peanuthub-custom-keyboard.css (or peanuthub-custom-keyboard.min.css) in your index.html

(4) Add peanuthub-custom-keyboard to your main module's list of dependencies

When you're done, your setup should look similar to the following:

<!doctype html>
<html ng-app="myApp">
<head>
	<!-- IONIC STUFF -->
    <script src="lib/angular/angular.js"></script>
    <script src="lib/ngCordova/dist/ng-cordova.js"></script>
    <script src="lib/ionic/js/ionic.js"></script>
    <script src="lib/ionic/js/ionic-angular.js"></script>
    <link rel="stylesheet" href="lib/ionic/css/ionic.css">
    <!-- PEANUT HUB COMPONENT -->
    <script src="lib/peanuthub-custom-keyboard.min.js"></script>
    <link href="lib/peanuthub-custom-keyboard.min.css" rel="stylesheet">
    <script>
        angular.module('myApp', ['peanuthub-custom-keyboard'])
        
        
        //Add Custom Keyboard 
        .config(function($peanuthubCustomKeyboardProvider) {
          $peanuthubCustomKeyboardProvider.addCustomKeyboard('CUSTOM_SKU', {
          keys: [
           { type: "CHAR_KEY", value: "1" },
           { type: "CHAR_KEY", value: "2", label: "ABC" },
           { type: "CHAR_KEY", value: "3", label: "DEF" },
           { type: "CHAR_KEY", value: "4" },
           { type: "CHAR_KEY", value: "5" },
           { type: "CHAR_KEY", value: "6" },
           { type: "CHAR_KEY", value: "7" },
           { type: "CHAR_KEY", value: "8" },
           { type: "CHAR_KEY", value: "9" },
           { type: "CHAR_KEY", value: "X" },
           { type: "CHAR_KEY", value: "0" },
           { type: "DELETE_KEY", icon: "ion-backspace-outline" }
         ]})

          //Add Custom Keyboard  With Directive Addon
        .config(function($peanuthubCustomKeyboardProvider) {
          $peanuthubCustomKeyboardProvider.addCustomKeyboard('KEYBOARD_WITH_ADDON', {
          keys: [
            { type: "CHAR_KEY", value: "1" },
            { type: "CHAR_KEY", value: "2", label: "ABC" },
            { type: "CHAR_KEY", value: "3", label: "DEF" },
            { type: "CHAR_KEY", value: "4" },
            { type: "CHAR_KEY", value: "5" },
            { type: "CHAR_KEY", value: "6" }
          ],
          addons: [{
            directive: "camera-read-addon",
            parameters: {
                "read-label": "Escanear código de barra"
            }
        }]})

       });
    </script>
    ...
</head>
<body>
    ...
    <!-- NUMERIC DIRECTIVE -->
    <input 
    	ng-model="numeric_value" 
    	peanuthub-numeric-keyboard 
    	keyboard-options="{doneText: 'Buscar', cleanTextOnClick: true}" 
    	keyboard-on-done-keypress="onSearch" 
    	type="text" 
    	placeholder="" />
	<!-- CUSTOM DIRECTIVE -->
	<input 
    	ng-model="custom_value" 
    	peanuthub-custom-keyboard 
    	keyboard-options="{keyboard:'CUSTOM_SKU', doneText: 'Ok', cleanTextOnClick: true, enableWAI:true, theme:'dark'}" 
    	keyboard-on-done-keypress="onSearch" 
    	type="text" 
    	placeholder="" />
    ...
</body>
</html>

Note: if you want the unstable version use: $ bower install https://bitbucket.org/peanuthub/peanuthub-custom-keyboard#master --save from your console

Report an Issue

Help us make Peanut Hub Components better! If you think you might have found a bug, or some other weirdness, start by making sure it hasn't already been reported. You can search through existing issues to see if someone's reported one similar to yours.

If not, then create a plunkr that demonstrates the problem (try to use as little code as possible: the more minimalist, the faster we can debug it).

Next, create a new issue that briefly explains the problem, and provides a bit of background as to the circumstances that triggered it. Don't forget to include the link to that plunkr you created!

Issues only! | -------------| Please keep in mind that the issue tracker is for issues. Please do not post an issue if you need help or support.

Contribute

(1) See the Developing section below, to get the development version of the component up and running on your local machine.

(2) Check out the roadmap to see where the project is headed, and if your feature idea fits with where we're headed.

(4) Finally, commit some code and open a pull request. Code & commits should abide by the following rules:

Always

  • Commits should represent one logical change each; if a feature goes through multiple iterations, squash your commits down to one
  • Changes should always respect the coding style of the project

Resources

Developing

 npm install & bower install
 grunt compile