On Wed, 2005-09-21 at 10:42 +0200, Dirk Meyer wrote: > We would rely 100% on evas. But evas knows that we use dfb and uses > dfb to do some stuff. That's the basic idea, have _one_ good canvas > lib which can handle all the different output types.
In point of fact, evas doesn't (and wouldn't) handle management of the
actual windows. (By management I mean hiding, showing, resizing,
raising, lowering, etc.) That will be handled by kaa.canvas.
kaa.canvas is looking like a very nice API. The test/ directory has
some vf_overlay code. It implements MPlayerOSDCanvas (subclassed from
canvas.BufferCanvas) and CanvasMovie (subclassed from
canvas.CanvasImage). Both of these things have pretty strange
requirements and need to hook in very specific ways, and have to get
updated at very specific times. It all seems to work quite well, which
I think is a testament to kaa.canvas's design.
OTOH kaa.canvas hasn't really been tested with anything serious yet. :)
I'll be working on it again soon, and will be cleaning it up (splitting
it up into separate files), documenting, and implementing CanvasMovie.
At that point, it will be ready for you guys to have a more serious look
at it.
I need to think a bit more about how to design CanvasMovie and how the
basic kaa architecture of media players and their interaction with the
canvas should be designed. I'm thinking of making a base Player class
(that's basically a protocol) and create MPlayer and Xine classes that
implements Player. Perhaps I'll rename kaa.mplayer to kaa.player and
add a higher level Xine API to that as well. Then kaa.canvas would use
that.
The last couple days has been a mad hacking frenzy to get the OSD code
into kaa.xine's special kaa driver. I have YV12 done. I need to
implement YUY2 at some point (because tvtime deinterlacers will use YUY2
unless cheap_mode = True). By the way, that work was sponsored by
Julian Scheel of Jusst Technologies GmbH (_julian) so everyone thank him
for that cool gesture that benefits Freevo. :)
Some candy:
http://sault.org/~tack/xineosd.jpg
(That video clipart is becoming a staple in all my OSD work, isn't
it :))
Cheers,
Jason.
signature.asc
Description: This is a digitally signed message part
