Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Extensibility Goals
Enable applications that truly extend the user experience look & feel on par with native apps Build applications that run in the network Build applications which leverage existing web data Evolve to richer environments and development tools
Microsoft Confidential 2
February 2009
PF application lifecycle
1 Author button visually
Author Publish
Test Simulator
Consume
3 ASP.NET knows which client requested control and generates appropriate XML
4 Button rendered as though native to client environment. e.g. Looks like core EPG`
February 2009 Microsoft Confidential 4
Microsoft Confidential
ASP.NET
Clients connect through http/https as any web app Pages are generated dynamically on the server Each client request is handled in its own context Rich server side development env: auth/authz, caching, .Net runtime, skins/themes
Microsoft Confidential 6
ASP.NET
World-class tool for building web applications and services Splits presentation and navigation (client) from application logic (server) Pages dynamically generated by server upon client requests (e.g. clicking buttons) Pages rendered to client capabilities Applications written without knowledge of markup Full .NET framework on server for implementing application logic
February 2009 Microsoft Confidential 7
PF Visual Authoring
Extensible controls
Visual Authoring
11 years of R&D, refinement Rich Debugging to promote low runtime errors Visual Designers for rapid application development Data bindings to quickly add heterogeneous data sources
February 2009 Microsoft Confidential 8
PF PC Simulator
Test applications as you write them on PC Decouple application development from full head-end Dramatic CAPEX reduction in # of STBs needed Enable larger developer audience
February 2009 Microsoft Confidential 9
Declarative actions
Intrinsic client functions that result from control interaction Tune, Show, Hide, Open, Sound
Events
Sent/received by controls Timers, Clicks, Key Press, Triggers
February 2009 Microsoft Confidential 10
Controls
Integrated in Visual Studio Generate private markup for Mediaroom box Developer does not have to deal with markup syntax and quirks All necessary properties are exposed at both design and runtime Easy to integrate with Mediaroom servers and any other web services
February 2009 Microsoft Confidential 11
Microsoft Confidential
12
Actions
Expose common client functionality. Much like an API, but used declaratively.
Actions Tune Show Set Audio Sound Navigate Play, Stop, Skip Focus Hide Refresh Submit Log/Debug Timers Animation
February 2009
Microsoft Confidential
Page 13
February 2009
Microsoft Confidential
Page 14
Triggering
Triggers provisioned by the operator Defined by a variety of trigger-able events Patterns in text, other triggers, programme/time Flexible actions in response to triggers Support for content pre-positioning Store-and-forward response collection
7/28/2009
Microsoft Confidential
15
Data Binding
Controls populate themselves with data asynchronously from data source APIs Similar to AJAX web pages Controls do this intrinsically No client code needed, just attach control to an API reference Generic APIs for accessing XML data Chunking APIs for large data sources
February 2009 Microsoft Confidential 16
2009 Microsoft Corporation. All rights reserved. Microsoft, Mediaroom, Segoe font and the Microsoft Mediaroom logo are trademarks of the Microsoft group of companies in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.