What remote keys are available for ETV applications?
I am looking to find a defined list of remote keys for ETV application use. If anyone can help on the following questions, I would greatly appreciate it.
1. Page 18 of the Enhanced TV User Interface Guidelines (OC-GL-ETV-UIG-V02-060418) states that the “ETV application is guaranteed access to the following ETV MOK keys across CableLabs, GuideWorks, and TWC ATG TV platforms:” What about other remote keys such as "A", "B", "C", "Help", "FF", "REW", “Pause”, etc - will they still be available for use in ETV apps?
0-9
Select
Up Arrow'
'Down Arrow'
'Left Arrow'
'Right Arrow'
Page Up / Plus
Page Down / Down
2. Also, on the same page, the document states that “the 'exit' is expected to cause the application to immediately transition to a state that causes it to lose focus and remove its presentation from the display. This is true during the prompt phase of the application.” Does the same thing happen when the application is running whereby the exit key removes its presentation from the display?
3. In table 95 of the ETV Binary Interchange Format 1.0 spec (OC-SP-ETV-BIF1.0-I04-070921), a comprehensive list of virtual key codes is listed along with their values and key strings. Is this actually a list of keys available to ETV applications? Or instead is it a list of remote key values for use in ETV?
Thank you in advance,
Roger Towne
Product Manager
ActiveVideo Networks
Thank you for the reply Scott.
What's not clear is whether there is a minimum set of requirements in terms of what keys should be available across all the User Agents. The only thing I could find was on page 18 of the Enhanced TV User Interface Guidelines (previously posted). But that only applies to "CableLabs, GuideWorks, and TWC ATG TV platforms" ... meaning if I am an advertiser and I want to develop an app that runs across UAs for TWC, Comcast and Verizon, the available remote keys may be different. What's more, they may behave differently.
I am in agreement with you. Currently, my understanding is that the authoring tool/User Agent platforms determine which remote keys will be available for use for ETV application developers. From the looks of it, some provide many keys, some provide few keys. Ultimately, that means there will be differing key sets available in the marketplace. What’s more, unless the EBIF spec describes specific, expected, acceptable behaviors for each key (i.e. menu key always brings up the Guide menu), commonality among platforms again will be at risk.
So … essentially I am digging for information to see if there is a common set of keys that all ETV authoring tool/User Agent platforms are required to provide, and what the expected behaviors of this key set will be. If we have this baseline established, minimal key sets will be provided by ETV authoring tool/User Agent platforms and expected behavior for each will be outlined. That way, there will truly be a write-once, run-all platform supporting a pre-defined key set and consistent user experience.
It sounds like CableLabs is working on this ... the upcoming ETV Interop Lab / program apparently is meant to determine gaps in the EBIF spec and to test User Agents so they better align with the spec. Seems like one of the ultimate goals was to ensure there would be a minimum set of features and functionalities across all UAs.
Anyhow, any further input is greatly appreciated.
Roger
community
1. These other keys should also be available in ebif applications.
2. Yes, this should also happen when the application is running. Though, there may be some discrepencies in user agents on whether the application is passed the onkey event prior to terminating or whether use of this key overides termination.
3. From my understanding, this is a list of keys available to ebif applications. Though the available authoring tools do not support all of the keys in the list.
Scott Miller