You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 25, 2021. It is now read-only.
tyranron opened this issue
Jan 9, 2019
· 1 comment
Labels
k::apiRelated to API (application interface)k::designRelated to overall design and/or architecturequestionFurther information is requestedRFCRequest for comments
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);
@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 freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
k::apiRelated to API (application interface)k::designRelated to overall design and/or architecturequestionFurther information is requestedRFCRequest for comments
@flexconstructor wrote:
The text was updated successfully, but these errors were encountered: