Thanks to my mate @edk from IRC I learned of the compose key. I configured my KDE Plasma desktop to use Right Alt as my compose key in System Settings -> Input Devices -> Keyboard -> Advanced. Then I updated the firmware and deployed a .XCompose file that I generated, and now I have a symbol keyboard on my Debian Linux workstation!
This is great: Is That A Coaster? No, It’s An LED Matrix!
I want to learn more about sigrok and OpenTechLab seems like a good place to start…
Today I found Kevin Hubbard here:
He seems to know a fair bit about PCB design and FPGAs, which are things I am becoming interested in too.
In Build – gusmanb’s 24 Channel 100MHz Logic Analyser from Happy Little Diodes I learned about this Logic Analyzer project. I would like to try building one of these for myself one day too.
This post is part of my video blog and you can find more information about this video over here.
You can support this channel on Patreon: patreon.com/JohnElliotV
Silly Job Title: Component Wrangler
In this video I add improved debouncing logic to the inaugural Silicon Chip and Jaycar Mini Project: JMP001.
Shout out and thank you to Tim Blythman for developing this project.
You can see Tim’s original code and my updates which improve the debouncing implementation.
In the video I mention that we use the pgmspace.h header from Arduino.
Thanks very much for watching! And please remember to hit like and subscribe! :)
Following is a product I use picked at random from my collection which may appear in my videos. Clicking through on this to find and click on the green affiliate links before purchasing from eBay or AliExpress is a great way to support the channel at no cost to you. Thanks!
Maxitronix 500 In 1 (500in1) Electronics Project Lab Kit notes |
Let’s go shopping!
This week I discovered Jan Axelson. She’s a tech writer and her website is here: http://janaxelson.com/.
I have ordered four of her books:
I’m reading Pro Git and I learned that GitHub maintains a list of .gitignore templates. Those might come in handy.
I have been chatting on IRC about how I’m learning git so I can use submodules and my friend @indigo wants to know my use case, so this post makes some effort to explain that with reference to one specific example.
I have a web framework/toolkit I am experimenting with called Mudball which is here: https://github.com/jj5/mudball
I use Mudball in (some of) my web projects, for example: https://github.com/jj5/www.jjlab.net
In the main project (in this case www.jjlab.net) I have a copy of Mudball in the ext/mudball directory. At the moment ext/mudball is setup as a git submodule.
I open the main project in my IDE (or text editor) and I want to be able to work on both the main application and the web framework/toolkit at the same time. Then when I’m done with some changes I want to run my `gui` script (it stands for “git update interactive”, not “graphical user interface”) which will increment my version numbers in inc/version.php and ext/mudball/inc/version.php and then add/commit/push any changes in both the main project and the web framework/toolkit.
The code for the `gui` command is here: kickass-libexec/bin/lx-gui.sh, it mostly just defers to lx_vcs_sync() which is here: kickass-libexec/src/2-module/vcs/vcs.sh.
The code which updates the version numbers is here: kickass-libexec/bin/lx-version-increment-patch.sh, it mostly just defers to other modules which are here: kickass-libexec/bin/libexec/version-increment-patch.php and here: kickass-libexec/bin/libexec/inc/version.php.
I have been using a similar setup for a long time with Subversion which uses the svn:externals facility (in place of git submodules) and I have a few scripts which help me manage that. My main tooling for this is known as svnman which is a bunch of scripts I wrote myself: Svnman.
Instead of passing positional arguments to constructors (or functions), instead pass a list of value objects. The type of the value object will tell you the type of the value, so you don’t need to worry about the position. This is a super powerful means of supporting back-compat within your code base so you can move ahead at speed. Having value objects instead of simple types (bools, ints, floats, strings, etc) might have performance implications, but it also can be quite handy. So far so good for my use cases.