The story is that I have spent decade writing a JavaScript UI library, I was hired during early days of jQuery movement, pivoted several times (html + images, html + css, flat html + css, canvas, canvas + webgl) however end up with unused tools and UI kit, few years later, during 2017 I have decided to rewrite some tools using Typescript and release as GPL2 (which I should change to LGPL2) and changed career.
Ask HN: What are some tools / libraries you built yourself?
81–90 of 617 posts
Re: Ask HN: What are some tools / libraries you built yourself?
#82Re: Ask HN: What are some tools / libraries you built yourself?
#83I was building a touchscreen music-production app for Windows, and I wanted it to have a phone/tablet style interface. It would have a stack of modal popup Views that the user could tap (or click) off of to close the top View and go back down. I ended up splitting the UI system off into a separate library and kept working on it. It now has DI (with scoping) and some other features. I've since used it for a few other…
Also question to the room, is DI really worth it ? All that complexity to switch out sub-classes . A clean design but in practice it just feels like too much work for the benefit.
Re: Ask HN: What are some tools / libraries you built yourself?
#84- JQ Live View (VS Code extension) [1]
Both used to create my game, a pokemon-ish roguelite (React, typescript) [2]
-- Links:
[0]: https://ldd.github.io/react-tech-tree/ [0-source]: https://github.com/ldd/react-tech-tree
Re: Ask HN: What are some tools / libraries you built yourself?
#85A Python program to make an embeddable search engine for a static website: https://github.com/joe-crawford/Static-Site-Search It indexes the site and generates search functionality in JavaScript (the index is just a static JSON file) that can be uploaded wherever JS/HTML/etc. files can be uploaded. I thought it might be useful for people with sites on GitHub pages or similar who don't want to use one of the major sea…
That’s pretty clever, I guess that for most personal blogs it will be more that sufficient.
I looked for a while to find something similar. I'm sure it must already be implemented out there, but to answer the question in the original post about why build something, I couldn't find an easily downloadable "tool" for doing it when I looked (2019) and it was simple enough to be "fun".
Re: Ask HN: What are some tools / libraries you built yourself?
#86I wasn't satisfied with writing the YAML or annotations manually.
Re: Ask HN: What are some tools / libraries you built yourself?
#87[1]: https://smocker.dev
Re: Ask HN: What are some tools / libraries you built yourself?
#88I wrote a cooperative multitasking system for Turbo Pascal because I needed to be able to stream data through a series of text pipes and it was easier than faking it with a bunch of temporary files. I also wrote a series of data entry routines to allow the quick creation of database editing programs. I haven't open sourced them because I doubt anyone would care about those old MS-DOS/TP7 tools now, and I'm not up for…
Maybe not a huge audience but I bet the people needing them would be hugely grateful. I use a couple old tools that I gladly contribute ( money ) to because despite being old they work great and there is no alternative.
Re: Ask HN: What are some tools / libraries you built yourself?
#89I wrote a library for animating image backgrounds on the web using After Effects style filters and transitions: https://aeroheim.github.io/midori/ It's basically a post-processing pipeline implemented with Three.js and WebGL using a few shaders that I wrote. I created it primarily because I needed it for one of my current projects, so the use case is fairly niche and mostly only relevant for stuff like creative codin…
Re: Ask HN: What are some tools / libraries you built yourself?
#90I've built several extensions to vscode. My best one has to be a tool to help you upgrade dependencies in your package.json: https://github.com/pgsandstrom/package-json-upgrade I just felt that other extensions lacked polish. The UX wasn't very good, or they didn't read all npm config properly.