KTp/Components/Call UI: Difference between revisions
< KTp
No edit summary |
update blockers |
||
| Line 9: | Line 9: | ||
===Blockers=== | ===Blockers=== | ||
* Needs telepathy-qt4 to export interfaces for the Call spec. | * 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. | * 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=== | ===GUI Ideas=== | ||
Revision as of 12:37, 1 February 2011
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.
Blockers
- 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.