summary of the aKademy meetings

[Charles Samuels]

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 instant my 
media player will need one of features, kdemm becomes completely useless and 
I have to drop down to whatever API I want.

<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>

-- 
Charles Samuels <charles at kde.org>
 Don't changes horses in the middle of an apocalypse!
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-multimedia/attachments/20040906/19993a82/attachment.sig>
-------------- next part --------------
_______________________________________________
kde-multimedia mailing list
kde-multimedia at kde.org
https://mail.kde.org/mailman/listinfo/kde-multimedia