| function mapValues(obj, fn) { | |
| return Object.keys(obj).reduce((result, key) => { | |
| result[key] = fn(obj[key], key); | |
| return result; | |
| }, {}); | |
| } | |
| function pick(obj, fn) { | |
| return Object.keys(obj).reduce((result, key) => { | |
| if (fn(obj[key])) { |
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
| DO WHAT THE FUCK YOU WANT TO PUBLIC LICENSE Version 2, December 2004 | |
| (http://www.wtfpl.net/about/) | |
| Copyright (C) 2015 Mario Mendes (@hyprstack) | |
| Copyright (C) 2015 Ivan Fraixedes (https://ivan.fraixed.es) | |
| Everyone is permitted to copy and distribute verbatim or modified | |
| copies of this license document, and changing it is allowed as long | |
| as the name is changed. |
| package com.ryanharter.mediaroute.widgets; | |
| import android.content.Context; | |
| import android.support.v7.app.MediaRouteActionProvider; | |
| import android.support.v7.app.MediaRouteButton; | |
| /** | |
| * A MediaRouteActionProvider that allows the use of a ThemeableMediaRouteButton. | |
| */ | |
| public class ThemeableMediaRouteActionProvider extends MediaRouteActionProvider { |
| Bitmap batmapBitmap = BitmapFactory.decodeResource(getResources(), R.drawable.batman); | |
| RoundedBitmapDrawable circularBitmapDrawable = RoundedBitmapDrawableFactory.create(getResources(), batmapBitmap); | |
| // option 1 h/t [Chris Banes](https://chris.banes.me/) | |
| circularBitmapDrawable.setCornerRadius(batmapBitmap.getWidth()); | |
| // option 2 h/t @csorgod in the comments | |
| circularBitmapDrawable.setCircular(true); | |
2015-01-29 Unofficial Relay FAQ
Compilation of questions and answers about Relay from React.js Conf.
Disclaimer: I work on Relay at Facebook. Relay is a complex system on which we're iterating aggressively. I'll do my best here to provide accurate, useful answers, but the details are subject to change. I may also be wrong. Feedback and additional questions are welcome.
Relay is a new framework from Facebook that provides data-fetching functionality for React applications. It was announced at React.js Conf (January 2015).
| /** | |
| * Example webpack.config.js for an AMD project (or AMD + CJS mixed project). | |
| * This file should be at the root of your project. | |
| * | |
| * This can then be used in combination with Karma as well | |
| * Just load this file and pass it to karma.webpack key | |
| * (see https://github.com/webpack/karma-webpack#alternative-usage) | |
| * | |
| * This example is a bit extreme. Typically in webpack, you don't need much | |
| * configuration if you have nicely behaving code and work with correctly |
These instructions will guide you through the process of setting up local, trusted websites on your own computer.
These instructions are intended to be used on macOS Sierra, but they have been known to work in El Capitan, Yosemite, Mavericks, and Mountain Lion.
NOTE: You may substitute the edit command for nano, vim, or whatever the editor of your choice is. Personally, I forward the edit command to Sublime Text:
alias edit="/Applications/Sublime\ Text.app/Contents/SharedSupport/bin/subl"
(by @andrestaltz)
If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.
Recently, I've been working on a Smart TV application targeted at both LG and Samsung models. I had problems keeping the main code platform independent because the key codes on events generated by the remote controls differed between the vendors. While LG's remote control keys generated fairly sane codes, Samsung's didn't, with the codes for numeric keys seeming completely random (for example, the numeric key 1 has the key code 101, but 5 has 9).
I eventually decided to polyfill KeyboardEvent.key, and allow passing a map to the polyfill so that the platform-dependent code could define their own keysets.
The property exposes itself on both the KeyEvent (non-standard) and KeyboardEvent (standard) objects and is ideal for use in specific, targeted environments.