1
0
Fork 0
why-cant-we-deploy-today/plugin
Jakub Holy 8fd28a9185 Better error reporting for external Markdown files
1. Show an alert when loading the file throws an exception
2. Whenever the status isn't success (2xx) - upon exception or e.g.
  "file not found" - replace the section's content with information
  about the failure (instead of being silent about it and showing
  a blank slide).

We need to inform the user something went wrong, not just be silent
about it. An experienced developer, upon seing a blank slide, will
likely check the javascript console - but the rest will profit from
being told about the problem (and solution) explicitely.
2013-03-24 18:06:44 +01:00
..
highlight Add Clojure to highlight.js, add code highlight example to README. 2013-01-21 17:53:39 -08:00
markdown Better error reporting for external Markdown files 2013-03-24 18:06:44 +01:00
multiplex remove unused file (closes #360) 2013-03-10 11:57:08 -04:00
notes update main window when current slide changes in notes (closes #343) 2013-02-27 16:55:42 -05:00
notes-server updated markdown references in notes plugin 2012-10-28 18:49:01 -04:00
postmessage cosmetical tweaks to postmessage plugin 2012-11-10 17:15:11 -05:00
print-pdf attribution for print-pdf phantom script (closes #276) 2013-01-10 09:40:03 -05:00
remotes disable remotes plugin on mobile 2013-01-04 17:12:20 -08:00
search merge search plugin, adjust styles 2013-03-08 19:48:30 -05:00
zoom-js disable zoom plugin while in overview mode 2013-02-03 13:21:42 -05:00