Feature suggestion: Video options

[ford--prefect]

Hi,

I'd like to suggest to add options for video playback, so the software becomes more configurable.
This could either be done by en/dis-abling several options (autoplay, preload, loop etc) or just passing an options string right into the html5 video tag.
Thank you for considering.

[anarcat]

@ford--prefect which options did you have in mind exactly? it may be useful to show a sample configuration file that would do what you need, for example. please expand what your use-case is.

[ford--prefect]

The HTML5 video tag has several options controlling e.g. loading, showing controls, repeat mode, and autoplaying of the movie.
My wish would be to control these in a versatile way by either identifying a common set, that is made configurable each (see example 1 below) or just passing a config string to the video tag which is user defined and pasted into the html5 video tag (example 2).
This would allow to play videos in a user defined manner without fiddling with the source code.
I hope the examples illustrate the above. Dont hesitate to ask for further clarifications.

EDIT: Markdown ate my style, corrected.

===== Example 1 ====
sigal.conf.py:

[…]
#_ control video preload: auto, metadata or none (default: auto)
video_preload = "auto"
#_ control video autoplay: bool (default: True)
video_autoplay = True
#_ control video loop: bool (default: False)
video_loop = False
#_ display video controls: bool (default: True)
video_controls = True
[…]

produces html5 output like:

<video width="500" height="550" preload="auto" autoplay controls>
  <source src="sourcefile.mp4" type="video/mp4">
  <source src="sourcefile.ogg" type="video/ogg">
  Your browser does not support the video tag.
</video> 

===== Example 2 ====
sigal.conf.py:

[…]
# video config string
video_config = 'preload="auto" autoplay loop controls"
[…]

produces html5 output like:

<video width="500" height="550" preload="auto" autoplay loop controls>
  <source src="sourcefile.mp4" type="video/mp4">
  <source src="sourcefile.ogg" type="video/ogg">
  Your browser does not support the video tag.
</video> 

[anarcat]

On 2017-10-25 17:13:25, ford--prefect wrote: The HTML5 video tag has several options controlling e.g. loading, showing controls, repeat mode, and autoplaying of the movie.

I guess the question is whether that is an exhaustive list or not. If it's exhaustive, then it would make sense to have one setting in the config file for every HTML5 setting. But otherwise, it may be better to have this free-form. A. -- Some believe it is only great power that can hold evil in check, but that is not what I have found. It is the small everyday deeds of ordinary folk that keep the darkness at bay. Small acts of kindness and love. - J.R.R. Tolkien

[ford--prefect]

According to the specification the full list is:

• src - Address of the resource
• crossorigin - How the element handles crossorigin requests
• poster - Poster frame to show prior to video playback
• preload - Hints how much buffering the media resource will likely need
• autoplay - Hint that the media resource can be started automatically when the page is loaded
• mediagroup - Groups media elements together with an implicit MediaController
• loop - Whether to loop the media resource
• muted - Whether to mute the media resource by default
• controls - Show user agent controls
• width - Horizontal dimension
• height - Vertical dimension

not all of which are applicable here (e.g. width, height, src, crossorigin arent settings one sets for all videos at once). This is unlikely to change anytime soon, so adding these config variables makes sense in my view.

[saimn]

I think I prefer the second option, to avoid the proliferation of settings, but no strong feelings (either one would be fine is someone wants to work on it 😉 )

[ford--prefect]

I can look into this, but I have not much clue of your code at all. Do you have any contributor documentation with some hints how the subsystem interplay and maybe a tip where to start?
I haven't got much time, would try nonetheless.

[saimn]

No real contributor documentation, sorry! But adding a new setting is easy (you can have a look at #270 or other PRs), and the settings dict is already available in the HTML templates.