pbojinov

Two way iframe communication

The main difference between the two pages is the method of sending messages. Recieving messages is the same in both.

Parent

Send messages to iframe using iframeEl.contentWindow.postMessage Recieve messages using window.addEventListener('message')

iframe

jmosbech

Webstorm and JSX

• make sure the WebStorm "Textmate bundles support" plugin is enabled
• download the Textmate bundle from https://github.com/andrespagella/JSX-TextMate-Bundle
• replace /Syntaxes/JSX.tmLanguage with this https://github.com/yungsters/sublime/blob/master/tmLanguage/JavaScript%20(JSX).tmLanguage (presumeably better?)
• add the textmate bundle to WebStorm
• make sure the *.jsx extension is handled by "Files supported via Textmate bundles"
• in case of color issues: you need to map your WebStorm scheme to a Textmate scheme. The Textmate color schemes are stored in .WebStorm7\config\plugins\textmate\lib\themes (on windows) and can be pruned to get rid of weird background artifacts

nkbt

{
	// -----------------
	// --------------------------------------------------------------------
	// JSHint Configuration, Strict Edition
	// --------------------------------------------------------------------
	//
	// This is a options template for [JSHint][1], using [JSHint example][2]
	// and [Ory Band's example][3] as basis and setting config values to
	// be most strict:
	//

nkbt

var loading = "\\|/—",
    tick = 0,
    loadingElement = document.createElement('div');

loadingElement.id = 'loading';
loadingElement.style.fontFamily = 'Consolas, "Liberation Mono", Courier, monospace';
document.body.innerHTML = '';
document.body.appendChild(loadingElement);
(function animate() {
    tick = (tick + 1) % loading.length;

listochkin

JavaScript Static Analysis Tools

Most people are familiar with these three tools:

1. [JSHint][1]
2. [JSLint][2]
3. [Google Closure Linter][3]

The first one is more popular among developers because it is style-agnostic. The other two enforce rules of [Crockford Style][4] and [Google Code Style][5] respectively.

aras-p

// 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,

klange

Since this is on Hacker News and reddit...

• No, I don't distribute my résumé like this. A friend of mine made a joke about me being the kind of person who would do this, so I did (the link on that page was added later). My actual résumé is a good bit crazier.
• I apologize for the use of _t in my types. I spend a lot of time at a level where I can do that; "reserved for system libraries? I am the system libraries".
• Since people kept complaining, I've fixed the assignments of string literals to non-const char *s.
• My use of type * name, however, is entirely intentional.
• If you're using an older compiler, you might have trouble with the anonymous unions and the designated initializers - I think gcc 4.4 requires some extra braces to get them working together. Anything reasonably recent should work fine. Clang and gcc (newer than 4.4, at le

piscisaureus

Locate the section for your github remote in the .git/config file. It looks like this:

[remote "origin"]
	fetch = +refs/heads/*:refs/remotes/origin/*
	url = git@github.com:joyent/node.git

Now add the line fetch = +refs/pull/*/head:refs/remotes/origin/pr/* to this section. Obviously, change the github url to match your project's URL. It ends up looking like this: