Question about the interface classes

[Matthias Kretz]

On Tuesday 26 June 2007, Håvard Wall wrote:
> On Monday 25 June 2007 10:05, Matthias Kretz wrote:
> > Whatever it is, it'll need checks in the frontend code or it needs to
> > disallow old-version backends (which is easy to do using KTrader)
[snip]
> Changing the backend will be probably be the common case for embedded
> people. On embedded people are used to hardware encoding/decoding support
> and there's usually a C-library that provides a higher level API. From what
> I've seen, these libraries are typically less than 100KB and of course
> highly optimized. Now, we want to use Phonon to provide a nice higher level
> API for Qt applications, but someone will still have to provide a plugin of
> some kind for special hardware/libraries. I guess this means writing a
> Phonon backend. Development time is expensive, so ideally you write your
> plugin once and can upgrade both Qt and Phonon independently at a later
> point.

Ugh, so how frequent can we break the backend requirements? And how do the Qt 
plugin version checks work? My ~/.config/Trolltech.conf currently has this 
entry:
[Qt%20Plugin%20Cache%204.3.debug]
home\kdevel\KDE\kde4\lib\kde4\plugins\phonon_platform\kde.so=40300, 1, i686 
Linux g++-4 full-config, 2007-06-20T10:01:28

When updating Qt, will it stop loading the kde plugin (if it isn't recompiled, 
of course)?

> Having to use more development time for each release of Qt or Phonon 
> is not good, so we try to avoid that as much as possible.
>   The hardware libraries available for embedded devices might be quite
> powerful (codecs for wmf, jpeg, mpeg,...) and very fast. I want to avoid
> that customers find that they won't use our convenience API because they
> find it to add too much overhead.
>
> Not sure if I answered your question -)
>
> The answer could also be that Qt should contain an abstraction above Phonon
> and using Phonon as a default backend, but providing a separate plugin API
> for customers wanting to bypass as much as possible... Ideally I'd like a
> solution that fits all though -)

I think that Phonon is really about solving this problem, so we should solve 
it here.

So you think that phonon on embedded should always dynamically load the 
backend? Or are there some cases where you want to have it compiled into 
libphonon?

-- 
________________________________________________________
Matthias Kretz (Germany)                            <><
http://Vir.homelinux.org/
MatthiasKretz at gmx.net, kretz at kde.org,
Matthias.Kretz at urz.uni-heidelberg.de
-------------- 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/phonon-backends/attachments/20070626/98c1f48e/attachment.pgp