Hi,

There is some documentation  being made that take account on this. It is not 
yet published. Answering to some question on my behalf

>1) Are the classes in Qt Mobility that are also present in Qt (like
>QAudioOutput) a _copy_ - or is it just simply relying on Qt, and if
>you include <QAudioOutput> from Mobility, it will actually include the
>.h from Qt?

Development is now being done in QtMobility repositories. Originally those 
classes where merged from Qt and the latest code is now under QtMobility. On 
Symbian system include will include headers from epoc32\include\ and there  
should not be 2 set of same headers under that directory tree. 

-antti

-----Original Message-----
From: [email protected] 
[mailto:[email protected]] On Behalf Of Espen Riskedal
Sent: 8. joulukuuta 2010 13:26
To: [email protected]
Subject: [Qt-mobility-feedback] Clarifying questions around QtMultimedia

I'm trying to grasp the current state of QtMultimedia:

In Qt 4.6 and 4.7 there is QtMultimedia, and they have the following classes:
 QAbstractVideoBuffer
 QAbstractVideoSurface
 QAudioDeviceInfo
 QAudioFormat
 QAudioInput
 QAudioOutput
 QVideoFrame
 QVideoSurfaceFormat

Then we have Qt Mobility 1.0 and 1.1. They have the exact same
classes, but also extend with more (complete list at
http://doc.qt.nokia.com/qtmobility-1.0/multimedia.html#reference-documentation).

My question is:

1) Are the classes in Qt Mobility that are also present in Qt (like
QAudioOutput) a _copy_ - or is it just simply relying on Qt, and if
you include <QAudioOutput> from Mobility, it will actually include the
.h from Qt?

2) Are there any plans of providing binaries for all platforms, not
just Symbian?

3) Is QtMoblity 1.1 tied to 4.7 and 1.0 to 4.6 - or will 1.1 be
compatible with 4.6 as well? Especially when thinking about the
connection with the low-level video/audio classes already in Qt

4) When are classes no longer "subject to change". If you look at
QMediaPlayer in Qt Mobility 1.1 it still says "This class is under
development and is subject to change." Ref:
http://doc.qt.nokia.com/qtmobility-1.1/qmediaplayer.html . I'm
assuming "subject to change" means you may yet break binary or
software compatibility?

regards
espen
_______________________________________________
Qt-mobility-feedback mailing list
[email protected]
http://lists.trolltech.com/mailman/listinfo/qt-mobility-feedback

_______________________________________________
Qt-mobility-feedback mailing list
[email protected]
http://lists.trolltech.com/mailman/listinfo/qt-mobility-feedback

Reply via email to