emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: John Hendy <jw.hendy@gmail.com>
To: Charles Berry <ccberry@ucsd.edu>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Proposal/request for input: slidify export for html slides
Date: Fri, 7 Feb 2014 23:38:32 -0600	[thread overview]
Message-ID: <CA+M2ft_mZtwvTpScZ=hQX50_dKQicxnmn0AWNYVarzodeMW7qQ@mail.gmail.com> (raw)
In-Reply-To: <loom.20140208T014253-595@post.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 3770 bytes --]

On Fri, Feb 7, 2014 at 7:04 PM, Charles Berry <ccberry@ucsd.edu> wrote:
> John Hendy <jw.hendy <at> gmail.com> writes:
>
>>
>> On Fri, Feb 7, 2014 at 3:50 PM, Charles Berry <ccberry <at> ucsd.edu> wrote:
>> > John Hendy <jw.hendy <at> gmail.com> writes:
>> >
>> >>
>> >> An interesting update on this. Aside from some image and code block
>>
> [snip - how John turn org to Rmd to md]
>

[snip]

>> I often get something squarish, which makes the map look really
>> compressed (see attached). Thus, I seem to need both this (name,
>> header)
>>
>
> This is a problem that results from rendering in a square rather than
> something proportional to what Mercator used: 202cm x 124cm, I think.
>
> slidify wants to have png files for images, so I think you are stuck
> having to set up the size of the device as well as the displayed size
> to get nice looking results.

Indeed. I've had to deal with that when exporting to html. Was just
curious if there was a more elegant way, and it seems there's not, but
I suppose it's just adjusting syntax from #+attr_latex stuff to the
knitr equivalents, which isn't bad to know anyway since I've been
working more with RStudio.

[snip]

>> I would love to avoid the above if you have more clarification on "just
> work" :)
>
> I wasn't thinking about the case you just demonstrated. I have to use
> a line that gives out.width, out.height, fig.width, and fig.height, which
> slidify ('knitr' under the hood) uses to render the png and the page as you
> did to make something that looks like the Mercator map and still have
> the text look OK. See http://yihui.name/knitr/options if the options
> listed are not familiar. (knitr chunk options can be put in #+ATTR_RAVEL:
> lines for ravel exports to use them.)

Thanks for the reference.

>
> [more deleted]
>
>>
>> One other question while we're at it... I noticed that
>> #+begin/end_center produces this in the output .md file:
>>
>> <div class="center">
>> ![nil](map.png)
>> </div>
>>
>> This doesn't export with slidify. [snip more details]
>
> Right. IMO, using the knitr tools for dealing with such issues beats
> wrestling with the babel and md exporter. i.e. fig.align="center" handles
> this. A good part of my motivation for ox-ravel is that I can deal with
> fine tuning output from knitr more easily than I can w/ babel exports.
>

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 babel blocks. I exported to .Rmd
successfully, but the presentation has a bunch of errors in the code
blocks from trying to actually execute the code. The .Rmd doesn't have
any instances of ```{r eval=F}; could this feature be added?

I'm also getting some odd code highlighting (see attached). Every once
in a while, it's like it can't differentiate non strings (black) from
strings (red)? Any idea why that might be? I still have some
attr_latex stuff to prune out, so perhaps that's gunking up proper
code recognition... then again, any of my latex options shouldn't be
touching the contents of ```{r} chunks, so I'm perplexed.

Other than that and figuring out my plot/image strategy, I think this
will work wonderfully! I won't be able to transition my slides to
Slidify by tomorrow, but am quite hopeful for transitioning in the
future! Love the idea of embedding shiny apps or d3 right in a
presentation vs. having to open a browser :) Also makes it so much
easier to share presentations, embed them in a web page, or whatnot.
No more things like relying on box/dropbox/google drive to have
in-browser PDF displays!


Thanks so much for chiming in -- I'd not seen ox-ravel before and am
really glad to have discovered it!
John

>
> HTH,
>
> Chuck
>
>
>
>

[-- Attachment #2: 2014-02-07_233046.png --]
[-- Type: image/png, Size: 36771 bytes --]

[-- Attachment #3: 2014-02-07_233122.png --]
[-- Type: image/png, Size: 80355 bytes --]

  reply	other threads:[~2014-02-08  5:38 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-30  0:05 Proposal/request for input: slidify export for html slides John Hendy
2014-01-30  0:57 ` Ahmadou Dicko
2014-01-30  1:45   ` Rick Frankel
2014-01-30  4:26     ` John Hendy
2014-02-07  1:26       ` John Hendy
2014-02-07  7:58         ` Andreas Leha
2014-02-07 21:50         ` Charles Berry
2014-02-07 22:18           ` John Hendy
2014-02-08  1:04             ` Charles Berry
2014-02-08  5:38               ` John Hendy [this message]
2014-02-08  5:51                 ` John Hendy
2014-02-08 17:18                   ` Charles Berry
2014-02-09 22:26                     ` John Hendy
2014-02-10  4:16                       ` Charles Berry
2014-02-10  4:54                         ` John Hendy
2014-02-08  9:33             ` Nicolas Goaziou
2014-02-08 14:11               ` John Hendy
2014-02-08 14:52                 ` Nicolas Goaziou

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CA+M2ft_mZtwvTpScZ=hQX50_dKQicxnmn0AWNYVarzodeMW7qQ@mail.gmail.com' \
    --to=jw.hendy@gmail.com \
    --cc=ccberry@ucsd.edu \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).