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

2014-02-09 Thread John Hendy
On Sun, Feb 9, 2014 at 10:16 PM, Charles Berry wrote: > John Hendy gmail.com> writes: > >> >> On Sat, Feb 8, 2014 at 11:18 AM, Charles Berry ucsd.edu> wrote: >> > [snip] > >> >> Ah. I think I follow this. If you knit the exported .org -> Rmd file >> in the same R session that Org is using, if yo

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

2014-02-09 Thread Charles Berry
John Hendy gmail.com> writes: > > On Sat, Feb 8, 2014 at 11:18 AM, Charles Berry ucsd.edu> wrote: > [snip] > > But there is some effort and overhead involved, so only the most > > useful (IMO) have been mapped. Right now, `:noweb yes' will expand the > > reference(s) in place before export, a

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

2014-02-09 Thread John Hendy
On Sat, Feb 8, 2014 at 11:18 AM, Charles Berry wrote: >> I still think it makes sense to allow :eval no. This seems more >> "Org-ish" since the ideology is to have one set of Org syntax where >> possible, which translates to any number of languages. [...] > > In principal, it makes sense to map b

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

2014-02-08 Thread Charles Berry
John Hendy gmail.com> writes: > > On Fri, Feb 7, 2014 at 11:38 PM, John Hendy gmail.com> wrote: > > On Fri, Feb 7, 2014 at 7:04 PM, Charles Berry ucsd.edu> wrote: > > [snip] > > > I'll look into those. I just cloned your repo and loaded ox-ravel. > > Quite nice! It worked /pretty/ well out o

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

2014-02-08 Thread Nicolas Goaziou
John Hendy writes: > Typical markup would be a description string on some sort. Maybe just 'img' > for general images and the content of #+name for Babel results? OK. I fixed it in maint. "img" will be always used as alt text. I also fixed caption location. Thank you. Regards, -- Nicolas Go

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

2014-02-08 Thread John Hendy
On Feb 8, 2014 3:32 AM, "Nicolas Goaziou" wrote: > > Hello, > > John Hendy writes: > > > One other question while we're at it... I noticed that > > #+begin/end_center produces this in the output .md file: > > > > > > ![nil](map.png) > > > > This "nil" looks like a bug. What should be expected i

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

2014-02-08 Thread Nicolas Goaziou
Hello, John Hendy writes: > One other question while we're at it... I noticed that > #+begin/end_center produces this in the output .md file: > > > ![nil](map.png) > This "nil" looks like a bug. What should be expected instead? Regards, -- Nicolas Goaziou

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

2014-02-07 Thread John Hendy
On Fri, Feb 7, 2014 at 11:38 PM, John Hendy wrote: > On Fri, Feb 7, 2014 at 7:04 PM, Charles Berry wrote: [snip] > I'll look into those. I just cloned your repo and loaded ox-ravel. > Quite nice! It worked /pretty/ well out of the box. One issue is that > it doesn't seem to obey :eval no for ba

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

2014-02-07 Thread Charles Berry
John Hendy gmail.com> writes: > > On Fri, Feb 7, 2014 at 3:50 PM, Charles Berry ucsd.edu> wrote: > > John Hendy gmail.com> writes: > > > >> > >> An interesting update on this. Aside from some image and code block > [snip - how John turn org to Rmd to md] > > > > John, > > > > You can put the

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

2014-02-07 Thread Charles Berry
John Hendy gmail.com> writes: > > 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

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

2014-02-06 Thread Andreas Leha
Hi John, John Hendy writes: > 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 dec

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

2014-02-06 Thread John Hendy
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 -

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

2014-01-29 Thread John Hendy
On Jan 29, 2014 7:46 PM, "Rick Frankel" wrote: > > On Thu, Jan 30, 2014 at 12:57:46AM +, 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 >

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

2014-01-29 Thread Rick Frankel
On Thu, Jan 30, 2014 at 12:57:46AM +, 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 libra

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

2014-01-29 Thread Ahmadou Dicko
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 yo

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

2014-01-29 Thread John Hendy
Greetings, I use R quite a bit, and ran into a new exporter sometime last year called Slidify: - http://slidify.org/start.html Would anyone be able to suggest a good starting place for creating a possible backend exporter for this? RStudio allows this pretty easily, but I really like my prose/co