Sam Wilson's Website

Home

  2. Where to store the version number

    It’s Wednesday morning, coffee is made, and SVG Translate is being upgraded to 2.0.0. I think that bumping major version numbers for underlying platform upgrades is slightly controversial, but I do it. My reasoning is that a major version primarily indicates that “something” must be done when you upgrade, and that’s definitely true when dropping support for old versions of PHP.

    A few of the tools that use the ToolforgeBundle for Symfony display their current version number in the footer, and they do so by running git describe to get the current tag. This is proving to be silly when the filesystem is slow, and is timing out. It’d be better to have the current version number within the codebase somewhere — the trouble with that is remembering to keep it in sync. Ideally, I think, it’d be in a VERSION file, and would get updated every time a change is made so that there’s only ever one commit with a given version (other than -dev ones; i.e. the next commit after a release would add that).

  3. In reply to this post by Sam Wilson.

    The above post should be a sufficient way for me to post a ‘like’, but it’s not yet. If I sort out link previews it might be, but for now it’s a plain URL with nothing. If webmentions were working it would at least send one of them, but they’re not.

    (Can I even say ‘above’ in a reply and know that the context is clear?)

  5. Blogs with stuff in the margins

    modern web design trends have stripped away a lot of what made blogs interesting, discoverable, and accessible. Superficial minimalism has meant people don’t include archive links, metadata, blogrolls, or even RSS icons.

    Ruben Schade’s blog is always interesting, and his post today about keeping tags, search, blogrolls, etc. visible on posts’ pages is on form.

    The idea that the blog format was pretty much figured out in the early days satisfies me, but that’s probably just because I liked it at the time and am starting to feel more of that old “things were fine before and I never really finished figuring them out so do we really have to change already?!”

  6. Having a good pair of headphones (Sennheiser 450 BT, currently) and a cup of coffee, in a quiet office, and without the summer heat baking the windows, is today making me happy. The ABC has a new(-ish) classical radio station, and the work I’ve been doing on SVG Translate is going well (or at least not breaking).

  7. I seem to be borking around with my website. That’s the point of having a website though, isn’t it?

  8. Entrance to the exhibition

    The file that is attached to this post.

    The generator was to power the whole thing; the two doors (entrance and exit) are further along with scaffolding over each of them.

  10. Vue in MediaWiki

    I’ve been working on my first real foray into Vue in MediaWiki: a special page that lists all of the pages for which the current user has Edit Recovery data saved (T347673). It’s not something that really needs to use it at the moment (it’s just a simple list), but it’ll evolve soon and be more complicated and hopefully end up looking better.

    Who knows, maybe I’ll learn more of this and get around to helping with moving all that old stuff away from jQuery UI? (The WikiEditor link-insertion dialog comes to mind, because I use that lots). Although I do wonder if I’m doing any of it right.