Meego Wiki
Views

TV Browser

From MeeGo wiki
(Difference between revisions)
Jump to: navigation, search
(→3, Overview)
 
(8 intermediate revisions not shown)
Line 1: Line 1:
= MeeGo TV Browser =
= MeeGo TV Browser =
-
  1 Short expression of the need
+
== 1, Short expression of the need ==
-
--------------------------------
+
-
TV industry and in particular IPTV has used browsers for years to create TV portals. In IPTV specialised companies such as ANT (Cambridge, UK), Opera (Oslo, Norway) or Access (Tokyo, Japan) have created specialised browser for these use cases.
+
-
These specialised browsers were optimized for TV at the detriment of their possibility to surf the open internet.
+
-
As today the requirement to browse the open internet is imposed on TV, there is a need to provide an “open internet” capable browser which can be integrated in a TV and can be used to create TV portals.
+
-
These portals are commonly used to provide the business logic which run locally on the device an is written in AJAX. To enable the control of the TV and Media Centre an API accessible from JavaScript must be added to the Browser.
+
-
  2 Purpose/audience
+
The TV industry, and in particular IPTV, has used browsers for years to create TV portals. In IPTV, specialized companies, such as ANT (Cambridge, UK), Opera (Oslo, Norway), or Access (Tokyo, Japan) have created specialized browsers for these use cases.
-
--------------------
+
These specialized browsers were optimized for TV, at the detriment of their potential to surf the open internet.
-
The purpose of this document is to provide an understanding of the solution which has been developed by the MeeGo TV project. It addresses the developers who will have to deliver a working implementation.
+
Today, the requirement to browse the open internet are imposed on TV, so there is a need to provide an “open internet” capable browser, which can be integrated in a TV and can be used to create TV portals.
 +
These portals are commonly used to provide the business logic which runs locally on the device and is written in AJAX. To enable the control of the TV and Media Center, an API accessible from JavaScript must be added to the browser.
-
  3 Overview
+
== 2, Purpose/audience ==
-
-------------
+
The purpose of this document is to provide an understanding of the solution which has been developed by the MeeGo TV project. It addresses the developers who will deliver a working implementation.
-
The internet world has created browser for PC. Assuming not only a mouse and a keyboard, but also a 50 cm viewing with a multi windows presentation layer and a skilled human who drive the beast.
+
 
-
Unfortunately, a TV has neither a keyboard or a mouse, the vision is done from 3m, there is no windowing concept and the Live TV presentation remains in control of the UI all the time. TV needs is a browser which address some critical issues.
+
== 3, Overview ==
 +
The internet world has created browsers for the PC. Assuming not only a mouse and a keyboard, but also 50 cm viewing with a multiple window presentation layer and a skilled human driving the beast.
 +
