Changed Operation

This is a very big commit so this description is going to be big as well.
1. Added binlock-chroot.tar.gz for building windows binaries in wine. Will have one more commit to add the url to the script
2. To go along with the tarball I've made a build.sh script to automatially build binaries. The icon folder is for the builds as well. This also means this will be the first version that comes with binaries!
3. I've updated the dev-test.sh script to reflect the changes in the main program.

Lets get into binlock main!
1. First I've added the GPL to the top of my files.
2. I've changed the imports from "import x" to "from x import y". This looks cleaner to me.
3. I took away my custom help message and changed up argparser a little bit. I'm custom formatting argparser so it works a little more sanely.
4. Made some readability changes and switched from my custom prints to logging. I still name them eprint, vprint etc.

My fucntion.py
1. I've renamed this to encoder.py. It makes more sense it doesn't really encrypt anything. Also I got rid of PrintTools, don't really need it.
2. My encoding stuff is no longer a class, i don't think it's very necessary and imo makes more sense to be separate functions. could still change in the future, just this way feels cleaner and clearer.
3. I made the functions MUCH easier to understand with less options than the class needed.

Finally updated the README to be better and include installation with binaries.

also adding my .git files.

README.md

@@ -1,24 +1,75 @@
 # binlock
 
+
+
 A simple encoder program for base64, base85 and ascii85.
 
+
+
 # TODO
 
 - Implement aes encryption.
 
-	>Make a switch to encrypt the entire filesystem.
-	>Make a switch to throw away the aes key.
+>Make a switch to encrypt the entire filesystem.
+
+>Make a switch to throw away the aes key.
+
 - Allow multiple input files.
-	>Multiple inputs to multiple outputs?
-	>Multiple inputs to a single output?
+
+>Multiple inputs to multiple outputs?
+
+>Multiple inputs to a single output?
+
 - Allow executing encrypted binaries?
+
 - Double encode switch
-- Implement different encoders
-- Clean up argparser? Implement my own help message?
+
 - Of course we always need to look at making the code better.
 
+
+
 # Usage
-All you have to do is have python3 installed and run ./binlock.py -h and it will instruct you. I may make binaries for it if it grows.
 
-# exit()
-I will definitley add to this as we go. There isn't much reason for Encrypter and PrintTools to be different files I just wanted it that way. The same reason that all my encoder functionality is in a class.
+
+
+**Python**
+
+>Make sure you have python3 installed.
+
+`git clone https://github.com/volitank/binlock.git`
+>or just download `binlock.py` and `encoder.py`. You don't need the rest
+
+`python3 binlock.py --help` or
+
+`/path/to/binlock.py --help` or
+
+`./binlock.py --help`
+
+**.deb:**
+
+`sudo dpkg -i binlock_ver-rev_arch.deb`
+
+`binlock --help`
+
+**AppImage:**
+
+`./binlock_ver-rev_arch.AppImage --help`
+
+**Windows:**
+
+>For Windows you can use the portable onefile.
+
+`binlock_ver-rev_arch-onefile.exe --help`
+
+>Other option is get the zip file and extract it.
+
+`binlock.exe --help`
+
+**Snap**
+>I don't have the snap on the snap store yet, It needs to be approved. For now I am distributing a --classic snap here.
+
+`sudo snap install binlock_ver-rev_arch.snap --classic --dangerous`
+
+`binlock --help`
+
+All binaries compiled with nuitka3