Changes between Version 2 and Version 3 of QtWebKitMediaElementSupport


Ignore:
Timestamp:
Dec 7, 2009 12:51:48 AM (10 years ago)
Author:
vestbo@webkit.org
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • QtWebKitMediaElementSupport

    v2 v3  
    11= Details of the QtWebKit HTML5 media element implementation =
    22
    3 [[Image(http://chaos.troll.no/~tavestbo/webkit/mediaelement/)]]
     3[[Image(http://chaos.troll.no/~tavestbo/webkit/mediaelement/screenshot.png)]]
    44
    55== Structure ==
     
    4949So what are the downsides of letting Phonon handle media loading? For one, the Phonon API does not have a way for the client to query how much of the media has been loaded. This is not only useful for displaying
    5050a visualization to the user of how much of the file has been loaded, but also required by the platform independent WebKit media element code to know whether or not it can seek to a given position. Confusingly enough
    51 Phonon does provide a =[[http://api.kde.org/4.0-api/kdelibs-apidocs/phonon/html/classPhonon_1_1MediaObject.html#0f5ce603d4a061e694ee3f531955d5f7][MediaObject::bufferStatus()]]= signal, but that
     51Phonon does provide a MediaObject::bufferStatus() signal, but that
    5252signal refers to how much of the internal _pre-buffering_ buffer has been filled (for example when you seek to a new position, Phonon goes into a buffering state where it fills this buffer, and then goes back to playing state), not
    5353to how much of the media files has been loaded. In effect, there is no way to provide a seek slider without lying to the WebKit platform independent code about how much data we've loaded (by claiming that we've got all the data, even though we don't know that).