Re: HTML Slidy remote - a Presentation API demo

Hi Francois, All,

On 22 Jul 2014, at 13:25, Francois Daoust <fd@w3.org> wrote:

> Hi Second Screen Presentation CG,
> 
> In the interest of experimenting with the Presentation API, I updated the Presentation API JS shim that Dominik had created for the initial Presentation API demo to support:
> 1. message passing as specified in the current report
> 2. Chromecast devices through the Google Cast extension in Google Chrome
> 
> I created an "HTML Slidy remote" demo that uses the shim and lets one project a presentation made with HTML Slidy onto a second screen and control it from the initial screen afterwards:
> 
>  http://tidoust.github.io/slidyremote/
> 
> For the source code, look at:
> 
>  https://github.com/tidoust/slidyremote/

Francois - it seems you’ve been doing some coding during the summer months :-) This is *excellent* work, thanks! Chromecast support works flawlessly with my setup (OS X, latest Chrome with the extensions installed).

We'll need to take your feedback from this experiment as it surely will help us iron out the rough edges in the API. This is what I call dogfooding :-)

> The goal of this demo was to test the Presentation API with another type of remote screen and to try out a second screen scenario that did not involve videos.

With your demo, we now have three experiments that demonstrate how the Presentation API can be used in a real world.

Francois - is there an easy way to create a custom category similar to “Reports” on the CG page (http://www.w3.org/community/webscreens/) for “Demos”? I think it would be good to make these demos more visible on the group’s page:

* HTML Slidy remote demo:

  http://tidoust.github.io/slidyremote/

* Experimental Chromium build and the initial video demo:

  http://webscreens.github.io/demo/

* requestShowMedia.js prollyfill and the <video> sharing demo:

  http://webscreens.github.io/requestshowmedia/demo/

Another thing that might be helpful would be to fork the production version of your slidyremote repo to the web screens GH org. You should now have the required privileges to do that.

I think there would be value in keeping the demos under the same organization. Later on, if we evolve the other demos to use your shim, we might consider merging the demos into the same repo, while the shim could live in its own repo. For the time being the demos could stay in their own repos but under the same GH org.

Thanks,

-Anssi

Received on Wednesday, 13 August 2014 15:00:43 UTC