From: John Kitchin <jkitchin@andrew.cmu.edu>
To: Scott Randby <srandby@gmail.com>
Cc: Arun Isaac <arunisaac@systemreboot.net>, emacs-orgmode@gnu.org
Subject: Re: Link type for HTML5 videos
Date: Sun, 22 Jan 2017 16:59:59 -0500 [thread overview]
Message-ID: <m21svueoww.fsf@andrew.cmu.edu> (raw)
In-Reply-To: <55050ad4-e40e-a20e-f25e-890930e31ebc@gmail.com>
That looks too rich for a link to me unless alot of it is always the
same, or derived, e.g. the id tags.
Something like this is what a link would look like:
video:quadratic.webm
and the html export could certainly generate what you put in the html
block below.
See
http://kitchingroup.cheme.cmu.edu/blog/2016/11/04/New-link-features-in-org-9/
for how to make a link, try it and report back if it is useful.
Scott Randby writes:
> On 01/22/2017 01:22 PM, John Kitchin wrote:
>> What would these links look like? And what should they render too?
>
> I wasn't suggesting support for the idea, I was just suggesting that it
> makes sense to to both video and audio if they are to be done.
>
> However, I currently use export blocks to do video and audio export. I
> don't have a problem with continuing that practice since it works well
> for me. Here are two examples:
>
> #+begin_export html
> <div id="audio-division">
> <audio
> id="audio-tag"
> controls
> preload="metadata">
> <source src="quadratic.mp3"/>
> Your browser does not support the <code>audio</code> tag.
> </audio>
> </div>
> #+end_export
>
> #+begin_export html
> <div id="video-division">
> <video
> id="video-tag"
> src="quadratic.webm"
> controls
> preload="metadata">
> Your browser does not support the <code>video</code> tag.
> </video>
> </div>
> #+end_export
>
> Styling is done via a CSS file.
>
> It might be difficult to agree on what a video or audio link type
> renders to by default.
>
> Scott
>
>>
>>
>> On Sun, Jan 22, 2017 at 1:09 PM Scott Randby <srandby@gmail.com
>> <mailto:srandby@gmail.com>> wrote:
>>
>> On 01/22/2017 12:15 PM, Arun Isaac wrote:
>>
>> >
>>
>> > It would be nice to have a link type to export HTML5 videos. Currently,
>>
>> > the only way to insert videos is to use the #+BEGIN_video, #+END_video
>>
>> > block with literal #+HTML in them. This seems a little kludgy. Thoughts?
>>
>>
>>
>> If there is to be a link type to videos, then I think there should be
>>
>> one for audio too.
>>
>>
>>
>> Scott Randby
>>
>>
>>
>> >
>>
>> > Thanks,
>>
>> > Arun Isaac.
>>
>> >
>>
>>
>>
--
Professor John Kitchin
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
@johnkitchin
http://kitchingroup.cheme.cmu.edu
next prev parent reply other threads:[~2017-01-22 22:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-22 17:15 Link type for HTML5 videos Arun Isaac
2017-01-22 18:08 ` Scott Randby
2017-01-22 18:22 ` John Kitchin
2017-01-22 21:40 ` Scott Randby
2017-01-22 21:59 ` John Kitchin [this message]
2017-01-23 3:02 ` Scott Randby
2017-01-23 5:01 ` Arun Isaac
2017-01-24 9:24 ` Rasmus
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=m21svueoww.fsf@andrew.cmu.edu \
--to=jkitchin@andrew.cmu.edu \
--cc=arunisaac@systemreboot.net \
--cc=emacs-orgmode@gnu.org \
--cc=srandby@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).