# 2Keys A easy to setup second keyboard, designed for everyone.
For a full setup guide, see [here](https://github.com/Gum-Joe/2Keys/blob/master/docs/SETUP.md)
For keyboard mappings, see [here](https://github.com/Gum-Joe/2Keys/blob/master/docs/MAPPINGS.md)
### Support Windows is supported only as the server (where the hotkeys will run) and a raspberry pi is required to run the detector.
## WARNING This will download a copy of [AutoHotkey_H](https://hotkeyit.github.io/v2/), a DLL version of [AutoHotkey](http://autohotkey.com/)
## Building To build the server, where hotkeys are run: ` $ cd server $ yarn `
To build the detector: ` $ cd detector $ pip3 install -r required.txt `
## Devices Server: The device running the hotkeys sever, i.e. where the hot keys will be run
Detecter: Device that handles detection of key presses & which keyboard it is and sends this to the server
## Sofware used & inspiration Inspired by LTT editor Taran’s second keyboard project: [https://github.com/TaranVH/2nd-keyboard](https://github.com/TaranVH/2nd-keyboard)
2Keys uses AutoHotkey_H (a DLL version of AutoHotkey): [https://hotkeyit.github.io/v2/](https://hotkeyit.github.io/v2/)
## License Copyright 2018 Kishan Sambhi
2Keys is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.
2Keys is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
You should have received a copy of the GNU General Public License along with 2Keys. If not, see <https://www.gnu.org/licenses/>.
Metadata
Release files for 2Keys 0.5.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| 2Keys-0.5.1.tar.gz | 33.1 kB | Without provenance | Details for 2Keys-0.5.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| 2Keys-0.5.1-py3-none-any.whl | Python 3 | none | any | Details for 2Keys-0.5.1-py3-none-any.whl |
Total release size: 69.9 kB
Release files / 2Keys-0.5.1.tar.gz
| Download URL | 2Keys-0.5.1.tar.gz |
|---|---|
| Size | 33.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c33be5cfbacd5d6391143f3d5e15fd20eb3183396a6c91cbb12ed4d149a7c6e6
|
|
BLAKE2b-256 checksum How to use checksums |
cb6eab56fdb1addd3cff4bddbca9a125582ed16e1d8403080e7b5d8cdc349c34
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.23.0 setuptools/41.0.1 requests-toolbelt/0.9.1 tqdm/4.32.2 CPython/3.5.3
|
Release files / 2Keys-0.5.1-py3-none-any.whl
| Download URL | 2Keys-0.5.1-py3-none-any.whl |
|---|---|
| Size | 36.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
441b28e5eef4ce961760111984cfd1579f1b676f974c51af0cc1f1df439194f5
|
|
BLAKE2b-256 checksum How to use checksums |
89694ed3dc05e87bfccc574453ecccbb08a88bd8c705ab3badd9f46cb47718c2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.23.0 setuptools/41.0.1 requests-toolbelt/0.9.1 tqdm/4.32.2 CPython/3.5.3
|
Security for 2Keys 0.5.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.