I recommend anyone in Scotland (or more specifically, anyone likely to get a COVID-19 test administered by NHS Scotland) with a compatible device to download and install it.
There is not much content there yet, besides details of everything that is on the channel. But those details are probably the most interesting part.
The process started simple and got more sophisticated over a few days. First I generate a page for each video. Then I get a list of all the channel playlists, and add a tag to each video page for each playlist. I also create a page for the tag that links to the actual YouTube playlist. Finally, for each video I parse the description adding YouTube chapter links where appropriate.
It highlights another interesting advantage of static site generators. It is really easy to create content with external tools. You don’t need to access any kind of API, you just generate text files.
After spending most of its time on Wordpress (initially a self-hosted version and then Wordpress.com), the blog is now a static site generated with Hugo and running as an Azure Static Web App.
Ever since I created the Tic-tac-toe Collection site on Hugo I’ve wanted to move the blog, but I never had the time. The recent events related to COVID-19 have, however, given me random bits of free time, so here we are.
Tic-tac-toe Collection is being run as a static website on Azure Blob Storage, which is a way of connecting various bits of Azure together to host a static site. The new Azure Static Web App Service joins them all for you in a much more straightforward fashion.
Under ideal circumstances, the minimal steps to set up a static web app are:
- Upload your site to Github.
- Create a new Static Web App pointing at your Github.
And, if you’re lucky, that’s it. It generates a GitHub action for you that does the actual building, and it’s based on Microsoft Oryx. Oryx is a slightly magical, slightly scary tool designed to auto-detect and then build static web apps using a range of different technologies.
Unfortunately, for me, the auto generated Hugo script did not actually work. I ultimately used the GitHub action from here.
One of the reasons I started retuning pieces to different modes was the hope that something good might come out of it by chance. One example has appeared. I don’t think “good” is the right word, but it at least sounds intentional (most pieces just sound accidentally out of tune).
Land of Hope and Glory retuned into Ultra Locrian.
It is dark and disharmonious. Hitting a note on nearly every beat combined with a lack of any real resolution gives it an unrelenting monotony. And somehow, halfway through when the higher octave repeat starts you still end up with the feeling of: “It’s still going? And somehow it’s worse?”.
I would like to end on a cheerful note. Nothing with “Locrian” in the name really does that. So instead, have some Sonic the Hedgehog music:
One big advantage of doing this to the Duke Nukem 3D theme is that the original was already a MIDI file. That means people familiar with it are already used to hearing slightly different versions, and the version I generate is no more or less authentic than any of the others.
Although I have to admit I do not remember hearing good quality tubular bells on the computer I first played it on (but they have since grown on me while making this).
I posted a link to a video of Jingle Bells in the 7 different modes of the major scale.
I’ve now improved my process for generating the videos so much that I’m confident I can generate enough content to maintain a channel.
Microsoft have just announced the future of Xamarin and Xamarin forms - the .NET Multi-platform App UI (or MAUI for short). As a name, it’s not great. The highlights are as follows:
- It’s an evolution of Xamarin Forms. It basically is Xamarin Forms, but finally accepting some breaking changes. To be honest, I’m hoping for a lot since there is a lot of weirdness in Xamarin Forms that has been holding it back.
- Single project, multi-targeted. It took a long time to get to the point where this was possible. From shared projects, to PCL projects, through .NET Standard. This should make things a lot easier.
- Still based on platform renderers using native controls. This is a mixed bag. Using native controls has long been a selling point of Xamarin (with or without Forms). With the rise of Flutter this has been shown to be less important. Many people have been asking for consistent platform agnostic renderers instead.
- The end of “Xamarin” as a name. Some time in the .NET 6 timeline (end of 2021) Xamarin.iOS will become .NET for iOS and Xamarin.Android will be .NET for Android. I have mixed feeling about this since this was a fairly succinct way to describe by top skillset.
I also already have my own enhancement issue submitted.