Scott J. Miles sjmiles

Using a polymorphic wrapper to forward bindings to an dynamic instance.

http://jsbin.com/noqiji/edit?html,output

Making paper-tab size fit it's content width

http://jsbin.com/bizoso/edit?html,output

Configuring themes in the main document, applying them inside the tree.

@sjmiles, 6/17/2015

... shooing away some flying monkeys ...

Attributes Use Dash-Case

First, when we use attributes in Polymer we always use dash-case for the name. In other words, we never write <x-foo coolSetting>, instead we always write <x-foo cool-setting>. This is true regardless of how we are going to use cool-setting, whether for styling, data binding, or whatever.

We do this because attributes in HTML are case-insensitive.

Howe: Was there something you wanted?

Woody: Well, uh, Miss Howe, I've been here at Cheers for quite a while now. I'm a good worker, I don't take vacations, I'm never sick, and I was just wondering if...

Howe: No, Woody, Woody, I'm going to have to stop you right there. I cannot give you a title.

Woody: "Title"?

Howe: Yes, I know you deserve it, but the front office just doesn't let me hand those things out.

Polymer Feedback

Things I've come accross that are unpleasant with polymer.

Template Binding

There is TemplateBinding which is standalone
It doesn't seem like a direct implementation of the template tag

The phrase explicit state comes up in discussions about component architecture. I find this an abstract concept, I'm guessing that it means there is a state object I can store/interrogate that contains the complete component state.

Forgiving for a moment the assumption that the state of the object is one thing (I suggest state is dependent on context), then it's true the DOM does not provide information in this format. It's also true that Web Components does not have anything to say on this point.

It's understandable that vendors of tools that want to consume state in this way would be happier if all DOM elements (and transitively all Custom Elements) produced such an object. Otherwise, there is an impedance mismatch with their particular flavor of application design.

IMO, there is a very similar issue with respect to dependency injection, where proponents want their particular inflection baked into the lowest level possible so they have maximum interoperability.

Again, such desires are understand

	// irand.html

	<script>
	modularize(function() {
	// whatever we return constitutes our `module`
	return function(n) {
	return Math.floor(Math.random() * n);
	}
	});
	</script>

	// index.html

	<!doctype html>

	<link href="sync-import.html" rel="import">
	<link async href="async-import.html" rel="import">

	<script>
	if (window.asyncImportHasExecuted) {
	alert('derp: async-import executed before body script');

	<link rel="import" href="../paper-form/paper-form.html">
	<link rel="import" href="../paper-form/paper-fields.html">

	<polymer-element name="my-element">

	<template>
	<style>
	:host {
	position: absolute;
	width: 100%;

	<!doctype html>
	<html lang="en">
	<head>

	<meta charset="UTF-8">
	<title>test-order-0</title>

	<style>
	body {
	background-color: orange;

	// Use Gists to store code you would like to remember later on
	console.log(window); // log the "window" object to the console