From: Rasmus <rasmus@gmx.us>
To: emacs-orgmode@gnu.org
Subject: Re: html export with editable/runnable js src blocks?
Date: Fri, 28 Oct 2016 11:55:50 +0200 [thread overview]
Message-ID: <87wpgs94rd.fsf@gmx.us> (raw)
In-Reply-To: CAN_Dec-KSP1AUcOMVePSP67bsDMNmrB-X-Sk3pENsg-WJRqg8Q@mail.gmail.com
Matt Price <moptop99@gmail.com> writes:
> I feel like I've seen people do this before but my search today did not
> turn up a working example online. I'd like to be able to export to html
> (and by extension, to a blog or a reveal.js presentation) and have my
> source code blocks -- at leas t the javascript ones -- placed in an editing
> environment that allows you to actually run the code. the idea is to help
> students experiment with code as you're talking about it in class.
You could add contenteditable="true" to your <pre ...> tags. E.g.
<pre class="src src-emacs-lisp" contenteditable="true">
On this page there’s some ideas for making it live.
http://html5doctor.com/the-contenteditable-attribute/
> Has anyone done this? I know it's not too hard to embed codemirror or ace
> in aweb page, but I odn't know how to get org to set the blocks up right.
> Would love some suggestions or examples. Thank you!
Unfortunately, org-html-src-block does not allow you to insert random keys
into <pre...>. Thus, you would either have to prepare your pages with JS
on pageload, do the correction with org-export-filter-body-functions or
maybe change org-html-src-block to allow the flexibility you need. You
might need to figure out what you want the final output to be like first.
The IPython notebook (which has some other name these days) might also be
appropriate here, though I don’t know if it does JS...
Hope it helps,
Rasmus
--
You people at the NSA are becoming my new best friends!
prev parent reply other threads:[~2016-10-28 9:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-27 16:01 html export with editable/runnable js src blocks? Matt Price
2016-10-28 9:55 ` Rasmus [this message]
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=87wpgs94rd.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).