Mailing List archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[vdr] Re: Remote-Timers (was: Re: vdr died just after start)
Am Sam, 2003-05-03 um 13.28 schrieb Sascha Volkenandt:
> On Freitag, 2. Mai 2003 20:52 Rene Bartsch wrote:
> > What about adding a new timers entry (e.g. named Remote-Timers)?
> On Freitag, 2. Mai 2003 21:45 Rantanen Teemu wrote:
> > I'm not familiar enough with the Plugin-API to know what you can do and
> > what not, but there's at least one crude way to do the polling. Take SVDRP
> > connection to master VDR and to local VDR to check timers. Quite ugly way I
> > admit, but I could live with that even if the polling was done only once /
> > minute or so...
> I must say I'd prefer the second way, because Remote-Timers would incorporate
> a lot of code-copying from the original VDR (which also requires to keep up
> with it when the original code changes). That's because "Timers" is not only
> the Menu itself. I like to program timers from within the "Programme" Menu,
> too (would have to be replaced as well).
> The only thing to do is to make the client VDR ignore all timers silently
> (which should not be a big problem) ;)
I've somewhere seen a patch from you, which feeds EPG-data into VDR. I
think patching is not that good (version changes, ...). Maybe your
plugin could update EPG of clients by SVDRP.
This way you have EPG in VDR-client and can program timers.
Now, you'll need to prevent the client from recording. I've already
asked Klaus for a commandline-switch preventing VDR from recording a
year ago, but couldn't persuade him to implement one into VDR. Maybe you
can persuade him?
Now, your plugin needs to get the timers from the table used in VDR for
transfering to server.
Maybe you can persuade Klaus to change some public/private statements
for the necessary classes to do inheritance.
To unsubscribe send a mail to email@example.com with "unsubscribe vdr" as subject.
Main Index |