| // Wrapper function for native Omniture SiteCatalyst link tracking (s.tl()) | |
| var trackLink = function (referenceObject, trackingData, targetReportSuite) { | |
| if (typeof referenceObject === 'undefined' || typeof trackingData === 'undefined') { | |
| // If you're missing your settings object or any variables/events to fire, you fail | |
| return; | |
| } | |
| var linkTrackVarsArray = [], | |
| // Get values out of the configuration object | |
| tEvents = trackingData.events, // String || undefined | |
| tVars = trackingData.variables, // Object || undefined |
| /** | |
| * Pure-CSS Space Invader, adapted to a 2px pixel size from | |
| * the original example at CSS-Tricks "The Shapes of CSS" | |
| * | |
| * @link: http://css-tricks.com/examples/ShapesOfCSS/ | |
| */ | |
| .invader { | |
| box-shadow: | |
| -4px -2px white, 4px -2px white, |
| // Pass the plugin reference and configuration parameter ('text') to the embed script | |
| jwplayer('id-of-container').setup({ | |
| file: '/path/to/my/video.mp4', | |
| plugins: { | |
| '/path/to/overlay.js': { | |
| text: 'Text that you want to go within the overlayed banner' | |
| } | |
| } | |
| }); |
| function findTextNodes( node ) { | |
| var text = []; | |
| if ( node.nodeType === 3 ) { | |
| text.push( node.nodeValue ); | |
| // TODO: Filter out carriage returns, whitespace. | |
| // POSSIBLE TODO: Restrict to nodes within the main content area of the page? (so don't get ads, etc) | |
| } else { | |
| for ( var i = 0, max = node.childNodes.length; i < max; i++ ) { | |
| text = text.concat( findTextNodes( node.childNodes[i] ) ); | |
| } |
| (function() { | |
| var css = "*{font-family:\"Blokk Regular\", blokk !important;}", | |
| head = document.getElementsByTagName("head")[0], | |
| style = document.createElement("style"); | |
| style.type = "text/css"; | |
| if ( style.styleSheet ) { | |
| style.styleSheet.cssText = css; | |
| } else { | |
| style.appendChild( document.createTextNode( css ) ); | |
| } |
| "flight/utils", [] | |
| "flight/compose", [] | |
| "flight/advice", ["./utils", "./compose"] | |
| "flight/registry", ["./utils"] | |
| "flight/component", ["./advice", "./utils", "./compose", "./registry"] | |
| "data/with_client", [] | |
| "data/accounts", ["flight/component", "data/with_client"] | |
| "data/column_manager", ["flight/component"] | |
| "data/embed_tweet", ["flight/component", "data/with_client"] | |
| "util/with_version_comparator", [] |
| module.directive('myDirective', [ | |
| '$compile', | |
| '$location', | |
| 'Notify', | |
| 'sharedData', | |
| function( | |
| $compile, | |
| $location, | |
| Notify, | |
| sharedData |
If you thought Smash Mouth has a strong drink connotation, this band's just cheating: There's a delicious drink just sitting there waiting for you, called, appropriately, the
BUT there is some contention about what that is. The one I know is apparently
The Clover Club version
The core WordPress PHP files become cleaner and easier to read with every release, thanks in part to our strong standards for PHP code style. Our JavaScript, on the other hand, hasn't gotten nearly enough love. This post is intended to open up the recent discussion around JavaScript style to the greater community so we can make up for lost time.
Back in March, @tommcfarlin added a set of coding standards for JavaScript to the developer handbook. These WordPress JS coding standards were a great work-in-progress, but weren't fully comprehensive (leading to some comment threads clarifying various areas). More importantly, without any clear implementation plan the style guide failed to gain traction.
At WordCamp Boston's core
