Decouple the Player from the Web Application

[nicolaslevy]

Currently, the MoQ player is built as part of the web application. This issue proposes separating the player into an independent module that can be published and utilized by other web applications. This modular approach will enhance re-usability and make the player easier to integrate into different projects

[emilsas]

To continue this thread, one idea to decouple the player is by creating a WebComponent for the player, ensuring that everything is encapsulated and reusable on any page.

Additionally, if the player is to remain within this repository, it would be beneficial to make all player-related content and the export of pertinent components the primary focus, while moving the example page to a directory named sample.

To address these points, I will open two new issues to track each discussion separately.
#10
#11

[nicolaslevy]

I really like this idea, I think we should close this issue and continue discussions in those @emilsas created

[JoaquinBCh]

With @nicolaslevy we are going to work on this.

[englishm]

I really like the idea of using Web Components. If we implement the <video> element API as described in #10, that should also allow us to use media-chrome's generic UI elements and player.style themes like this great X-mas theme. I imagine we could also port some of the work already done in #12 over to that model, too.

[englishm]

It's worth mentioning that the main way that the player is currently coupled to the site has to do with how the workers are configured to work with different build/packaging systems.

Before the transfork split, @rmallick6806 had a go at sorting that out in a fork, and I found I was able to use that package on a very bare-bones vanilla HTML/JS demo page like so: https://gist.github.com/englishm/1fed0f40de9f05bfc98e5aadd7b65d3b

There may be some details of interest in the commit history of @rmallick6806's moq-js fork, but I think newer work in that repo now tracks transfork changes.

I think if we can not only sort out the worker packaging/build issues, but also go all the way to a generic web component, that would be ideal. Getting to someplace similar to the above bare-bones demo might be a good intermediate milestone along the way for #11.

[JoaquinBCh]

PR created.

[arturparkhisenko]

@englishm And one more cleanup, the PR was merged :)