emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Rasmus <rasmus@gmx.us>
To: emacs-orgmode@gnu.org
Subject: Re: allow live execution of code snippets in html export
Date: Tue, 13 Dec 2016 17:11:31 +0100	[thread overview]
Message-ID: <87mvfzzu4s.fsf@gmx.us> (raw)
In-Reply-To: CAN_Dec_Xp0LKxCV_-6GSQcKR8o209zenv9QkbEZgD6X0o_AeFQ@mail.gmail.com

Hi Matt,

> In other threads I've been describing a method to allow live code snippets
> to be embedded in reveal.js export, using klipse (
> https://github.com/viebel/klipse).  I have to say it feels somewhat
> transformative to me, and I wonder if it would be worth integrating into
> ox-html.  I'd be happy to hack together a patch but I wanted to ask if
> anyone else likes the idea.  The great thing about putting it into ox-html
> instead of building a derived mode is that the other derived mode would
> potentially inherit the functionality directly.

I like it.  The clearest example seems to be this one:

      https://jsfiddle.net/viebel/50oLnykk/

Some observations follow:

The syntax for Klipse source blocks is nice and simple:

    <div class="klipse">
     function foo(name) {return "Hello " + name;}
     foo("Klipse");
    </div>

It might be worth investigating whether you can just run Klipse on <pre>
blocks as that would potentially make it backward compatible.
Potentially, an extension to Klipse that recognizes Org src blocks (in
html) might be nice.

The Klipse license is GPL3.

The README recommends to get the files from googleapis.com.  I’m not sure
we would want to generate html files that get stuff from Google.  Then
again, maybe googleapis.com is perfectly OK...

It could easily become a mess in complex cases, e.g. if your Python code
blocks use Pandas, which does not seem to be supported by Skulpt.

Nonetheless, Klipse looks intriguing.  I think it could be great if you
look further into it.

Thanks,
Rasmus

-- 
Dung makes an excellent fertilizer

  reply	other threads:[~2016-12-13 16:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-13 14:55 allow live execution of code snippets in html export Matt Price
2016-12-13 16:11 ` Rasmus [this message]
     [not found]   ` <CAN_Dec8cw4QNFhcS7G7ktuY-A9vQEUftKLX4fN9c1XJ1TjF0Wg@mail.gmail.com>
2016-12-14 10:06     ` Rasmus
2016-12-14 10:36       ` Bastien Guerry
2016-12-15  3:18         ` Matt Price
2016-12-15 10:07           ` Bastien
2016-12-15 15:50             ` Matt Price
2016-12-15 20:55               ` Yehonathan Sharvit
2016-12-18  3:25                 ` Yehonathan Sharvit
2016-12-14 17:55       ` Matt Price
2016-12-14 21:07         ` Yehonathan Sharvit
2016-12-15  2:10         ` Bastien Guerry
     [not found] <44cd312833be418b92f225baf0940026@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2016-12-13 15:39 ` Eric S Fraga

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=87mvfzzu4s.fsf@gmx.us \
    --to=rasmus@gmx.us \
    --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).