Projects/Telepathy - Revision history

Grundleborg: we've moved

2010-04-16T14:44:30Z

we've moved

Grundleborg: point to community.kde.org

2010-01-25T20:03:51Z

point to community.kde.org

Abnerf at 18:29, 7 August 2009

2009-08-07T18:29:57Z

Grundleborg: /* Problems */

2009-07-22T15:46:25Z

‎Problems

Grundleborg: add warning

2009-07-22T15:27:25Z

add warning

Grundleborg: /* Telepathy Integration Daemon */

2009-07-22T15:26:27Z

‎Telepathy Integration Daemon

Grundleborg: add warning

2009-07-22T15:25:55Z

add warning

Grundleborg: /* KWallet Account Manager */

2009-07-22T15:20:27Z

‎KWallet Account Manager

Grundleborg: FAQ: What happened to Decibel

2009-07-10T13:40:08Z

FAQ: What happened to Decibel

Grundleborg: basic info on what to install/compile to try telepathy

2009-07-10T13:37:28Z

basic info on what to install/compile to try telepathy

@@ Line 1: / Line 1: @@
-{{Warning| The Telepathy-On-KDE project pages have moved to community.kde.org. [http://community.kde.org/Real-Time_Communication_and_Collaboration]}}
+{{Warning| The Telepathy-On-KDE project pages have moved to [http://community.kde.org/Real-Time_Communication_and_Collaboration community.kde.org/Telepathy]}}
-−
-==Introduction==
-[http://telepathy.freedesktop.org The Telepathy framework] is a DBus specification which provides a cross-desktop and cross-protocol abstraction layer for instant messaging, voice/video over IP and collaborative applications. See the [http://telepathy.freedesktop.org Telepathy web site] for more information about Telepathy itself.
-−
-This project is focused on integrating Telepathy with KDE. Our high-level aims are the following:
-* to provide a unified instant messaging and voice/video communication framework within KDE, which integrates throughout the desktop experience.
-* to provide collaborative features in applications which fit seemlessly into the KDE platform
-* to provide the infrastructure within KDE necessary to acheive the above two, using cross-desktop specifications and implementations wherever possible.
-−
-==Infrastructure==
-This section contains details of all the Telepathy-in-KDE infrastructure components, and their statuses.
-−
-===Telepathy Integration Daemon===
-−
-{{Warning| Before working on this component, please talk to grundleborg on #kde-telepathy. See [[/TelepathyNepomukPlans|here]] for more information on Telepathy/Semantic Desktop Integration.}}
-−
-This is a small light-weight daemon that monitors the Telepathy Account Manager and keeps ensures that all Accounts are recorded in Nepomuk as NCO:Contact instances of "myself" and that they each have a Telepathy Contacts Akonadi Resource instance.
-−
-It could possibly be made into a KDED module, but I'm not sure if this is a good idea. [[User:Grundleborg|Grundleborg]]
-−
-====Status====
-The bare bones are implemented, but the Nepomuk part is blocking on standardising the Ontologies for telepathy specific stuff and how to access the "myself" PIMO:Person through Nepomuk. The Akonadi part is blocking on getting the Telepathy Contacts Akonadi Resource below implemented.
-−
-====Source Code====
-Source code can be found in KDE svn at:
-<pre>
-svn://anonsvn.kde.org/home/kde/trunk/playground/network/telepathy-integration-daemon
-</pre>
-[http://websvn.kde.org/trunk/playground/network/telepathy-integration-daemon websvn link].
-−
-===Telepathy Contacts Akonadi Resource===
-−
-{{Warning| Before working on this component, please talk to grundleborg on #kde-telepathy. See [[/TelepathyNepomukPlans|here]] for more information on Telepathy/Semantic Desktop Integration.}}
-−
-This is an Akonadi Resource that synchronises the contacts of a Telepathy Account into Akonadi as vcards. The instances of this resource are managed by the telepathy-integration-daemon mentioned above.
-−
-====Status====
-Partially implemented. Requires some Telepathy CM's to implement the org.freedesktop.Telepathy.Connection.Interface.ContactInfo.DRAFT interface to complete it, since we shouldn't try and support legacy CM's which don't support that interface.
-−
-====Source Code====
-The code can be found in the KDE svn playground at the following URL:
-−
-<pre>
-svn://anonsvn.kde.org/home/kde/trunk/playground/network/telepathy-contacts-resource
-</pre>
-[http://websvn.kde.org/trunk/playground/network/telepathy-contacts-resource websvn link].
-−
-===Presence Dataengine and Plasmoid===
-−
-====Status====
-−
-The dataengine is functional, allowing you to set the Requested Presence and Status Message, and view the Current Presence, Status Message, Avatar, Alias and name of all Telepathy Accounts.
-−
-The applet is working well on its first version, supporting to set up presence status and presence message. It still needs some polishing and love from designers.
-−
-====Source Code====
-−
-Applet in KDE svn:
-<pre>
-svn://anonsvn.kde.org/home/kde/trunk/playground/base/plasma/applets/presence
-</pre>
-−
-[http://websvn.kde.org/trunk/playground/base/plasma/applets/presence websvn link].
-−
-Dataengine in KDE svn:
-<pre>
-svn://anonsvn.kde.org/home/kde/trunk/playground/base/plasma/dataengines/presence
-</pre>
-−
-[http://websvn.kde.org/trunk/playground/base/plasma/dataengines/presence websvn link].
-−
-===Account Management KCM===
-====Ideas====
-* One single UI that any application can load for add/edit/delete Telepathy Accounts
-−
-* Creates a dynamic UI on-the-fly using Connection Manager parameters, but this should be used only when a specific UI plugin for that CM isn't installed.
-−
-* Create specialised UI plugins for the popular CM's (e.g. gabble) since dynamic UI will be pretty crap usability-wise.
-−
-====Status====
-−
-Some code is there in svn, but it's pretty much just experimental shell-files. So feel free to ignore existing code to implement this :) [[User:Grundleborg|Grundleborg]]
-−
-====Source Code====
-−
-Source code is in KDE svn playground at:
-−
-<pre>
-svn://anonsvn.kde.org/home/kde/trunk/playground/network/telepathy-accounts-kcm/
-</pre>
-−
-[http://websvn.kde.org/trunk/playground/network/telepathy-accounts-kcm/ websvn link].
-−
-===KWallet Account Manager===
-This was originally intended to be an implementation of the Telepathy AccountManager which was integrated with KDE and KWallet for the account data storage. However, in light of the shared-secrets API being developed on freedesktop.org which will unify the KWallet and Gnome-Keyring API it would probably be a better use of resources to just get Mission Control ported to that instead.
-−
-In light of that, its probably best not to work on telepathy-accountmanager-kwallet or telepathy-qt4-accountmanager at the moment.
-−
-==Telepathy Enabled Applications==
-−
-==Problems==
-−
-* QtDBus doesn't have peer-to-peer DBus implemented properly - the classes are just non-functional stubs. This stops us from implementing D-tubes in KDE/Qt based Telepathy applications. Upstream bug is private in Qt Software's tracker and this is unlikely to get fixed by Qt Software, so if anyone feels like implementing it and then merging it upstream into Qt, that would be really fantastic.
-−
-* Telepathy-Mission-Control still requires you to use both the channel dispatcher part of it and the Account Manager. For KDE, we need to be able to use only the Channel Dispatcher from Mission-Control and have that talk over the standard Telepathy DBus interfaces to the KDE KWallet based Account Manager.(OR we need MC's AM to start using the shared-secrets API)
-−
-==Trying out Telepathy==
-−
-=== Prerequisites ===
-* telepathy-mission-control 5
-* telepathy-qt4
-* telepathy-gabble, telepathy-butterfly, telepathy-haze (for jabber/msn/everything else support respectively)
-−
-=== KDE Stuff ===
-All the KDE Telepathy infrastructure components are detailed above, and they may or may not be in working/compiling order. Any problems, ask in #kde-telepathy.
-−
-==How to Get Involved==
-Come and talk to us in #kde-telepathy on irc.freenode.net. There is also a #telepathy channel for talking about Telepathy stuff that is not specific to KDE.
-−
-==Frequently Asked Questions==
-−
-=== What happened to Decibel? ===
-−
-Decibel development has completely stagnated and it no longer works with recent Telepathy components. It is not necessary to use Decibel to get Telepathy support in KDE - all the applications/components above do not require Decibel to compile or function.

← Older revision		Revision as of 20:03, 25 January 2010
Line 1:		Line 1:
		+	{{Warning\| The Telepathy-On-KDE project pages have moved to community.kde.org. [http://community.kde.org/Real-Time_Communication_and_Collaboration]}}
		+
	==Introduction==		==Introduction==
	[http://telepathy.freedesktop.org The Telepathy framework] is a DBus specification which provides a cross-desktop and cross-protocol abstraction layer for instant messaging, voice/video over IP and collaborative applications. See the [http://telepathy.freedesktop.org Telepathy web site] for more information about Telepathy itself.		[http://telepathy.freedesktop.org The Telepathy framework] is a DBus specification which provides a cross-desktop and cross-protocol abstraction layer for instant messaging, voice/video over IP and collaborative applications. See the [http://telepathy.freedesktop.org Telepathy web site] for more information about Telepathy itself.

@@ Line 49: / Line 49: @@
 ====Status====
-The dataengine is functional, allowing you to set the Requested Presence and Status Message, and view the Current Presence and Status Message of all Telepathy Accounts.
+The dataengine is functional, allowing you to set the Requested Presence and Status Message, and view the Current Presence, Status Message, Avatar, Alias and name of all Telepathy Accounts.
-The applet is not really functional. Andrunko has asked Nuno for some mockups of how to make a nice looking applet.
+The applet is working well on its first version, supporting to set up presence status and presence message. It still needs some polishing and love from designers.
 ====Source Code====

@@ Line 102: / Line 102: @@
 * QtDBus doesn't have peer-to-peer DBus implemented properly - the classes are just non-functional stubs. This stops us from implementing D-tubes in KDE/Qt based Telepathy applications. Upstream bug is private in Qt Software's tracker and this is unlikely to get fixed by Qt Software, so if anyone feels like implementing it and then merging it upstream into Qt, that would be really fantastic.
-* Telepathy-Mission-Control still requires you to use both the channel dispatcher part of it and the Account Manager. For KDE, we need to be able to use only the Channel Dispatcher from Mission-Control and have that talk over the standard Telepathy DBus interfaces to the KDE KWallet based Account Manager.
+* Telepathy-Mission-Control still requires you to use both the channel dispatcher part of it and the Account Manager. For KDE, we need to be able to use only the Channel Dispatcher from Mission-Control and have that talk over the standard Telepathy DBus interfaces to the KDE KWallet based Account Manager.(OR we need MC's AM to start using the shared-secrets API)
 ==Trying out Telepathy==

← Older revision		Revision as of 15:27, 22 July 2009
Line 29:		Line 29:

	===Telepathy Contacts Akonadi Resource===		===Telepathy Contacts Akonadi Resource===
		+
		+	{{Warning\| Before working on this component, please talk to grundleborg on #kde-telepathy. See [[/TelepathyNepomukPlans\|here]] for more information on Telepathy/Semantic Desktop Integration.}}
		+
	This is an Akonadi Resource that synchronises the contacts of a Telepathy Account into Akonadi as vcards. The instances of this resource are managed by the telepathy-integration-daemon mentioned above.		This is an Akonadi Resource that synchronises the contacts of a Telepathy Account into Akonadi as vcards. The instances of this resource are managed by the telepathy-integration-daemon mentioned above.

← Older revision		Revision as of 15:25, 22 July 2009
Line 11:		Line 11:

	===Telepathy Integration Daemon===		===Telepathy Integration Daemon===
		+
		+	{{Warning\| Before working on this component, please talk to grundleborg on #kde-telepathy. See [[TelepathyNepomukPlans\|here]] for more information on Telepathy/Semantic Desktop Integration.}}
		+
	This is a small light-weight daemon that monitors the Telepathy Account Manager and keeps ensures that all Accounts are recorded in Nepomuk as NCO:Contact instances of "myself" and that they each have a Telepathy Contacts Akonadi Resource instance.		This is a small light-weight daemon that monitors the Telepathy Account Manager and keeps ensures that all Accounts are recorded in Nepomuk as NCO:Contact instances of "myself" and that they each have a Telepathy Contacts Akonadi Resource instance.

← Older revision		Revision as of 15:20, 22 July 2009
Line 86:		Line 86:

	===KWallet Account Manager===		===KWallet Account Manager===
		+	This was originally intended to be an implementation of the Telepathy AccountManager which was integrated with KDE and KWallet for the account data storage. However, in light of the shared-secrets API being developed on freedesktop.org which will unify the KWallet and Gnome-Keyring API it would probably be a better use of resources to just get Mission Control ported to that instead.

		+	In light of that, its probably best not to work on telepathy-accountmanager-kwallet or telepathy-qt4-accountmanager at the moment.

	==Telepathy Enabled Applications==		==Telepathy Enabled Applications==

← Older revision		Revision as of 13:40, 10 July 2009
Line 110:		Line 110:

	==Frequently Asked Questions==		==Frequently Asked Questions==
		+
		+	=== What happened to Decibel? ===
		+
		+	Decibel development has completely stagnated and it no longer works with recent Telepathy components. It is not necessary to use Decibel to get Telepathy support in KDE - all the applications/components above do not require Decibel to compile or function.

← Older revision		Revision as of 13:37, 10 July 2009
Line 97:		Line 97:

	==Trying out Telepathy==		==Trying out Telepathy==
		+
		+	=== Prerequisites ===
		+	* telepathy-mission-control 5
		+	* telepathy-qt4
		+	* telepathy-gabble, telepathy-butterfly, telepathy-haze (for jabber/msn/everything else support respectively)
		+
		+	=== KDE Stuff ===
		+	All the KDE Telepathy infrastructure components are detailed above, and they may or may not be in working/compiling order. Any problems, ask in #kde-telepathy.

	==How to Get Involved==		==How to Get Involved==