This is a Livecoding Recap – an almost-weekly post about interesting things discovered while livecoding ?. Always under 500 words and with pictures. You can follow my channel, here. New content almost every Sunday at 2pm PDT. There’s live chat, come say hai ?

This Sunday, we built a colorful map and discovered that a marathon is 138,435 feet long. I don't know why Google thinks that's a useful answer to "How long is a marathon?”.

Our map shows migrations into the selected country and uses color to show migration magnitude. The more people that moved into a country in 2015, the warmer the color of that country and its curve. Or rather, the more to the right on the d3.interpolateWarm color scale.

I wouldn't describe green as warmer than purple… to be honest, I'm not sure what exactly interpolateWarm is meant to correspond to. But the way we used it, to the right is more and to the left is less. shrug

Guess we'll have to add a legend next week ?

But first, the curves. Last week, we discovered that a curve between two points is a straight line. We fixed that by adding a middle point calculated using high school geometry.

Our new Curve component looks like this:

const Curve = ({ start, end, color }) => {
    const line = d3.line()
          [x1, y1] = start,
          [x2, y2] = end,
          middle = [(x1 + x2)/2, (y1 + y2)/2-200];
    return (
        <path d={line([start, middle, end])}
              style={{stroke: color,
                      strokeWidth: '1.6px',
                      strokeOpacity: '0.7',
                      fillOpacity: 0}} />

A line generator with a curve interpolator, some geometry for the middle point pulled up by -200 pixels, and returns a <path> element of a given color, and some other styling. We got the -200 number by fiddling around until it looked good.

That and some looping created a map with very many curves all over it. It was not very useful.

nikivansevdon suggested we add some sort of filtering, and daemon92 had great ideas around colors and highlighting source countries on the map itself. Thanks guys!

So we used react-select to make a drop down and spent far too much time rejigging our calculations to make the map aware of them. This is where having Redux or MobX becomes useful: When you want to move things around.

With those, you have data and calculations in a global state somewhere. With our haphazard approach, most logic gets slapped into the nearest component that uses it. It works great until you want to move something, then you're in a world of pain.

Watch the stream recording from about 1h20min onwards. You'll see what I mean. Copy-pasting. So much copy-pasting 😀

You can see the final code on Github.

It came out quite well I think.

Next week, we'll add useful text info, a color legend, and add some animation to make the visualization quicker to understand. I want to add something that shows directionality for those curves.

If we can get special regions like World, Developed countries, etc. to work, that would be great too. ?

Learned something new? 💌

Join 8,400+ people becoming better Frontend Engineers!

Here's the deal: leave your email and I'll send you an Interactive ES6 Cheatsheet 📖 right away.  After that you'll get an email once a week with my writings about React, JavaScript,  and life as an engineer.

You should follow me on twitter, here.