aboutsummaryrefslogtreecommitdiff
path: root/plugin
Commit message (Collapse)AuthorAge
* escape HTML entities in code parsed from markdown, fixes #2744Hakim El Hattab2020-09-09
|
* dependency upgradesHakim El Hattab2020-08-19
|
* add support for wrapping code in script tempalte to avoid html parser #2684Hakim El Hattab2020-06-05
|
* export the highlight.js instanceHakim El Hattab2020-05-27
|
* fix polyfills, add ie11 supportHakim El Hattab2020-05-26
|
* update dependenciesHakim El Hattab2020-05-19
|
* reveal.netlify.app -> revealjs.comHakim El Hattab2020-05-19
|
* move highlight themes from lib/css/ to plugin/highlight/Hakim El Hattab2020-05-19
|
* restore support for markdown speaker notesHakim El Hattab2020-05-18
|
* bundle html inside of notes.js, no more need for relatively locating ↵Hakim El Hattab2020-05-18
| | | | external html
* removed phantomjs-based print-pdf pluginHakim El Hattab2020-05-18
|
* move built plugin files from /dist/plugin/ to /plugin/<name>/Hakim El Hattab2020-05-18
|
* .esm suffix for module bundle, marked/highlight.js are installed via npmHakim El Hattab2020-05-04
|
* plugin consistencyHakim El Hattab2020-04-29
|
* move markdown example from /plugins to /examplesHakim El Hattab2020-04-27
|
* add markdown support for code line numbers and line highlights #2371Hakim El Hattab2020-04-27
|
* remove unused code from md pluginHakim El Hattab2020-04-27
|
* make plugins work with multiple presentations on same pageHakim El Hattab2020-04-23
|
* move notes-server plugin out of reveal.js coreHakim El Hattab2020-04-22
|
* move multiplex plugin out to reveal/reveal-multiplex repoHakim El Hattab2020-04-22
|
* tweak plugin initialization to enable multi-instance pluginsHakim El Hattab2020-04-17
|
* two js bundles; reveal.js (es6) and reveal.es5.js, add source mapsHakim El Hattab2020-04-17
|
* add 'plugins' config option, new way of registering es5 pluginsHakim El Hattab2020-04-17
|
* initialize plugins seriallyHakim El Hattab2020-04-16
|
* fix code highlighting in markdown decksHakim El Hattab2020-04-16
|
* convert plugins to ES modules, transpile es5 versions backwards compatibilityHakim El Hattab2020-04-15
|
* changes to plugin api; registerPlugin only accepts plugin instance, instance ↵Hakim El Hattab2020-04-08
| | | | exposes .id
* Reveal.add/remveEventListener -> Reveal.on/offHakim El Hattab2020-04-07
|
* add support for automatically scrolling code highlights into viewHakim El Hattab2020-03-12
|
* remove code slide from exampleHakim El Hattab2020-03-09
|
* fix markdown exampleHakim El Hattab2020-03-09
|
* Merge pull request #2515 from Bagira80/boolean-attributes-from-markdownHakim El Hattab2020-03-03
|\ | | | | Markdown: Boolean (data-)attributes will now be added to elements, too.
| * Markdown: Boolean (data-)attributes will now be added to elements, too.Deniz Bahadir2019-10-23
| |
* | update to highlight.js 9.18.0 #2562Hakim El Hattab2020-01-29
|/
* highlight.js 9.11 -> 9.15Hakim El Hattab2019-08-22
|
* Merge branch 'alternate-timing' of https://github.com/fghaas/reveal.js into devHakim El Hattab2019-05-27
|\
| * Notes: Weakly enforce a minimum allocated pacing time per slideFlorian Haas2019-05-22
| | | | | | | | | | | | | | | | | | | | | | When using the totalTime-based pacing calculation, a presenter may inadvertently set totalTime and per-slide data-timing attributes in such a way that the pacing time for some slides is impossibly low or even negative. Add a check to ensure that the pacing on a slide never falls below a configurable minimum, defaulting to 0. Display an alert if the pacing for any slide(s) falls below the threshold.
| * Notes: Introduce alternate pacing timer, based on total presentation timeFlorian Haas2019-05-12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The current pacing timer operates on the assumption that there is a default amount of time to be allocated to each slide, and that individual slides can deviate from that default by specifying their own data-timing attribute. This patch introduces an alternate pacing method: by specifying the totalTime configuration option, the presenter can set the total time available to present. The pacing timer will then continue to allocate the exact pacing time for slides that do have data-timing set, as before. However, rather than applying the defaultTiming constant to all others, it will - Add up the time already allocated to slides via data-timing; - subtract that from totalTime; - divide the difference by the number of slides without data-timing set; - apply the thus-calculated average to those slides. totalTime has no default, and if both defaultTiming and totalTime are set, totalTime wins. This preserves backward compatibility: if a presenter has set defaultTiming and updates reveal.js, totalTime will be null and defaultTiming is still applied to all slides without a data-timing attribute. The presenter can then switch to the automatic calculation, if desired, by setting a value for totalTime.
* | avoid exception when highlighting empty code blocksHakim El Hattab2019-05-27
|/
* fix numeric presence conditionHakim El Hattab2019-04-10
|
* refinements for multi-step code highlightsHakim El Hattab2019-04-05
|
* first version of multi-step code highlightsHakim El Hattab2019-04-05
|
* fix typosHakim El Hattab2019-04-01
|
* support for plugins where the init method doesn't return a PromiseHakim El Hattab2019-03-14
|
* more forgiving code highlight line number format, add Promise polyfillHakim El Hattab2019-03-14
|
* highlight.js plugin improvementsHakim El Hattab2019-03-12
|
* switch to monokai as default syntax highlight themeHakim El Hattab2019-03-12
|
* notes plugin: callRevealApi wants apply, not callDougal J. Sutherland2019-03-11
|
* validate code line numbers to highlightHakim El Hattab2019-03-11
|
* more succinct syntax for code block line highlightsHakim El Hattab2019-03-11
|
generated by cgit v1.2.3 (git 2.25.4) at 2024-05-19 18:07:51 +0000