Thomas Schueppel wrote:
I attached the initial version. Comments are welcome.
And off course the Interface can be discussed, too. I'm
not completely happy with it myself.
It looks ok. But I have one question before I could really use it: is
there any linux tool to write avi
Gustavo Sverzut Barbieri wrote:
--- Dirk Meyer [EMAIL PROTECTED] escreveu: Gustavo Sverzut Barbieri
Please take a look at blue1_big.xml and blue2_big.xml, I would like
to hear some comments from you what you thing about the xml
structure.
Wow! It's gorgeous...
Thanks.
I'll myself
Update of /cvsroot/freevo/freevo/src
In directory sc8-pr-cvs1:/tmp/cvs-serv1710
Modified Files:
osd.py
Log Message:
Faster caching and there is no need for fchksum anymore
Index: osd.py
===
RCS file:
Update of /cvsroot/freevo/freevo/src/tv
In directory sc8-pr-cvs1:/tmp/cvs-serv4270
Modified Files:
epg_xmltv.py
Log Message:
moved pickled file to cache dir
Index: epg_xmltv.py
===
RCS file:
Update of /cvsroot/freevo/freevo/skins/dischi1
In directory sc8-pr-cvs1:/tmp/cvs-serv13694
Modified Files:
tvlisting_area.py
Log Message:
added channel logos
Index: tvlisting_area.py
===
RCS file:
Update of /cvsroot/freevo/freevo/src
In directory sc8-pr-cvs1:/tmp/cvs-serv23663/src
Modified Files:
main.py
Log Message:
make the shutdown look nicer for mga video
Index: main.py
===
RCS file:
Update of /cvsroot/freevo/freevo/skins/icons/AquaFusion/mimetypes
In directory sc8-pr-cvs1:/tmp/cvs-serv449
Added Files:
audiocd.png cdrom.png dvd.png empty_cdrom.png vcd.png
Log Message:
add rom drive images
--- NEW FILE: audiocd.png ---
(This appears to be a binary file; contents
Update of /cvsroot/freevo/freevo/src
In directory sc8-pr-cvs1:/tmp/cvs-serv841
Modified Files:
identifymedia.py main.py mediamenu.py
Log Message:
store rom drive type in media
Index: identifymedia.py
===
RCS file:
While you sold me with the idea of a persistant server alone, I'm not
clear on what the benefits of OOP for the recording schedule are...
Also, while this is only in my test skin, show highlighting (and
timeslot highlighting) are present already.
Another thing; is it possible for the recording
On Fri, Mar 14, 2003 at 07:41:42PM -0500, Alan Murrell wrote:
But the 'irw' program worked flawlessly prior to the
starting of Freevo (and generation of the
'/etc/freevo/lircrc' file). it was after this that
'irw' stopped responded, or rather, accepting commands
from the remote. I did not
On Sat, Mar 15, 2003 at 02:17:09PM -0500, Aubin Paul wrote:
Another thing; is it possible for the recording server to be spawned
by init?
Do you mean started during system startup from an rc script? This
would be most likely as the recording server should be a stand-alone
server that accepts
On Sat, Mar 15, 2003 at 03:03:26PM -0500, Brian J. Murrell wrote:
Oh, you mean run directly from inittab, like with an action of
respawn? Why? This should be unnecessary and for a daemon almost
always indicates bad design and/or programming.
Perhaps; I'm just going to be annoyed if it
Thanks for your comments. I wasn't aware that the format of freevo_record.lst had
changed. I am using the 1.3.2pre2 release and I don't see the channel ID like you
said. Secondly I only see two commas for each item in the freevo_record.lst file and
they are before the show title. Thirdly as
13 matches
Mail list logo
