adjustments to reveal.js initialization flow

This commit is contained in:
Hakim El Hattab
2020-03-10 18:37:37 +01:00
parent 9336fc11ca
commit ddbe06eb7e
4 changed files with 30 additions and 25 deletions

View File

@ -1,21 +1,16 @@
import Presentation from './reveal.js'
// The Reveal class can be instantiated to run multiple
// presentations on the same page
//
// let rvl = new Reveal( <HTMLElement>, { controls: false } )
// rvl.initialize()
// rvl.slide(2)
window.Reveal = Presentation;
// Simplified way to create a reveal.js instance on
// a page with only one presentation, makes us backwards
// compatible with reveal.js pre 4.0
// Provides a backwards compatible way to initialize
// reveal.js when there is only one presentation on
// the page.
//
// Reveal.initialize({ controls: false })
// Revea.slide(2)
window.Reveal.initialize = options => {
window.Reveal = new Presentation( document.querySelector( '.reveal' ), options );
window.Reveal.initialize();
return new Promise( resolve => window.Reveal.addEventListener( 'ready', resolve ) );
// Reveal.slide(2)
window.Reveal = {
initialize: options => {
window.Reveal = new Presentation( document.querySelector( '.reveal' ), options );
return window.Reveal.initialize();
}
}

View File

@ -153,7 +153,7 @@ export default function( revealElement, options ) {
// Load plugins then move on to #start()
plugins.load( config.dependencies ).then( start )
return Reveal;
return new Promise( resolve => Reveal.addEventListener( 'ready', resolve ) );
}