[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kfm-devel
Subject:    Re: aKtion video player - konqueror (fwd)
From:       Simon Hausmann <shaus () uermel ! Med ! Uni-Magdeburg ! DE>
Date:       1999-09-12 12:33:00
[Download RAW message or body]


FYI :-)

What do you think about including aKtion into kdegraphics?
I wonder about objections because it depends on xanim, so could it be a
problem to have an application in the core packages depending on a program
probably not installed application?

Bye,
 Simon

P.S.: the video mimetypes in kdelibs already "bind" to aktion -
      strange, isn't it? ;)

---------- Forwarded message ----------
Date: Sat, 11 Sep 1999 17:23:51 -0300
From: Guillermo P. Marotte <g-marotte@usa.net>
To: Simon Hausmann <shaus@neuro2.med.uni-magdeburg.de>
Subject: Re: aKtion video player - konqueror

Hello!

Simon Hausmann wrote:
> 
> Hi,
> 
> I'm one of the guys hacking the new Konqueror, and as you probably know
> this beast is able to seamlessly embed other applications to display
> URLs.
> 
> One example of this is KView, which embeds itself into Konqueror when the
> user clicks on an image in Konqueror.
> 
> We would really like to see aKtion support this, too, and I already had a
> look at the lastest version of your nice video player (definitely the best
> xanim frontend out there!) . I "discovered" ;) your kxanim widget and I
> already wrote the necessary wrapper code for the Browser::View CORBA
> interface.

Great news! I always wanted to integrate aKtion with CORBA, but due to
my little disk space and internet bandwith (28.8k modem :) it wasn't
able to get in touch with the cutting edge KDE 2.0 technologies.
 
> Now we discussed a few ways to integrate the code into the existing
> codebase (CVS) .
> 
> One option would be to use your kxanim widget (you get full credits of
> course) and provide an extra executable (in a plugin subdirectory of
> konqueror) .
> 
> However we would prefer another approach, as it saves resources and avoids
> code duplicate: We would like to integrate this code into aKtion itself
> :-)
> 
> This would mean
> 
>  1) that we need your permission to put aKtion into CVS (into the
>     kdegraphics module)
>     (of course you will get an account on KDE's CVS server if appreciated)

You have it!
 
>  2) we would just add some code and link aKtion against a few additional
>     libraries (thus the need to put it in CVS)
> 
> This are just some first thoughts/points, we can talk about details later
> :-)
> 
> What do you think?

A couple of months ago, I startetd a complete rewrinting of the kxanim
widget, maily because it was too "xanim dependant", and was willing to
integrate support for other players (specifically mtvp). At some point I
get dissapointed by the legal restrictions that the mtvp people impossed
me, so the the development was stopped.
The main goal of it was to provide a generic interface to the different
players (through an abstract class) called KVideoBackend, and then
derivate specific class that implements the functionality (currently:
KXanim and KMtvp), but I don't know if this is the better approach
(maybe there's some OO pattern for this kind of stuff).

So, the situation is:
* If you're happy with xanim-only support, then use kxanim (with some
modificatios. because it was written one year ago, and it's pretty
bloated and ugly)
* If you want generic support for many video backends, then tell me so
and I'll send you the semi-completed new code (or we can think about a
better solution).

Cya!
Guillermo.

[prev in list] [next in list] [prev in thread] [next in thread]