thomaswilburn

#include QMK_KEYBOARD_H

enum ctrl_keycodes {
    L_BRI = SAFE_RANGE, //LED Brightness Increase                                   //Working
    L_BRD,              //LED Brightness Decrease                                   //Working
    L_EDG_I,            //LED Edge Brightness Increase
    L_EDG_D,            //LED Edge Brightness Decrease
    L_EDG_M,            //LED Edge lighting mode
    L_PTN,              //LED Pattern Select Next                                   //Working
    L_PTP,              //LED Pattern Select Previous                               //Working

thomaswilburn

Reading lit-html

I've been interested in lit-html for a while now: it's an HTML templating solution that doesn't require a build step like JSX, uses standard JavaScript tagged literals for its syntax, and claims to selectively update the DOM without a V-DOM. At 8KB minified, it's also reasonably-sized--not quite as tiny as my go-to dot.js micromodule, but the functionality is much higher.

In the past, reading through library code has been one of the ways that I got better at development. I remember Paul Irish's classic "10 things I learned from reading the jQuery source" video, which had inspired me to do my own spelunking back in the day. Figuring out how jQuery, D3, and Backbone translated high-level function calls into the low-level browser API taught me a lot, and I figured lit-html would be a similar chance to learn something new.

I was right! It turns out, there's a lot going on under the hood of lit-html. Even better, much of it is built on top of platform features, as opposed to pure JS abstracti

thomaswilburn

set -x
set -e

mkdir -p output

cd original
for f in *.jpg; do
  # first image in the stack is the base image
  convert $f \
    # second image is the same thing, but with dilate/erode applied to remove thin lines (i.e., text)

thomaswilburn

Using <custom-elements> in production

Who am I?

• Thomas Wilburn
• News Developer at the Seattle Times
• @thomaswilburn on Twitter, GitHub

thomaswilburn

<style>
:host {
  width: 300px;
  height: 150px;
  display: block;
  position: relative;
}

canvas {
  position: absolute;

thomaswilburn

var presets = {
  starting: {
    r: 55,
    efficacy: 95,
    immunity: 0
  },
  baseline: {
    immunity: 0
  },
  lowImmunity: {

thomaswilburn

/*

Register functions to be notified if a specific selector matches (or stops matching)

*/

var watchList = new Map();

var glance = function(watch) {
  var result = document.querySelector(watch.selector);

thomaswilburn

var ElementBase = require("../elementBase.js");
var Retriever = require("../retriever.js");

/*
Let's make a web component the elections20-primaries way! We're going to start by 
subclassing our base element, since it makes the setup a little more declarative. 
You'll see how that works in a minute.
*/
class DemoElement extends ElementBase {

thomaswilburn

Sub GetMessages()
  readdir "folder_location"
End Sub

Sub readdir(folderName As String)
  Dim fs As Scripting.FileSystemObject
  Dim folder As Scripting.folder
  Dim file As Scripting.file
  Dim message As Object
  

thomaswilburn

Set ShellApp = CreateObject("Shell.Application")
Set FSO = CreateObject("Scripting.FileSystemObject")

homeFolder = ShellApp.NameSpace(&H28).Self.Path

PinnedPath = homeFolder & "\AppData\Roaming\Microsoft\Internet Explorer\Quick Launch\User Pinned\TaskBar"

Set PinnedNS = ShellApp.NameSpace(PinnedPath)
Set PinnedFolder = FSO.GetFolder(PinnedPath)
Set PinnedFiles = PinnedFolder.Files