From now on the form module should be used and extended.

This removes the background and borders from the button.

These new styles include labels by default and error styles. It also
gives a little more breathing room between form elements.

The buttons now have a more consistent hover/active state without the
glossy highlight and the disabled state looks disabled.

Starting with the form elements, the new view is available at
/dev/pattern-library and currently only shows form fields.

Update Annotor's PDF plugin to 9acc6554 (typed-packaging).

Remove useless Annotator source maps. Fixes #1341.

This change was necessary to adapt to updates of the PDF.js version
shipped with newer FF releases.

There were three small changes. Our code now works with both
the old version (currently used with Chrome) and the old version
(embedded in FF).

Turn the standalone page into the app

Close #427
Close #754

Fix quirks with show/hide on the search bar

This is a small consistency improvement which ensures that whenever the
search is cleared the input becomes invisible. Previously, this only
worked correctly on the sidebar. Now, it works everywhere, including
when navigating using the back button to get to the unfiltered stream.

Isolate static assets in h:static

Drop the icomoon directory, saving only selection.json. The rest is not
needed, and is regenerated from the .json by the icomoon app.

Drop the font icon declarations in base.scss and use the css generated
by icomoon.

Move everything to h:static/fonts.

The icomoon css is not in styles because it has "fonts" as a relative
url, and we want "../fonts".

There are a number of reasons to isolate the static assets into their
own directory.

- An edge case in Pyramid: https://github.com/Pylons/pyramid/pull/1377
- Make serving them with a reverse proxy safer by ensuring that no code
  or configuration lives beneath the static directory
- Cleanliness

To avoid a big move happening shortly after this, also rename some of
the asset subdirectories to close #1317.

- js -> scripts
- css -> stylesheets
- lib -> scripts/vendor
- lib/images -> images
- browser/chrome/js/background.js -> browser/chrome/background.js
- browser/chrome/public/js/destroy.js -> browser/chrome/public/destroy.js

Finally, the locale directory was totally busted. The annotator.po file
included is the defualt locale, and it should have been .pot. Since it
includes only the default strings, there's no reason to serve it. I've
stripped it and we'll reinstate it correctly later.

Close #1311

374 sign in button firefox fix

If anyone doesn't like this, it's easy to revert, so it's going
straight to master.

Improve the usability and transitions of toolbar

Change the toolbar transitions, hover actions, and push states to
improve usability and feel.

- Animate from the right, so that all buttons enter as a group, so
  as to give them all equal "weight"
- Colorize the pushed buttons even when not hovering so it's easier
  to see which are active
- Further emphasize pushed state by "docking" them to the right
- Rework curves, delays, and durations for great beauty
- Show hidden buttons when hovering anywhere, not just the top

Close #1268

Turn Stream into App

- Vertically align the thread expander using ems and taking into
  account the size of the header it's aligned with.
- Fix excerpt bottom margin to match viewer
- Tuck the thread border under the content of the parent with a little
  extra padding
- Align the padding of the content class with card margins
- Rather than using a space character in the font icon styles, use the
  offset margin by choosing a sensible, non-zero default

Close #1290

Rather than having the annotator service handle the API service
discovery event, handle it in the app controller. That allows for
all the calls to add the Store plugin to be centralized in this
controller.

The `reloadAnnotations` function is modified so as not to assume
that a Store is already loaded, cleaning up only if one is. The
new store is placed on the scope so that its entities can be watched.

Rather than racing with the store, the updater is configured with
a new filter when the entities change. When the stream route is loaded,
these entities are empty, but the configured stream filter is sent
without re-initializing the filter. The stream search controller only
has to send a new filter if an updater is already open, otherwise it
is opened when the store is configured.

The patched `Store.loadAnnotations` is changed so that it creates a
fresh entities object on each invocation. This change ensures that if
provider frame disconnection is handled at some point the entities will
not continue to be included in searches and it makes the scope watcher
for this property very cheap.

Fixes #1306