Robin Böhm, Philipp Tarasiewicz
AngularJS: Overview, Best Practices and Pitfalls
Slides
Twitter (Robin, @roobijn)
Twitter (Philipp, @justphilmusic)
Christian Schaefer
HTTP/2: Die Zukunft beginnt jetzt.
Slides
Twitter (@derSchepp)
// @include font-face($style-name, $file, $family, $category); | |
// $style-name being the name of the font e.g. Helvetica | |
// $file meaning the file name, without the file extensions | |
// $family being the folder inside the fonts folder where the font files are | |
// $category is serif or sans-serif or monospace etc. as a fall back in CSS | |
// Here with real values: | |
// | |
// @include font-face('Ashbury', 'AshburyLig-webfont', 'Ashbury', 'serif'); | |
// use with iconmoon: https://icomoon.io/app/#/select/font |
Robin Böhm, Philipp Tarasiewicz
AngularJS: Overview, Best Practices and Pitfalls
Slides
Twitter (Robin, @roobijn)
Twitter (Philipp, @justphilmusic)
Christian Schaefer
HTTP/2: Die Zukunft beginnt jetzt.
Slides
Twitter (@derSchepp)
// 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' | |
}); | |
}); |
// not sure how to detect this yet, stay tuned or leave a comment | |
window.document._createElement = window.document.createElement; | |
window.document.createElement = function(name, attributes) { | |
if (typeOf attributes === 'string') { | |
// Chrome adds an undefined 'is' attribute for the second arg, why is this? | |
// Chrome is also throwing a TypeError for any third arg I can think of (number, string, object) | |
return window.document._createElement(arguments); | |
} else { | |
var elm = window.document._createElement(name); |
import android.content.Context; | |
import android.graphics.drawable.Drawable; | |
import android.os.Parcel; | |
import android.os.Parcelable; | |
import android.util.AttributeSet; | |
import android.view.MotionEvent; | |
import android.view.View; | |
import android.view.ViewGroup; | |
import android.widget.Checkable; | |
import android.widget.LinearLayout; |
var myPrototype = { | |
methodA: function methodA() {}, | |
methodB: function methodB() {}, | |
methodC: function methodC() {} | |
}; | |
createFoo = function createFoo() { | |
return (Object.create(myPrototype)); | |
}; |
Handlebars.registerHelper('loc', function(property, fn) { | |
var str; | |
// we are bound to a value, it is now the context | |
if (fn.contexts && typeof fn.contexts[0] === 'string') { | |
str = fn.contexts[0]; | |
// Convention, start all localization keys with _ | |
} else if (property[0] === '_') { | |
str = property; |
<!doctype html> | |
<html> | |
<head> | |
<meta charset="utf-8"> | |
<title>App Redirection</title> | |
</head> | |
<body> | |
<!-- | |
NOTE: This was a great hack in days gone by, but now both Apple and Google have improved their support for custom | |
protocol handlers. |