Polymer Web Components Tutorial
For all the front-end developers who just started to feel comfortable with last week's tools, it was recently announced at Google I/O that Google's Polymer version 1.0 is about to modernize your perception of the "widget." Known as Web Components, Polymer streamlines the process of implementing the Web Component standard and adds cross-browser support that makes Polymer just about production ready.To give a better example as to why Polymer and Web Components are so great, I'll take you through building a photo stream component using the API from our GIF photo booth app, Gifn, and explain each part as we go along.
A step-by-step tutorial
To start, create a new folder in the command line using:mkdir polymer_tutorialAnd then enter the folder using:cd polymer_tutorialTo install Polymer, we are going to use Bower, which is a package management tool for JavaScript. If you do not have Bower installed you can do so with:npm install -g bowerand then initialize Bower.bower initFrom there, follow the tool's prompts. If you're not sure how to answer a question, just push enter and use the default option. After Bower initializes, it should place a bower.json file in your directory. To add Polymer as a dependency, run this command:bower install --save Polymer/polymer#^1.0.0You should now have a bower_components/ folder in your directory that contains Polymer and its dependencies. Now, add two files to your root directory: an index.html file and a gifn-feed.html file that will contain your Polymer component. Your directory should now look something like this:polymer_tutorial/First, let's open up the index.html file and set up our HTML to display the Polymer component. Here is all of the HTML needed to use a simple component.
bower_components/
bower.json
gifn-feed.html
index.html<!doctype html>There are three main parts to initializing the component in your index.html file. First you need to add the webcomponents library:
<html>
<head>
<title>Gifn Polymer</title>
<script src="bower_components/webcomponentsjs/webcomponents.min.js"></script>
<link rel="import" href="gifn-feed.html">
</head>
<body>
<gifn-feed event="prplhq"></gifn-feed>
</body>
</html><script src="bower_components/webcomponentsjs/webcomponents.min.js"></script>This library is required for all Polymer components and any custom components you create yourself. There is also a smaller webcomponents-lite.min.js library that can be used in replacement, if you are only building elements for browsers that currently support the Web Components API (Chrome 36+, for example). Next is the link tag importing our gifn-feed web component to be used.<link rel="import" href="gifn-feed.html">And then our actual web component in use:<gifn-feed event="prplhq"></gifn-feed>Everything looks pretty normal, except for the actual web component. The gifn-feed element is obviously not your normal HTML, and event="prplhq" is not an attribute you would expect, either. Fear not, this will all make sense once we start fleshing out the component.Let's get started. First, open up the gifn-feed.html file and add the required base Polymer element at the top of your file:<link rel="import" href="bower_components/polymer/polymer.html">One of the cool aspects about Polymer is that it allows you to import and extend elements in a very modular way. Outside of the required base polymer.html you could also import iron-ajax.html for easy Ajax calls or even a material design button with paper-button.html. You can check out some ready-to-use components Google has created.Since gifn-feed is going to be used in our HTML, we are going to initialize it as a DOM module like so:<dom-module id="gifn-feed">Now, for the fun part! Let's initialize the Polymer component with the base setup inside a script tag.
</dom-module><dom-module id="gifn-feed"> <script>The "is:" attribute tells Polymer to look for an element with the tag gifn-feed and the "properties:" attribute tells Polymer to look for an "event" attribute that will have a string value.Our web component still does nothing, it's simply initialized. To add an action to the component, you can use one of the lifecycle callbacks, or in our case, use the "ready" callback for when our component's DOM has been initialized. Here is the gifn-feed component with the "ready" callback.
Polymer({
is: "gifn-feed", properties: {
event: String
}
});
</script></dom-module><dom-module id="gifn-feed">What we are doing in this ready function is making an Ajax request to the Gifn API to retrieve a list of GIF images. We then build out the URLs and place them in an array that is set to our Polymer object. Let me explain some of the more important aspects.
<script>
Polymer({
is: "gifn-feed", properties: {
event: String
}, ready: function() {
var self = this;
var xhr = new XMLHttpRequest();
var baseUrl = 'http://demo.gifn.it';
self.gifns = []; // Send an ajax request to get the gif data
xhr.open('GET', baseUrl + '/gif/' + self.event);
xhr.send();
xhr.onreadystatechange = function() { if(xhr.readyState == 4 && xhr.status == 200){
var gifns = [];
var response = JSON.parse(xhr.responseText); //Build out the urls for the 5 latest gifs
for(var i = 0; i < 5; i++){
var gifUrl = baseUrl+'/asset/'+self.event +'/'+ response.gifs[i].slug+'.thumb.gif';
gifns.push({ url: gifUrl });
} self.gifns = gifns;
}
}
}
});
</script></dom-module>var self = this;Although this is a common practice for dealing with internal scope in JavaScript functions, it's especially important to have access to the parent Polymer object so you can bind data to the view. Here's an example of it being used:xhr.open('GET', baseUrl + '/gif/' + self.event);This line is responsible for initializing the Ajax request to our API, but self.event is what makes it truly special. Remember the event="prplhq" attribute on our gifn-feed tag? It is now directly bound to our Polymer object for use in the JavaScript, HTML template, and even in our component's CSS. Here's another example:self.gifns = gifns;This time, instead of taking a value from our component's element attribute, we are creating an array of URLs inside the component that can then be used throughout. Polymer is flexible in that it allows for both one-way and two-way data binding.Now that we have our data set, let's create the view for our component. Above our script tag, add<template>This is the base template tag required for all views. Inside of the template tag you can add HTML, other imported Polymer web components, and even some special helper elements used for if-statements and looping through data. Since we have an array of URLs, let's add a dom-repeat helper tag.
</template><template>Notice the {{gifns}} value in the items tag? This is how you directly access attributes bound to your Polymer object. So if you wanted to, you could also add a title for the event, like so:
<template is="dom-repeat" items="{{gifns}}">
<img src="{{item.url}}" />
</template>
</template><h1>{{event}}</h1>In the case of the special dom-repeat element, it requires an "items" attribute that references an array value. The dom-repeat element will then loop through the array with each value being accessed using the "item" variable.After seeing the completed view, some of you may be wondering why I chose to make this string concatenation mess in the ready function.for(var i = 0; i < 5; i++){You all would probably agree this is the better and cleaner option.
var gifUrl = baseUrl + '/asset/' + self.event + '/' + response.gifs[i].slug + '.thumb.gif';
gifns.push({ url: gifUrl });
}<template is="dom-repeat" items="{{gifns}}">However, this is currently not possible, and is probably one of the biggest downfalls of the template builder in Polymer 1.0. String concatenation and whitespace with view variables is currently not supported in Polymer. Each element must take up the entire space of a view's element or the entire space of a string in an attribute.For example, this will work:
<img src="https://demo.gifn.it/asset/{{event}}/{{item.slug}}.thumb.gif" />
</template><h1>Welcome <span>{{name}}</span></h1>but this will not:<h1>Welcome {{name}}</h1>To finalize the view, we'll add a touch of CSS to our component to make everything a little more fancy. Let's add this style block above our template tags.<style>Alright, maybe not that fancy, but I really hate floats. Another great feature of Polymer is that it keeps your component's CSS local, so you do not need to worry about conflicting CSS rules.And that's it! Here is the polymer component in its entirety.
img {
display:inline-block;
}
</style><link rel="import" href="bower_components/polymer/polymer.html"><dom-module id="gifn-feed">To view your Polymer component, you will need to host it through some type of server. This could be a local server, Vagrant box, MAMP, or one of my quick command line favoritespython -m SimpleHTTPServerEnjoy!A working demo can be seen at http://polymer.gifn.it, and all of the source code can be viewed on my GitHub at https://github.com/adamboerema/polymertutorial.For further documentation, check out:
<style>
img {
display:inline-block;
}
</style> <template>
<template is="dom-repeat" items="{{gifns}}">
<img src="{{item.url}}" />
</template>
</template> <script>
Polymer({
is: "gifn-feed",
properties: {
event: String
},
ready: function() { var self = this;
var xhr = new XMLHttpRequest();
var baseUrl = 'http://demo.gifn.it';
self.gifns = []; // Send an ajax request to get the gif data
xhr.open('GET', baseUrl + '/gif/' + self.event);
xhr.send();
xhr.onreadystatechange = function() {
if(xhr.readyState == 4 && xhr.status == 200){ var gifns = [];
var response = JSON.parse(xhr.responseText); //Build out the urls for the 5 latest gifs
for(var i = 0; i < 5; i++){
var gifUrl = baseUrl+'/asset/'+self.event+'/'+response.gifs[i].slug+'.thumb.gif';
gifns.push({ url: gifUrl });
} // Bind the response back to the {{gifns}} repeater
self.gifns = gifns;
}
}
}
});
</script>
</dom-module>
- https://www.polymer-project.org/1.0/
- http://webcomponents.org/
.webp)