[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [O] Proposal/request for input: slidify export for html slides

From: John Hendy
Subject: Re: [O] Proposal/request for input: slidify export for html slides
Date: Thu, 6 Feb 2014 19:26:42 -0600

An interesting update on this. Aside from some image and code block
stuff, the following works surprisingly well!
- Export Org -> markdown (md)
- Start an R session and `setwd("/path/to/file.md")`
- Run `library(slidify)` and `author("deck")
- Copy the deck/assets folder into the parent directory
- Copy the header code from the resultant deck/index.Rmd file into
exported .md file
- Add three hyphens before each heading (headings are # Slide title)
- Save the file as file.Rmd (vs. file.md)
- From the R session, do `setwd("../")` (running `author("deck")`
changes the working directory to deck/
- Run `slidify("file.Rmd")`

I was coming from Beamer, so all of my generated plots are .pdfs. I
plan to create a new directory and use imagemagic to convert them all
to png or jpg, and then modify my original .org file tailored for
Beamer to use the images vs. pdfs, as well as adding #+attr_html
headings instead of the existent #+attr_latex ones in my current file.

I'll post a test file and the process if anyone is interested in replicating!

It seems that src blocks aren't *always* detected properly in the .md
file, so I need to figure out what's happening there.

I think I should be able to do a pretty easy replace-regexp to replace
[^#] (beginning of line followed by #, indicating a header) with [---
[RET] [RET] #] to automatically populate the slide divisions.

If any rough spots could be identified and tweaked, the current .md
exporter might work brilliantly to create a .Rmd file compatible with
slidify if it's of interest to folks. The boilerplate slidify text at
the beginning is simple enough to populate, and some variables could
set the framework, (io2012, deckjs, etc.), title, author, etc.

Best regards,

On Wed, Jan 29, 2014 at 10:26 PM, John Hendy <address@hidden> wrote:
> On Jan 29, 2014 7:46 PM, "Rick Frankel" <address@hidden> wrote:
>> On Thu, Jan 30, 2014 at 12:57:46AM +0000, Ahmadou Dicko wrote:
>> >    I love slidify too and I think that having similar functionnality in
>> > org
>> >    could be great.
>> >    I think that you have everything to do that using the html backend,
>> > you
>> >    just need to interface the right Javascript/HTML5 library.
>> >    In slidify you can use io2012, deck.js, shower and landslide and I
>> > know
>> >    that you can use deck.js through ox-deck and it will not be difficult
>> > to
>> >    create and interface for other library too.
>> >    For example if you need a nice non Beamer library you can also check
>> >    ox-reveal which interface reveal.js.
>> Just to follow-up and expand. It looks like slidy is an interface for
>> Rstudio to a number of html slide (javascript) libraries, and uses
>> markdown as it markup language, while providing the ability to execute
>> R code interspersed with the markup (literate programming/reproducable
>> results)
>> Org is it's own markup language and allow interspersing executable
>> code (and its output) in a literate, reproducable way
>> (babel). Including, but not limited to, R.
>> In addion org has export interfaces to multiple output types. For
>> slideshow there are (at least):
>>           - ox-s5
>>           - ox-deck
>>           - ox-reveal
>>           - beamer
>> As well as pdf, html and others.
>> So it doesn't seem to make sense to use org as a frontend to Rstudio,
>> but i may be wrong...
> Agree on most points, and will be checking out the HTML org options as I
> mentioned.
> I did want to correct that slidify is not tied to rstudio, even though it
> integrates nicely with it. I was playing with it when straight from an R
> session within Emacs when I wrote the post.
> It also has some nice web publishing features to send the presentation right
> to git, dropbox, or rpubs from R, (though I didn't try that outside of
> rstudio, so there could be caveats).
> John
>> rick

reply via email to

[Prev in Thread] Current Thread [Next in Thread]