W3C home > Mailing lists > Public > public-secondscreen@w3.org > June 2015

Re: Announcing the Presentation-Cast polyfill and slideshow demo

From: Mark Watson <watsonm@netflix.com>
Date: Tue, 2 Jun 2015 10:55:50 -0700
Message-ID: <CAEnTvdCinVS4H9Adv=TcfnWUT1RJ91GVK4krs7f1=4Agd1Z_rQ@mail.gmail.com>
To: "mark a. foltz" <mfoltz@google.com>
Cc: Fran├žois Daoust <fd@w3.org>, "Rottsches, Dominik" <dominik.rottsches@intel.com>, "Kostiainen, Anssi" <anssi.kostiainen@intel.com>, Mark Scott <markdavidscott@google.com>, Anton Vayvod <avayvod@google.com>, "public-secondscreen@w3.org" <public-secondscreen@w3.org>, "public-webscreens@w3.org" <public-webscreens@w3.org>
All,

I have created a pull request [1] to Mark's presentation-case polyfill [2]
implementing a simple version of DIAL integration, as presented and
demonstrated at the face-to-face.

Mark's original SlidyRemote demo probably needs updating to work with the
new polyfill, so I wouldn't expect Mark to accept the PR until that is done.

The new code is here [3].

... Mark

[1] https://github.com/mfoltzgoogle/presentation-cast/pull/1
[2] https://github.com/mfoltzgoogle/presentation-cast
[3] https://github.com/mwatson2/presentation-cast
<https://github.com/mfoltzgoogle/presentation-cast>

On Fri, Jan 16, 2015 at 1:44 PM, mark a. foltz <mfoltz@google.com> wrote:

> Francois, Dominik, group members,
>
> I'm pleased to announce a (mostly-)complete polyfill [1] for the
> Presentation API draft specification [2] using the Google Cast Sender SDK
> for Chrome [3].  It includes a simple demo Web application starting and
> controlling a photo slideshow [4].
>
> This polyfill is more limited in scope than the slidyremote one published
> earlier by Francois [5], but is more up-to-date with the current
> specification.   It is only compatible with Cast devices and only
> implements the opener/controller aspects of the Presentation API.
>
> I plan to extend it to implement more of the API, including the
> joinSession and presentation-side behaviors, and to have a fallback for
> those without access to a Cast device.
>
> I also plan to implement a prototype of a remotable <video> tag and a
> multi-player game to help prototyping relevant aspects of the API.
> Finally, it may be possible to prototype the 1-UA situation using the
> tab-casting features of the Cast extension, but this will require some more
> investigation.
>
> Once the polyfill is more feature complete I hope we can use it to analyze
> the current state of the specification.
>
> m.
>
> [1] https://github.com/mfoltzgoogle/presentation-cast
> [2] http://w3c.github.io/presentation-api/
> [3] https://developers.google.com/cast/docs/reference/chrome/
> [4] https://mfoltzgoogle.github.io/presentation-cast/demo/slideshow/
> [5] https://github.com/webscreens/slidyremote
>
> P.S. In order to send messages from the presentation document back to the
> controlling document, I needed to fork slidyremote and make a small patch
> to the receiver shim [6].
>
> [6] https://github.com/mfoltzgoogle/slidyremote
>
>
Received on Tuesday, 2 June 2015 17:56:19 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:18:56 UTC