November 2017

The instructions in castledb‘s README.md don’t cover Mac. I might suggest to ncannasse to add some but only after I’m sure the way I’m doing it is the best way to do it. Or, conversely, if this is now how it has to be done regardless of platform because of changes to nwjs. In short, just like for other platforms, I compile first:

haxe castle.hxmlCode language: Bash (bash)

Then change to ./bin and I directly run the executable. It doesn’t matter if you copy it to that directory or just install it in /Applications and run from there but here I do the latter:

./nwjs/nwjs.app/Contents/MacOS/nwjs --load-extension . .Code language: Bash (bash)

Also two of my minor fixes have been merged in as of this morning so now ctrl+Q actually quits, etc. Stay tuned for a bigger improvement that I need for a game I’m working on.

This blog post originally appeared on my blog at webbmaster.com, which I’m taking down to consolidate with this personal blog. The timestamp is set to the timestamp from the original blog post.

I wrote a post with this same title ages ago on my old blog, which I don’t really feel like bringing back (something about being haunted by things I wrote 15 years ago). But I swear, this post is better anyway! [note: you are reading this on the original blog in terms of the domain, though old posts haven’t been restored]

So in short, there are fonts out there that let you write runes or other ancient sets of characters, but they map the symbols to Roman characters. Meaning you type ‘a’ and you get ᚪ. You change to a different font, you get an a instead of an ᚪ. That’s fine if you’re able to force the text to use a certain font and only that font or if the final product is an image, not text.

Month: November 2017

Developing Castle on Mac

Write Runes on Your Computer