Skip to content
This repository has been archived by the owner on Sep 10, 2022. It is now read-only.

Split this web component to 2 web components #17

Open
FluorescentHallucinogen opened this issue Apr 13, 2017 · 6 comments
Open

Split this web component to 2 web components #17

FluorescentHallucinogen opened this issue Apr 13, 2017 · 6 comments

Comments

@FluorescentHallucinogen
Copy link
Contributor

FluorescentHallucinogen commented Apr 13, 2017

Thanks to @jeffposnick, since version 2.0.0 <google-youtube-upload> supports capturing video directly from a camera via MediaRecorder API.

What about "Do one thing and do it well" philosophy and split <google-youtube-upload> to 2 web components:

  1. web component for uploading video files to YouTube
  2. full-featured (fully configurable via properties) MediaRecorder API web component for recording video from the camera or screen

and share data between these 2 web components use data binding?

From this point of view these 2 web components are independent, they only share data. If you want to replace MediaRecorder API web component with another component, you can easily do that. There is only one requirement, that another web component must provide video data. E.g. it may be a web component which receives a WebRTC video stream from another device or a web component which receives a video file from WebTorrent (BitTorrent over WebRTC) decentralized peer-to-peer network (for more info see https://github.com/feross/webtorrent, https://webtorrent.io).

@FluorescentHallucinogen
Copy link
Contributor Author

For MediaRecorder API web component see: https://github.com/PolymerElements/app-media. 😉

@FluorescentHallucinogen
Copy link
Contributor Author

@cdata @e111077 WDYT?

@e111077
Copy link
Contributor

e111077 commented Jul 7, 2017

Personally I believe that this element should be a media element + a javascript library or class that does the uploading. Though this change cannot happen on this element now. It would be a huge breaking change. Perhaps a new repo would be in order.

@e111077
Copy link
Contributor

e111077 commented Jul 7, 2017

Will come back to this thread when we do the next round of major changes to our library (which should start ~the end of the quarter or Q4)

@FluorescentHallucinogen
Copy link
Contributor Author

@e111077 Could you please provide more info about the next round of major changes to the library? What major changes?

@e111077
Copy link
Contributor

e111077 commented Jul 21, 2017

By major change I mean a version bump from 2.x.y to 3.a.b. With a major version change we can make changes that can break people relying on these elements.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants