Example 3 : Cantor Dust
First, let’s define our L-System:
The interesting thing about this example is that we need to draw, not only the current generation, but also all the preceding generations too.
So I had to approach things slightly differently, and instead of dealing with a Signal(State), I need a Signal(List(State)):
This signal of List(State) is then passed to the display function (along with the dimension of the window):
We can use rectangle to represent the individual bars, and for my screen 25 pixels seems to be a good height.
For each generation we want to place them some distance apart. That is to say that the state for each generation should have a stepped Y position.
so now, we need to add a drawState function that will take in:
- the width of the window;
- the y position for its rectangles; and
- the state it needs to draw
and return a list of rectangles for that state.
You may remember the following paragraph from Part 2:
So to work out the x positions of the first rectangle for this state, we have this slightly dubious looking line of code:
and the next block of code generates the x positions for all the rectangles:
Running this example in Elm Reactor I can get the demo to gen 8, after that it takes noticeably longer to render and the bars are so thin that they’re barely visible.
Live Demo (here)
Use LEFT and RIGHT arrow keys to evolve/devolve the L-System.
Source Code (here)
Next : Koch Curve
I’m an AWS Serverless Hero and the author of Production-Ready Serverless. I have run production workload at scale in AWS for nearly 10 years and I have been an architect or principal engineer with a variety of industries ranging from banking, e-commerce, sports streaming to mobile gaming. I currently work as an independent consultant focused on AWS and serverless.
Here is a complete list of all my posts on serverless and AWS Lambda. In the meantime, here are a few of my most popular blog posts.
- Lambda optimization tip – enable HTTP keep-alive
- You are thinking about serverless costs all wrong
- Many faced threats to Serverless security
- We can do better than percentile latencies
- I’m afraid you’re thinking about AWS Lambda cold starts all wrong
- Yubl’s road to Serverless
- AWS Lambda – should you have few monolithic functions or many single-purposed functions?
- AWS Lambda – compare coldstart time with different languages, memory and code sizes
- Guys, we’re doing pagination wrong