February and the first sunny days in 2021. What a delight! Have fun, sitting in the sun, discovering my newest finds on the web. This time, all regarding JavaScript…
github1s: One second to read GitHub code with VS Code
How to enhance fetch() with the Decorator Pattern
Ky - Delightful HTTP Requests
VS Code’s REST Client Plugin is All You Need to Make API Calls
json-view
You might not need jQuery
JavaScript Algorithms and Data Structures
date-fns - Modern JavaScript date utility library
Parsing Markdown into an Automated Table of Contents
In the project I’m currently working on, I faced the “problem” to integrate multilanguage support, but due to the fact that the new app should be written in vanilla JS, without any plugins, libraries or other dependencies, I had to develop my own localization layer. In this article I want to show you my approach on this…
How to test a local site on a mobile device and debug it locally
Developing a website or web app means, you have installed an editor locally on your computer, writing your code locally and start a tiny, built-in web server for debugging locally in your preferred browser. In most browsers, there are some features to mimic a smartphone, to see if your solution is working on such a device too, but you only get a hint if it’s running properly. Some mobile features like navigator.canShare do not work at all. Better is to see it live on your device.
This article will show you firstly, how to test your local solution on a smartphone and secondly, how to debug it locally, when it runs on the smartphone after releasing.
2020 is over and history. Well, may 2021 be with us. With this post I would like to continue the Discoveries, with new momentum. There was a lot to read over the holidays.
All the finds in this issue have something to do with visual aspects of web design in the broadest sense.
Drop-Shadow: The Underrated CSS Filter
css.gg - 700+ CSS Icons
SVGBox - API for Web Icons
Change Color of SVG on Hover
CSS filter generator to convert from black to target hex color
Depending on your design, sometimes it is nice to drop a shadow on an image to highlight it:
1
<imgsrc="my-image.jpg" />
1 2 3
img { box-shadow: 0px25px25px -10px#666; }
But … it looks like a paper print of the image, with a light bulb in the first third above it. The shade is grey, boring and has been used and seen many times before…
An design related Instagram post from Muhammad Abdull of thewilsonthings, inspired me to use the image itself as the shadow in order to make the image look a bit translucent. Should be the same technique as that of a reflection. Here is the HTML/CSS code for it, as the people asking for it in the comments.
Writing a Web App with HTML and JavaScript means you deal with several classes on your DOM elements in order to visualize state changes. And there are some pitfalls to be aware of with regard to removal.
Assuming you want to open some kind of sidebar above a container. In this sidebar you have several buttons to show different content via JavaScript and a close button, which closes the sidebar again. You HTML code maybe looks like this:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18
<html> <body> <divid="container">... Main Content ...</div>
By clicking on the open-sidebar button, the sidebar is opened and the action, respectively the new state, is vizualized by adding an appropriate class to the parent sidebar element. In order to make it easy for the user, the default content (Content 1) will be loaded also and its state will be marked with another class.
1
<asideclass="sidebar open open-content1">
A click on of the other content buttons (let’s say Content 2), will replace the current content and the aside classes will change into:
1
<asideclass="sidebar open open-content2">
Now we want to close the sidebar again, assuming that we don’t have stored the currently opened content in the JavaScript code…
For a new project I needed to have Node 14 running on my Windows 10 machine, so installation was done quickly via downloading and running the setup file.
A short time later I wanted to write a new blog post here on kiko.io, which depends on the Node.js based static site generator Hexo … and ran into several problems.
First of all my hero image processing script (see Automatic Header Images in Hexo) returned an exception. The script uses hexo-fs and the problem is known quite some time, according to this Github issue. The guys recommend to downgrade to an older version of Node.js … :(
Ok … I needed a solution to install multiple Node.js versions and switch between them, depending on which project I want to work on … and there is one: nvm-windows by Corey Butler!
I’m working on a new web app that contains a sliding out panel with some additional information on the selected element. This panel can be closed by the user via the ESC key. The implementation on initializing the panel seems very straight forward:
Problem is: the panel, which is part of the basic HTML, will be initialized with its content and functionality in a ES6 class. So … on every init, another event listener is added.
You can easily figure that out, by calling getEventListeners(document) in the Chrome DevTools: