cherry-pick from merged set in GerHobbelt/master: updated README
cherry-pick from merged set in GerHobbelt/master: truly no jQuery required for nprogress.js so don't list it in component.json either
cherry-pick from merged set in GerHobbelt/master: no jQuery required for the example index.html either
cherry-pick from merged set in GerHobbelt/master: CSS absolute positioning + left+right=0 (see also commit SHA-1: b207cc798a66cc70a57f24218c57fb0a433654bb * Changed from width: 100% to right: 0 for the .bar)
cherry-pick from merged set in GerHobbelt/master: - fixed the queue logic so that NProgress.done() indeed *does* animate the 'done'; in other words: now you can invoke NProgress.set() multiple times in the same run and those will then be queued. (NProgress.done() executes NProgress.inc().set() and the second set() nuked the transition setup done by the first inc())
- NProgress.done(force, t) now accepts a text message as second parameter, just like NProgress.set() et al. It will show while the done animation progresses (during 2 * NProgress.settings.speed milliseconds...)

- NProgress.set() et all accept a message as second parameter: now, if that parameter is null or not specified at all, the previously set up message is kept intact. This simplifies your .set()/.inc() calls when you don't want to change the message with every progress update (see for example the example index.html: only .start() sets the 'Hello World...' message which is shown until .done() changes the message at the very end, despite several .inc() calls being issued in the mean time.
- index.html: the final fade-in of the page content is attached via NProgress.settings.onDoneBegin: this means the fade-in sequence will already start to happen while NProgress is still animating the hiding of the progress bar; use NProgress.settings.onDone instead if you want that one *completely* done before you do yours.

- introduced the callbacks NProgress.settings.onDoneBegin and NProgress.settings.onDone: these are fired when NProgress.done() completes (see also source code comments at NProgress.Settings)
SHA-1: d57bafb5bb2a75c7b2cd6cccc21d7c00f5eafe1c

- fixed the ultimate fallback using margins: it is no use manipulating the margin-left, but instead you have to animate the margin-right; this fallback behaviour is easily triggered via NProgress.settings.positionUsing = 0 (contrast this with NProgress.settings.positionUsing = '' which is the default)
SHA-1: d57bafb5bb2a75c7b2cd6cccc21d7c00f5eafe1c

- NProgress.render() would still produce CSS3 translate3D styling when your settings specifically request the use of the margin-right fallback rendering style: NProgress.settings.positionUsing = false or NProgress.settings.positionUsing = 0. (NProgress.render() simply did not use the internal barPositionCSS() function for rendering the relevant CSS.)
Merge branch 'piprog-master'

Conflicts:
	nprogress.css
ignore editor bak files