search

foam-framework / foam

Feature-Oriented Active Modeller
Apache License 2.0
786 stars 55 forks source link

Build and test Virtual Keyboard support for App Builder #359

Open mdittmer opened 9 years ago

mdittmer commented 9 years ago

Correctly integrate https://developer.chrome.com/apps/accessibilityFeatures#property-virtualKeyboard into App Builder, starting with kiosk apps.

mdittmer commented 9 years ago

According to this: https://code.google.com/p/chromium/codesearch#chromium/src/chrome/common/extensions/api/accessibility_features.json&q=virtualKeyboard%20file:js&sq=package:chromium&type=cs&l=48

The set() interface described in the developer documentation probably takes a Boolean Javascript value.

mdittmer commented 9 years ago

Setting of value in packaged apps still needs testing. I can do that. Jackson, can you add this to template app views that make sense? Also, do you think that a defaultValue of true is the right thing here?

jacksonic commented 9 years ago

The default should vary by app type. Event Calendars and catalogues, for instance, might not require any user text input unless search is enabled. Questionnaires will always require text input except in very specific circumstances (only checkboxes, for instance).