You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Rather than a keyboard, I've been wanting an a-frame component which would allow a more general layout, with general text corresponding to buttons, and embedded 'keys' which provide feedback rather than being pressable - you can specify their id so as to access them in code.
The focus is on enabling end-users easily to create new and complex panels, rather than just providing a keyboard for data-entry.
The a-frame-keyboard proved a fruitful starting point, in particular the way it constructs things, but I found myself needing to change too much of it to make it sensible to propose it as a straight pull request.
However, I have put my code up on github in https://github.com/bilkusg/aframe-control-panel.
It is more or less backward compatible with the current system, in the sense that the default keyboard looks and works the same as the one in this repo. But the format of the keyboard description is different, and the custom event is too ( see next para for the reason )
I also allow multiple control panels in the same scene - keyboard presses affect whichever use that keystroke in a key, while VR presses only affect the one. ( the custom event has the name of the layout added to its name to allow listening separately on different panels
I'm open to suggestions regarding either finding a way of merging my work with this repo, or if not just treating it as an offshoot with different objectives which may be of use to some of the same people using a-frame-keyboard.
Gary Bilkus
The text was updated successfully, but these errors were encountered:
Rather than a keyboard, I've been wanting an a-frame component which would allow a more general layout, with general text corresponding to buttons, and embedded 'keys' which provide feedback rather than being pressable - you can specify their id so as to access them in code.
The focus is on enabling end-users easily to create new and complex panels, rather than just providing a keyboard for data-entry.
The a-frame-keyboard proved a fruitful starting point, in particular the way it constructs things, but I found myself needing to change too much of it to make it sensible to propose it as a straight pull request.
However, I have put my code up on github in https://github.com/bilkusg/aframe-control-panel.
It is more or less backward compatible with the current system, in the sense that the default keyboard looks and works the same as the one in this repo. But the format of the keyboard description is different, and the custom event is too ( see next para for the reason )
I also allow multiple control panels in the same scene - keyboard presses affect whichever use that keystroke in a key, while VR presses only affect the one. ( the custom event has the name of the layout added to its name to allow listening separately on different panels
I'm open to suggestions regarding either finding a way of merging my work with this repo, or if not just treating it as an offshoot with different objectives which may be of use to some of the same people using a-frame-keyboard.
Gary Bilkus
The text was updated successfully, but these errors were encountered: