Creating a Twitter tweet box with Svelte

We will not be attempting to build all of these features in our version, I am even inclined to say that our version like most versions you find online are not really Twitter tweet box clones. They are something completely different. So the only feature we will be adding to ours is the Character count feature, but lets look into this even more.

What normally happen with the tweet box is that, as the user types, the character count become less, as the count gets below 21 we notice that the character counter becomes a red colour to highlight we are running low on characters. Now as we continue typing and our character count gets below 0, we start to notice that the actual text we are typing in the textarea now has a red background behind each character below 0. The red background behind the text is also something we won’t be tackling in this tutorial. Now as you can see, we (nor any of the other tutorials out there) are not really re-creating the Twitter tweet box as the title of the tutorial stated.

What we are really creating is a textarea that has a character counter and some flags that will decide when the submit button become active or not.

We can start off by creating our HTML and CSS in our single file component. But what do we need, we need an textarea, an button and a text placeholder of where out character counter will go.

This on its own doesn’t look like much by itself, I mean if you were to view that in a browser it wouldn’t look like much. Lets nice it up by adding some CSS.

Now we should have something looking more appealing. Yeah I know its definitely not the greatest design in the world, but its good enough to build our tweet box functionality on.

Now this will become hard to maintain over time, as you can see we are doing a lot of work inside the HTML code itself, what we should do is move most of this into the JavaScript blocks and figure out all of our computations there.

You can now see we are getting a clearer picture when we introduced one computed property, we can now move on to introducing more computed properties to almost rid the HTML code of all the JavaScript expressions.

What you will notice in some of the code is that we are calculating computed properties based upon another computed property. So this will ensure that when one computed property changes, it will trigger the others to change in an efficient way and it also stops us duplicating code like we were doing before when we had everything in the HTML template.

Related posts:

If you are a web programmer you may have thought about using a Content Management System ( CMS) before such a Wordpress or Joomla. But the lack of personalization and modularity in some of this CMS…

Looking to maximize your pumpkin harvest? With a few simple techniques and considerations, you can increase the quantity of pumpkins grown in your garden. From selecting the right varieties to…

I woke up the other morning and (thanks to photographer Austin Chan on Unsplash) I saw the sign. To quote Swedish pop group, Ace of Base, ‘it opened up my eyes’. After all, it was a neon sign…