[mythtvnz] RedButton

[Solor Vox]

> On Mon, May 24, 2010 at 9:22 PM, Hadley Rich <hads at nice.net.nz> wrote:
>> > So if I were undertaking such an exercise I would start
>> > with python, because there are good tutorials and I find it easier to
>> > understand than perl, and I have a book (somewhere, maybe my son stole
>> > it!)

For what it's worth, both sed and awk are designed to do the same
thing, string/stream functions.  The execution time is less than two
seconds is rather good considering the amount of processing done on
the files.  At the end of the day awk/python/perl are all interpreted
scripts as well.  I myself don't care for perl or python so used what
I liked to write what I needed.  And there lies the beauty of open
source, if someone else wants to rewrite/port it to python, more power
too them.

On 24 May 2010 21:39, Steve Hodge <stevehodge at gmail.com> wrote:
> People have had a few problems with versions or modules or whatever - I
> remember a couple of threads here. And when I tried it I had some weird
> issue with character sets. I wouldn't say the choice of Python has been
> entirely transparent. OTOH I'm sure it was a lot quicker to develop than
> using say C.
>

For me at least, this project started by the need to convert the data.
 As sysadmin for years and because the files are basically text,
sed/awk came as natural fit for me.  While the script has evolved much
more then the original almost one line sed/awk calls, it still runs
well for me.  I just wanted to help out others who may needed to do
the same thing.  It was an added bonus that the GNU versions of sed,
awk, and bash I'm using make it easy for me to do what I needed all
inside one file without any other dependencies.  However, I could see
this project turning into a much larger animal at some point.  Such as
real-time lookup via thetvdb.com/themoviedb.org for extra metadata.
While it's still possible in bash/wget, it would be much easier to use
tools designed for working with html and xml data.

sV