From: Robert Goldman <rpgoldman@sift.info>
To: Eric Schulte <schulte.eric@gmail.com>
Cc: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: HTML5 presentations
Date: Thu, 16 Jun 2011 14:35:52 -0500 [thread overview]
Message-ID: <4DFA5B18.4090209@sift.info> (raw)
In-Reply-To: <87y611bmmr.fsf@gmail.com>
On 6/16/11 Jun 16 -2:29 PM, Eric Schulte wrote:
> Robert Goldman <rpgoldman@sift.info> writes:
>
>> On 6/7/11 Jun 7 -3:01 PM, Tassilo Horn wrote:
>>> Vinh Nguyen <vinhdizzo@gmail.com> writes:
>>>
>>>> After the recent org-mode to S5 discussion, I stumbled onto
>>>> [these](https://gist.github.com/509761) code. It offers a way to
>>>> export org files to HTML5 presentations. I think it looks quite nice.
>>>> I see it being better than S5 in that no "ui" folder is required.
>>>> What do you all think? Is it worthy of being incorporated into
>>>> org-mode?
>>>
>>> Just tried it, and it's pretty cool! Easy to use and nicely looking.
>>>
>>> Bye,
>>> Tassilo
>>>
>>>
>>>
>>
>> I have tried the version here:
>> https://github.com/twada/org-html5presentation.el
>>
>> and it does not seem to be ready for prime-time. Org-babel features
>> don't work, and there seems to be not a clear integration with the
>> org-export-preprocessor. See my two issues, one (not satisfactorily)
>> closed, one open.
>>
>> Possibly this should be folded into contrib, so that people could
>> cooperate on it more easily than when it lives off in a separate git
>> repo, but it shouldn't be enabled for the unwary until it's been
>> thoroughly exercised.
>>
>> Is there a "tries to use all features" org presentation somewhere that
>> would serve as a good acid test for an export facility? It would be
>> very handy to have that.
>>
>
> This export target seems to re-implement much of the org HTML export
> mechanics which is most likely the reason for the incomplete coverage of
> Org's large functionality.
>
> Perhaps it would be possible to change this so that it works more like
> org-s5, that is, so that it firsts exports using the existing html
> export functionality, and then simply manipulates the resulting html.
Alternatively, would it be possible to have this behave mostly like
conventional HTML export (i.e., have the org-export-current-backend be
'html), and then simply have the code that does the emitting override
particular bits of the normal org-html behavior?
The problem with this approach is that a side-effect of setting the
org-export-current-backend to 'foo is to (require 'org-foo). This means
it's difficult to make something like org-export-as-html5presentation be
parasitic on org-export-as-html...
I confess to not understanding how beamer and conventional latex export
interact; possibly that would provide valuable precedent for this.
best,
r
next prev parent reply other threads:[~2011-06-16 19:36 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-07 18:56 HTML5 presentations Vinh Nguyen
2011-06-07 20:01 ` Tassilo Horn
2011-06-07 20:35 ` Eric Schulte
2011-06-08 7:21 ` Jambunathan K
2011-06-15 18:19 ` Eric S Fraga
2011-06-15 19:35 ` Eric Schulte
2011-06-15 20:57 ` Joost Kremers
2011-06-16 7:45 ` Eric S Fraga
2011-06-15 22:07 ` Juan Pechiar
2011-06-16 7:44 ` Eric S Fraga
2011-06-16 15:49 ` Achim Gratz
2011-06-17 19:35 ` Eric S Fraga
2011-06-18 7:09 ` Achim Gratz
2011-06-16 19:07 ` Robert Goldman
2011-06-16 19:29 ` Eric Schulte
2011-06-16 19:35 ` Robert Goldman [this message]
2011-06-16 20:36 ` Jambunathan K
2011-06-16 21:50 ` Robert Goldman
2011-06-16 23:19 ` Eric Schulte
2011-06-17 2:50 ` Jambunathan K
2011-06-17 1:09 ` Jambunathan K
2011-06-07 22:05 ` Christian Moe
2011-06-08 7:24 ` Tassilo Horn
2011-06-08 11:27 ` Rainer M Krug
2011-06-08 13:01 ` Tassilo Horn
2011-06-08 13:13 ` Rainer M Krug
2011-06-08 13:45 ` Tassilo Horn
-- strict thread matches above, loose matches on Subject: below --
2011-08-24 15:33 Matt Price
2011-08-25 22:38 ` Eric Schulte
2011-08-26 10:58 ` zwz
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=4DFA5B18.4090209@sift.info \
--to=rpgoldman@sift.info \
--cc=emacs-orgmode@gnu.org \
--cc=schulte.eric@gmail.com \
/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).