#Css

Failing at web components

I think I should know about Web Components™ I have no idea how this is going to work, but I have used Vue & React components in the past. I personally feel like Web Components should be the way forward, but my lazy self has not spent any serious time trying to get to grips with them

but here’s what I imagine a web component might look like. Absolute pseudo-code. I know nothing.

<script>
	// some JS goes in here to make things work
</script>
<template>
	<!-- some HTML goes in here -->
</template>
<style>
	/* some scoped CSS go in here */
</style>

This is probably a reflection of how much time I’ve spent in Vue.js recently, but it’s conceptually what I’m imagining is required to build something as a Web Component.

HexClock 2.0

Another clock experiment, this time a direct successor to my original Hexclock from 10+ years ago. I wanted to update it a little, to use multiple gradients and improve the way that they were calculated. As with the TV ident clock I’m not using any libraries, frameworks or stuff like that, with the aim of keeping my JS & CSS skills up to scratch.

TV Ident Clock 1

This is the first of my re-visits of a project I did a while ago, the ‘Hex clock’ (which was itself a CSS copy of a thing called the colourclock, which I think is now defunct)

This is inspired by those clocks that used to run before educational programming on BBC2 in the 70s and 80s.

View in full page - It just runs in the browser, and if you want to install it as an ‘app’ you can use Chrome’s “cast, save & share” tool.

Colourful Clocks

Just a fun bunch of experiments using JS, a timer, and some CSS gradient manipulation.