How to interface with a Ajazz Stream Deck device.
The device uses the HID protocol to communicate with its software.
The number of keys can be determined from the HID device descriptors. There is currently no known provision to determine their layout or size. The buttons on the current version of the device (AKP153)
| #include <stdio.h> | |
| #include <stdlib.h> | |
| #include <memory> | |
| #include <cstring> | |
| #include <vector> | |
| #include <string.h> | |
| #include <assert.h> | |
| #include <getopt.h> /* getopt_long() */ | |
| #include <fcntl.h> /* low-level i/o */ |
| #!/bin/bash | |
| set -euo pipefail | |
| base_dir=$(realpath $HOME/.var/app --relative-to=$(pwd)) | |
| comm -13 <(flatpak list --columns=application | sort) <(ls -1 $HOME/.var/app/ | sort) \ | |
| | sed "s#^#$base_dir/#" | tr '\n' '\0' | du -sch --files0-from=- |
| /* | |
| * Copyright (c) superblaubeere27 2020 | |
| * | |
| * Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: | |
| * | |
| * The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. | |
| * | |
| * THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOF |
| #!/usr/bin/env python3 | |
| """ | |
| Code from http://www.labri.fr/perso/nrougier/python-opengl/#the-hard-way | |
| """ | |
| import ctypes | |
| import logging |
| #!/usr/bin/env bash | |
| # | |
| # Usage: dev_signed_cert.sh HOSTNAME | |
| # | |
| # Creates a CA cert and then generates an SSL certificate signed by that CA for the | |
| # given hostname. | |
| # | |
| # After running this, add the generated dev_cert_ca.cert.pem to the trusted root | |
| # authorities in your browser / client system. | |
| # |
| #include <mutex> | |
| #include <vlc/vlc.h> | |
| #include <stb_image.h> | |
| #include <nanogui/nanogui.h> | |
| class VideoView: public nanogui::GLCanvas { | |
| public: | |
| nanogui::GLShader shader; | |
| GLuint textureId; |
Reed Slaby, March 2018
Having grown tired of wasting a perfectly good monitor on my ethereum mining rig, I finally decided to replace the Ubuntu Desktop 16.04 installation with Ubuntu Server 16.04. Many of the gtutorials available at the time of this writing range from unecessarily complicated to flat-out wrong. This guide is intended to address many of those shortfalls.
To complete this guide, you should already have:
So, you've created a Python app (be it a graphical user interface with Qt or the like, or a simple command line interface). Great! But how are others going to use it? Python applications often have dependencies (e.g. from third-party modules), and they also need a Python interpreter to run them. For a developer, installing all the necessary bits and bobs to make things work is okay, but that's unacceptable for a normal user - they just want to download the thing and run it.
Below are simple instructions to publish your app on the three main operating systems: Windows, macOS and Linux.
| def get_window_id(name): | |
| import Xlib.display | |
| d = Xlib.display.Display() | |
| r = d.screen().root | |
| window_ids = r.get_full_property( | |
| d.intern_atom('_NET_CLIENT_LIST'), Xlib.X.AnyPropertyType | |
| ).value |
