Re: Filtering out non compatible displays (was: Draft of Second Screen Presentation Working Group Charter available)

Hi Anssi,

>> The point is that we should not show the user the
"cast/fling/present" icon at all if there are no suitable screens available.

> This is a good requirement, but it seems we haven’t yet settled on the
approach as there are pros and cons for all the approaches discussed so far.

I agree that more discussion is needed regarding this behaviour.

There are arguments for showing the icon permanently to avoid confusion,
similar to a wifi icon which remains visible but may change state/colour
when no networks are available.


Daniel Davis


On 10/06/14 03:28, Kostiainen, Anssi wrote:
> On 09 Jun 2014, at 19:08, mark a. foltz <mfoltz@google.com> wrote:
> 
>> MarkW, I am happy to help with this, as our project has implemented this ability for Cast and DIAL.
> 
> MarkFo - thanks for volunteering to help!
> 
>> Anssi, it would be helpful to be specific as to what you expect to be delivered to the group:
>>
>> (1) Use cases demonstrating the feature
>> (2) API proposal or proposals
>> (3) Interoperability test suites or requirements per earlier thread
>> (4) Prototype implementations?
> 
> Anything that helps the group make progress and be productive with this issue is good. I’d start with use cases and requirements, scrutinize them, ensure they are well understood and address real problems end users face. Then I’d move on to evaluate existing solutions, and experiment with new solutions if the existing ones do not address the requirements.
> 
> There’s no strict format how to do this. You can use e.g. the W3C wiki or anything else that works for you to document your findings as long as you keep the group in the loop (e.g. ping the mailing list for feedback).
> 
> Thanks,
> 
> -Anssi
>

Received on Wednesday, 2 July 2014 07:27:24 UTC