| // Live video stream management for HTML5 video. Uses FFMPEG to connect to H.264 camera stream, | |
| // Camera stream is remuxed to a MP4 stream for HTML5 video compatibility and segments are recorded for later playback | |
| var liveStream = function (req, resp) { // handle each client request by instantiating a new FFMPEG instance | |
| // For live streaming, create a fragmented MP4 file with empty moov (no seeking possible). | |
| var reqUrl = url.parse(req.url, true) | |
| var cameraName = typeof reqUrl.pathname === "string" ? reqUrl.pathname.substring(1) : undefined; | |
| if (cameraName) { | |
| try { | |
| cameraName = decodeURIComponent(cameraName); |
| # Compiled source # | |
| ################### | |
| *.com | |
| *.class | |
| *.dll | |
| *.exe | |
| *.o | |
| *.so | |
| # Packages # |
| application:open-your-keymap | |
| application:open-your-stylesheet | |
| autocomplete:attach | |
| autoflow:reflow-paragraph | |
| bookmarks:clear-bookmarks | |
| bookmarks:jump-to-next-bookmark | |
| bookmarks:jump-to-previous-bookmark | |
| bookmarks:toggle-bookmark | |
| bookmarks:view-all | |
| check:correct-misspelling |
Suppose you have an array of complex data that you wish you filter. The property to filter upon is bound to the value of a text input field.
By default, this means that every keystroke will result in the filter being computed and (that particular section of) the template re-rendered.
However, let's say we do not want this to happen, as we deem it to be too expensive. _.throttle combined with Ember observes using an property on a controller as an intermediary, makes this possible.
I was tired of Chrome eating all my laptop resources so I decided to put some limit to it with cgroup.
As I was using Ubuntu 12.04 with support for cgroup, I installed the package cgroup-bin and add the following group to the file /etc/cgconfig.conf:
group browsers {
cpu {
# Set the relative share of CPU resources equal to 25%
cpu.shares = "256";
}
| Ember.Handlebars.helper('math', function(operand1, operator, operand2) { | |
| var result; | |
| switch (operator) { | |
| case '+': | |
| result = operand1 + operand2; | |
| break; | |
| case '-': | |
| result = operand1 - operand2; |
I have moved this over to the Tech Interview Cheat Sheet Repo and has been expanded and even has code challenges you can run and practice against!
\
This is part of a series of examples that describe the basic operation of the D3.js force layout. Eventually they may end up in a blog post that wraps everything together. If you missed the beginning of the series, here's a link to first example.
The previous example
shows how linkDistance tells the force layout the desired distance
between connected nodes. It may seem strange that D3 doesn't simply
compel all links to be that distance. The force layout, however, takes
| // | |
| // Swift-KVO | |
| // | |
| // Created by Jim Correia on 6/5/14. | |
| // Copyright (c) 2014-2015 Jim Correia. All rights reserved. | |
| // | |
| // Update: 6/17/2014 | |
| // | |
| // KVOContext has gone away; use the same idiom you'd use from Objective-C for the context | |
| // |
| import itertools | |
| import string | |
| import re | |
| class PhraseMatcher(object): | |
| ACTIONS = [] | |
| WORDS = {} | |
| @classmethod | |
| def get_possible_phrases(cls): | |
| # Sample implementation, there might be a better one |
