Latest posts
-
Nanonote 1.3.0 released
I just released Nanonote 1.3.0, my minimalist note-taking application! This release comes with two new features:
First a search bar, implemented by Pavol Oresky:
Second, the ability to reorder selected lines using Alt+Shift+Up and Alt+Shift+Down. This is very handy to order lists:
-
Pixel Wheels 0.17.0!
I just released Pixel Wheels 0.17.0. The main focus on this version has been the graphics, lot of work has been done on the various background tiles: roof, roads, trees, sidewalks, bridge, sand have been improved.
I spent way too long time working on the roof tiles in particular, to the point where I was starring at roofs every time I went outside, looking for inspiration. You can see the evolution of the tiles in this short time-lapse:
-
Simplifying unit tests using a custom markup language
Today I want to present a testing technique I now use in Nanonote unit tests.
Nanonote main component is a QTextEdit with several "extensions" to provide custom behaviors such as indenting/unindenting selected lines with tab/shift+tab or moving selected lines up and down with alt+shift+arrow keys (next version feature, #spoileralert!).
Testing these extensions is not particularly difficult but it requires tedious setup to set the text, position the cursor, define the selection. Then you perform the action and have to write more tedious code to check the new text, cursor position and selection match your expectations. Not only is it tedious to write, it is also error-prone and hard to read.
-
Pixel Wheels 0.16.0
I finally found the time and motivation to get a new version of Pixel Wheels out, so here comes 0.16.0.
Not many engine changes in this new version, mostly new content: first a new track: "Welcome". This track takes place in the countryside, so you'll race among fields and should spot an old tractor. As its name imply it's a simple track, designed to be the track new players begin with.
It is part of a new championship called "Country Life", which for now contains only this track, so it's very short... I plan to add a new track to it in the next version.
The other content addition is a new car: the Dark M.
It's a bit longer than the others. Maybe I should shorten it a bit, what do you think?
-
Generating reports with Python, Markdown and entr
Let's say you need to parse and analyse some raw data, for example a log file, to generate a report.
An easy way to get started with this is to write some Python, Perl, Ruby or shell code to work on your file and print meaningful information about it.
To illustrate this article I am going to write a Python script to "analyze" the
var/log/sysloglog file, whose entries look like this:Apr 12 11:53:42 dozer org.kde.KScreen[6995]: kscreen.xrandr: #011Primary: false Apr 12 11:53:42 dozer org.kde.KScreen[6995]: kscreen.xrandr: Output 68 : connected = false , enabled = false Apr 12 11:53:43 dozer org.kde.KScreen[6995]: kscreen.xrandr: Emitting configChanged() Apr 12 11:53:47 dozer dbus-daemon[991]: [system] Activating service name='org.kde.powerdevil.backlighthelper' requested by ':1.416652' (uid=1001 pid=7186 comm="/usr/lib/x86_64-linux-gnu/libexec/org_kde_powerdev" label="unconfined") (usi Apr 12 11:53:47 dozer org.kde.powerdevil.backlighthelper: QDBusArgument: read from a write-only object Apr 12 11:53:47 dozer org.kde.powerdevil.backlighthelper: message repeated 2 times: [ QDBusArgument: read from a write-only object] Apr 12 11:53:47 dozer dbus-daemon[991]: [system] Successfully activated service 'org.kde.powerdevil.backlighthelper' Apr 12 11:54:04 dozer kernel: [716525.975149] usb 3-2: USB disconnect, device number 64 Apr 12 11:54:04 dozer kernel: [716525.975156] usb 3-2.1: USB disconnect, device number 65 Apr 12 11:54:04 dozer kernel: [716526.040164] usb 3-2.3: USB disconnect, device number 66 Apr 12 11:54:04 dozer upowerd[1672]: unhandled action 'unbind' on /sys/devices/pci0000:00/0000:00:14.0/usb3/3-2/3-2.1/3-2.1:1.0/0003:046D:C046.0025 Apr 12 11:54:04 dozer upowerd[1672]: unhandled action 'unbind' on /sys/devices/pci0000:00/0000:00:14.0/usb3/3-2/3-2.1/3-2.1:1.0 Apr 12 11:54:04 dozer upowerd[1672]: unhandled action 'unbind' on /sys/devices/pci0000:00/0000:00:14.0/usb3/3-2/3-2.1 Apr 12 11:54:04 dozer acpid: input device has been disconnected, fd 6The script is going to take the log entries from stdin, iterate on the lines and produce a report on stdout.
Parsing the log file
The first thing to do is to parse the log file. Since we read the log from stdin, we can start with something like this:
import sys def parse_line(line): # TODO def parse_log(): for line in sys.stdin.readlines(): entry = parse_line(line) if entry: yield entry def main(): for entry in parse_log(): print(entry) if __name__ == "__main__": main() -
Introducing Git Bonsai
I don't know about you, but when I work in a git repository for a long time, I tend to accumulate branches, which I need to clean up.
There are a number of tools to do this, but since I have been teaching myself Rust I thought it was a good topic for a first "real" program. So here is "Git Bonsai", a command-line tool to help you keep your git repository clean and tidy by:
- updating all branches to their remote ones
- deleting the merged branches
For example, given a repository like this:
$ git log --all --oneline --graph * f97c782 (HEAD -> master) Merging topic1 |\ | * f6bfa90 (topic1) Merging topic1-1 | |\ | | * 6943ed2 (topic1-1) Create topic1-1 | |/ | * 4ea41ff Create topic1 |/ | * eec4ebe (topic2) Create topic2 |/ * b8b1506 Init $ git branch * master topic1 topic1-1 topic2 -
Bluetooth Speaker part 5 - Electronics, take 3
This article is part of a series on creating a Bluetooth speaker from an old vacuum tube radio and spare parts I had lying around in the house.
- Part 1: Introduction
- Part 2: Attempting to update the audio hardware
- Part 3: Using an existing Bluetooth speaker
- Part 4: Frontend work
- Part 5: Electronics, take 3
If you remember well, my first attempt at electronics for this Bluetooth speaker project was using an all-in-one Bluetooth + amplifier board. It did not go well, so I tried to use the guts of an existing Bluetooth speaker instead. That almost worked, but I experienced stability issues I was not able to solve :(
This article is about the third attempt: following the instructions from the Radio Workshop (which I mentioned at the end of part 3) to get a working Bluetooth + mono amplifier (hopefully).
-
Pixel Wheels 0.15.0
I am happy to announce the release of Pixel Wheels 0.15.0, the first version of year 2020! This version could almost have been called 0.14.2 as it's mostly made of bug fixes. Take this as an hint that the game is almost feature complete... at least that is how I analyze it :)
What's in this new version, you ask?
-
Bluetooth Speaker - Part 4 - Frontend work
This article is part of a series on creating a Bluetooth speaker from an old vacuum tube radio and spare parts I had lying around in the house.
- Part 1: Introduction
- Part 2: Attempting to update the audio hardware
- Part 3: Using an existing Bluetooth speaker
- Part 4: Frontend work
- Part 5: Electronics, take 3
So, while I was waiting for the components I ordered at the end of part 3 to arrive, I spent some time working on the "frontend": the front panel of the radio.
In case you forgot, this is what the original front panel looked like at the beginning:
After some work on the cabinet itself, the wood looked much better:
But the original radio had a cloth and a grille to hide the speaker, so there was more work to do on the front side.
-
Bluetooth Speaker - Part 3 - Using an existing Bluetooth speaker
This article is part of a series on creating a Bluetooth speaker from an old vacuum tube radio and spare parts I had lying around in the house.
- Part 1: Introduction
- Part 2: Attempting to update the audio hardware
- Part 3: Using an existing Bluetooth speaker
- Part 4: Frontend work
- Part 5: Electronics, take 3
So after the failure of part 2, I decided to try a seemingly safer approach: buy a small Bluetooth speaker, tear it down and use its guts to power my radio.
I bought a small portable Grundig GSB 710 Bluetooth speaker. It's a mono speaker, but since the radio I am working was also mono, as was common by the time it was created, it felt like a good fit. I checked it worked and started to tear it down:
