Posts Tagged Tools

Posted on Programming

Don’t starve together

I’ve been playing Don’t Starve Together lately, and it’s awesome. There’s a constant sense of pressure imposed by the passage of time, days turn to night, a mild Autumn to bleak Winter. It makes any wasted time seem at worst dire, or at best mildly frustrating.

There are so many items you can cobble together, with twigs, bunny-flesh, and the like. At least 144, by my count. But unless you memorize their positions and ingredients, you’re going to waste a lot of time searching through categories for some item you’re sure you’d seen but just can’t seem to find.

I, myself, often kept a wikia tab open on my secondary monitor. But as I’m sure you’re aware, Wikia is slow and prone to annoying ads blaring sound this way and that. And even so, didn’t provide an ideal interface for that sort of thing.

I wanted to type in “charcoal” and immediately see what I could make. Or “crock pot” and see what I needed. Or even “science” to see everything that’s in that category.

And now I can!

The What can I make page is where I spend most of my time. The What do I need page is for those situations where I’m starting a new game, and know I want to create, say, 2 crock pots and 1 bird cage. It’ll tell me everything I need to collect to fulfill my crafting dreams.

If you find anything that doesn’t work, let me know, I haven’t tested it all that much.

I made it just using jquery. Then I remade it using backbone. Then I remade it using webpack, sass and react. Because why not?

This is the backbone version, because the react interface felt strangely clunky.


Posted on Programming

The secrets of an elusive santa

At some point late last year I decided should have a secret Santa tool. As useful a feature as it may be, I couldn’t decide on the details of integration. And as most of you know without a clear idea for a solution or interface, it’s easier to just put a feature off. There are just so many potential complications.

So put it off is what I did. However, I confidently marked Friday November 27, 2010 off on my calendar as the day that I would implement the secret Santa tool. And as unexpected as expected, that day eventually came.

I’m only partially joking. I did in fact mark November 27 for secret santa development, but did so on November 25. Less impressive, true, but — well, just less impressive all around.

Posted on Uncategorised

Codepaste 2 and Google Chrome: friends at last?

Codepaste2 displays correctly in Chrome. Finally!

In Opera, Safari, Firefox, and IE everything was great; in Chrome things went so very wrong — lines would wrap, lose opacity, and display behind themselves. Code was super difficult to read.

But now it works! And, to be honest, I’m not sure why. I updated the version of EditArea it uses, and didn’t see a change. When I switched its allow_resize option from both to y everything magically got better.

I was pretty happy. But then I changed y back to both and things didn’t get worse, which left me confused and a little scared.

I hope the issue was resolved by updating EditArea, and all the confusion was caused by some weird caching issue. Or maybe I forgot to refresh.

Codepaste v1 still gets heavier use than Codepaste v2. I wonder if that is by conscious decision, or if people just don’t know about Codepaste v2 and how much better it is.


Posted on Uncategorised

Another summary? Again? Seriously?

So much random stuff today!

Tacotime wanted a script to redirect visitors to affiliate websites; I made one for him. He wanted it to keep track of how many times it sent people to each site, which meant an interface for managing affiliates – and is how a 30 minute project turns into a 2 hour one. And that extra 1.5 hours is so boring. Oh, well. It’s done now.

Link selection is weighted by past redirects, which results in the interesting side-effect of it being far more likely for new affiliates to be chosen than any other – at least until they catch up.

Posted on Programming

An image splits; time lacks distinctinction

A man named Shaun E. Kiernan asks if I know of any programs purposed toward splitting PNG files. Barring image editors, I do not.

Saying no to people is not something I do well. I offer to make him one. Development time should be brief.

I do so. It is so.

I rebel against the common over-use of text fields. I do not worry about certain conditions. If an image cannot be evenly divided, it will try for pixel fractions. This is an obvious mistake, but the fault is theirs.

I implement tarring, for increased ease-of-use. I commandeer and massage code from Bradicon. It is done in under an hour.

He laments its interface, though it seems functional. He claims it suits his need.

I spend some more time on the user interface. This is as far as I see it going.

It is a program that splits an image, and split images is what it does.


Posted on Programming


A flurry of ill-formatted code works its way across the internet, neatly wrapped in tiny packages generated by instant messagers. Pasting code into an instant message, while convenient, rarely works out well.
And that is where this “World Wide Web” comes in. It saunters in, wearing its glittering shades with an easy confidence as its poorly chosen hat rests awkwardly atop its head. He carries with him a solution, though difficult to pick out against the backdrop of a shirt he seemingly purchased solely for its garish juxtaposition of bright and strangely flashing colours.

I, myself, have sent my share of code via MSN or GoogleTalk. Foreign eyes can often better detect errors than those that have become familiar with the tangle of semicolons and brackets before them.

But, no more. Well, hopefully at least, less frequently.

codepaste. Just paste in some code, and it will store it for anyone to view. Using Geshi, it will probably even syntax highlight it. If you don’t want to paste the link, you can have codepaste e-mail it to whomever you wish.

codepaste: now featuring dark and light skins.