Late last week, California Rep. Eric Swalwell decided to double-down on previous anti-gun comments. In the process, he sparked a debate that led to one of the worst possible comments an elected official could make.

And it would be a short war my friend. The government has nukes. Too many of them. But they’re legit. I’m sure if we talked we could find common ground to protect our families and communities.

— Rep. Eric Swalwell (@RepSwalwell) November 16, 2018

That’s right, he implied that the United States government would use nukes to deal with Second Amendment activists who resist gun confiscation.

With that in mind, I wanted to pen a bit of an open letter to Rep. Swalwell.

Dear Rep. Swalwell.

On Friday, I fired up Twitter to see what was going on and I saw something baffling. That was the above tweet where you respond to someone warning of a civil war in the even your assault weapon confiscation scheme ever came to fruition. You actually brought up nuclear weapons.

Seriously?

You then began to mischaracterize the entire thing, first calling it “sarcasm” while still ignoring the reality that you brought up the argument of nuking Americans who disagree with you. Then you tweet this:

America’s gun debate in one thread.

1) I propose a buy-back of assault weapons

2) Gun owner says he’ll go to war with USA if that happens

3) I sarcastically point out USA isn’t losing to his assault weapon (it’s not the 18th Century)

4) I’m called a tyrant

5) 0 progress

— Rep. Eric Swalwell (@RepSwalwell) November 16, 2018

Wow. Look at the lies.

First, you propose a “buy-back” sure enough…but notice how you said you wanted the police to go after anyone who didn’t want to sell their AR-15s for a fraction of their purchase price?

You’re not proposing a method to potentially reduce the number of AR-15s on the streets, you were talking about confiscating the single most effective rifle for self-defense and going after anyone who didn’t want to go along with the program.

You were then warned that if you do that, it’ll spark a civil war. To be clear, this point was made long before. This Twitter user can’t be the first one to have ever mentioned the possibility to you. American gun owners will not become subjects. We don’t trust the government enough, regardless of who is in power, to just accept them as the only one with these weapons.

It’s also interesting that you claim you “sarcastically point out the USA isn’t losing to his assault weapons” and claiming that is leading to you being called a tyrant.

No.

You’re being called a tyrant because you are seeking to ignore the Second Amendment, deprive people of their property without due process, and seek to create the perfect environment for tyranny to take hold in this great nation. You’re called a tyrant because you then respond to warnings of what that might lead to with comments about nuclear weapons.

However, I’m going to clue you in on a little something, Mr. Swalwell.

In the 1960’s, my father went on an all-expenses-paid trip to the far east. His destination was a tiny country few people had even heard of a decade before. It was called “Vietnam.” There, the mighty American military came face to face with an enemy that was little more than guys with assault rifles and how did that work out?

We didn’t nuke them.

Then fast forward to 2001. A group of terrorists hijacked some planes and flew them into buildings. We knew who was responsible and roughly where he was. We told the Taliban to give him over, and they refused. We rolled right over them.

Now, little more than guys with assault rifles, they’ve been a major headache for the military since then.

The same thing played out in Iraq. Saddam’s army fell in no time, but we were stymied by the guerrilla warfare that followed.

Should, God forbid, a civil war come to our American shores, it won’t be pretty. However, I can also tell you that the combined might of the United States will have a damn hard time neutralizing that rebellion.

And that’s if the military is even interested in fighting. Don’t be surprised, Mr. Swalwell, to find out that most of the guys on the sharp end actually disagree with you over this crap. And they’re the ones who will have to kick in doors and be the ones who get shot.

The same is true of law enforcement. Don’t mistake police chiefs pontificating on gun control to mean that the regular beat cop is your ally in this. They often know damn good and well they can’t be everywhere, but an armed citizen can at least protect themselves.

In other words, the people who you want to stand against these Americans aren’t likely to side with you on any particular level.

But then again, maybe you did know that. Maybe that is why you brought up nukes in the first place.

Look, Rep. Swalwell, I get you’re from California and people there seem to love them some gun control. California isn’t the rest of the United States, and I’m thankful for that. However, you should also realize that many of us have seen what is transpiring in other countries and are bound and determined not to allow that to happen here. We’ve watched the UK ban guns, then start going after free speech at a time when crime is becoming more and more of an epidemic, for example. We watch Europe do the same thing as “refugees” act however they want and the governments of Europe seem unwilling to do anything about it, but the idea of average Europeans having the means to defend themselves is unconscionable.

We’ve seen that and we’re not interested in it ourselves.

If that means you want to nuke us, then so be it. However, look at the writings of our Founding Fathers when it comes to guns. They explicitly wanted us to be able to overthrow the government if it fails to act in our interests.

By making your crack about nukes, you didn’t take down the pro-gun argument. You may have created a “pro-civilian ownership of nukes” argument, though, so good job for that.

Maybe the next time you decide to be so flippant over a gun owner’s concerns about his constitutionally protected rights, you’ll stop being such an elitist schmuck and recognize there are real concerns at work on this side of the aisle, and your attitude isn’t making anyone more willing to sit down with you and talk about finding “common ground to protect our families and our communities.”

Especially since the only common ground you want us to find better boils down to “your way or the highway.”

So no. We’re not giving up our weapons.

And yes, if you insist on coming after us, it will spark a civil war.

You need to come to terms with this reality if you’re going to keep pushing this ban of yours. Man up and admit that you want us dead and I might at least be able to respect your guts. But stop pretending that you want anything else.

Build An Interactive Infographic With Vue.js

Have you ever had a requirement in which you had to design and build an interactive web experience but the grid system fell short? Furthermore, the design elements turned into unusual shapes that just wouldn’t fit into the regular web layouts? In this article, we’re going to build an interactive infographic using Vue.js, SVG and GreenSock by using dynamic data and unusual layout.

This article presents a modern approach to building an interactive infographic. You sure can have plain infographic with all the information available upfront — without any user interaction. But, thinking of building an interactive experience — changes the technology landscape we choose. Therefore, let’s understand first, why Vue.js? And you’ll see why GSAP (GreenSock Animation Platform) and SVG (Scalable Vector Graphics) become obvious choices.

Vue.js provides practical ways to build component-based, dynamic user interfaces where you can manipulate and manage DOM elements in powerful ways. In this instance, it’s going to be SVG. You can easily update and manage different SVG elements — dynamically — using only a small subset of features available in Vue.js — some of the staple features that fit the bill here, are, data binding, list rendering, dynamic class binding to name a few. This also allows you to group relevant SVG elements together, and componentize them.

Vue.js plays nice with external libraries without losing its glory, that is GSAP here. There are many other benefits of using Vue.js, one of which is that, Vue.js allows you to isolate related templates, scripts, and styles for each component. This way, Vue.js promotes modular application structure.

Recommended reading: Replacing jQuery With Vue.js: No Build Step Necessary

Vue.js also comes packaged with powerful lifecycle hooks that let you tap into the different stages of application to modify application behavior. Setting up and maintaining Vue.js applications doesn’t require a big commitment, meaning you can take phased-approach to scale your project as you go.

The infographic is very light-weight in a visual sense, as the main aim of this article is to learn how to think in terms of data, visual elements, and of course, Vue.js — the framework that makes all the interactivity possible. In addition, we’ll use GreenSock, a library for animating SVG elements. Before we dive in, take a look at the demo.

We’ll start with:

1. The overview of the data for infographic;
2. SVG image preparation;
3. An overview of Vue components in context of the SVG artwork;
4. Code samples and diagrams of key interactivity.

The infographic that we’re going to build is about Tour De France, the annual bicycle racing event held in France.

Overview Of Tour De France Data

In infographic design, data drives the design of your infographic. Therefore, while planning your infographic design, it’s always a good idea to have all data, information, and statistics available for the given subject matter.

During Tour De France of 2017, I learned everything about this biggest cycling event that I could in 21 days of the game in July, and I familiarized myself with the subject.

Basic entities of the race that I decided to go for in my design are,

• Stages,
• Teams,
• Routes,
• Winners,
• Length and classifications of each routes.

This next part of the process depends on your thinking style, so you can be creative here.

I created two sets of data, one for stages and other for teams. These two datasets have multiple rows of data (but within limit)  —  which matched with two wheels of the bicycle with multiple spokes in each. And that defined the key element of the design, The Bicycle Art that you saw at the beginning  —  where each spoke will be interactive & responsible to drive what information is revealed on screen.

I mentioned within limits above, because what we’re aiming for in this instance is not a full-blown data-visualization in context of big data but rather an infographic with high-level data.

Therefore, spend quality time with data and look for similarities, differences, hierarchy or trends that can help you convey a visual story. And don’t forget about the amazing combination of SVG and Vue.js while you’re at it, as it will help you bring about the right balance between information (data), interactivity (Vue.js) and design elements (SVG Artwork) of infographic.

Here’s the snippet of a stage data object:

{
    "ID": 1,
    "NAME": "STAGE 01",
    "DISTANCE": "14",
    "ROUTE": "KMDÜSSELDORF / DÜSSELDORF",
    "WINNER": "THOMAS G.",
    "UCI_CODE": "SKY",
    "TYPE": "Individual Time Trial",
    "DATE": "Saturday July 1st",
    "KEY_MOMENT": " Geraint Thomas takes his first win at 32"
}

And team data object snippet as below:

{
    "ID": 1,
    "UCI_CODE": "SKY",
    "NAME": " TEAM SKY",
    "COUNTRY": "Great Britain",
    "STAGE_VICTORIES": 1,
    "RIDERS": 8
}

This infographic is operated by a very simple logic.

UCI_CODE (Union Cycliste Internationale) is the connecting key between the stage and the team object. When a stage is clicked, first we’ll activate that stage, but also use UCI_CODE key to activate corresponding winning team.

SVG Preparation

Having a couple of datasets and a rough concept of bicycle art ready, here’s the static SVG CodePen of the infographic I came up with.

See the Pen Static Bicycle SVG by Krutie(@krutie) on CodePen.

We have created only one spoke for each wheel, that is because we’ll dynamically create rest of the spokes using a number of records found in the dataset, and animate them using GreenSock Library.

The workflow to create this SVG code is also very simple. Create your Infographic artwork in Adobe Illustrator and save as SVG. Make sure to name each group and layer while working in Illustrator, because you will need those ids to separate parts of SVG code that will eventually populate <template> area of Vue components. Remember that layer names given in Illustrator become element ids in SVG markup.

You can also use SVGOMG and further optimize SVG code exported from Adobe Illustrator.

Important Note: If you use SVGOMG to optimize SVG markup, your code certainly will look neat, but note that it will convert all <rect> elements into <path> with d attribute. This results into losing x and y values of the rectangle, in case you wish to adjust few pixels manually later-on.

Second thing, make sure to uncheck Clean Id option (right-hand side options in SVGOMG interface), this will help maintain all groups and ids intact that were created in Illustrator.

Vue Component Overview

Even if interactivity and data-flow in your infographic project is quite simple in nature, you should always take a moment to draw up a tree diagram of components.

This will especially help in case you’re not using any shared-data mechanism, where child components are dependent on the values sent from the parent component (i.e. via props) or vice-versa (i.e. this.$emit events). This is your chance to brainstorm these prop values, emit events and local data — and document them before starting to write the code.

Diagram above is the snapshot of Vue components that is partially derived from interactivity requirements and partially based on SVG markup. You should be able to see how SVG markup will be split up based on this tree structure. It’s pretty self-explanatory from hierarchy view-point.

1. Chain-wheel will imitate rotation of spokes.
2. Stage component is the rear wheel that will list all 21 stages.
3. Stage-detail component will display related information on a curved path (left-hand side).
4. Team component is the front wheel that will list all participating teams on spokes.
5. Team-detail component will display related information on a curved path (right-hand side).
6. Navigation will include back and next button to access stages.

The diagram below represents the same Vue components seen above, but in the context of the infographic design.

Less is more — should be the approach you should try to take while working on similar projects. Think through the animation and transition requirements you have, if you can get away with using TweenLite instead of TweenMax — do so. If you have the option to choose elementary shapes and simpler paths over complex ones — by all means try to opt-in for light-weight elements that are easy to animate — without any performance penalty.

Next section will take you through an exciting part with GreenSock animation and Vue.js.

GreenSock Animation

Let’s take a closer look at:

1. Text animation on a curved path;
2. Spoke animation on a wheel.

Animating Text On A Curved Path

Remember the curve path seen around the bicycle wheel, that curved path is slightly bigger than the radius of the bicycle wheel. Therefore, when we animate text on this path, it will look as if it follows the shape of the wheel.

See the Pen Text on a Curved Path by Krutie (@krutie) on CodePen.

path and textPath is a sweet combination of SVG elements that allows you to set text on any path using xlink:href attribute.

<path id="curvedPath" stroke="none" fill="none" d="..."/>

<text>

  <textPath xlink:href="#curvedPath"
          class="stageDetail"
          startOffset="0%">
          
   </textPath>

</text>

To animate text along the path, we’ll simply animate its startOffset attribute using GreenSock.

tl.fromTo( ".stageDetail", 1,

{
  opacity: 0,

  attr: { startOffset: "0%" }

},

{

  opacity: 1,

  attr: { startOffset: "10%" }

}, 0.5 );

As you increase the startOffset percentage, text will travel further through the circle perimeter.

In our final project, this animation is triggered every time any spoke is clicked. Now, let’s move on to a more exciting part of the animation.

Animating Stages/Spokes Inside The Wheel

It’s visible from the demo that stage and team components are similar in nature with couple of small differences. So, let’s focus on just one wheel of the bicycle.

The CodePen example below zooms in on just the three key ideas:

1. Fetch stage data;
2. Arrange spokes dynamically based on the data;
3. Re-arrange spokes when stage (spoke) is clicked.

See the Pen TDF Wheel Animation by Krutie (@krutie) on CodePen.

You may have noticed in the static SVG CodePen above that the spokes are nothing but SVG rectangles and text grouped together. I have grouped them together since I wanted to pick both text and rectangle for the purpose of animation.

<g v-for="stage in stages" class="stage">

    <rect x="249" y="250" width="215" height="1" stroke="#3F51B5" stroke-width="1"/>

    <text transform="translate(410 245)" fill="#3F51B5" >

      

    </text>

</g>

We will render them in <template> area of the Vue component using values fetched from the data-source.

When all 21 stages are available on screen, we’ll set their initial positions by calling, let’s say, setSpokes().

// setSpokes()

let stageSpokes = document.querySelectorAll(".stage")
let stageAngle = 360/this.stages.length

_.map(stageSpokes, (item, index) => {
    TweenMax.to(item, 2, 
    { rotation: stageAngle*index, 
      transformOrigin: "0% 100%"
    }, 1)
}

Three key elements of setting the stage are:

1. Rotation
   To rotate spokes, we’ll simply map through all elements with className stage, and set dynamic rotation value that is calculated for each spoke.
2. Transform Origin
   Notice transformOrigin value in the code above, which is as important as index value, because “0% 100%” enables each spoke to rotate from the center of the wheel.
3. stageAngle
   This is calculated using total number of stages divided by 360-degree. This will help us lay every spokes evenly in 360-degree circle.

ADDING INTERACTIVITY

Next step would be to add click-event on each stage to make it interactive and reactive to data changes  —  hence, it will breathe more life into an SVG image!

Let’s say, if stage/spoke is clicked, it executes goAnimate(), which is responsible to activate and rotate the stage being clicked using the stageId parameter.

goAnimate (stageId) {

  // activate stage id
  this.activeId = stageId

  // rotate spokes

}

We’ll use DirectionalRotationPlugin…which is a key ingredient for this interactivity. And yes, it is included in TweenMax.

There are three different ways of using this plugin. It animates rotation property in 1) clockwise, 2) counter-clockwise and 3) in the shortest distance calculated to the destination.

As you’d have guessed by now, we’re using the third option to rotate the shortest distance between the current stage and new stage.

Review the CodePen above and you’ll see how Stage 01 is constantly moving around the circle, leaving its original spot for new active stage at 0-degree angle.

First, we need to find the angle of a stage being clicked, and interchange its rotation with Stage 01. So, how do we find the rotation value of the stage being clicked? Check out the diagram below.

For example, if Stage 05 is clicked (as you can see above), the journey from Stage 01 to Stage 05  —  requires 4 x angle-value.

And therefore, we can get the correct angle using, (Active stage Id - 1) * 17 degree, followed by ‘_short’ string postfix to trigger directional rotation plugin.

angle = 360/21 stages = 17
activeId = 5
new angle = ((activeId-1)*angle)+'_short'
          = ((5-1)\*17)+'_short'
          = 68

The final goAnimate() function will look something like below:

_.map(spokes, (item, index) => {

  if(activeId == index+1) { 
    // active stage
    TweenMax.to(item, 2, 
    { rotation: 0+'_short', 
      transformOrigin: "0 100%"
    })   

  } else if (index == 0) { 
    // first stage
    TweenMax.to(item, 2,
    { rotation: (activeId*angle)-angle+'_short',
      transformOrigin: "0 100%"
    })

  } else {
    TweenMax.to(item, 2, 
    { rotation: index*angle+'_short', 
      transformOrigin: "0 100%"
    })
  }

}) // end of map

Once we have the rear wheel ready, the front wheel (for team) should follow the same logic with a couple of tweaks.

Instead of stage, we’ll fetch team data and update registration point of transformOrigin attribute to enable spokes generation from opposite registration point than the stage wheel.

// set team spokes

map(teamSpokes, (index, key) => {
  TweenMax.to(index, 2, 
  { rotation: angle*key, 
    transformOrigin: "100% 100%"
  }, 1)
})

Final Project

Like me, if you have written all animation and data related functions in Vue components itself. It’s time to clean them up using Vuex and Mixins.

VUEX

Vuex eases up the management of shared data among components, and more importantly, it streamlines your code, keeping methods and data() clean and tidy, leaving components only to render the data, not to handle it.

Lifecycle hooks are a very suitable place to perform any HTTP requests. We fetch initial data in created hook, when the Vue application has initialized, but hasn’t yet mounted into the DOM.

Empty state variables, stages and teams are updated using mutations at this stage. We then, use watcher (only once) to keep track of these two variables, and soon as they’re updated, we call in animation script (from mixin.js).

Every time user interacts with stage or team component, it will communicate with Vuex store, executes setActiveData, and updates current stage and current team values. That is how we set active data.

And when the active data is set after state update, goAnimate will kick in to animate (directional rotate) spokes using updated values.

Recommended reading: Creating Custom Inputs With Vue.js

Mixins

Now that the data is handled by Vuex, we’ll separate out GreenSock animations. This will prevent our Vue components being cluttered with long animation scripts. All GreenSock functions are grouped together in mixin.js file.

Since you have access to Vuex Store within Mixins, all GSAP functions use state variables to animate SVG elements. You can see fully functional store.js and mixin.js in the CodeSandbox example over here.

Conclusion

Creating interactive and engaging infographics requires you to be analytical with the data, creative with visuals and efficient with the technology you use, which in this case is Vue.js. You can further use these concepts in your project. As a closing note, I’ll leave you with this circular interactive color wheel below that uses an idea similar to the one we’ve discussed in this article.

See the Pen Material UI Circular Colour Palette made with Vue JS and GSAP by Krutie (@krutie) on CodePen.

With no doubt, Vue.js has many great features; we’re able to create interactive infographics with just a few things, such as watchers, computed properties, mixins, directive (see color-wheel example) and a few other methods. Vue.js is the glue that holds both SVG and GreenSock animation together efficiently, giving you ample of opportunity to be creative with any number of subject matter and custom interactivity at the same time.

