| /** | |
| * Read Linux mouse(s) in node.js | |
| * Author: Marc Loehe (marcloehe@gmail.com) | |
| * | |
| * Adapted from Tim Caswell's nice solution to read a linux joystick | |
| * http://nodebits.org/linux-joystick | |
| * https://github.com/nodebits/linux-joystick | |
| */ | |
| var fs = require('fs'), |
| Latency Comparison Numbers (~2012) | |
| ---------------------------------- | |
| L1 cache reference 0.5 ns | |
| Branch mispredict 5 ns | |
| L2 cache reference 7 ns 14x L1 cache | |
| Mutex lock/unlock 25 ns | |
| Main memory reference 100 ns 20x L2 cache, 200x L1 cache | |
| Compress 1K bytes with Zippy 3,000 ns 3 us | |
| Send 1K bytes over 1 Gbps network 10,000 ns 10 us | |
| Read 4K randomly from SSD* 150,000 ns 150 us ~1GB/sec SSD |
rbackup is a lightweight, rsync-powered backup utility that creates time-stamped backups.
It can save backups to your local filesystem (probably an attached USB device) or to a remote host.
Backups are saved in time-stamped directories. Backups are cheap on storage, because hard-links are used for files that haven't changed between backups.
| import java.io.*; | |
| import java.nio.file.*; | |
| import java.security.*; | |
| import java.security.cert.*; | |
| import javax.net.ssl.*; | |
| import org.bouncycastle.jce.provider.*; | |
| import org.bouncycastle.openssl.*; | |
| public class SslUtil |
| // Just before switching jobs: | |
| // Add one of these. | |
| // Preferably into the same commit where you do a large merge. | |
| // | |
| // This started as a tweet with a joke of "C++ pro-tip: #define private public", | |
| // and then it quickly escalated into more and more evil suggestions. | |
| // I've tried to capture interesting suggestions here. | |
| // | |
| // Contributors: @r2d2rigo, @joeldevahl, @msinilo, @_Humus_, | |
| // @YuriyODonnell, @rygorous, @cmuratori, @mike_acton, @grumpygiant, |
| var firmata = require('firmata'); | |
| var repl = require('repl'); | |
| var board = new firmata.Board('/dev/ttyAMA0',function(err){ | |
| //arduino is ready to communicate | |
| if (err) { | |
| console.log("err:" + err); | |
| return; | |
| } | |
| console.log("Firmata Firing LEDs"); |
| #!/usr/bin/env python | |
| import gi | |
| import sys | |
| gi.require_version('Gst', '1.0') | |
| from gi.repository import GObject, Gst | |
| import cairo | |
| class Renderer(): | |
| OVERLAY_FRAME_WIDTH = 320 |
| require "lifx" # http://www.rubydoc.info/gems/lifx | |
| def calculate_color(i) # 0 <= i <= 1 | |
| h = [40 * 2 * i, 40].min # will be 40 (yellow) at i=1/2 and stay there | |
| s = 1.0 - [(i - 0.5) * 2, 0].max # will be 1 until i=1/2 and then go down to 0 | |
| b = i | |
| LIFX::Color.hsbk(h, s, b, LIFX::Color::KELVIN_MIN) | |
| end | |
| duration = 10 * 60 # seconds |
Controlling your nodebot using a USB cable is great and all, and obviously you could shell out and grab a sparkcore or some other dedicated controller but what if you've got a standard arduino and you want to take an existing nodebot wireless?
Bluetooth is an option and there's this excellent JohnnyFive wiki entry that will help you there. Bluetooth can be a bit flaky though and it's range is pretty lousy. You can also look at things like XBees and what not using point to point serial, but these are expensive and very fiddly to get working.
Really, what we want is a method of transferring data over a nice, simple, standard method, requiring little configuration, low cost and we can utilise a whole stack of the code we've already produced.
Enter the WiFi232 module. These little beauties are [available from AliExpress for $12 each](http://www.aliexpress.com/item/USR-WIFI232-T-wifi-to-uart-tt
| require 'rubygems' | |
| require 'logger' | |
| require 'sonos' | |
| require 'lifx' | |
| require 'matrix' | |
| SPEAKER = "Master Bedroom" | |
| LIFX_TAG = "Master Bedroom" | |
| LIFX_RETRIES = 3 |
