Hi,
the S2API implementation would be a perfect place to integrate my frontend facilities patch in a way or another.
The patch simply extends the current cDevice API to include some common frontend related statistics (now available only in femon), so that skins and all the other plugins can easily use them. This would simplify the femon plugin and also would enable skin plugins to show for example signal strength, snr, bit error rate, etc., in channel info window.
Also other input plugins (IPTV, pvrinput, analogtv, ..) could implement these new methods and therefore provide some feasible information for femon (or any other plugin) to show up.
http://www.saunalahti.fi/~rahrenbe/vdr/patches/vdr-1.6.0-frontend-facilities...
BR, -- rofa
On 09.12.2008 16:40, Rolf Ahrenberg wrote:
Hi,
the S2API implementation would be a perfect place to integrate my frontend facilities patch in a way or another.
The patch simply extends the current cDevice API to include some common frontend related statistics (now available only in femon), so that skins and all the other plugins can easily use them. This would simplify the femon plugin and also would enable skin plugins to show for example signal strength, snr, bit error rate, etc., in channel info window.
Also other input plugins (IPTV, pvrinput, analogtv, ..) could implement these new methods and therefore provide some feasible information for femon (or any other plugin) to show up.
http://www.saunalahti.fi/~rahrenbe/vdr/patches/vdr-1.6.0-frontend-facilities...
I have been thinking about something along that line for quite a while, and also saw your patch you sent me earlier in a PM. My actual implementation will most likely be somewhat different, but should fulfill the same purpose.
Klaus
On Tue, 9 Dec 2008, Klaus Schmidinger wrote:
I have been thinking about something along that line for quite a while, and also saw your patch you sent me earlier in a PM. My actual implementation will most likely be somewhat different, but should fulfill the same purpose.
This is off-topic, but what's the status of implementing the parental rating and content descriptions for events? My patch has existed for ages, so should I simply forget it or refactor according to received feedback (non-existent currently :) ? The interface could be cleaner as always and data should also be stored into epg.data...
http://www.saunalahti.fi/~rahrenbe/vdr/patches/vdr-1.6.0-parentalrating-cont...
BR, -- rofa
On 09.12.2008 18:54, Rolf Ahrenberg wrote:
On Tue, 9 Dec 2008, Klaus Schmidinger wrote:
I have been thinking about something along that line for quite a while, and also saw your patch you sent me earlier in a PM. My actual implementation will most likely be somewhat different, but should fulfill the same purpose.
This is off-topic, but what's the status of implementing the parental rating and content descriptions for events? My patch has existed for ages, so should I simply forget it or refactor according to received feedback (non-existent currently :) ? The interface could be cleaner as always and data should also be stored into epg.data...
http://www.saunalahti.fi/~rahrenbe/vdr/patches/vdr-1.6.0-parentalrating-cont...
To be honest, there's currently so much to do (and I'm just catching up again with VDR development) that this has very little priority to me. I'll leave this in my inbox, in case I come across it again at some point ;-)
Klaus