Update READMEs

Author: RedFantom

README.md

@@ -36,7 +36,10 @@ The current list of supported devices includes:
 - MasterKeys Pro L RGB ISO (untested)
 
 If you would like for your device to be supported as well, please run 
-the `record` executable.
+the `record` executable. Enter the row and column coordinates of each
+key according to the Cooler Master reference each time for the key that
+lights up in red. The shared `layout.c` can be attached to an issue, and
+then your device is added in no-time!
 
 Keyboards with only monochrome lighting may use a different protocol and
 thus they would probably require more modifications than just adding a
@@ -50,20 +53,22 @@ To be able to compile and install any of the targets in this library,
 distribution, the name of the packages (if they are provided) may 
 differ from the ones given here. The reference commands are for Ubuntu.
 ```bash
-# Include libx11-dev if you wish to run the ambilight example
-sudo apt-get install cmake libusb-1.0.0-dev
+# libx11-dev is for the AmbiLight and notifications examples
+# python3-gtk2.0 is for the notifications example
+sudo apt-get install cmake libusb-1.0.0-dev libx11-dev python3-gtk2.0
 cd Source/masterkeys-linux  # Or wherever you have cloned the repo
-# Automatically also builds target ambilight
-# Exclude the examples in the CMakeLists.txt if you do not have libx11-dev
+
+# Builds library, utilities and C examples
+# Exclude them from the file if you don't want them to be built
 cmake .
 make
 sudo make install
 
-# For the Python library (system-wide install)
+# For the Python library (system-wide install) and Python examples
 sudo python -m pip install scikit-build
-sudo python setup.py install
+sudo python setup.py build install  # Python examples not installed
 
-# Or if you would rather install from PyPI
+# Or if you would rather install from PyPI, still requires dependencies
 sudo python -m pip install masterkeys
 ```
 
@@ -107,7 +112,7 @@ along with this program.  If not, see <https://www.gnu.org/licenses/>.
 ```
 
 ## Credits
-Part of the implementation of this library is based on the more
+Part of the implementation of the `libmk` library is based on the more
 extensive protocol description written by [`chmod222`](https://github.com/chmod222),
 available under the LGPLv3 license in [`libcmmk`](https://github.com/chmod222/libcmmk),
 which has the same goal as this project.

examples/README.md

@@ -14,3 +14,16 @@ Takes the average of sections of the image to correspond to the color
 of a single key, thus showing the image selected on the keyboard in 
 a much reduced resolution. As it is pure Python and it loops over a PIL
 pixel access object, the current implementation is quite slow.
+
+## Notifications
+Mostly an improvement of the AmbiLight example, the notifications
+example is a completely rewritten version that runs from Python.
+Performance critical functions are implemented in C.
+
+Where AmbiLight only displays the dominant color shown on the screen,
+the notifications example will interrupt the AmbiLight color stream and
+flash the keyboard in the dominant color of a notification.
+
+Options are available to be set through the Python file
+`notifications.py`. The notifications example shows the potential of
+RGB keyboards as more than just gimmicks.

utils/README.md

@@ -0,0 +1,20 @@
+# Utilities
+
+## main
+The program `main.c` is the testing executable for the functionality
+of `libmk`. Run this to check if your keyboard is properly supported.
+Tests include setting full keyboard color, effects, individual LED
+control and profile control. The profile in slot 4 will be overwritten!
+
+## ctrl
+The program `ctrl.c` is the testing executable for the functionality
+of `libmkc` and shows of the performance of the Cooler Master MasterKeys
+RGB keyboards using a high speed, high refresh-rate software defined
+color wave. `libmkc` works asynchronously to allow programs to achieve
+such fast effects.
+
+## record
+The program `record.c` is used for adding support for new layouts for
+devices with an already known protocol. Unfortunately, supporting
+keyboards with a different protocol requires significant work in packet
+sniffing to reverse engineer the protocol used.