7 replies to this topic

[daddelfalk]

Hi,

attached you will find the required Patches, that I have created to add HbbTV Digitaltext Support in E2. The Patches already passed my QS-Phase, everything works like a charm.

This enables HbbTV Digitaltext Support for ET-WebBrowser Plugin. For sure the Plugin needs to be adjusted or upgraded to a newer Version to make use of the Digitaltext feature.
For the other STBs nothing is changed, as they don't support HbbTV, yet. Therefore always legacy Teletext will be opened.

If available Digitaltext will be opended on Keypress "TEXT". Otherwise legacy teletext will be displayed. And long Keypress on "TEXT"-Button opens legacy Teletext. And you will also be notified if your Box is not connected to Internet, but Digitaltext is available, or Service has no legacy teletext available, but only Digitaltext. And on top of this: Teletext won't be opened, when Service will not broadcast any TXTPID, so no need for strange "Teletext Searching actions" will take place, anymore. All things are fully compliant to the ETSI HbbTV Specification.


Hope you enjoy it.

Attached Files

•  HbbTV-Digitaltext-Support.zip   3.38KB   49 downloads

Edited by daddelfalk, 2 December 2011 - 17:24.

[pieterg]

Teletext won't be opened, when Service will not broadcast any TXTPID, so no need for strange "Teletext Searching actions" will take place, anymore.

this was actually a desired (or should I say 'demanded'...) option by some users, so we purposely added support for this

[daddelfalk]

Hi,

this "wished behaviour" is crap as it actually does not add any useful use case scenario. And do not displaying anything, when both Digitaltext and Teletext are available, is fully up to the HbbTV Specification, which should be followed in Software Implementations.

Teletext won't be opened, when Service will not broadcast any TXTPID, so no need for strange "Teletext Searching actions" will take place, anymore.

this was actually a desired (or should I say 'demanded'...) option by some users, so we purposely added support for this

[pieterg]

maybe we are referring to different things.
What I meant was, when you have no txtpid associated with the current channel (and no digitaltext), you can still open tuxtxt, and select any txtpid on the current transponder.
I think there is no problem to keep that as it was, apparently people are using this feature.

[daddelfalk]

Hi Pieter,

yes, i know it. You can keep the "Feature" by simply removing the TXTPID-Check, but keep in mind, that this behaviour is outdated and not compliant to the HbbTV specification anymore.

Maybe people should vote, if this "Feature" is really used by anyone out there.

[pieterg]

Hi Pieter,

yes, i know it. You can keep the "Feature" by simply removing the TXTPID-Check, but keep in mind, that this behaviour is outdated and not compliant to the HbbTV specification anymore.

Maybe people should vote, if this "Feature" is really used by anyone out there.

this behaviour not related to hbbtv specifications, it's up to us to support it or not

[daddelfalk]

Hi Pieter,

it is clearly described in ETSI Sepc Page 22 Case E., if no Teletext and Digitaltext is available, nothing "should" happen.
For me it overrules tradional behaviour and in commerical HbbTV Implementations it is implemented this way.

But if you evaluate the word "SHOULD" in HbbTV-Specs as obligatory and not as "MUST", I think we can follow your direction and keep up the "Transponder Searching Feature", so people won't be worry about a "lost" feature. When the TXTPID Check is getting removed, I think there is nothing more, that would be against commiting the Patches.

Edited by daddelfalk, 3 December 2011 - 13:08.

[mogli123]

hello daddelfalk

your idea is nice, i think many peoples like also...
i hope this can be imported/patched on git

nice work