A new Litter Survey
In a culmination of litter surveys and litter picks, linked data() and data exploration, and remoteStorage and ActivityPub, I have created a web-based litter pick/survey app that I hope will allow federated citizen science.
In a culmination of litter surveys and litter picks, linked data() and data exploration, and remoteStorage and ActivityPub, I have created a web-based litter pick/survey app that I hope will allow federated citizen science.
My latest litter pick target was Hoe Stream and the White Rose Lane Local Nature Reserve. Here's how it went.
I just created a Gitlab CI job to create a release with information from a CHANGELOG.md file for some of my projects. Here's how I did it.
I noticed something strange happening during build process during a multi-tasking bug fix. Turns out I was using Gitlab CI's caching incorrectly. I should have been using artifacts. Here's what I saw.
As a birthday treat, I took the day off work to try out my electronerised litter picker. Here's how it went.
In preparation for a day of litter picking, I finally got round to a project idea - attaching a camera to a litter picker to record it all. Here's what I did.
I finally started implementing UI testing on first-draft using WebdriverIO. While writing tests was easy, getting the tests running was a little more difficult. Here is how I did it.
Hooray! My new blog is live! Based on Sapper, using MongoDB and eventually ActivityPub and ActivityStreams, it will be my federated posting hub to the world.
Creating this new blog, I wanted to make sure there was no metadata data leaking personal information. Here's how I removed all the metadata tags except the ones I wanted from my photos.
Using tmux for your terminal multiplexer but want an easy to reattach to a session? Here's a small bash script to do it.
Here's how to help your readers save time by making your post's shell commands easy to select and copy - with a simple CSS property.
Articles, how-tos, blogs and knowledge forums are all great places to figure out how to solve your computer troubles. Most of them have a list of commands to run and some even show the output they got or that should expect.
Another common thing is to add a prompt to the start of all the commands. This makes it really easy to see what the commands are and it can also tell you which user to run them as - $ for a normal user and # for the super user, aka root.
The only issue with these practices is that it makes copying and pasting take a little more time - each command needs to be individually selected and copied rather than selecting them all in one.
One great and under-utilised CSS property that can solve this issue is the user-select property. It allows the developer to specify what should be selectable and what shouldn't. It can also be used to make copying stuff slightly more difficult if you are that way inclined.
The two main keyword values are none and text - none disables selection (you won't be able to select this text in the brackets), and text allows text selection as per normal.
The other values are (the explanations are in a <span> tags with the user-select to show how they work):
contain - meaning a selection started in the element can only contain text that is in that element (hardly supported)all - meaning that if any text inside the element is selected, then all text in that item is selectedauto - a slightly more complex working as documented on MDN- The used value of auto is determined as follows:On this site, I currently use highlight.js to render syntax highlighting. The classes used for the shell highlighting can be easily augmented to incorporate better command selection by adding the user-select property to . Below is the CSS that does just that (I put the highlighted code inside <pre> and <code> tags with the language as a class on the <pre> tag)
pre.shell > code {
user-select: none;
}
pre.shell .bash {
user-select: text;
}
pre.shell .hljs-comment {
user-select: none;
}Here is a demo of without using user-select
$ echo do this
do this
$ echo then do this
then do this and with user-select: none; on everything, but the actual commands
$ echo do this
do this
$ echo then do this
then do thisHere is the HTML of the above syntax-highlighted block for completeness.
<pre class="shell"><code>
<span class="hljs-meta">$</span><span class="bash"> <span class="hljs-built_in">echo</span> <span class="hljs-keyword">do</span> this</span>
do this
<span class="hljs-meta">$</span><span class="bash"> <span class="hljs-built_in">echo</span> <span class="hljs-keyword">then</span> <span class="hljs-keyword">do</span> this</span>
then do this
</code></pre>A couple of issues with using it with higlight.js:
hljs-meta or the bash class.span with the command in it. Again, adding padding to the bash class makes this a little nicer.Making my new blog, I didn't initially set the published dates to be native dates in the database. Here what I did to change them ...and do all the upgrades I needed.
I recently needed to test that some Vue components were creating the correct HTML. To do this, I decided to create snapshots of Object representations of the rendered HTML.
HTML5 number inputs aren't useful, but tel inputs, have all the power
I decided to look into the extortion emails I have been getting and wrote a small script to extract the bitcoin addresses that have been used.
As part of my pledge not to upgrade, I decided to repair two of my failing mice instead of replacing them with a brand new model (as tempting as it was). Here's what I did.