AT&T U-verse Enabled. How to Respond to On-screen User Events. Publication Date: November 1 st, 2013

Transcription

1 AT&T U-verse Enabled How to Respond to On-screen User Events Publication Date: November 1 st, 2013

2 Legal Disclaimer This document and the information contained herein (collectively, the "Information") is provided to you (both the individual receiving this document and any legal entity on behalf of which such individual is acting) ("You" and "Your") by AT&T, on behalf of itself and its affiliates ("AT&T") for informational purposes only. AT&T is providing the Information to You because AT&T believes the Information may be useful to You. The Information is provided to You solely on the basis that You will be responsible for making Your own assessments of the Information and are advised to verify all representations, statements and information before using or relying upon any of the Information. Although AT&T has exercised reasonable care in providing the Information to You, AT&T does not warrant the accuracy of the Information and is not responsible for any damages arising from Your use of or reliance upon the Information. You further understand and agree that AT&T in no way represents, and You in no way rely on a belief, that AT&T is providing the Information in accordance with any standard or service (routine, customary or otherwise) related to the consulting, services, hardware or software industries. AT&T DOES NOT WARRANT THAT THE INFORMATION IS ERROR-FREE. AT&T IS PROVIDING THE INFORMATION TO YOU "AS IS" AND "WITH ALL FAULTS." AT&T DOES NOT WARRANT, BY VIRTUE OF THIS DOCUMENT, OR BY ANY COURSE OF PERFORMANCE, COURSE OF DEALING, USAGE OF TRADE OR ANY COLLATERAL DOCUMENT HEREUNDER OR OTHERWISE, AND HEREBY EXPRESSLY DISCLAIMS, ANY REPRESENTATION OR WARRANTY OF ANY KIND WITH RESPECT TO THE INFORMATION, INCLUDING, WITHOUT LIMITATION, ANY REPRESENTATION OR WARRANTY OF DESIGN, PERFORMANCE, MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, OR ANY REPRESENTATION OR WARRANTY THAT THE INFORMATION IS APPLICABLE TO OR INTEROPERABLE WITH ANY SYSTEM, DATA, HARDWARE OR SOFTWARE OF ANY KIND. AT&T DISCLAIMS AND IN NO EVENT SHALL BE LIABLE FOR ANY LOSSES OR DAMAGES OF ANY KIND, WHETHER DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, PUNITIVE, SPECIAL OR EXEMPLARY, INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF BUSINESS PROFITS, BUSINESS INTERRUPTION, LOSS OF BUSINESS INFORMATION, LOSS OF GOODWILL, COVER, TORTIOUS CONDUCT OR OTHER PECUNIARY LOSS, ARISING OUT OF OR IN ANY WAY RELATED TO THE PROVISION, NON-PROVISION, USE OR NON-USE OF THE INFORMATION, EVEN IF AT&T HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH LOSSES OR DAMAGES. IOS is a trademark or registered trademark of Cisco in the U.S. and other countries. i

3 Table of Contents Contents 1 Introduction Additional Resources Responding to on-screen user events Send Notification Example... 3 ii

4 Table of Examples Example 3-1: Obtaining a reference to the receiver Example 3-2: setuplistencommands method... 4 Example 3-3: registerfornotifications... 5 Example 3-4: uvesettopboxcustomeventoccurred... 5 Example 3-5: PageForName... 8 iii

5 1 Introduction This document is intended for developers who need a host-mode application that can send notifications to a device application when an event occurs on the TV screen. For example, if the user presses a button on the screen, you could update the UI on the device so that it could respond to the event. This document contains an example that sends notifications when one of three buttons (Red, Blue, and Green) is pressed. 1.1 Additional Resources In addition to this document, you may find the following documents helpful when developing U-verse Enabled ios apps. How to Write Your First AT&T U-verse Enabled ios App How to Setup a U-verse Enabled Project in Xcode In addition, you can find more technical information on the AT&T Developer Program web site. See Develop AT&T U-verse Enabled Apps and select the development platform that you are interested in. Page 1 of 8

