In a previous tutorial I explained how events can be implemented as properties on a class using Strongly Typed Events for TypeScript. Let’s explore how these work on interfaces. Interfaces work a little different, because they don’t have getters and setters on them (at least nog in TypeScript 1.8). Let’s explore how these work on interfaces.
As a C# programming I have a lot of interest in the TypeScript project. Lately I’ve been playing around with it to look what it can do. I found myself in need of some event handling, so I decided to build something that looks like the event handling .Net gives you.
Lately I’ve been playing around with some API’s. Most of them need a bunch of settings that I’m storing them in my config files. I found myself doing the same work over and over again: creating a settings class, filling the class with information and using it. So I came up with a way to leverage reflection to fill my setting classes with .config values.
Today we had a problem on the server: our app was causing the application pool to crash. Windows error reporting didn’t give a clear result of what was causing a stack overflow exception within the app. No stack-trace, no nothing. So how to solve a problem like this?
HTML is often easier to generate than SVG. Can it be converted to SVG? I’ve found a cloud service with an API that does a nice job converting various formats: CloudConvert. I ended up implementing a small part of their API to do the conversion.
I recently switched to WPExplorer’s Bogger Template, because it is simple and focused on the articles. What’s not to love? But there is still a lot to do to whip this template into shape. To help you out, I’ve created this post.
Many small applications need to store user credentials, but it’s hard to create a good username/password infrastructure. What if you could just use a small XML file with credentials that don’t actually stores the password, but just a hash and some salt.
For a small cloud project I ended up creating such a solution. This blog explains how to generate the credentials that can be stored in the XML. The aim is to make a solution that works on the client using JavaScript.
I like to browse the web using my computer, but I like to share the content with my friends on social platforms. Is this hard? Not with QR Codes and your mobile…
I noticed that the Time To First Byte (TTFB) of my website was taking way too long. First I thought it should be resolved by caching, but I noticed that it couldn’t be the caching, because TTFB kept being pretty high. After some research I found the culprit: IPv6 with the MySQL driver.
Recently I had the pleasure of building a calculator example exercise. Begin a good programmer I used the some HTML entities as values on the buttons: ×, ÷ and ± as values. It turned out to be quite difficult to parse them with native JavaScript. It is not so hard with LoDash or jQuery, but I wanted to do it native.