| import urllib2 | |
| import re | |
| import sys | |
| from collections import defaultdict | |
| from random import random | |
| """ | |
| PLEASE DO NOT RUN THIS QUOTED CODE FOR THE SAKE OF daemonology's SERVER, IT IS | |
| NOT MY SERVER AND I FEEL BAD FOR ABUSING IT. JUST GET THE RESULTS OF THE | |
| CRAWL HERE: http://pastebin.com/raw.php?i=nqpsnTtW AND SAVE THEM TO "archive.txt" |
When the directory structure of your Node.js application (not library!) has some depth, you end up with a lot of annoying relative paths in your require calls like:
const Article = require('../../../../app/models/article');Those suck for maintenance and they're ugly.
| // this is the background code... | |
| // listen for our browerAction to be clicked | |
| chrome.browserAction.onClicked.addListener(function (tab) { | |
| // for the current tab, inject the "inject.js" file & execute it | |
| chrome.tabs.executeScript(tab.ib, { | |
| file: 'inject.js' | |
| }); | |
| }); |
You're probably getting this warning because you're accessing methods on a component before it gets mounted. This will be soon be an unsupported use case.
The component that gets created by invoking the convenience constructor MyComponent(props, children) or using the JSX syntax <MyComponent /> is not guaranteed to be the instance that actually gets mounted. It's a description of what the actual mounted instance should look like.
Anti-pattern:
The component also doesn't have access to state or other important information such as the final props. As a consequence you shouldn't be calling custom methods on this object.
var MyComponent = React.createClass({
| var _ = require('underscore'); | |
| var Backbone = require('backbone'); | |
| var cheerio = require('cheerio'); | |
| var request = require('request'); | |
| Backbone.ajax = function(options) { | |
| options.json = true; | |
| return request(options, function(error, result) { | |
| if (error) { |
| //demo: http://jsfiddle.net/heZ4z/ | |
| if (document.addEventListener) { // standard | |
| document.addEventListener('click', function onclick(e) { | |
| var r; | |
| if (document.caretRangeFromPoint) { // standard (WebKit) | |
| r = document.caretRangeFromPoint(e.pageX, e.pageY); | |
| } else if (e.rangeParent) { // Mozilla | |
| r = document.createRange(); |
| /* | |
| * How to detect which element is the scrolling element in charge of scrolling the viewport: | |
| * | |
| * - in Quirks mode the scrolling element is the "body" | |
| * - in Standard mode the scrolling element is the "documentElement" | |
| * | |
| * webkit based browsers always use the "body" element, disrespectful of the specifications: | |
| * | |
| * http://dev.w3.org/csswg/cssom-view/#dom-element-scrolltop | |
| * |
Custom recipe to get OS X 10.10 Yosemite running from scratch, setup applications and developer environment. I use this gist to keep track of the important software and steps required to have a functioning system after a semi-annual fresh install. On average, I reinstall each computer from scratch every 6 months, and I do not perform upgrades between distros.
This keeps the system performing at top speeds, clean of trojans, spyware, and ensures that I maintain good organizational practices for my content and backups. I highly recommend this.
You are encouraged to fork this and modify it to your heart's content to match your own needs.
Disclaimer: This is an unofficial post by a random person from the community. I am not an official representative of io.js. Want to ask a question? open an issue on the node-forward discussions repo
| brew update | |
| brew link yasm | |
| brew link x264 | |
| brew link lame | |
| brew link xvid | |
| brew install ffmpeg | |
| ffmpeg wiki: | |
| https://trac.ffmpeg.org/wiki/Encode/MP3 |
