A new Onscreen Keyboard built using GNOME JS
Note: Binary files aren't shown on the web site. To see all files, please download the extension zipfile.
| Version | Status |
|---|---|
| 50 | Active |
| 49 | Active |
| 48 | Inactive |
| 47 | Inactive |
| 46 | Inactive |
| 45 | Inactive |
| 44 | Inactive |
| 43 | Inactive |
| 42 | Inactive |
| 41 | Inactive |
| 40 | Inactive |
| 39 | Inactive |
| 38 | Inactive |
| 37 | Inactive |
| 36 | Rejected |
| 35 | Rejected |
| 34 | Rejected |
| 33 | Rejected |
| 32 | Inactive |
| 31 | Inactive |
| 30 | Rejected |
| 29 | Inactive |
| 28 | Inactive |
| 27 | Inactive |
| 26 | Inactive |
| 25 | Inactive |
| 24 | Rejected |
| 23 | Rejected |
| 22 | Rejected |
| 21 | Rejected |
| 20 | Inactive |
| 19 | Inactive |
| 18 | Inactive |
| 17 | Inactive |
| 16 | Inactive |
| 15 | Inactive |
| 14 | Rejected |
| 13 | Rejected |
| 12 | Rejected |
| 11 | Rejected |
| 10 | Inactive |
| 9 | Rejected |
| 8 | Rejected |
| 7 | Rejected |
| 6 | Rejected |
| 5 | Rejected |
| 4 | Inactive |
| 3 | Rejected |
| 2 | Rejected |
| 1 | Rejected |
Is there any way to make the key codes a dependency without including `keycodes.tar.xz` in the package? Like npm, ... Unpacking that file on each enable is too much.
"keycodes.tar.gz" is generated using a Python program that utilizes `xkbcommon`, a library that isn't available through GJS or NPM (as far as I know, if it is possible, please let me know and I will implement a GJS equivalent of this Python script). Additionally, using a plain text file or a folder results in the final extension archive being too large for usage. I tried to call the Python script through GLib.spawn_command_line_sync, but it seemed too painful for the end user to have to install all of the dependencies. Please suggest any alternatives if possible. (Python script which generates a single keymap: https://github.com/Vishram1123/gjs-osk/blob/main/genKeyMap.py) (Shell script which generates a folder of all keymaps: https://github.com/Vishram1123/gjs-osk/blob/main/genAllKeyMaps.sh)
Ok but I'm going to reject this one since you are extracting on each enable without checking whether it is unpacked before (line 145 `extension.js`). btw, as we [recommended on EGO review guidelines](https://gjs.guide/extensions/review-guidelines/review-guidelines.html#scripts-and-binaries), you can mention `pip` command in the description for the dependencies.