summary of the aKademy meetings

[Alexander Neundorf]

On Tuesday 07 September 2004 19:59, Marco Lohse wrote:
...
> But seriously, let us consider another example for
> abstraction/meta-architecture: Qt. From my understanding, Qt is (also) a
> wrapper for lower-level interfaces. It is no one-to-one mapping. It does
> provide abstraction. Therefore, it works with different underlying
> lower-level interfaces. That is possible because different underlying
> lower-level interfaces provide a set of common facilities.
>
> Yes, I know, some people argueed that the multimedia meta-architecture
> can only offer the 'common denominator', as Ronald said. But what is the
> common denominator? Why is that not sufficient for the multimedia
> framework for KDE? (Sure, it is not sufficient for all possible
> applications out there.)
>
> Have fun, Marco.

IMHO this is simply too much work.
All the frameworks (nmm, gstreamer, mas, xine, mplayer [ok it's no framework]) 
are already wrappers around the different decoders and stuff. 
This would be more like Qt working on top of wxwindows I'd say. 
If we wrap these wrappers again, we won't have significantly less work than 
the authors of these frameworks I'd say.

A simple KDE API for simple purposes and a recommended framework for advanced 
purposes is IMO a really good solution. And I guess most KDE developers 
writing advanced MM apps will write some kind of bindings for their preferred 
framework. Maybe this will naturally lead to one preferred framework with its 
bindings, which can then (maybe in 2..5 years) become the defacto KDE 
standard MM framework.

Bye
Alex
-- 
Work: alexander.neundorf at jenoptik.com - http://www.jenoptik-los.de
Home: neundorf at kde.org                - http://www.kde.org
      alex at neundorf.net               - http://www.neundorf.net