Dear all,
I'm trying to make a telepathy-based IRC client to show every
channel's description. For that, I'm using RoomInfo.get_description().
However, that method always returns null. I'm not sure why. I've
checked other information in RoomInfo, and there are other
The "Ages Later" release.
tarball:
https://telepathy.freedesktop.org/releases/telepathy-glib/telepathy-glib-0.24.2.tar.gz
signature:
https://telepathy.freedesktop.org/releases/telepathy-glib/telepathy-glib-0.24.2.tar.gz.asc
git: https://cgit.freedesktop.org/telepathy/tele
Ralph Meijer
- Daniel-Constantin Mierla
- Daniel Pocock
- Guus der Kinderen
___
telepathy mailing list
telepathy@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/telepathy
tarball:
http://telepathy.freedesktop.org/releases/telepathy-haze/telepathy-haze-0.8.1.tar.gz
signature:
http://telepathy.freedesktop.org/releases/telepathy-haze/telepathy-haze-0.8.1.tar.gz.asc
git: http://cgit.freedesktop.org/telepathy/telepathy-haze
Dependencies:
• libpurple ≥ 2.10.12 is now
tarball:
http://telepathy.freedesktop.org/releases/telepathy-idle/telepathy-idle-0.2.2.tar.gz
signature:
http://telepathy.freedesktop.org/releases/telepathy-idle/telepathy-idle-0.2.2.tar.gz.asc
git: https://gitlab.freedesktop.org/telepathy/telepathy-idle
It seems that I accidentally merged
telepathy-idle 0.2.1 release.
tarball:
https://telepathy.freedesktop.org/releases/telepathy-idle/telepathy-idle-0.2.1.tar.gz
signature:
https://telepathy.freedesktop.org/releases/telepathy-idle/telepathy-idle-0.2.1.tar.gz.asc
git: https://gitlab.freedesktop.org/telepathy/telepathy-idle
___
telepathy mailing list
telepathy@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/telepathy
The "leave no space" release.
tarball:
http://telepathy.freedesktop.org/releases/telepathy-mission-control/telepathy-mission-control-5.16.6.tar.gz
signature:
http://telepathy.freedesktop.org/releases/telepathy-mission-control/telepathy-mission-control-5.16.6.tar.gz.asc
The "three plus one" release.
tarball:
http://telepathy.freedesktop.org/releases/telepathy-spec/telepathy-spec-0.27.4.tar.gz
signature:
http://telepathy.freedesktop.org/releases/telepathy-spec/telepathy-spec-0.27.4.tar.gz.asc
git: http://cgit.freedesktop.org/telepathy/telepathy-spe
The "Still moving" release.
tarball:
https://telepathy.freedesktop.org/releases/telepathy-qt/telepathy-qt-0.9.8.tar.gz
signature:
https://telepathy.freedesktop.org/releases/telepathy-qt/telepathy-qt-0.9.8.tar.gz.asc
git: http://cgit.freedesktop.org/telepathy/telepathy-qt
Dependencies
rla
- Daniel Pocock
- Guus der Kinderen
_______
telepathy mailing list
telepathy@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/telepathy
The "magic number three" release.
tarball:
http://telepathy.freedesktop.org/releases/telepathy-mission-control/telepathy-mission-control-5.16.5.tar.gz
signature:
http://telepathy.freedesktop.org/releases/telepathy-mission-control/telepathy-mission-control-5.16.5.tar.gz.asc
Hello!
I'm looking for the list of supported XMPP XEPs by Empathy. All I
could find was this
https://telepathy.freedesktop.org/components/telepathy-gabble/ webpage
with a warning "This list is incomplete and quite possibly out of
date"
So where can I find the complete up-to-da
Folks,
Is there a current release manager for telepathy and/or telepathy-gabble?
Back on November 30th, 2018, a critical build fix to resolves failure to
build from source for telepathy-gabble 0.18.4 was made.
I would like to request that whomever is capable of doing so release
telepathy
Mierla
Daniel Pocock
Guus der Kinderen
_______
telepathy mailing list
telepathy@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/telepathy
.
Olivier
On Thu, 2018-08-23 at 12:40 +0200, Johannes Winter wrote:
> Hello everybody,
>
> I'm running empathy with telepathy-rakia on latest debian sid and
> like
> to use my fritzbox router for making SIP calls.
>
> Calling works, but sound quality is far beyond
Hello everybody,
I'm running empathy with telepathy-rakia on latest debian sid and like
to use my fritzbox router for making SIP calls.
Calling works, but sound quality is far beyond acceptable, only grunting
sounds arrive at the other side.
Looking at the system messages they show these
Hi,
I am Rahul, contributing to Sugar Labs.
I am porting our code from telepathy-python to TelepathyGLib (PyGI).
(1) While porting, I could not figure out how to specify the
`ready_handler` and `error_handler` functions in TelepathyGLib.Channel.
Eg: We are using it here -
https://github.com/Pro
On Tue, May 15, 2018 at 03:36:36PM +0200, Emilio Pozuelo Monfort wrote:
> On 15/05/18 14:38, Rahul Bothra wrote:
> > Hi,
> >
> > We (Sugar), are using telepathy for our Python 2 version. We are
> > porting to Python 3.
> >
> > Is a Python 3.x telepathy
Hi,
Thank you, but I didn't quite understand what you proposed.
Currently, our code is written in Python 2 (and PyGTK+ 3) and we are using
the telepathy python library. We are porting to Python 3, and I am looking
for a Python 3 version of Telepathy (preferably, maintained).
If it i
y.
I like to ask, should it work also, and I have something wrong here,
or it is really the only piece od GOA which is not working with 2step
verification?
--
Pozdrawiam, Jakub.
Milion osób dziennie pobiera Firefoksa... pobierz i Ty! firefox.pl
___
tele
On 15/05/18 14:38, Rahul Bothra wrote:
> Hi,
>
> We (Sugar), are using telepathy for our Python 2 version. We are porting to
> Python 3.
>
> Is a Python 3.x telepathy build available or are there any plans to release
> the same ?
The GObject Introspection bindings of
Hi,
We (Sugar), are using telepathy for our Python 2 version. We are porting to
Python 3.
Is a Python 3.x telepathy build available or are there any plans to release
the same ?
Thanks and Regards
Rahul
___
telepathy mailing list
telepathy
Hello
>
> Please, go ahead. I can also make releases, but I have a lot in my
> backlog right now. The instructions should be straightforward.
They look pretty straight forward... Thank you for updating the wiki.
> Please, also push the changes on the github telepathy-idle
> r
of
>> things. Maybe there is something like "maintainer-upload-release"
>> target in telepathy-idle? We have such one in telepathy-qt.
>
> Yay! George left instructions
>
> https://telepathy.freedesktop.org/resources/making_releases/
>
> As far as I can tell without
all project presented at freedesktop.org
> via freedesktop.org at the first place and via github.com as the
> second place. I can help with both, but I develop only Qt side of
> things. Maybe there is something like "maintainer-upload-release"
> target in telepathy-idle? We h
ngs. Maybe there is something like "maintainer-upload-release"
target in telepathy-idle? We have such one in telepathy-qt.
On Sat, Nov 4, 2017 at 12:31 AM, Diane Trout wrote:
> On Fri, 2017-11-03 at 17:18 -0400, Olivier Crête wrote:
>> Hi,
>>
>> I believe the most
On Fri, 2017-11-03 at 17:18 -0400, Olivier Crête wrote:
> Hi,
>
> I believe the most active maintenance of Telepathy is now at
>
> https://github.com/TelepathyIM
>
> Olivier
I believe so too...
Should we have new releases go through freedesktop.org? or just make
github r
Hi,
I believe the most active maintenance of Telepathy is now at
https://github.com/TelepathyIM
Olivier
On Fri, 2017-11-03 at 10:35 -0700, Diane Trout wrote:
> Hi,
>
> Anyone still around who can handle doing releases?
>
> There's a request for a new release of telep
Hi,
Anyone still around who can handle doing releases?
There's a request for a new release of telepathy-idle
https://bugs.freedesktop.org/show_bug.cgi?id=94189
And Polari is actually maintained and reasonably well liked.
(Also Hi team members, I'm starting to have time again. I
lists.fsfe.org/mailman/listinfo/free-rtc
The dev-room administration team:
Saúl Ibarra Corretgé
Iain R. Learmonth
Ralph Meijer
Daniel-Constantin Mierla
Daniel Pocock
_______
telepathy mailing list
telepathy@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/telepathy
rote:
>> > Hi Daniel
>> >
>> > On Sat, Nov 19, 2016 at 12:54 PM, Daniel Pocock > <mailto:dan...@pocock.pro>
>> > <mailto:dan...@pocock.pro <mailto:dan...@pocock.pro>>> wrote:
>> >
>> >
>
:54 PM, Daniel Pocock <mailto:dan...@pocock.pro>
> > <mailto:dan...@pocock.pro <mailto:dan...@pocock.pro>>> wrote:
> >
> >
> > Debian has telepathy-qt for both qt4 and qt5:
> >
> > https://packages.qa.deb
Hi
On Wed, Dec 7, 2016 at 1:33 PM, Daniel Pocock wrote:
>
>
> On 07/12/16 16:22, Gustavo Boiko wrote:
> > Hi Daniel
> >
> > On Sat, Nov 19, 2016 at 12:54 PM, Daniel Pocock > <mailto:dan...@pocock.pro>> wrote:
> >
> >
> > Debian
On 07/12/16 16:22, Gustavo Boiko wrote:
> Hi Daniel
>
> On Sat, Nov 19, 2016 at 12:54 PM, Daniel Pocock <mailto:dan...@pocock.pro>> wrote:
>
>
> Debian has telepathy-qt for both qt4 and qt5:
>
> https://packages.qa.debian.org/t/telepathy-qt.html
>
Hi Daniel
On Sat, Nov 19, 2016 at 12:54 PM, Daniel Pocock wrote:
>
> Debian has telepathy-qt for both qt4 and qt5:
>
> https://packages.qa.debian.org/t/telepathy-qt.html
>
> So far, we've been building and testing telepathy-resiprocate with qt4 only
>
> I've j
Debian has telepathy-qt for both qt4 and qt5:
https://packages.qa.debian.org/t/telepathy-qt.html
So far, we've been building and testing telepathy-resiprocate with qt4 only
I've just updated the resiprocate 1.11.0~alpha1 to Debian, which adds a
telepathy-resiprocate.deb for the
On 18/11/16 09:59, George Kiagiadakis wrote:
> On 11/18/2016 10:27 AM, Daniel Pocock wrote:
>>
>> Debian unstable and testing currently have TelepathyQt 0.9.6.1:
>>
>> https://packages.qa.debian.org/t/telepathy-qt.html
>>
>> I'm going to make a resipro
On 11/18/2016 10:27 AM, Daniel Pocock wrote:
>
> Debian unstable and testing currently have TelepathyQt 0.9.6.1:
>
> https://packages.qa.debian.org/t/telepathy-qt.html
>
> I'm going to make a resiprocate 1.11 release depending on that specific
> version for the telepa
Debian unstable and testing currently have TelepathyQt 0.9.6.1:
https://packages.qa.debian.org/t/telepathy-qt.html
I'm going to make a resiprocate 1.11 release depending on that specific
version for the telepathy-resiprocate connection manager. That will
then be uploaded to Debian as a pa
ntial speakers and participants to discuss the selection
process and other aspects of FOSDEM on the Free-RTC mailing list:
https://lists.fsfe.org/mailman/listinfo/free-rtc
___
telepathy mailing list
telepathy@lists.freedesktop.org
The "crawling" release.
tarball:
http://telepathy.freedesktop.org/releases/telepathy-gabble/telepathy-gabble-0.18.4.tar.gz
signature:
http://telepathy.freedesktop.org/releases/telepathy-gabble/telepathy-gabble-0.18.4.tar.gz.asc
git: http://cgit.freedesktop.org/telepathy/telepathy-gab
o
imo no
reason to not keep the project all under single roof. It should be where
the development
happens.
Wiki - as Gergely mentioned, Github pages may be a very good alternative.
From
there it could even link to individual project's wikis.
Cheers
--
Martin Klapetek | KDE Developer
__
here
the development
happens.
Wiki - as Gergely mentioned, Github pages may be a very good alternative.
From
there it could even link to individual project's wikis.
Cheers
--
Martin Klapetek | KDE Developer
___
telepathy mailing list
telepathy@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/telepathy
* There's no big "MERGE NOW" button to be tempted by mid-review (I'm
> > >guilty of this)
> >
> > It is not a problem of github. You should be able to resist from clicking
> > on buttons. :)
>
> Perhaps, but I don't think code review U
clicking
> on buttons. :)
Perhaps, but I don't think code review UI should be steering a reviewer into
accepting code. You're probably right, though, the more I think about it the
more it seems like a non-issue; the Telepathy committers aren't me ;)
> > * Poor commit me
understood as valid grounds to reject a
>patch
It is equally a valid point to reject a commit.
> * editing a patch is easier than rewriting branch history
No. Rewriting a branch is easier, if you use a proper tool (git rebase
--interactive; git add --patch at the very least).
>
rewriting branch history
* There's no argument over git merge vs git rebase, over a commit log
full of merge commits or rewriting history
Particularly with a project with as many components as Telepathy, I feel
like GitHub issues would be a definite step backward.
I'd also recommend
id, so the new plan now is to finish
> > Telepathy 1.0 as soon as possible and then carry on with a clean spec
> > and codebase.
> >
>
> Has any target date been set for this?
>
> Is it intended to be part of the next Debian release? If so, the freeze
&g
gt;> >
>> > We can not use "Github releases" feature, because:
>> > 1) We need to prepare release in some special way. Namely, we generate
>> > documentation for release tarballs. Github archives contains only the
>> > tree snapshot from a tagged
On 30/10/16 17:59, George Kiagiadakis wrote:
> Therefore, the point is valid, so the new plan now is to finish
> Telepathy 1.0 as soon as possible and then carry on with a clean spec
> and codebase.
>
Has any target date been set for this?
Is it intended to be part of the next De
generate
> > documentation for release tarballs. Github archives contains only the
> > tree snapshot from a tagged commit.
> > 2) The archive directory name is project name + tag name. For
> > TelepathyQt we have archive "telepathy-qt-0.9.7.tar.gz"
pecial way. Namely, we generate
> documentation for release tarballs. Github archives contains only the
> tree snapshot from a tagged commit.
> 2) The archive directory name is project name + tag name. For
> TelepathyQt we have archive "telepathy-qt-0.9.7.tar.gz" with directory
s contains only the tree
snapshot from a tagged commit.
2) The archive directory name is project name + tag name. For TelepathyQt
we have archive "telepathy-qt-0.9.7.tar.gz" with directory
"telepathy-qt-telepathy-qt-0.9.7".
I think we should use https://telepathy.freedesktop.org/re
be
object to code review.
Best,
Gergely
On Sun, Oct 30, 2016, 18:43 George Kiagiadakis wrote:
> Hi all,
>
> There was a discussion on IRC on Friday about our short-term plans. I
> will summarize it here for the archive and for anyone else who is
> interested in project news.
&g
Hi all,
There was a discussion on IRC on Friday about our short-term plans. I
will summarize it here for the archive and for anyone else who is
interested in project news.
Telepathy 1.0
=
After some discussion with ramcq, Kaffeine suggested that we should
proceed with releasing
list:
https://lists.fsfe.org/mailman/listinfo/free-rtc
The dev-room administration team:
Saúl Ibarra Corretgé
Iain R. Learmonth
Ralph Meijer
Daniel-Constantin Mierla
Daniel Pocock
_______
telepathy mailing list
telepathy@lists.freedesktop.org
h
On 14/10/16 15:31, ronald.ev...@l-3com.com wrote:
> /Hello, We are looking for a library that we can build or link into a
> Visual Studio project, that would allow us to send voice over an
> Ethernet link from one Windows PC to another. No other functionality at
> this time. Would
Hello, We are looking for a library that we can build or link into a Visual
Studio project, that would allow us to send voice over an Ethernet link from
one Windows PC to another. No other functionality at this time. Would
Telepathy be suitable for this? Can you please recommend what
; list (like [1] and [2]), right?
>
> [1]
> https://github.com/TelepathyQt/telepathy-nonsense/blob/master/connection.cc#L499
> [2]
> https://github.com/TelepathyQt/telepathy-morse/blob/master/connection.cpp#L661
>
You're right, there should be an "official" list and nonsense
I have just noticed that telepathy-morse actually uses the m_handles as the
'oficial' contact list: it is used to get the contacts in
GetContactListAttributes() and the contacts are added there in the
requestHandles() calling.
[1]
https://github.com/TelepathyQt/telepathy-morse/b
ate...@test.sip5060.net) in the map that shouldn't be a problem, right?
And if so, then you would have another way of getting the 'official'
contact list (like [1] and [2]), right?
[1]
https://github.com/TelepathyQt/telepathy-nonsense/blob/master/connection.cc#L499
[2]
https://
Morse and Nonsense both returns a handle list.
In case of Nonsense: type of the list is UniqueHandleMap with
operators and the used operator [] will return a new handle for each
new identifier.
https://github.com/TelepathyQt/telepathy-nonsense/blob/master/uniquehandlemap.cc#L32
The identifier
l list of contacts?
> The RequestHandles method do exactly
> one thing: returns valid handle for identifier. Error "Invalid
> Handle" should be returned if the given identifier does not identify a
> valid entity of the given type.
Looking at telepathy-nonsense [1] it ret
On 09/19/2016 08:59 PM, Mateus Bellomo wrote:
> Hello,
>
> I have implemented the requestSubscription() and requestHandles()
> methods at telepathy-resiprocate [1]. I'm using Empathy as a client and
> testing it I noticed that when I try to add a contact in the contact
> l
is valid and exists. Telepathy have no such API, so Empathy
> has to workaround it via trying to get info about the contact by typed
> identifier, which (usually) triggers handle assignment, or results in
> "InvalidHandle" error.
>
> The thing is that ensureHandle()
Hello,
I have implemented the requestSubscription() and requestHandles() methods
at telepathy-resiprocate [1]. I'm using Empathy as a client and testing it
I noticed that when I try to add a contact in the contact list, in the
window that opens, the method requestHandle() is being called se
The "get modern" release.
tarball:
http://telepathy.freedesktop.org/releases/telepathy-mission-control/telepathy-mission-control-5.16.4.tar.gz
signature:
http://telepathy.freedesktop.org/releases/telepathy-mission-control/telepathy-mission-control-5.16.4.tar.gz.asc
Fixes:
• exit gra
Would you consider adding Mozilla's IRC settings to irc-networks.xml?
Here are the settings:
https://wiki.mozilla.org/IRC
And I think this is where the file is currently maintained?
https://git.gnome.org/browse/telepathy-account-widgets/tree/tp-account-widgets/irc-network
before I can start typing the name of a contact I'm interested
> in.
>
> Regards,
> Piotr Dobrogost
>
> ps.
> If "Instant Messaging" systray applet is not being developed by the
> telepathy team then please point me to the right place.
Sorry, but this is th
Hi!
I set "Log to a file" for specific contact for "Contact status
changed" notification yet there are no entries in the file given when
setting this option.
Am I missing something?
Regards,
Piotr Dobrogost
___
telepathy ma
Is there some bug or request for this feature present?
Regards,
Piotr Dobrogost
___
telepathy mailing list
telepathy@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/telepathy
Piotr Dobrogost
ps.
If "Instant Messaging" systray applet is not being developed by the
telepathy team then please point me to the right place.
___
telepathy mailing list
telepathy@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/telepathy
On 07/25/2016 04:14 PM, Mateus Bellomo wrote:
> I think it's better if I could look at the source code as you said
> before. Just to confirm. the Empathy source is at [1] and telepathy-qt
> is at [2], right?
>
> [1] https://github.com/GNOME/empathy
> [2] https://cgit.fr
I think it's better if I could look at the source code as you said before.
Just to confirm. the Empathy source is at [1] and telepathy-qt is at [2],
right?
[1] https://github.com/GNOME/empathy
[2] https://cgit.freedesktop.org/telepathy/telepathy-qt
2016-07-25 2:05 GMT-03:00 George Kiagia
On 24.07.2016 16:45, Mateus Bellomo wrote:
My guess is that telepathy-logger and Empathy try to get the
contact's
> name by using the Connection.I.Aliasing interface [2]. Do you
implement
Tp::BaseConnectionAliasingInterface [3] in your CM?
I think so. At [1] I've c
> My guess is that telepathy-logger and Empathy try to get the contact's
> name by using the Connection.I.Aliasing interface [2]. Do you implement
> Tp::BaseConnectionAliasingInterface [3] in your CM?
I think so. At [1] I've created the Tp::BaseConnectionAliasingInterface and
a
On 07/23/2016 11:48 PM, Mateus Bellomo wrote:
> Hello,
>
> I would like to know if there is a page describing the
> addReceivedMessage() telepathy method. I have searched at google but
> didn't find anything, just usage examples at [1], [2], [3] and [4].
I don't th
Hello,
I would like to know if there is a page describing the addReceivedMessage()
telepathy method. I have searched at google but didn't find anything, just
usage examples at [1], [2], [3] and [4].
At [5] there is a Tp::BaseChannelTextTye class reference but there is no
descripti
Just one more question: I don't know if this is related to telepathy but
> when I receive a message at Empathy and the chat window is not open, it
> appears a little box at the bottom of the screen with that message. I saw
> at the debug log that a new channel is being created. Whe
great...many thanks for all this explanation!
I've changed for the way you said [1] and it's working.
Just one more question: I don't know if this is related to telepathy but
when I receive a message at Empathy and the chat window is not open, it
appears a little box at the botto
om the "to" header, and since this is a
"message received" method, the "to" is your self contact, not the remote
one. In 1-1 channels, TargetHandle must be the remote contact.
I just had a look at how telepathy-qt implements ensureChannel() and now
I fully understand
here is no definite answer for the
format of these identifiers in the spec, but telepathy-glib docs [2] do
mention that it should be a SIP URI (so, with the prefix) in the case of
SIP. In the end I think this is your choice. It just needs to be
something that can *uniquely* identify a contact i
he prefix "sip:"
> (e.g. sip:mateusbell...@sip.antisip.com)?
>
> 2016-07-22 2:35 GMT-03:00 George Kiagiadakis :
>
>> On 21.07.2016 22:07, Mateus Bellomo wrote:
>>
>>> Hello,
>>>
>>> I've implemented methods to send and receive text
t;> I've implemented methods to send and receive text message at
>> telepathy-resiprocate but I think I'm mixing the sender/receiver
>> handles. I'm using telepathy-morse [1] as a guide and I would like to
>> know what is the meaning of contactHandle, targetHandle
On 21.07.2016 22:07, Mateus Bellomo wrote:
Hello,
I've implemented methods to send and receive text message at
telepathy-resiprocate but I think I'm mixing the sender/receiver
handles. I'm using telepathy-morse [1] as a guide and I would like to
know what is the meaning o
Hello,
I've implemented methods to send and receive text message at
telepathy-resiprocate but I think I'm mixing the sender/receiver handles.
I'm using telepathy-morse [1] as a guide and I would like to know what is
the meaning of contactHandle, targetHandle and initiatorHandle.
Will anybody from the Telepathy community be at QtCon[1] ?
I've been invited to speak about free real-time communications at the
FSFE Summit[2], which is happening in conjunction with QtCon this year.
Regards,
Daniel
1. https://qtcon.org/
2. https://fsfe.org/community/events/2016/s
On Mon, Jul 4, 2016 at 9:38 PM, Diane Trout wrote:
> Do you have kaccounts, signond, and telepathy sign on plugin (I think
I think so:
[piotr@demon ~]$ rpm -qa | grep kaccounts
kaccounts-integration-16.04.2-1.fc24.x86_64
kaccounts-providers-16.04.2-1.fc24.x86_64
[piotr@demon ~]$ rpm -qa | g
Do you have kaccounts, signond, and telepathy sign on plugin (I think those are
package names, I'm not at computer right now). I think I also has issues with
upgrades, so if the accounts created pre kaccounts they might not have password
saved, also there's a ag-tool command for insp
x86_64
ktp-accounts-kcm-16.04.2-1.fc24.x86_64
ktp-desktop-applets-16.04.2-1.fc24.x86_64
Regards,
Piotr Dobrogost
___
telepathy mailing list
telepathy@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/telepathy
> > import gi
> > gi.extend_path('/telepathy-glib/telepathy-glib/',
> > 'TelepathyGLib-0.12')
> > gi.require_version('TelepathyGLib', '0.12')
> >
> > To try and grab the recently built typelib instead of any one
> &
On 01.07.2016 08:49, Diane Trout wrote:
Hi,
A long time ago I had briefly tried to use telepathy-glib from python
and gave up because it kept segfaulting.
I've been wondering how hard it would be to add tests to telepathy-glib
to verify that the gobject introspection bindings are wo
Hi,
A long time ago I had briefly tried to use telepathy-glib from python
and gave up because it kept segfaulting.
I've been wondering how hard it would be to add tests to telepathy-glib
to verify that the gobject introspection bindings are working
correctly. (And give examples of how t
Hi Mateus,
For message *receiving* you don't have to implement a method in
interface (because method is something to be called by a telepathy
client application). Instead, client listens for messageReceived
signal [1], which you should emit for every incoming message.
[1]
essages.html
[2] https://telepathy.freedesktop.org/spec/Channel_Type_Text.html
[3]
https://github.com/TelepathyQt/telepathy-morse/blob/master/textchannel.cpp
[4]
https://github.com/TelepathyQt/telepathy-nonsense/blob/master/textchannel.cc
___
telepathy mailing
On 06/21/2016 11:38 PM, Diane Trout wrote:
> On Mon, 2016-06-20 at 12:33 +0300, George Kiagiadakis wrote:
>> Hi,
>>
>> I've taken the liberty of reviving a large portion of the old
>> telepathy
>> wiki and polishing some pages so that it's usable and mor
k you, I just
noticed that there is outdated link to Qt docs
(http://doc.qt.nokia.com/latest/). I'll investigate how it used and
fix it sometime soon.
Probably glib and spec docs can be updated via rsync too.
[1] https://telepathy.freedesktop.org/doc/telepathy-qt/
[2]
https://cgit.freedeskt
On Mon, 2016-06-20 at 12:33 +0300, George Kiagiadakis wrote:
> Hi,
>
> I've taken the liberty of reviving a large portion of the old
> telepathy
> wiki and polishing some pages so that it's usable and more current.
>
> Take a look [1] and let me know what
On Mon, 20 Jun 2016 12:33:08 +0300
George Kiagiadakis wrote:
> I've taken the liberty of reviving a large portion of the old
> telepathy wiki and polishing some pages so that it's usable and more
> current.
For someone like me who is just finding his way into the project a
1 - 100 of 6637 matches
Mail list logo