Unfortunately, a TV has neither a keyboard or a mouse, the vision is done from 3m, there is no windowing concept, and the Live TV presentation remains in control of the UI all the time. The TV needs a browser which address some critical issues.
Controllable by an external application.
Controllable by an external application.
* Instant start
* Instant start
Line 21: Line 19:
* Support HW accelerated Video
* Support HW accelerated Video
* Asset browsing
* Asset browsing
-
* Web API for TV (conform to OpenIPTV OIPF DAE specification)
+
* Web API for TV (conform to [http://www.oipf.tv/docs/Release2/V2.1/OIPF-T1-R2-Specification-Volume-5-Declarative-Application-Environment-v2_1-2011-06-21.pdf OpenIPTV Forum DAE specification])
-
** Open IPTV broadcasting API
+
** Open IPTV Forum DAE configuration API (section 7.3)
-
** Open IPTV video playback control API
+
** Open IPTV Forum DAE broadcasting API (section 7.13)
-
** Open IPTV system configuration API
+
** Open IPTV Forum DAE video playback control API (section 7.14)
-
* Remote control integration
+
* [[TV Browser Control API]]
 +
* [[TV Browser Javascript API]]
 +
* [[TV Browser Video HW acceleration]]
 +
* [[TV Browser Transparency Management]]
-
 
+
== 4, Documentation ==
-
  4 Documentation
+
-
----------------------------
+
Requirements
Requirements
* [[File:Meego TV JavaScriptAPI requirement.pdf | Requirement for a TV Javascript API]]<br>
* [[File:Meego TV JavaScriptAPI requirement.pdf | Requirement for a TV Javascript API]]<br>
* [[File:Meego TV Browser V0.2.odt | Requirement for TV Browser]] <br>
* [[File:Meego TV Browser V0.2.odt | Requirement for TV Browser]] <br>
 +
* [http://www.oipf.tv/docs/Release2/V2.1/OIPF-T1-R2-Specification-Volume-5-Declarative-Application-Environment-v2_1-2011-06-21.pdf Declarative Application Environment V2.1]
User Manual
User Manual
Line 44: Line 44:
* Universal Multi Media Service [[umms | UMMS]]
* Universal Multi Media Service [[umms | UMMS]]
-
 
+
== 5, Where is the code ==
-
  5 Where is the code
+
-
-----------------
+
Visit MeeGo OBS and search for meego-tv-browser  
Visit MeeGo OBS and search for meego-tv-browser  
https://build.meego.com
https://build.meego.com
or directly in the GIT repo<br>
or directly in the GIT repo<br>
-
http://meego.gitorious.org/meego-middleware/meego-tv-browser<br>
+
http://meego.gitorious.org/meego-middleware/meego-tv-browser   git branch 874-base-webkit <br>
http://meego.gitorious.org/meego-middleware/mutter-meego-tv<br>
http://meego.gitorious.org/meego-middleware/mutter-meego-tv<br>
 +
 +
 +
== 6, How to Build the MeeGo TV browser with UMMS support ==
 +
Visit the "How to build" wiki page to build the browser
 +
http://wiki.meego.com/TV_Browser_How_to_Build

Latest revision as of 01:07, 4 July 2012

Contents

MeeGo TV Browser

1, Short expression of the need

The TV industry, and in particular IPTV, has used browsers for years to create TV portals. In IPTV, specialized companies, such as ANT (Cambridge, UK), Opera (Oslo, Norway), or Access (Tokyo, Japan) have created specialized browsers for these use cases. These specialized browsers were optimized for TV, at the detriment of their potential to surf the open internet. Today, the requirement to browse the open internet are imposed on TV, so there is a need to provide an “open internet” capable browser, which can be integrated in a TV and can be used to create TV portals. These portals are commonly used to provide the business logic which runs locally on the device and is written in AJAX. To enable the control of the TV and Media Center, an API accessible from JavaScript must be added to the browser.

2, Purpose/audience

The purpose of this document is to provide an understanding of the solution which has been developed by the MeeGo TV project. It addresses the developers who will deliver a working implementation.

3, Overview

The internet world has created browsers for the PC. Assuming not only a mouse and a keyboard, but also 50 cm viewing with a multiple window presentation layer and a skilled human driving the beast. Unfortunately, a TV has neither a keyboard or a mouse, the vision is done from 3m, there is no windowing concept, and the Live TV presentation remains in control of the UI all the time. The TV needs a browser which address some critical issues. Controllable by an external application.

4, Documentation

Requirements

User Manual

Related Topics

  • Universal Multi Media Service UMMS

5, Where is the code

Visit MeeGo OBS and search for meego-tv-browser https://build.meego.com

or directly in the GIT repo
http://meego.gitorious.org/meego-middleware/meego-tv-browser git branch 874-base-webkit
http://meego.gitorious.org/meego-middleware/mutter-meego-tv


6, How to Build the MeeGo TV browser with UMMS support

Visit the "How to build" wiki page to build the browser http://wiki.meego.com/TV_Browser_How_to_Build

Retrieved from "http://wiki.meego.com/TV_Browser"
Personal tools