Re: [xine-devel] Couple of xine-ui questions

[Siggi L. <si...@us...>]

Hi Ed,

On Sun, 2 Jan 2005, Ed Wildgoose wrote:

[...]
> the move to switch to xine.  Now mythtv's video module is built around
> the idea of one file = one film, so I need to rip the DVD's to an ISO
> image - however, unless I am simply falling foul of operator error doing
> "xine dvd://somefile.iso" just gives a message about "no demuxer
> available for file type .iso".  Is this operator error, or something
> that I should consider programming around?

Probably both.
Right now, dvd:/ MRLs require the full path. So if you just say

xine dvd:/home/media/somefile.iso

(assuming the file is in "/home/media"), it should work fine.

> My other point was the error messages not being easily cleared.  This
> might be partly a UI setup issue though.  Basically I seem to actually
> need to press the OK buttons rather than simply pressing escape.
> Possibly "enter" works, but I can't remember.  Basically though for my
> use it would be nice if it either appeared briefly, died instantly and
> simply wrote a message to a log file, or printed the error on the output
> device.  However, will simply put it down as a feature request...

Hmmm, for a desktop media player, diplaying a popup window that requires
the user to acknowlege errors is probably the right thing to do...
My point was that your usage of xine-ui as a video playback module for
mythtv is actually abusing this desktop player, so you'd probably want
something more like oxine (aka. "OSDxine"). OTOH, that comes with its own
menu stuff, so you can't really use that, either.
Maybe toxine is what you need: It's easily scriptable and should return
all errors in it's shell...

> Anyway, xine is a lovely app, congrats to all developers.  There are
> tons of little things I would like to tweak on it of course - for
> example I don't have enough buttons on my remote for all functions and I
> would love it if the event left/right/up/down buttons could be
> overridden to do different things when we are playing a feature and
> there are no menus visible (I could then map them to the large skip
> forward backwards functions).  However, perhaps I should learn a little
> more about the xine-ui internals first.

Well, I still have a feeling that xine-ui is the wrong front end for this
kind of usage, but then I don't know any "right" front end.
I guess some kind of thin libxine wrapper, such as pyxine or toxine comes
close to what you need.
Have a look at out download page! The front ends are all listed there...

HTH,
	Siggi