On Oct 25, Michael Ruelle wrote:
> set DEBUG=1 in local_conf.py, some events get different names depending
> on context. I think there is a print for the events and it will show in
> main-0.log
The problem is not the name of the event. The problem is, that the
particular events (eg. MENU_UP/DOWN,
Update of /cvsroot/freevo/freevo/src
In directory sc8-pr-cvs1:/tmp/cvs-serv28408
Modified Files:
.cvsignore
Log Message:
Added mmpython.
Index: .cvsignore
===
RCS file: /cvsroot/freevo/freevo/src/.cvsignore,v
retrieving revi
I have a version of Xine that does not support lirc. In
./src/video/plugins/xine.py the option --no-lirc is added to the xine
command. Xine doesn't like that and stops when called (thus giving no
dvd output).
Maybe it's an idea to parse the output of "xine --version" in __init__
as well for av
I have a version of Xine that does not support lirc. In
./src/video/plugins/xine.py the option --no-lirc is added to the xine
command. Xine doesn't like that and stops when called (thus giving no
dvd output).
Maybe it's an idea to parse the output of "xine --version" in __init__
as well for av
Unfortuneately not a complete fix. A user withthe problem emailed me and
he is getting an ordinal not in range exception now. sigh, back to the
drawing board.
On Fri, 2003-10-24 at 04:22, Dirk Meyer wrote:
> Michael Ruelle wrote:
> > I would like to apply this but don't want to incur dischi's rath
set DEBUG=1 in local_conf.py, some events get different names depending
on context. I think there is a print for the events and it will show in
main-0.log
--
Mike Ruelle
[EMAIL PROTECTED]
http://world.std.com/~mruelle/
On Sat, 2003-10-25 at 16:41, [EMAIL PROTECTED] wrote:
> Hello,
>
> Thanks fo
I had an idea to use OpenGL for the interface.. Make a vo-plugin to MPlayer to
display the video on a GL-surface in a separate thread and have "freevo"
display on separate surfaces.. You'll get a lot of stuff for free if you use
that approach... No need for bmovl, hardware accelerated alphablend
Hello,
Thanks for your answer.
On Oct 25, Michael Ruelle wrote:
> look at WIP/Ruelle/externaltuner.py
I tried it this way. As i noticed now, the plugin catches events,
but _not_ MENU_UP, MENU_DOWN etc. But i need to catch these
events, because i am running freevo on a machine, where only a joyst
Hi Jason,
I read mplayer lists too and already forwarded your email to this list.
I saw no replies, but I'll work on that... by now we have only some
tests, but in future I plan to use our skin framework to render things
on the screen using BMOVL... probably we will not use that many
functions, m
look at WIP/Ruelle/externaltuner.py
On Sat, 2003-10-25 at 13:24, Andreas Meiner wrote:
> Hi,
>
> once again the event stuff in plugins.
> While browsing the archive i noticed, that it is
> somehow possible to get all events with a DaemonPlugin.
> But i am afraid i am to silly to make this work.
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Freevo Wiki" for change
notification.
The following page has been changed by 65.49.70.167:
http://freevo.sourceforge.net/cgi-bin/moin.cgi/FrequentlyAskedQuestions
Hi,
once again the event stuff in plugins.
While browsing the archive i noticed, that it is
somehow possible to get all events with a DaemonPlugin.
But i am afraid i am to silly to make this work.
It would be very nice, if someone can give me a short example
how to do this.
Thanks in advance,
A
Update of /cvsroot/freevo/freevo/src/plugins
In directory sc8-pr-cvs1:/tmp/cvs-serv24240
Modified Files:
idlebar.py
Log Message:
If we run into HTTP problems, don't keep slamming the METAR server, wait
for the next update.
Index: idlebar.py
==
Hi,
I will be extremely busy for the next few weeks, and won't have any
cycles to spare on the FreeBSD port. I'll resume working on this
sometime in December.
An older 1.4 rc ran great on FreeBSD already, so I imagine there won't
be many changes required then to arrive at a complete FreeBSD po
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Freevo Wiki" for change
notification.
The following page has been changed by 80.212.148.41:
http://freevo.sourceforge.net/cgi-bin/moin.cgi/LinkPage
The comment on the change is:
updated bad url
Update of /cvsroot/freevo/freevo/contrib/debian
In directory sc8-pr-cvs1:/tmp/cvs-serv7041
Modified Files:
rules BUILDING
Log Message:
Fix the build rules and update the BUILDING documentation.
Index: rules
===
RCS file: /c
Update of /cvsroot/freevo/freevo/contrib/debian
In directory sc8-pr-cvs1:/tmp/cvs-serv27485
Modified Files:
freevo.postinst
Log Message:
If there is no lircrc file, use makelircrc to autogenerate one.
Index: freevo.postinst
===
If you're using Debian packages of Freevo, I've added a ton of stuff
to make the experience a little nicer. (This will be coming in the
1.4rc2 release, it's not in the apt source yet)
1. You can now configure freevo's basic system (display, TV norm,
etc.) using debconf. This means that instead of
Update of /cvsroot/freevo/freevo/contrib/debian
In directory sc8-pr-cvs1:/tmp/cvs-serv24148
Modified Files:
BUILDING freevo.config freevo.postinst freevo.templates rules
Added Files:
init.d
Log Message:
Added an init script, and a debconf question to ask the user if they
want to
Update of /cvsroot/freevo/freevo/contrib/debian
In directory sc8-pr-cvs1:/tmp/cvs-serv20706
Modified Files:
changelog
Log Message:
Mention debconf
Index: changelog
===
RCS file: /cvsroot/freevo/freevo/contrib/debian/changel
Update of /cvsroot/freevo/freevo/contrib/debian
In directory sc8-pr-cvs1:/tmp/cvs-serv20266
Modified Files:
control freevo.postinst rules
Added Files:
freevo.config freevo.templates
Log Message:
Added initial debconf support to the package.
What does this mean?
When you install
--- Robert Rozman <[EMAIL PROTECTED]> escreveu:
> Also looking at pyui is probably right thing. Sooner or later Freevo
> will
> contain lot of code in similar manner os more general GUIs. So
> adopting this
> kind of cooperation Freevo will IMHO get some more time to
> concentrate on
> more inter
On Sat, Oct 25, 2003 at 01:22:37PM +0200, Robert Rozman wrote:
> I see that there are two different fucntionalities currently done in Freevo:
> one being TV GUI and other fetching data to display on TV. What do you think
> about solution that we separate those two functionalities further away and
>
Update of /cvsroot/freevo/freevo/src
In directory sc8-pr-cvs1:/tmp/cvs-serv11221
Modified Files:
childapp.py
Log Message:
add kill() function to kill the thread
Index: childapp.py
===
RCS file: /cvsroot/freevo/freevo/src/chi
Hello,
I'm Freevo newbie but would liek to add 2cents...
I see that there are two different fucntionalities currently done in Freevo:
one being TV GUI and other fetching data to display on TV. What do you think
about solution that we separate those two functionalities further away and
put some so
Since last post I've decoupled the datatypes from the menu structure.
This makes it possible to define one structure for web and one for
osd. This could be usefull for long category descriptions that are
suitable for web but not for osd.
It also makes it a lot easier to move settings between categ
First I'd like to point out (what I didn't explain thourough last
mail) that this is just the xml for how to build the menus i.e. on
web. The data supplied in this document is default values, and
user data will be supplied in another file.
During parsing, an object of the proper datatype is creat
Update of /cvsroot/freevo/freevo
In directory sc8-pr-cvs1:/tmp/cvs-serv14687
Modified Files:
freevo
Log Message:
do not KILL the child
Index: freevo
===
RCS file: /cvsroot/freevo/freevo/freevo,v
retrieving revision 1.91
retr
28 matches
Mail list logo
