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

List:       kde-multimedia
Subject:    Re: summary of the aKademy meetings
From:       Alexander Neundorf <neundorf () kde ! org>
Date:       2004-09-06 21:33:58
Message-ID: 200409062333.58112.neundorf () kde ! org
[Download RAW message or body]

On Monday 06 September 2004 23:08, Charles Samuels wrote:
> On Monday 2004 September 06 09:30 am, Michael Pyne wrote:
> > Well, if we pick an API, app writers will have to do one of two things:
> >
> > 1) Use the backend API directly, or
> > 2) Use a KDE-provided wrapper for simplicity.
> >
> > If we do number 2), then making it 'pluggable' is almost free, so I'll
> > assume you'd rather have option 1). ;)
>
> No, it's not, if you want all the features of the backend API, then you
> have to drop down to that backend API. The stuff in make-it-cool doesn't
> let you insert filters, or change its output mode... or anything. The

As far as I understood, it is intended to be a simple API for simple purposes. 
For advanced stuff use the backend API directly.

> <read me>
> What applications want is something to play audio/video with.  What
> applications want is a kpart to do it.  They don't care how the kpart does
> it.  This way we don't have a weak API in cvs and call it "the KDE MM
> Framework."
> </read me>

Why would I want to have a kpart ? I have a perfectly working widget here 
which can play videos for me. Wrapping this widget in a kpart so that it can 
be embedded in konqy is trivial.

Bye
Alex
-- 
Work: alexander.neundorf@jenoptik.com - http://www.jenoptik-los.de
Home: neundorf@kde.org                - http://www.kde.org
      alex@neundorf.net               - http://www.neundorf.net
_______________________________________________
kde-multimedia mailing list
kde-multimedia@kde.org
https://mail.kde.org/mailman/listinfo/kde-multimedia
[prev in list] [next in list] [prev in thread] [next in thread]