As I wrote almost a year ago, every church should have one or more good guys with guns protecting the flock. Every synagogue, temple and mosque. Anyplace people gather to worship should have a ballistic response ready for the worst case scenario. Does yours have one? It should to improve church safety.

The first step in creating a safer house of worship involves recognizing that evil does exist. And that sometimes worldly evil will invade sacred locations. Only fools expect bad people to honor society’s norms in and outside of churches. Burying one’s head in the sand doesn’t keep anyone safe. Just ask the do-gooder couple who hiked through ISIS-controlled territory.

Some folks think that creating a security team for their church simply involves finding volunteers to carry guns to church services. Not so. While that’s better than nothing, when well-meaning people only have a hammer, every problem can ten to look like a nail.

Want to get a church security team off the ground in your house or worship? First off, get off on the right foot. Call it a “safety team.” Good word choice will help keep your flock from becoming alarmed. Most folks don’t want to think about the need for armed security in their church, but everyone can rally behind “safety.”

Once you have a team willing to do more than carry a gun, spend some money on good communications. Get radios. Issue them to ushers, greeters and security folks. Greeters and ushers can discretely report potential problems. In fact, your greeters stand as the congregation’s eyes and ears, evaluating everyone at the entry points as they welcome them at services. They will often identify potential problems first – including both security- and health-related issues.

Conversely, if security detects a problem and can communicate instantly, ushers and greeters can immediately help direct the flock away from that threat.

Surveillance cameras help too. Church congregations face a greater risk of criminal violence (robbery) in the parking lots than they do when sitting in the pews. Watching cameras can detect suspicious behavior from non-church members. In larger churches, roving patrols in cars or golf carts can go a long way to deter criminal activity.

Just like schools, churches should lock their doors shortly after services begin. A greeter can welcome latecomers at a locked door. However, why make it easy for a lunatic to invade the sanctuary at an unmanned, unlocked door when everyone’s attention is directed at the preacher?

Included in the safety plan: good first aid skills. Frankly, knowing some basic first aid and how to use an AED or perform CPR will likely save far more lives than that gun on the hip.

Frankly, safety team members should have good skills at de-escalating potential violence, too. Knowing the basics of talking people down while taking steps to lessen one’s personal risk help. And if the verbal judo fails, knowing some hands-on tactics can help quickly restrain troublemakers for police without the need for a full-on brawl.

Ideally, off-duty local law enforcement members of the congregation will join the team.

Lastly, those select safety team members with guns should face a vetting process with church leaders. Yes, while anyone legally able may should carry during a church service, safety team members represent the church to some degree. And the last thing any house of worship needs is an ill-trained, gun-toting “security team” member pulling a gun over a mildly-heated child custody dispute near the kids’ area during or after a service.

I still remember after the Sutherland Springs church shooting in Texas, people approached me asking about the legality of carrying without a license in church here in Illinois. God bless those Christians for volunteering.

On one hand, these well-meaning men and women expressed a willingness to protect their family and friends from bad people. On the other hand, they didn’t even know the law on carrying on private property in Illinois. Will they have a good handle on the nuances of deadly force law to keep themselves out of jail afterwards? I hope so, but I doubt it.

I would think some training on the legal use of deadly force is reasonable and prudent. Especially for those who wish to formalize their role providing security in their church.

While I’d prefer well-trained (and well-armed) gun owners in a time of trouble, I would eagerly welcome even any gun owner over a whole passel of hysterical Moms Demanding Action cowering under pews or desks. And you should too.

Stephen Willeford, pictured above, proved that in Sutherland Springs. Mr. Willeford didn’t have a background as a Navy SEAL or police officer. Instead, as John Q. Public, he courageously engaged a maniac and stopped the shooter’s attack at the nearby First Baptist Church. In fact, Willeford’s shots put down the murderous attacker, saving taxpayers the cost of incarcerating the killer.

If your church doesn’t have a safety team, take the initiative to start one. The life you save might be your own.