Open GoogleCodeExporter opened 9 years ago
It depends. Could you enumerate these sources, as well as the mechanism you'd
use to play the videos in the embedded view? (Are you thinking just HTML5
<video>, for example?)
Original comment by s...@seanlip.org
on 8 Jan 2015 at 2:39
We store a lot of our videos on heanet https://media.heanet.ie/. You need
to login to access but embed URL is like:
<iframe src="https://media.heanet.ie/player/07382fd5b6364102a6fe334c12cd20bc"
name="07382fd5b6364102a6fe334c12cd20bc" width="640" height="360"
marginwidth="0" marginheight="0" scrolling="no" frameborder="0"
webkitAllowFullScreen allowFullScreen></iframe>
Original comment by niall.wa...@ucd.ie
on 8 Jan 2015 at 3:04
Ah, I see. Thanks for the clarification.
We won't be able to implement this in the general codebase, since it's very
specific and only relevant to a particular set of users (i.e., those from UCD).
However, if it's possible on your end to expose a URL that can be used with
HTML5's <video> tag, we might be able to write a general noninteractive widget
for that, similar to what we were thinking of for audio files. Would this be
feasible?
Alternatively, if you would like to do this on a local installation, you can
certainly create a new non-interactive widget for local use by mimicking the
other ones in extensions/widgets/noninteractive. This should be fairly
straightforward.
Original comment by s...@seanlip.org
on 8 Jan 2015 at 3:18
Ok but there are also other public web sources of video e.g. vimeo
Original comment by niall.wa...@ucd.ie
on 8 Jan 2015 at 4:15
That's true (and local extensions can be similarly constructed for those).
However, for the mainline branch, I think we should wait to see if there's
sufficient demand for these before implementing. In addition, I'm concerned
that having a whole bunch of different video embedders would significantly
complicate things (from the editor's perspective). So I'd look for a common
standard, and the closest seems to me to be HTML5 video, but it's not clear if
that works for vimeo etc.
Another idea for a standard is: why not just embed any arbitrary website? The
issue with that is basically security -- if we allowed arbitrary iframe
sources, then this allows someone to create an exploration that runs arbitrary
JavaScript in other users' browsers, and that's not a good thing.
I hope that makes sense. Another possibility is to upload the videos on
YouTube; would that be an issue?
Original comment by s...@seanlip.org
on 8 Jan 2015 at 4:30
Hi,
it would really be a nice feature if you can embed local stored videos or audio
files via HTML5.
That's a feature I need if I want to use oppia.
Regards,
Tom
Original comment by thomas.s...@gmail.com
on 26 Mar 2015 at 12:48
Original issue reported on code.google.com by
niall.wa...@ucd.ie
on 8 Jan 2015 at 10:33