Communication as a Service T elepathy and the KDE Software - - PowerPoint PPT Presentation

▶
communication as a service
SMART_READER_LITE
LIVE PREVIEW

Communication as a Service T elepathy and the KDE Software - - PowerPoint PPT Presentation

Jan 21, 2024 444 likes •877 views

Communication as a Service T elepathy and the KDE Software Compilation George Goldberg Akademy 2010 Tampere, Finland Introduction 1. Introduction to Telepathy 2. Telepathy and KDE The plan, the present and the future 3. The Flying Car

slide-1
SLIDE 1

T elepathy and the KDE Software Compilation

Communication as a Service

George Goldberg

Akademy 2010 Tampere, Finland

slide-2
SLIDE 2

Introduction

  • 1. Introduction to Telepathy
  • 2. Telepathy and KDE

The plan, the present and the future

  • 3. The Flying Car Future

Plasma, Nepomuk and beyond...

slide-3
SLIDE 3

What's Not Covered?

This talk will not cover:

  • The rationale behind the design of the

Telepathy Framework

  • Low-level detail of the workings of the

Telepathy Framework

slide-4
SLIDE 4

What's Not Covered?

There have been plenty of excellent talks

  • n these topics before. If you are

interested, slides are available from:

http://telepathy.freedesktop.org/wiki/Presentations

slide-5
SLIDE 5
  • 1. Introduction to Telepathy
slide-6
SLIDE 6

What is Telepathy?

“Telepathy is a flexible, modular communications framework that enables real-time communication via pluggable protocol backends.”

“Telepathy creates the idea of communication as a desktop service. It uses D- Bus to separate components running in separate processes. Telepathy clients use this D-Bus API (usually via a convenience library — e.g. telepathy-glib) to share connections between multiple clients (e.g. an instant messaging program, presence in email application, collaboration in word processor).”

source: http://telepathy.freedesktop.org

slide-7
SLIDE 7

What is Telepathy?

  • A Real-time Communication Framework
  • A set of Standardised DBus Interfaces
  • A set of components implementing those

DBus Interfaces

slide-8
SLIDE 8

Architecture

SIP XMPP MSN Chat Voice VNC D-Bus

slide-9
SLIDE 9

Connection Managers

SIP XMPP MSN Chat Voice VNC D-Bus

slide-10
SLIDE 10

Connection Managers

  • Connect to the IM network
  • Make connections available over DBus
  • Only one connection to each IM account
slide-11
SLIDE 11

Clients

SIP XMPP MSN Chat Voice VNC D-Bus

slide-12
SLIDE 12

Clients

  • Do stuff!

 Text Chat  Voice/Video  File Transfer  VNC  ...

slide-13
SLIDE 13

Account Manager and Channel Dispatcher

SIP XMPP MSN Chat Voice VNC D-Bus

slide-14
SLIDE 14

Account Manager

  • Service to store account information
  • Centralised storage of user names,

passwords etc.

  • Storage to Freedesktop.org shared

secrets compatible store (KWallet etc)

slide-15
SLIDE 15

Channel Dispatcher

  • Service between CMs and Clients
  • Request a communication channel to a

contact

  • Pass an incoming communication channel

to the appropriate client

slide-16
SLIDE 16

What Can Telepathy Do?

  • Text Chat
  • Voice and Video Chat
  • File Transfers
  • Tubes
  • ...
slide-17
SLIDE 17

Tubes

  • Two types of tube:

 Stream Tubes (TCP Socket over IM)  DBus Tubes (DBus over IM)

slide-18
SLIDE 18
  • 2. Telepathy and KDE
slide-19
SLIDE 19

It's been a long time in coming...

slide-20
SLIDE 20

The Plan

  • Focus on unique features
  • Reuse existing Telepathy components
  • Provide convenience API and reusable

widgets

  • Deep integration
slide-21
SLIDE 21

First, the basics...

slide-22
SLIDE 22

Accounts UI

slide-23
SLIDE 23

Accounts UI

slide-24
SLIDE 24

Contact List

slide-25
SLIDE 25

Text Chat UI

Sorry, still under construction... But, in the meantime you can use Kopete with the Telepathy Protocol Plugin.

slide-26
SLIDE 26

Presence Plasmoid

slide-27
SLIDE 27

UI Designers, we (obviously) need your help!

slide-28
SLIDE 28

Nepomuk for Contact Storage

Nepomuk is a key component of our Telepathy integration. “Meta-Contacts” should not be limited to instant messaging applications. They should be replaced by the desktop-wide concept of “People”. Nepomuk makes this possible.

slide-29
SLIDE 29

Nepomuk for Contact Storage

  • We make use of two ontologies:

 PIMO – to represent a real person  NCO – to represent a contact, ie. a single

address book/buddy list entry for a person

  • One person can have multiple contacts
slide-30
SLIDE 30

Nepomuk for Contact Storage

NCO:Contact

gberg@jabber.org Jabber Account

PIMO:Person George NCO:Contact

gberg@hotmail.com MSN Account

NCO:Contact

gberg@collabora.co.uk Groupware Server

slide-31
SLIDE 31

The Future

  • Deeper integration with applications:

 Plasma?  Kontact?  KOffice?  KDE Games?  ...

slide-32
SLIDE 32

The Future

  • More advanced features:

 Collaboration  Voice/Video  Conferencing

slide-33
SLIDE 33
  • 3. Flying Car Future
slide-34
SLIDE 34

Nepomuk

  • Sharing of meta-data is a logical next step

for Nepomuk

  • XMPP based protocol for meta-data

interchange

  • Nepomuk service acting as a Telepathy

client to handle Meta-Data channels.

slide-35
SLIDE 35

Related Google Summer of Code project by Vishesh Handa

Nepomuk

slide-36
SLIDE 36

Plasma People

  • Why not have a Person as a Plasmoid?
  • You can:

 See their picture  Easily contact them in many ways, or interact with

them, or play games with them...

 Look up your chat history, shared documents, game

stats...

slide-37
SLIDE 37

Conclusion

  • We have:

 Basic IM components  Lots of CMs, an AM and a CD  An API and Widgets for use in applications  Lots of cool ideas

slide-38
SLIDE 38

Conclusion

  • We need:

 Advanced communication and collaboration

features

 Better user interfaces  Deeper integration and adoption in other

applications

slide-39
SLIDE 39

The Workshop Wednesday 14:00 -> 18:00+ Area 3

slide-40
SLIDE 40

Questions?

slide-41
SLIDE 41

And finally, free T-Shirts!!!