pwittchen

1. Include Weather Icons in your app: https://github.com/erikflowers/weather-icons

2. Include the below JSON in your application, for example purposes, lets assume it's a global named weatherIcons.

3. Make a request to OpenWeatherMap:

req = $.getJSON('http://api.openweathermap.org/data/2.5/weather?q=London,uk&callback=?');

pwittchen

var process = require('child_process');
process.exec('ifconfig',function (err,stdout,stderr) {
    if (err) {
        console.log("\n"+stderr);
    } else {
        console.log(stdout);
    }
});

pwittchen

Reposted from Qiita

For almost a year now, I've been using this "flux" architecture to organize my React applications and to work on other people's projects, and its popularity has grown quite a lot, to the point where it shows up on job listings for React and a lot of people get confused about what it is.

Why I'm tired of using and teaching flux

There are a billion explainations on the internet, so I'll skip explaining the parts. Instead, let's cut to the chase -- the main parts I hate about flux are the Dispatcher and the Store's own updating mechanism.

If you use a setup similar to the examples in facebook/flux, and you use flux.Dispatcher, you probably have this kind of flow:

pwittchen

The Ultimate Git Alias Setup

If you use git on the command-line, you'll eventually find yourself wanting aliases for your most commonly-used commands. It's incredibly useful to be able to explore your repos with only a few keystrokes that eventually get hardcoded into muscle memory.

Some people don't add aliases because they don't want to have to adjust to not having them on a remote server. Personally, I find that having aliases doesn't mean I that forget the underlying commands, and aliases provide such a massive improvement to my workflow that it would be crazy not to have them.

The simplest way to add an alias for a specific git command is to use a standard bash alias.

# .bashrc

pwittchen

Observable React elements with RxJS

Note: if you want to skip history behind this, and just looking for final result see: rx-react-container

When I just started using RxJS with React, I was subscribing to observables in componentDidMount and disposing subscriptions at componentWillUnmount.

But, soon I realised that it is not fun to do all that subscriptions(that are just updating property in component state) manually, and written mixin for this...

Later I have rewritten it as "high order component" and added possibility to pass also obsarvers that will receive events from component.

pwittchen

import sys
import ply.yacc as yacc
import ply.lex as lex

tokens = (
    'INCREMENT',
    'DECREMENT',
    'SHIFT_LEFT',
    'SHIFT_RIGHT',
    'OUTPUT',

pwittchen

ifconfig | grep inet | awk 'END{print}' | awk '{print $2}'

pwittchen

for(final Annotation annotation : this.getClass().getAnnotations()) {
 final Class<? extends Annotation> annotationType = annotation.annotationType();
 final boolean classIsAnnotated = annotationType.equals(MyCustomAnnotation.class);
}

pwittchen

  __         __    _           _          _
 / / __   __ \ \  | |__  _   _| |__  _ __(_)___
| |  \ \ / /  | | | '_ \| | | | '_ \| '__| / __|
| |   \ V /   | | | | | | |_| | |_) | |  | \__ \
| |    \ \    | | |_| |_|\__, |_.__/|_|  |_|___/
 \_\    \_\  /_/        |___/

pwittchen

ps aux | grep outlook | awk '{print $2}' | xargs kill -9