I've had to install and configure these things a few times, and I always forget how to do it, so here it is for posterity:
-
Update brew and install pandoc:
brew update brew install pandoc
-
Install mactex from https://www.tug.org/mactex/
I've had to install and configure these things a few times, and I always forget how to do it, so here it is for posterity:
Update brew and install pandoc:
brew update
brew install pandoc
Install mactex from https://www.tug.org/mactex/
This is a project for https://cartodb.github.io/hackarto.vl (2018, June 6th). The objective is to create a VIZ with CARTO.VL library to show AIR QUALITY in Madrid, using Madrid's OpenData
These were the main steps:
{ | |
"name": "webpack-sass", | |
"version": "1.0.0", | |
"scripts": { | |
"start": "webpack-dev-server --open --mode development", | |
"build": "webpack -p" | |
}, | |
"devDependencies": { | |
"babel-core": "^6.26.0", | |
"babel-loader": "^7.1.4", |
#Setting Up TinCan API with Moodle LMS and Learning Locker LRS
#Part 1: Virtual Container
Before we get our hands dirty with the entire setup, it is necessary to ensure we do not mess with the existing installation. Setting up and configuring a local server is tricky and may sometimes break your existing configuration rendering other programs which rely on it useless. So we will use LXC to create a virtual container, where we will do all good stuff. You can read the official LXC documentation here or a brief introduction about LXC here or get started right away with the commands below.
sudo apt-get install lxc lxd-client
sudo lxc-create -t download -n LMSprototype
Picking the right architecture = Picking the right battles + Managing trade-offs
date | num_customers | distinct_customers | total_bananas | total_revenue | revenue_per_sale | |
---|---|---|---|---|---|---|
2016-01-01 | 345 | 287 | 564 | 3689 | 6.54 | |
2016-01-02 | 364 | 299 | 582 | 4080 | 7.01 | |
... | ... | ... | ... | ... | ... |
All of the below properties or methods, when requested/called in JavaScript, will trigger the browser to synchronously calculate the style and layout*. This is also called reflow or layout thrashing, and is common performance bottleneck.
Generally, all APIs that synchronously provide layout metrics will trigger forced reflow / layout. Read on for additional cases and details.
elem.offsetLeft
, elem.offsetTop
, elem.offsetWidth
, elem.offsetHeight
, elem.offsetParent
#!/bin/bash | |
# Assume we have two semantic versions that we want to compare: | |
version1=0.12.0 | |
version2=1.15.5 | |
# First, we replace the dots by blank spaces, like this: | |
version1=${version1//./ } |
/** | |
* @desc Welsh Powell static graph coloring algorithm.. | |
* | |
* @author Misha M.-Kupriyanov https://google.com/+MishaMKupriyanov | |
* @link https://gist.github.com/printminion/a337eeb63ba232084dfc | |
*/ | |
//Source: https://github.com/graphstream/gs-algo/blob/master/src/org/graphstream/algorithm/coloring/WelshPowell.java | |
function WelshPowell() { |
Making the web accessible is important. We have ethical and, in some cases, legal obligations to ensuring access to all of users.
Luckily for us, it's easy to make an accessible Ember Component.
To understand the accessibility story around Ember Components, we have to start by talking about Web Components. Ember Components are designed to be interoperable with the final Web Components API.