Liushouqun (Talk | contribs) |
(→MeeGo TV Browser) |
||
| Line 3: | Line 3: | ||
== 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 | + | 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 | + | 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 | + | 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 == | == 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 | + | 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 == | == 3, Overview == | ||
| - | The internet world has created | + | 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. TV needs | + | 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 39: | Line 39: | ||
* [[TV Browser Control API]] | * [[TV Browser Control API]] | ||
* [[TV Browser Javascript API]] | * [[TV Browser Javascript API]] | ||
| - | * [[TV Browser Video HW | + | * [[TV Browser Video HW Acceleration]] |
* [[TV Browser Transparency Management]] | * [[TV Browser Transparency Management]] | ||
| Line 56: | Line 56: | ||
== 6, How to Build the MeeGo TV browser with UMMS support == | == 6, How to Build the MeeGo TV browser with UMMS support == | ||
| - | Visit "How to build" wiki page to build browser | + | Visit the "How to build" wiki page to build the browser |
http://wiki.meego.com/TV_Browser_How_to_Build | http://wiki.meego.com/TV_Browser_How_to_Build | ||
Contents |
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.
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 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.
Requirements
User Manual
Related Topics
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
Visit the "How to build" wiki page to build the browser http://wiki.meego.com/TV_Browser_How_to_Build