Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add facility for the opening page to add cloud paired screens as presentation targets #61

Open
markafoltz opened this issue Feb 25, 2015 · 3 comments
Labels

Comments

@markafoltz
Copy link
Contributor

The assumption thus far is that the user agent is the only entity that can determine what screens are available for presentation. However, some sites will be able to access screens entirely based on interaction over the Internet, i.e. using XHR or WebSockets to a server, or perhaps WebRTC. Ideally these should be offered to the user as presentation targets alongside browser-discovered screens, so that the site author doesn't have to offer two distinct presentation mechanisms.

Considerations:

  • The browser would only be responsible for offering the screen as a choice, and informing the app that it was chosen for presentation. It would not be responsible for any further interaction.
  • These screens would need to be clearly and distinctly labeled as belonging to the site, and not part of the automatic discovery process by the browser.

I think this is a useful enhancement that would allow innovation and extension over browser-provided presentation capabilities.

@markafoltz markafoltz added the v2 label Feb 25, 2015
@louaybassbouss
Copy link
Contributor

Hi Mark, I like your proposal. I already experimented with something similar to this the implementation in [1] is purely JavaScript (sorry it is minified) and offers same Presentation API interfaces (not the latest version of the API). It communicates with our server via WebSockets. If you like to try some examples you can open [2] that acts as Display in a Browser of your choice (tested in chrome) and then the example applications [3..6] in the Browser on the same or any other device. you can replace the room value 123456 with any other value. please make sure that the room is the same in all URLs.
Your proposal will allow us to replace the selection dialog (we use confirm dialog :( ) with the native dialog provided by the UA.

[1] http://famium.fokus.fraunhofer.de/js/webscreens.all.min.js

[2] http://famium.fokus.fraunhofer.de/display.html#room=123456&name=Display1

[3] http://famium.fokus.fraunhofer.de/apps/helloworld/sender.html#room=123456

[4] http://famium.fokus.fraunhofer.de/apps/youtube/sender.html#room=123456

[5] http://famium.fokus.fraunhofer.de/apps/flickr/sender.html#room=123456

[6] http://famium.fokus.fraunhofer.de/apps/slides/sender.html#room=123456

@tidoust
Copy link
Member

tidoust commented Sep 26, 2016

For reference, see discussion at TPAC

@markafoltz markafoltz added the F2F label Sep 21, 2017
@markafoltz
Copy link
Contributor Author

Labeling for possible followup at TPAC.

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

No branches or pull requests

5 participants