Roger <[email protected]> wrote: > My script's goal was just to simplify Linux DVB recording, and using existing > (Unix ;-) tools versus implementing another all-in-one solution. Anything > added, usually immediately increases size and complexity with being easily > read > scripting/coding. One could take time and implement a simple text file for > stating recording times, but then we're back to dealing with users whom then > do > not know how to open and edit a simple text config file. (For which that is > all a crontab consists of to begin with, except for learning the syntax.) > Most > users I find at this point, usually do not mind using something like MythTV. > Albeit, you're getting smarter and seeing you really do not need all that > just > to record. It's a fact of marriage, for better or worse. ;-)
A few years ago I used the combination of a text file, a web page with a perl script to modify the text file, and an interface to the Unix "at" command for scheduling recording jobs. I wrote the web interface for my wife, but in the end none of us used it much. Total code size for this feature was about ~300 lines of code. The major pain point in that experiment was the interface to the "at" command. I'd probably hardwire a crontab entry if I were to do it again. -- Björn Danielsson <[email protected]> _______________________________________________ pvrusb2 mailing list [email protected] http://www.isely.net/cgi-bin/mailman/listinfo/pvrusb2
