Using the latest Uglify JS with --no-seqs and deleting 'use strict' statement for use in production.

Conflicts:
	js/reveal.min.js

Need to generate a new minified version afterwards.

Its was impossible (at least for me) to keep the windows in sync without bloating the code too much.

Using the latest Uglify JS with --no-seqs and deleting 'use strict' statement for use in production.

Change source from reveal.min.js to reveal.js for testing purposes.

Add nextFragment and previousFragment to the API:
Making it possible to call the methods Reveal.nextFragment()
and Reveal.previousFragment() from »outside«.

Update README.md:
Add the new API Methods Reveal.prevFragment() and Reveal.nextFragment()

Adding info about the fullscreen mode to README.md

Add info about the fullscreen mode

Using the latest Uglify JS with --no-seqs and deleting 'use strict' statement for use in production.

See b957d0b8

Add the new API Methods Reveal.prevFragment() and Reveal.nextFragment()

Because of consistency with the existent methods Reveal.prev() and Reveal.next()

Might be better to use one variable with different values.

And emit 'fragmentchanged' with the appropriate fragmentData to show or hide fragments.