It didn’t look easy to modify this in the KeyboardView, it would probably be better to write this logic from scratch if you need it.The stock keyboard that comes by default with your Android device is never sufficient. The pop-up was animating around the screen and not behaving like the new Android material keyboard. I’ve removed the preview text in this example (the semi-transparent pop-up that appears just above the letter as you type). This implementation uses the dictionary which seemed like a reasonable predictive text option but it could be updated to include a app specific dictionary of words that builds up over time. The text selection position should be updated to check for white space and more intelligently select the word. In addition to that, predictive text doesn’t work correctly if you hit backspace half way through a word. This would give more control over the behavior and prevent content on the screen from being covered up. I’ve been reading that it’s easier to manage by including it in the keyboard layout instead of using the candidates view. The predictive text appears over the top of content on the screen. Popup keyboard layout file (set in the input.xml keyboard layout): Snipet from original keyboard XML template: The new keyboard is automatically created and displayed as a modal above your existing keyboard. It was a bit confusing at first but makes sense after you take a look at the code. When you add pop-up keys (alternate keys that appear on long press) you’re actually creating a new keyboard for the pop-up. Most of the styling can be done in the input.xml file. On top of that it’s really just adding your icons, layout and XML files. At a high level you have a class that extends Keyboard, a KeyboardView and a KeyboardService that extends InputMethodService. There are already resources that walk through aspects of the keyboard code in great detail. There is still a lot of room for improvement but this is a much better starting point. This keyboard contains styling, predictive complete spell check and alternate keys. This only took a couple of hours to put together but required a number of different resources including blogs, documentation and Stackoverflow. I’ve made some minor updates to Google’s base keyboard example and applied some of the common customizations to the keyboard. On top of that, many of the common customizations are spread out across a wide array of stack overflow posts. It’s a very helpful starting point but requires some minor changes to get it working as expected. Google’s sample keyboard project is a little out of date.
0 kommentar(er)
