Difference between revisions of "KTp/Components/Call UI"

< KTp
Jump to: navigation, search
(GUI Ideas)
(Dependency hell)
Line 35: Line 35:
** http://cgit.freedesktop.org/gstreamer/qt-gstreamer
** http://cgit.freedesktop.org/gstreamer/qt-gstreamer
* farsight2 (soon to be farstream):
* farstream:
** This is the library and gstreamer elements that do the actual media streaming.
** This is the library and gstreamer elements that do the actual media streaming.
** http://cgit.collabora.com/git/farsight2.git/
** http://cgit.collabora.com/git/farstream.git/
* telepathy-farstream:
* telepathy-farstream:

Revision as of 15:34, 4 February 2012

The plan

  • The current code is wrong by design, needs to be replaced.
  • Build a simple Qt library that exports the whole call application logic with a QML-izable interface, using QtGStreamer/farsight/farsight utils/telepathy-qt4.
  • Build a GUI that possibly consists of a standard KXmlGuiWindow that embeds a QDeclarativeView, which implements the call GUI.


  • Needs telepathy-qt4 to export interfaces for the Call spec.
    • tp-qt4-yell exports them now. will soon be merged to tp-qt4.
  • Needs a QML video widget in QtGStreamer.
    • this is work in progress.
    • we need it if and only if we build the interface using QML.

GUI Ideas

Dependency hell

How it all blends together

telepathy-qt-yell provides the Tpy::CallChannel class, which wraps the Channel.Type.Call d-bus object. From this object, we create a TfChannel (provided by tp-farstream) and we wrap it in a QTf::Channel object (provided by libqtf inside the call-ui repository; this is qt-gstreamer based bindings for tp-farstream). This TfChannel object does all the internal communication with the CM and constructs some GStreamer bin (using farsight2/farstream internally) that will do all the streaming. On this bin, we connect our GStreamer sources and sinks using the QtGStreamer API.

Content is available under Creative Commons License SA 4.0 unless otherwise noted.