6 2 Responding to on-screen user events The uvelistencommand and uveactioncustom objects are needed for event notifications. The uvelistencommand object is used to set up a device so that it can listen for an event. This set up is required before an object can receive a notification. The uvelistencommand object has the following properties: Event: This property specifies the name of the event (NSString) and has to be prefixed with urn:. For example, for an event named myevent, the parameter value would be: urn:myevent ExpiryDate: This property specifies the date and time (NSDate) for time limited notifications. If you do not wish to have time limited notifications, set this parameter to nil. The uveactioncustom object is a uveaction that you set up to be triggered by an event in the host-mode application. The example in this document attaches an instance of the uveactioncustom to the onclick property of an on-screen button so that each time the button is clicked this action is invoked. The uveactioncustom object has the following properties: name: This property is inherited from uveaction. It specifies the name of the action that can be used to reference the object from other uvegadgets at runtime. customeventname: This property specifies the name of the event and must match the event property of the uvelistencommand object. The value of the customeventname property must be prefixed with urn:. For example, for an event named myevent the parameter value will be urn:myevent. data: This property specifies data that you can provide to the event that is called. In Example 3-1, the uvelistencommand object is set up when the uveappliationdelegate is set up, and the uveactioncustom objects are attached to the onclick properties of the uvebuttons object. Page 2 of 8

7 3 Send Notification Example In the following example the uvelistencommand object is set up when the uveappliationdelegate is set up, and the uveactioncustom objects are attached to the onclick properties of the uvebuttons. In the default initializer, a reference to the receiver that is in use is obtained and then a check is made to see whether the application server is started. If the application server is not started, this example starts the application server and sets this class as the delegate. In addition, the listen commands are set up in a method that is called from here. If the application server is already started, the page is displayed. Obtain Reference to Receiver 1 - (id)initwithnibname:(nsstring *)nibnameornil bundle:(nsbundle *)nibbundleornil 2 { 3 self = [super initwithnibname:nibnameornil bundle:nibbundleornil]; 4 if (self) { 5 UverseConnectedManager *uvcmgr = [UverseConnectedManager sharedmanager]; 6 _associatedstb = uvcmgr.mostrecentlyengagedsettopbox; 7 8 if (uvcmgr.appserverstate!= AppServerStarted){ 9 [self setuplistencommands]; 10 [_associatedstb starttvapplicationwithdelegate:self]; 11 } 12 else { 13 [_associatedstb displaypagewithname:@"test"]; 14 } 15 } 16 return self; 17 } Example 3-1: Obtaining a reference to the receiver. Page 3 of 8

8 In the setuplistencommands method (see Example 3-2) each listen command is implemented. The commands then notify the device, when the event matching the name of the event argument occurs on the receiver. (Note that event names need to be prefixed with urn:.) After the command is created it is sent to the receiver. setuplistencommands Method 1 -(void)setuplistencommands 2 { 3 // setup a listen command to send a notification to the device 4 // with the red button is pressed on screen 5 uvelistencommand *redlisten = [[uvelistencommand alloc] initwithevent:@"urn:red" expirydate:nil]; 6 [selfassociatedstb sendsettopboxcommand:redlisten]; 7 [redlisten release]; 8 9 // setup a listen command to send a notification to the device 10 // with the blue button is pressed on screen 11 uvelistencommand *bluelisten = [[uvelistencommand alloc] initwithevent:@"urn:blue" expirydate:nil]; 12 [self.associatedstb sendsettopboxcommand:bluelisten]; 13 [bluelisten release]; // setup a listen command to send a notification to the device 16 // with the green button is pressed on screen 17 uvelistencommand *greenlisten = [[uvelistencommand alloc] initwithevent:@"urn:green" expirydate:nil]; 18 [self.associatedstb sendsettopboxcommand:greenlisten]; 19 [greenlisten release]; 20 } 21 } Example 3-2: setuplistencommands method Page 4 of 8

9 In the registerfornotifications class, along with other notifications, this example adds this class as an observer for the uvesettopboxcustomeventoccurred notification, which will set the uvestbcustomevent as the callback. registerfornotifications Class 1 -(void)registerfornotifications 2 { 3 [[NSNotificationCenter defaultcenter] addobserver:self selector:@selector(uvestbcustomevent:) name:uvesettopboxcustomeventoccurred object:nil]; 4 [[NSNotificationCenter defaultcenter] addobserver:self selector:@selector(uvestbcommandsucceeded:) name:uvesettopboxcommanddidsucceed object:nil]; 5 [[NSNotificationCenter defaultcenter] addobserver:self selector:@selector(uvestbcommandfailed:) name:uvesettopboxcommanddidfail object:nil]; 6 } Example 3-3: registerfornotifications class In the uvesettopboxcustomeventoccurred callback method, this example checks the value of the uvesettopboxcustomeventkey property and then sets the background color of the device s view to match the color of the button that is pressed. uvesettopboxcustomeventoccurred Callback 1 -(void)uvestbcustomevent:(nsnotification *)note 2 { 3 NSLog(@"CUSTOM: %@", note); 4 id userinfo = [note valueforkey:@"userinfo"]; 5 if ([[userinfo valueforkey:@"uvesettopboxcustomeventkey"] 6 { 7 self.view.backgroundcolor = [UIColor redcolor]; 8 } 9 else if ([[userinfo valueforkey:@"uvesettopboxcustomeventkey"] 10 { 11 self.view.backgroundcolor = [UIColor bluecolor]; 12 } 13 else if ([[userinfo valueforkey:@"uvesettopboxcustomeventkey"] 14 { 15 elf.view.backgroundcolor = [UIColor greencolor]; 16 } 17 } Example 3-4: uvesettopboxcustomeventoccurred callback Page 5 of 8

10 The device is now set up to receive the custom event notifications and to respond to each event. The next part will be to create the page that is displayed on the receiver, along with the actions that are attached to the on-screen buttons and that cause the custom event notification to be sent when these actions are invoked. This will all be done in the PageForName method. The first part of this method is a check to determine whether the screen is widescreen formatted. If the screen is widescreen, this example then sets the screen to be the widescreen size for standard definition. It is generally recommended to use this screen size when possible as it reduces the texture memory footprint of your application and the receiver will scale the content to high definition when a high definition screen is attached to the receiver. In the rest of the pageforname method, this example creates three buttons to display on the screen. When creating buttons, this includes specifying the name of the button, the text to be displayed on the button, and the frame of the button in the screen. This example then sets the background color and the focusbackgroundcolor property to the color of the button, and then adds the button to the page. The focusbackgroundcolor property should always be set to the same color as the button. When you set this property, the button will be highlighted when it has the on-screen focus, but it will not use the default highlight color which might not integrate with your color scheme. Page 6 of 8

11 This example then create the custom action. The important argument here is the argument for the customeventname property. This name must be the same as the name that you set up in the uvelistencommand and it must be prefixed with urn:. The example then adds the action to the page and sets the action to be the onclick handler for the button. This is repeated for the red, green, and blue buttons. PageForName Method 1 -(uvepage *)pageforname:(nsstring *)pagename withparams:(nsmutabledictionary *)params forframe:(cgrect)tvframe 2 { 3 if ([pagename isequaltostring:@"test"]){ 4 NSLog(@"START pageforname:%@", pagename); 5 self.page = [[uvepage alloc] initpagewithname:@"test"]; 6 if (tvframe.size.width > 640){ 7 self.page.frame = CGRectMake(0,0,854,480); 8 } 9 10 self.page.alpha = 1.0; 11 //self.page.backgroundcolor = [UIColor whitecolor]; uvebutton *redbutton = [[uvebutton alloc] initbuttonwithname:@"redbutton" text:@"red" frame:cgrectmake(220, 200, 100, 50)]; 14 redbutton.backgroundcolor = [UIColor redcolor]; 15 redbutton.focusbackgroundcolor = [UIColor redcolor]; 16 [self.page addgadget:redbutton]; 17 uveactioncustom *redcustomaction = [[uveactioncustom alloc] initactionwithname:@"redcustomaction" customeventname:@"urn:red" data:nil]; 18 [self.page addaction:redcustomaction]; 19 redbutton.onclick = redcustomaction; 20 [redbutton release]; 21 [redcustomaction release]; uvebutton *bluebutton = [[uvebutton alloc] initbuttonwithname:@"bluebutton" text:@"blue" frame:cgrectmake(370, 200, 100, 50)]; 24 bluebutton.backgroundcolor = [UIColor bluecolor]; 25 bluebutton.focusbackgroundcolor = [UIColor bluecolor]; 26 [self.page addgadget:bluebutton]; 27 uveactioncustom *bluecustomaction = [[uveactioncustom alloc] initactionwithname:@"bluecustomaction" customeventname:@"urn:blue" data:nil]; 28 [self.page addaction:bluecustomaction]; 29 bluebutton.onclick = bluecustomaction; 30 [bluebutton release]; 31 [bluecustomaction release]; Page 7 of 8

12 32 33 uvebutton *greenbutton = [[uvebutton alloc] initbuttonwithname:@"greenbutton" text:@"green" frame:cgrectmake(520, 200, 100, 50)]; 34 greenbutton.backgroundcolor = [UIColor greencolor]; 35 greenbutton.focusbackgroundcolor = [UIColor greencolor]; 36 [self.page addgadget:greenbutton]; 37 uveactioncustom *greencustomaction = [[uveactioncustom alloc] initactionwithname:@"greencustomaction" customeventname:@"urn:green" data:nil]; 38 [self.page addaction:greencustomaction]; 39 greenbutton.onclick = greencustomaction; 40 [greenbutton release]; 41 [greencustomaction release]; 42 return self.page; 43 } 44 else { 45 return nil; 46 } 47 } Example 3-5: PageForName method Page 8 of 8