From 1838cc2d82c7a1591350ffda78e1ca94ea9d6e84 Mon Sep 17 00:00:00 2001 From: damianavila Date: Mon, 30 Dec 2013 14:45:15 -0300 Subject: [PATCH 1/3] Added --post-serve explanation into the nbconvert docs. --- docs/source/interactive/nbconvert.rst | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/docs/source/interactive/nbconvert.rst b/docs/source/interactive/nbconvert.rst index 1789a6200..610edf0a9 100644 --- a/docs/source/interactive/nbconvert.rst +++ b/docs/source/interactive/nbconvert.rst @@ -61,8 +61,12 @@ The currently supported export formats are: * ``--to slides`` This generates a Reveal.js HTML slideshow. - It must be served by an HTTP server. The easiest way to do this is adding - ``--post serve`` on the command-line. + It must be served by an HTTP server. The easiest way to do this is adding + ``--post serve`` on the command-line. The ``--post serve`` post-processor + proxies Reveal.js requests to a CDN if no local Reveal.js library is present. + For low connectivity environments, just place the Reveal.js library in the + same directory where your_talk.slides.html is located or point to another + directory using the ``--reveal-prefix`` alias. * ``--to markdown`` @@ -224,4 +228,3 @@ The corresponding Python script is:: Note that indeed the output of the code cell, which is present in the JSON container, has been removed in the ``.py`` script. - From 78e41cd76612880b8a532f90518d73918c5797a1 Mon Sep 17 00:00:00 2001 From: damianavila Date: Mon, 6 Jan 2014 16:37:33 -0300 Subject: [PATCH 2/3] It is the serve post processor and not the way to specify it. --- docs/source/interactive/nbconvert.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/source/interactive/nbconvert.rst b/docs/source/interactive/nbconvert.rst index 610edf0a9..05e4b1ab0 100644 --- a/docs/source/interactive/nbconvert.rst +++ b/docs/source/interactive/nbconvert.rst @@ -62,7 +62,7 @@ The currently supported export formats are: This generates a Reveal.js HTML slideshow. It must be served by an HTTP server. The easiest way to do this is adding - ``--post serve`` on the command-line. The ``--post serve`` post-processor + ``--post serve`` on the command-line. The ``serve`` post-processor proxies Reveal.js requests to a CDN if no local Reveal.js library is present. For low connectivity environments, just place the Reveal.js library in the same directory where your_talk.slides.html is located or point to another From f308b127216f4f0ffc2959beaa6223345ef70310 Mon Sep 17 00:00:00 2001 From: damianavila Date: Tue, 7 Jan 2014 17:17:03 -0300 Subject: [PATCH 3/3] Deleted jargon-ish reference to no-connectity. --- docs/source/interactive/nbconvert.rst | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/docs/source/interactive/nbconvert.rst b/docs/source/interactive/nbconvert.rst index 05e4b1ab0..d4be56306 100644 --- a/docs/source/interactive/nbconvert.rst +++ b/docs/source/interactive/nbconvert.rst @@ -61,12 +61,12 @@ The currently supported export formats are: * ``--to slides`` This generates a Reveal.js HTML slideshow. - It must be served by an HTTP server. The easiest way to do this is adding - ``--post serve`` on the command-line. The ``serve`` post-processor - proxies Reveal.js requests to a CDN if no local Reveal.js library is present. - For low connectivity environments, just place the Reveal.js library in the - same directory where your_talk.slides.html is located or point to another - directory using the ``--reveal-prefix`` alias. + It must be served by an HTTP server. The easiest way to do this is adding + ``--post serve`` on the command-line. The ``serve`` post-processor proxies + Reveal.js requests to a CDN if no local Reveal.js library is present. + To make slides that don't require an internet connection, just place the + Reveal.js library in the same directory where your_talk.slides.html is located, + or point to another directory using the ``--reveal-prefix`` alias. * ``--to markdown``