TaranVH / 2nd-keyboard

ALL of Taran's scripts - not just for the 2nd keyboard.
https://www.youtube.com/watch?v=O6ERELse_QY
1.66k stars 534 forks source link

Installer script for intercept [Feedback wanted] #26

Open jlndk opened 7 years ago

jlndk commented 7 years ago

Installer Script

After i saw the new video on Taran's channel (https://www.youtube.com/watch?v=y3e_ri-vOIo&t=1s) where he explains the long and tedious process of getting intercept.exe to work, I wondered to myself if there wasn't a simpler way of doing this. Luckyly there's way of making automated scripts directly in windows (if you didn't know) through batch (.bat) files. I therefore wrote an comment on the video suggesting making such script. After the approval of Taran himself I've now started hacking on a initial draft.

I just wanted to make this issue to collect feedback and hear peoples thoughts before i submit the script :).

My basic thought is to create a file that automaticly does all the things described in the video. As i see it the steps are as follows: 1: download the two programs (interception and intercept.exe). 2: Install interception as a admin user (We dont need to install intercept.exe, just unzip it) 3: Fiqure out the keyboard's id (maybe through intercept.exe) 4: Fill out the template keymap by taran. 5: Download the autohotkey script 6: Profit!

I'm gonna try to keep the dependencies as few as possible, since we dont want people to install even more programs on their computer, just to make this work. Therefore i try to stick to tools already avalible in windows by default (hence the use of batch). We might have to pull some libraries for when we want to populate the keymap with the keyboard id, but I'll give you an update on that later ;).

jlndk commented 7 years ago

Okay, time for a quick update.

I've now finished the inital installation script (can be seen on my fork of this repo for now). You're welcome to test it and provide feedback if you want :).

While creating the script I realised that we would have to split the installation process itself into two seperate files, since intercetion requires a restart before we can use it. Because of that I've now started work on a new file that's supposed to get the device id from a given keyboard and populate tarans keyremap.ini file.

However I was unable to find an automated way to get the device id in an easy way. Luckily for us the source code for both intercept and interception is available which means that I can extract the parts we need for keyboard detection. Someone could actually make a rewrite tailored our specific needs, but that would be a kinda big undertaking.

So for now im gonna create a little program, based on intercept, that gets the device id so that we can automate the original process.