Spend a month making one beautiful thing per day, given a bunch of prompts. A month late, but as they say, ’the second best time is now'.
Let’s do it!
Spend a month making one beautiful thing per day, given a bunch of prompts. A month late, but as they say, ’the second best time is now'.
Let’s do it!
Last time we had Runelang: A Bind Rune Generator. This time, let’s make ‘summoning circles’. Basically, we want to make a circle with stars and other circles inscribed and around the borders with various ‘mystic’ text in the mix. Something like this:
generate_summoning_circle
generate_summoning_circle
again)Continuing with my Runelang in the Browser series, I had the idea to automatically generate runes. So basically reversing the parsing step, rather than to take what I’ve written and make it look good, to write something that Runelang can parse–and still look good.
In a nutshell, I want to write a series of functions that can recursively call one another to render runes:
generate_bind_rune
generate_bind_rune_arm
As they say, life is what happens when you’re making other plans. But I’m back, so let’s talk some more about Runelang. In the interest of not dragging on months without finishing, we’re going to go ahead and push through the rest of the project. Onward!
Earlier this week, we started parsing, getting through groups, nodes, params, and lists. A pretty good start, but it also leaves out two very powerful things (expressions and defines), one of which we absolutely do need to start actually evaluating things: expressions. Since we use them in every param, we pretty much need to know how to parse them, so let’s do it!
I’m still here! And less sick now.
Last time(s), we described and lexed) Runelang! This time around, let’s take the lexed tokens and go one step further and parse them!
So, how do we go about this? With a recursive descent parser!
group
/ identifier
/ literal
/ expression
/ etc)parseGroup
etc) that will:Let’s LEX!
So this is actually one of the easier parts of a programming language. In this case, we need to turn the raw text of a program into a sequence of tokens / lexemes that will be easier to parse. In this case, we want to:
So let’s do it!
Previously, I wrote a post about making a DSL in Ruby that could render magic circles/runes. It worked pretty well. I could turn things like this:
rune do
scale 0.9 do
circle
polygon 7
star 14, 3
star 7, 2
children 7, scale: 1/8r, offset: 1 do |i|
circle
invert do
text (0x2641 + i).chr Encoding::UTF_8
end
end
end
scale 0.15 do
translate x: -2 do circle; moon 0.45 end
circle
translate x: 2 do circle; moon 0.55 end
end
end
Into this:
But… I decided to completely rewrite it. Now it’s an entirely separate language:
Okay. A random post on the /r/cellular_automata subreddit inspired me.
Let’s generate a cellular automata where each pixel updates based on a neural network given as input:
Let’s do it!
L-Systems are pretty awesome. With only a bare few rules, you can turn something like this:
LSystem.new("Barnsley Fern") do
start "+++X"
rule "X", "F+[[X]-X]-F[-FX]+X"
rule "F", "FF"
terminal "F" do forward end
terminal "[" do push end
terminal "]" do pop end
terminal "-" do rotate -25 end
terminal "+" do rotate +25 end
end
Into this: