https://github.com/jswrenn/google-book

A polymer element wrapping the Google Books Embedded Viewer API
https://github.com/jswrenn/google-book

Last synced: about 1 month ago
JSON representation

A polymer element wrapping the Google Books Embedded Viewer API

• Host: GitHub
• URL: https://github.com/jswrenn/google-book
• Owner: jswrenn
• Created: 2015-11-23T23:21:14.000Z (about 9 years ago)
• Default Branch: master
• Last Pushed: 2015-11-23T23:47:13.000Z (about 9 years ago)
• Last Synced: 2024-10-14T16:47:26.971Z (3 months ago)
• Language: HTML
• Size: 2.12 MB
• Stars: 0
• Watchers: 3
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# Google Book 

Built upon the seed-element starter kit for creating reusable Polymer elements. Seed-Element readme left intact for my own reference:

An element providing a starting point for your own reusable Polymer elements.

## Dependencies

Element dependencies are managed via [Bower](http://bower.io/). You can

install that via:

    npm install -g bower

Then, go ahead and download the element's dependencies:

    bower install

## Playing With Your Element

If you wish to work on your element in isolation, we recommend that you use

[Polyserve](https://github.com/PolymerLabs/polyserve) to keep your element's

bower dependencies in line. You can install it via:

    npm install -g polyserve

And you can run it via:

    polyserve

Once running, you can preview your element at

`http://localhost:8080/components/seed-element/`, where `seed-element` is the name of the directory containing it.

## Testing Your Element

Simply navigate to the `/test` directory of your element to run its tests. If

you are using Polyserve: `http://localhost:8080/components/seed-element/test/`

### web-component-tester

The tests are compatible with [web-component-tester](https://github.com/Polymer/web-component-tester).

Install it via:

    npm install -g web-component-tester

Then, you can run your tests on _all_ of your local browsers via:

    wct

#### WCT Tips

`wct -l chrome` will only run tests in chrome.

`wct -p` will keep the browsers alive after test runs (refresh to re-run).

`wct test/some-file.html` will test only the files you specify.