Skip to content
This repository has been archived by the owner on Aug 25, 2021. It is now read-only.

Video.js integration #9

Open
tyranron opened this issue Jan 9, 2019 · 1 comment
Open

Video.js integration #9

tyranron opened this issue Jan 9, 2019 · 1 comment
Labels
k::api Related to API (application interface) k::design Related to overall design and/or architecture question Further information is requested RFC Request for comments

Comments

@tyranron
Copy link
Member

tyranron commented Jan 9, 2019

@flexconstructor wrote:

Gentlemen, as part of the development of the Medea Web Client module, please draw your attention to the Video.js project. I think it makes sense to develop a browser application as a plug-in for video.js.

Motivation:

  • Today it is the most popular media player in the world (Video JS runs on over 400,000 websites);
  • Mature developer community;
  • A large number of possibilities for customizing the appearance and functionality of the player;
  • A large number of already developed skins and plug-ins.
@tyranron tyranron added question Further information is requested RFC Request for comments k::api Related to API (application interface) k::design Related to overall design and/or architecture labels Jan 9, 2019
@tyranron tyranron mentioned this issue Jan 9, 2019
5 tasks
@tyranron
Copy link
Member Author

tyranron commented Jan 9, 2019

@flexconstructor I suppose that in the core of its capabilities Medea Web Client (maybe we can call it Jason later ? 🤔) should provide only protocol implementation/encapsulation and expose some quite raw primitives. This is vital to not restrict any possible implementations/scenarios on top of it.

But, for Video.js, I think, it's easy to provide an adapter/wrapper/binding/connector to be able to plug-in Medea Web Client into Video.js naturally.

However, this is the topic far from initial releases... maybe 0.5/0.6/0.7, or even after 1.0? Will see what we have there.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
k::api Related to API (application interface) k::design Related to overall design and/or architecture question Further information is requested RFC Request for comments
Projects
None yet
Development

No branches or pull requests

2 participants