Simon McVittie wrote:
On Wed, 10 Dec 2008 at 12:37:38 +, Andre Moreira Magalhaes wrote:
- Move all client code from TelepathyQt4 to TelepathyQt4/Client, this
includes moving all cli-*.* files to the Client subdir and renaming
them, removing the cli- prefix.
I agree
Simon McVittie wrote:
The other character allowed in interface/member names but not in key
files is the underscore.
We have already defined parameters containing -, so we can't define an
escape syntax like -FF in a .manager file means the single character \xFF
without breaking backwards
So we are now in time to develop a high-level channel API for tp-qt4,
this API is meant to be simple but extensible, allowing custom channel
types to be constructed
So here is a sketch of this high-level API:
class Channel:
{
public:
string channelType();
uint targetHandle();
uint
Andre Moreira Magalhaes wrote:
Simon McVittie wrote:
The Group API should be based on Contact objects, not handles (at least
as a Feature, but probably as a core thing).
Just forgot to mention that this is already what is on the sketch, so yes.
BR
Andrunko
Hi,
Olli Salli wrote:
More on how I would implement this in the next mail.
Currently, everything doing state download inside Connection revolves
around a central introspection queue. Functions to introspect items
on the Connection are put into this queue, and fired one by one, when
Olli Salli wrote:
On Fri, Feb 6, 2009 at 10:34 PM, Andre Moreira Magalhaes
andre.magalh...@collabora.co.uk wrote:
Hi,
Olli Salli wrote:
I might implement these changes myself, but that would occur during
the latter half of next week at the earliest - so if you happen to
find
Olli Salli wrote:
Maybe I misunderstood some points here but let me say what I understood,
feel free to correct me if I am wrong:
- In your proposal, connection ready by calling becomeReady will work in 2
different situations, when you are offline and when you are online. So if
the connection
Original Message
Subject:tp-qt4 qsharedpointer usage
Date: Wed, 18 Mar 2009 01:24:37 -0300
From: Andre Moreira Magalhaes andre.magalh...@collabora.co.uk
To: Simon McVittie simon.mcvit...@collabora.co.uk, Olli Salli
olli.sa...@collabora.co.uk
Hi guys,
While
Ian Monroe wrote:
I wrote a bug about the issue last month:
https://bugs.freedesktop.org/show_bug.cgi?id=20299
Like I said in the bug report, using KSharedPtr would allow us to always
return a KSharedPtr since the counting occurs in the object itself (via
QSharedPointer), instead of an
Andre Moreira Magalhaes wrote:
Ian Monroe wrote:
I wrote a bug about the issue last month:
https://bugs.freedesktop.org/show_bug.cgi?id=20299
Like I said in the bug report, using KSharedPtr would allow us to always
return a KSharedPtr since the counting occurs in the object itself (via
Kenneth Rohde Christiansen wrote:
Maybe it is interesting for you to look at the WebKit smart pointers.
There is a document explaining them here:
http://webkit.org/coding/RefPtr.html
RefPtr is like more or less like an optimized
QExplictlySharedDataPointer, and RefCounted is like
Hi all,
I would like to make a proposal for tp-qt4 refcounted classes.
1 - Rationale:
Many objects (read all high-level DBus interfaces classes AccoutManager,
Account, Channel, Connection, ...) in tp-qt4 are reference counted.
The pattern used is that classes inherit QSharedData and are used
to
GObjects world.
On Fri, 20 Mar 2009 at 17:50:23 -0300, Andre Moreira Magalhaes wrote:
2.1 - Problems:
2.1.1 - Circular dependency:
In the ideal world we should use QExplicitlySharedDataPointerObject in
the library, even for objects that needs to know about each other, for
example
Simon McVittie wrote:
On Mon, 23 Mar 2009 at 10:35:11 -0500, Ian Monroe wrote
You could declare typedef AccountPtr on account.h and typedef
AccountManagerPtr on account-manager.h and both headers have to include
the other, so this wouldn't work.
You could break each cycle by
Andre Moreira Magalhaes wrote:
Hi all,
I would like to make a proposal for tp-qt4 refcounted classes.
1 - Rationale:
Many objects (read all high-level DBus interfaces classes AccoutManager,
Account, Channel, Connection, ...) in tp-qt4 are reference counted.
The pattern used
Hi all
So here is a proposal for Client Observer, Approver, Handler high-level
API.
Design:
Clients that intend to be an observer, handler, approver, should inherit
the corresponding base classes and implement the pure virtual methods.
To make the methods async a handle for each operation
Simon McVittie wrote:
On Fri, 03 Apr 2009 at 13:00:55 -0300, Andre Moreira Magalhaes wrote:
void setOperationFinished(uint operationHandle);
void setOperationFinishedWithError(uint operationHandle,
const QString errorName, const QString errorMessage);
Eww
Kenneth Rohde Christiansen wrote:
void setOperationFinished(uint operationHandle);
void setOperationFinishedWithError(uint operationHandle,
const QString errorName, const QString errorMessage);
Why not just overload the function?
void setOperationFinished(uint
Revised API attached.
BR
Andrunko
typedef uint OperationHandle;
typedef SharedPtrChannelDispatchOperation ChannelDispatchOperationPtr;
typedef SharedPtrChannelRequest ChannelRequestPtr;
class ChannelDispatchOperation : public StatefulDBusProxy,
private
Simon McVittie wrote:
On Fri, 03 Apr 2009 at 15:15:59 -0300, Andre Moreira Magalhaes wrote:
Simon McVittie wrote:
Can't we have this happen at construct time?
Yeah, we can, But I was thinking if we will be able to add filters at
runtime.
We have 2 solutions:
- Receive
Kenneth Rohde Christiansen wrote:
class ChannelRequest
PendingOperation *proceed();
PendingOperation *cancel();
Dont you accept/reject a request? How can I cancel something that
isn't started yet?
Wrong thread :D. But yes you can, see spec for ChannelRequest.DRAFT
BR
Andrunko
Another try replacing operationHandle with PendingOperation, to be
consistent with the rest of the library.
BR
Andrunko
typedef SharedPtrChannelDispatchOperation ChannelDispatchOperationPtr;
typedef SharedPtrChannelRequest ChannelRequestPtr;
class ChannelDispatchOperation : public
Kenneth Rohde Christiansen wrote:
What about
operationFinished
operationFailed ?
If it failed it didn't really finish, did it?
It means the operation has finished but with an error. I sent another
sketch using PendingOperation, a class that we use all over tp-qt4.
BR
Andrunko
Jonathon Jongsma wrote:
Andre Moreira Magalhaes wrote:
First version of the proposal with all suggestions is up on my shared
branch:
http://git.collabora.co.uk/?p=user/andrunko/telepathy-qt4.git;a=shortlog;h=refs/heads/shared
BR
Andre
OK, I took a look at the current implementation
Jonathon Jongsma wrote:
Andre Moreira Magalhaes wrote:
First version of the proposal with all suggestions is up on my shared
branch:
http://git.collabora.co.uk/?p=user/andrunko/telepathy-qt4.git;a=shortlog;h=refs/heads/shared
BR
Andre
OK, I took a look at the current implementation
Jonathon Jongsma wrote:
Andre Moreira Magalhaes wrote:
[explicit inline SharedPtr(T *d) : d(d) { if (d) { d-ref(); } }]
boost::shared_ptr uses a templated constructor for this case (e.g.
template
class Y SharedPtr(Y *d) ...) which allows it to somehow remember
the actual
pointer type
New revised API attached
Changes:
- Updated to spec 0.17.23
- Removed BaseHandlerClient::addRequest/removeFailedRequest
- Added BaseHandlerClient::requestAdded/requestRemoved signals
- Added ChannelDispatchOperation::reject()
- Removed ChannelRequest::proceed
- Some other small changes
I will
Here's telepathy-qt4 0.1.5, the do not look at the conductor release.
Tarball:
http://telepathy.freedesktop.org/releases/telepathy-qt4/telepathy-qt4-0.1.5.tar.gz
Signature:
http://telepathy.freedesktop.org/releases/telepathy-qt4/telepathy-qt4-0.1.5.tar.gz.asc
The latest reviewed code is always
Here's telepathy-qt4 0.1.8, the approver release.
Tarball:
http://telepathy.freedesktop.org/releases/telepathy-qt4/telepathy-qt4-0.1.8.tar.gz
Signature:
http://telepathy.freedesktop.org/releases/telepathy-qt4/telepathy-qt4-0.1.8.tar.gz.asc
The latest reviewed code is always available from:
Read 0.1.7 where it says 0.1.8, my mistake
Tarball is at:
http://telepathy.freedesktop.org/releases/telepathy-qt4/telepathy-qt4-0.1.7.tar.gz
and Signature:
http://telepathy.freedesktop.org/releases/telepathy-qt4/telepathy-qt4-0.1.7.tar.gz.asc
Andre Moreira Magalhaes wrote:
Here's
Forwarding to the list
Original Message
Subject:Re: [Telepathy] tp-qt4 Requesting channels using
ChannelDispatcher high-level API proposal
Date: Mon, 08 Jun 2009 20:50:41 -0500
From: Matt Rogers ma...@kde.org
To: Andre Moreira Magalhaes andre.magalh
Simon McVittie wrote:
On Mon, 08 Jun 2009 at 17:40:05 -0300, Andre Moreira Magalhaes wrote:
bool canEnsureTextChannel();
ChannelRequestPtr ensureTextChat(
Looks good to me.
:)
bool canEnsureGroupTextChat();
ChannelRequestPtr ensureGroupTextChat
Hey,
First thanks for the helping, below are some comments about the patches
George Kiagiadakis wrote:
Hello everyone,
I have been playing with Tp::AbstractClientApprover and
Tp::ChannelDispatchOperation this weekend in order to implement an approver
for my gsoc project (kcall) and I have
Here's telepathy-qt4 0.1.8, the Every Good Boy Deserves Frontalot release.
Tarball:
http://telepathy.freedesktop.org/releases/telepathy-qt4/telepathy-qt4-0.1.8.tar.gz
Signature:
http://telepathy.freedesktop.org/releases/telepathy-qt4/telepathy-qt4-0.1.8.tar.gz.asc
The latest reviewed code
Simon McVittie wrote:
On Thu, 25 Jun 2009 at 00:11:11 +0300, George Kiagiadakis wrote:
I was about to report this bug now to mission-control, but then I
noticed a detail in the spec:
In
http://telepathy.freedesktop.org/spec.html#type-Qualified_Property_Value_Map
it says:
Key - s
Here's telepathy-qt4 0.1.9, the never too late release.
Tarball:
http://telepathy.freedesktop.org/releases/telepathy-qt4/telepathy-qt4-0.1.9.tar.gz
Signature:
http://telepathy.freedesktop.org/releases/telepathy-qt4/telepathy-qt4-0.1.9.tar.gz.asc
The latest reviewed code is always available
Esben Stien wrote:
Andre Moreira Magalhaes andre.magalh...@collabora.co.uk writes:
Here's telepathy-qt4 0.1.9, the never too late release.
What is it?. Would be nice if you could tell what it is in an
announcement.
???. The announcement contains a full changelog.
BR
Andre
Here's telepathy-qt4 0.1.10, the not yet stable release.
Tarball:
http://telepathy.freedesktop.org/releases/telepathy-qt4/telepathy-qt4-0.1.10.tar.gz
Signature:
http://telepathy.freedesktop.org/releases/telepathy-qt4/telepathy-qt4-0.1.10.tar.gz.asc
The latest reviewed code is always
Hi,
One more API sketch for review. This time we are going to implement
FileTransfer
support on tp-qt4 and I would like to have some review comments on the API.
For those not familiar with FileTransfer please refer to
Kenneth Rohde Christiansen wrote:
PendingChannelRequest *createFileTransfer(
Shouldn't this be requestFileTransfer?
The constructors (though with many defaults) seems very scary and
complex. Is the request immediately, or would be be possible to change
some of these initialization
The code seems ok, except it's missing qRegisterMetatype for
ParametersDefinition/List. You can also try TelepathyQt4
ConnectionManager API, it does that for you, and also reads from manager
file if available.
BR
Andrunko
chen zheng wrote:
Hello,
I want use QDBus invoke some function of
Here's telepathy-qt4 0.1.11, the on more to go release.
Tarball:
http://telepathy.freedesktop.org/releases/telepathy-qt4/telepathy-qt4-0.1.11.tar.gz
Signature:
http://telepathy.freedesktop.org/releases/telepathy-qt4/telepathy-qt4-0.1.11.tar.gz.asc
The latest reviewed code is always
Here's telepathy-qt4 0.2.0, the I Shot the Sheriff release.
Tarball:
http://telepathy.freedesktop.org/releases/telepathy-qt4/telepathy-qt4-0.2.0.tar.gz
Signature:
http://telepathy.freedesktop.org/releases/telepathy-qt4/telepathy-qt4-0.2.0.tar.gz.asc
The latest reviewed code is always
The no pain, no gain release. This is a bugfix release for 0.2.x series.
telepathy-qt4 is a Qt 4 C++ binding for the Telepathy real-time communication
framework, which can be used to implement user interfaces, loggers and
other Telepathy components.
Tarball:
The With My Own Two Hands release.
telepathy-qt4 is a Qt 4 C++ binding for the Telepathy real-time
communication
framework, which can be used to implement user interfaces, loggers and
other Telepathy components.
Tarball:
The it's all about coffee release.
telepathy-qt4 is a Qt 4 C++ binding for the Telepathy real-time
communication
framework, which can be used to implement user interfaces, loggers and
other Telepathy components.
Tarball:
On 18/04/10 10:09, Dario Freddi wrote:
Hello all,
as discussed with Andre on IRC, I drafted a small API for managing Tubes in
tp-qt4 (see attachment). There's really nothing fancy here: it's a quite
straightforward mapping of the spec to a Qt-like API, and it's mostly what tp-
glib does as
The poisoned with anti-coffee release.
telepathy-qt4 is a Qt 4 C++ binding for the Telepathy real-time
communication
framework, which can be used to implement user interfaces, loggers and
other Telepathy components.
Tarball:
on this one - if you're happy enough, I'll start hacking on
them straight away ;)
On Monday 19 April 2010 19:57:40 Andre Moreira Magalhaes wrote:
On 18/04/10 10:09, Dario Freddi wrote:
Hello all,
as discussed with Andre on IRC, I drafted a small API for managing Tubes
in tp-qt4 (see
Hey there,
Great that you were able to figure it out why it is failing. Now we need
to check if changing the spec is an option as maybe we have other CMs
that actually send q instead of u.
If a spec change is possible we just need to update tp-qt4 to use the
new spec and everything should
On 03/05/10 14:51, Simon McVittie wrote:
On Sun, 02 May 2010 at 12:31:34 +0200, Dario Freddi wrote:
so after some further debugging with George, we found out the problem that
made File transfers and stream tubes crash. It looks like dbus-glib is sending
u instead of q, due to the fact that
The generic fun release.
telepathy-qt4 is a Qt 4 C++ binding for the Telepathy real-time
communication
framework, which can be used to implement user interfaces, loggers and
other Telepathy components.
Tarball:
http://telepathy.freedesktop.org/releases/telepathy-qt4/telepathy-qt4-0.3.3.tar.gz
On 11/05/10 13:36, Olli Salli wrote:
Finally had time to take a more thorough look at your code. Some observations:
Account::createStreamTube: about including TargetHandle == 0 in the
request when contact is NULL: the spec states about TargetHandle that
If this is present in a channel request,
On 12/05/10 11:30, Andre Moreira Magalhaes wrote:
On 11/05/10 13:36, Olli Salli wrote:
Finally had time to take a more thorough look at your code. Some
observations:
Account::createStreamTube: about including TargetHandle == 0 in the
request when contact is NULL: the spec states about
The Cause time takes time, ya know release.
telepathy-qt4 is a Qt 4 C++ binding for the Telepathy real-time
communication
framework, which can be used to implement user interfaces, loggers and
other Telepathy components.
Tarball:
automatically.
BR
--
Andre Moreira Magalhaes (andrunko)
Jabber: andru...@gmail.com
MSN: andru...@hotmail.com
Skype: andrunko
IRC: andrunko
Blog: http://andrunko.blogspot.com
___
telepathy mailing list
, meaning it is ready to
merge.
Please don't merge this before I am able to fully review it, which is on
my priority list.
BR
--
Andre Moreira Magalhaes (andrunko)
Jabber: andru...@gmail.com
MSN: andru...@hotmail.com
Skype: andrunko
IRC
On Thu, 2010-06-03 at 00:54 -0300, Andre Moreira Magalhaes wrote:
Also please file a bug in fd.o (Product Telepathy, Component tp-qt4)
Already filed 2 bugs for this. The first one is to add the Tube
interface (fd.o#28366) support and the second is to add StreamTube
(fd.o#28367) support. Feel free
On Thu, 2010-06-03 at 07:55 +0300, Olli Salli wrote:
On Thu, Jun 3, 2010 at 7:13 AM, Andre Moreira Magalhaes
andre.magalh...@collabora.co.uk wrote:
Please split your changes in 2 branches one for Tube specific changes
and the other one on top of you tube branch to implement StreamTube
telepathy-qt4 0.3.5 (2010-06-21)
The Think I'll get it done yesterday release.
telepathy-qt4 is a Qt 4 C++ binding for the Telepathy real-time
communication
framework, which can be used to implement user interfaces, loggers and
other Telepathy components.
Hi all,
So after working on implementing support for profiles in tp-qt4 I came
up with some issues and ideas I would like to discuss.
The proposal here is based on the work done by Vivek found in
http://people.collabora.co.uk/~vivek/drafts/
You can find the modified XMLs in
On Fri, 2010-10-15 at 21:19 -0300, Andre Moreira Magalhaes wrote:
New API:
* Added ChannelDispatchOperation high-level class.
Read Added ContactSearch high-level class here.
BR
Andre
___
telepathy mailing list
telepathy@lists.freedesktop.org
http
Hey all,
So I filed a bug report for this, we can continue the discussion there.
https://bugs.freedesktop.org/show_bug.cgi?id=31195
BR
--
Andre Moreira Magalhaes (andrunko)
Jabber: andru...@gmail.com
MSN: andru...@hotmail.com
Skype
The sickness won't slow us down release.
telepathy-qt4 is a Qt 4 C++ binding for the Telepathy real-time
communication framework, which can be used to implement user interfaces,
loggers and other Telepathy components.
Tarball:
The O HAI MY NAME IS CONFERENCE release.
telepathy-qt4 is a Qt 4 C++ binding for the Telepathy real-time
communication framework, which can be used to implement user interfaces,
loggers and other Telepathy components.
Tarball:
Hey,
On Fri, 2010-12-17 at 12:26 +0100, nic...@nicoladefilippo.it wrote:
Hi,
i have installed telepathy-qt4-0..5.0 (sudo make install), but
in /usr/local/include/telepathy-1.0/TelepathyQt4/ missing
ConnectionManagerLowlevel header file. I copied it with cp. Is it a
bug?
Yep, it's a bug and
On Thu, 2010-12-23 at 12:44 +, Will Thompson wrote:
CCing the list again.
On 23/12/10 12:35, nic...@nicoladefilippo.it wrote:
Hi,
On 22/12/10 09:20, nic...@nicoladefilippo.it wrote:
is this issue also in version 0.21?
Which issue? 0.21 looks like a specification version
The I'm not subscribed now, right? WRONG release.
telepathy-qt4 is a Qt 4 C++ binding for the Telepathy real-time
communication framework, which can be used to implement user interfaces,
loggers and other Telepathy components.
Tarball:
The contact factorization release.
telepathy-qt4 is a Qt 4 C++ binding for the Telepathy real-time
communication framework, which can be used to implement user interfaces,
loggers and other Telepathy components.
Tarball:
The the shower of golden paper bags release.
telepathy-qt4 is a Qt 4 C++ binding for the Telepathy real-time
communication framework, which can be used to implement user interfaces,
loggers and other Telepathy components.
Tarball:
The I wish I had less contacts release.
telepathy-qt4 is a Qt 4 C++ binding for the Telepathy real-time
communication framework, which can be used to implement user interfaces,
loggers and other Telepathy components.
Tarball:
The accept/decline release.
telepathy-qt4 is a Qt 4 C++ binding for the Telepathy real-time
communication framework, which can be used to implement user interfaces,
loggers and other Telepathy components.
Tarball:
The beginning release.
TelepathyQt4Yell is an extension library for TelepathyQt4. It adds
support for some DRAFT interfaces that could not land in TelepathyQt4
itself due to API/ABI stability rules as well as some not-yet-final
utility classes.
Once the interfaces are final and the implementation
The fit for galoshes release.
telepathy-qt4 is a Qt 4 C++ binding for the Telepathy real-time
communication framework, which can be used to implement user interfaces,
loggers and other Telepathy components.
Tarball:
The nothing big release.
telepathy-qt4 is a Qt 4 C++ binding for the Telepathy real-time
communication framework, which can be used to implement user interfaces,
loggers and other Telepathy components.
Tarball:
http://telepathy.freedesktop.org/releases/telepathy-qt4/telepathy-qt4-0.4.4.tar.gz
The keep calling release.
TelepathyQt4Yell is an extension library for TelepathyQt4. It adds
support for some DRAFT interfaces that could not land in TelepathyQt4
itself due to API/ABI stability rules as well as some not-yet-final
utility classes.
Once the interfaces are final and the
The where are my contacts? release.
telepathy-qt4 is a Qt 4 C++ binding for the Telepathy real-time
communication framework, which can be used to implement user interfaces,
loggers and other Telepathy components.
Tarball:
The planned engineering works for the last year release.
telepathy-qt4 is a Qt 4 C++ binding for the Telepathy real-time
communication framework, which can be used to implement user interfaces,
loggers and other Telepathy components.
Tarball:
The more contacts? release.
telepathy-qt4 is a Qt 4 C++ binding for the Telepathy real-time
communication framework, which can be used to implement user interfaces,
loggers and other Telepathy components.
Tarball:
The How to remove a hole from a set of holes release.
telepathy-qt4 is a Qt 4 C++ binding for the Telepathy real-time
communication framework, which can be used to implement user interfaces,
loggers and other Telepathy components.
Tarball:
The can I call release.
TelepathyQt4Yell is an extension library for TelepathyQt4. It adds
support for some DRAFT interfaces that could not land in TelepathyQt4
itself due to API/ABI stability rules as well as some not-yet-final
utility classes.
Once the interfaces are final and the
The A brown paper bagful of Easter Eggs release.
telepathy-qt4 is a Qt 4 C++ binding for the Telepathy real-time
communication framework, which can be used to implement user interfaces,
loggers and other Telepathy components.
Tarball:
The Doc(tor) Love release.
telepathy-qt4 is a Qt 4 C++ binding for the Telepathy real-time
communication framework, which can be used to implement user interfaces,
loggers and other Telepathy components.
Tarball:
http://telepathy.freedesktop.org/releases/telepathy-qt4/telepathy-qt4-0.6.1.tar.gz
The Doctor Love knew this so he made another great invention just for
the lonely you! release.
telepathy-qt4 is a Qt 4 C++ binding for the Telepathy real-time
communication framework, which can be used to implement user interfaces,
loggers and other Telepathy components.
This release begins the
Hi,
On Mon, 2011-05-30 at 18:17 +0100, Will Thompson wrote:
Concretely, telepathy-glib would be split into three shared libraries:
• telepathy-glib-proxy, which basically just contains TpProxy (and
would go away in a future where something equivalent is in GLib and
tp-glib moves to it).
The where is the file? release.
telepathy-qt4 is a Qt 4 C++ binding for the Telepathy real-time
communication framework, which can be used to implement user interfaces,
loggers and other Telepathy components.
Tarball:
The Oh! I am still alive release.
telepathy-qt4 is a Qt 4 C++ binding for the Telepathy real-time
communication framework, which can be used to implement user interfaces,
loggers and other Telepathy components.
Tarball:
The small but important release.
telepathy-qt4 is a Qt 4 C++ binding for the Telepathy real-time
communication framework, which can be used to implement user interfaces,
loggers and other Telepathy components.
Tarball:
Hey David,
On Wed, 2011-09-28 at 19:49 +0100, David Edmundson wrote:
Not sure where the right place for patches is into TpQt4. So I'll just
spam the list.
First thanks for the patch. As Simon said, our preferred patch tracking
system is the bugtracker, so I would like to ask you to file a bug
The A Very British Cover-up release.
telepathy-qt4 is a Qt 4 C++ binding for the Telepathy real-time
communication framework, which can be used to implement user interfaces,
loggers and other Telepathy components.
Tarball:
telepathy-qt4 is a Qt 4 C++ binding for the Telepathy real-time
communication framework, which can be used to implement user interfaces,
loggers and other Telepathy components.
Tarball:
http://telepathy.freedesktop.org/releases/telepathy-qt4/telepathy-qt4-0.6.5.tar.gz
Signature:
The a must release.
telepathy-qt4 is a Qt 4 C++ binding for the Telepathy real-time
communication framework, which can be used to implement user interfaces,
loggers and other Telepathy components.
Tarball:
http://telepathy.freedesktop.org/releases/telepathy-qt4/telepathy-qt4-0.7.3.tar.gz
The Make your own vacuum tubes release.
telepathy-qt4 is a Qt 4 C++ binding for the Telepathy real-time
communication framework, which can be used to implement user interfaces,
loggers and other Telepathy components.
This release begins the feature frozen 0.8 stable release series. 0.9
will be
The Merry Christmas release.
telepathy-qt is a Qt C++ binding for the Telepathy real-time
communication framework, which can be used to implement user interfaces,
loggers and other Telepathy components.
This release begins the new 0.9 development series for feature additions
following the 0.8
The it is call time release.
telepathy-qt is a Qt C++ binding for the Telepathy real-time
communication framework, which can be used to implement user interfaces,
loggers and other Telepathy components.
Tarball:
http://telepathy.freedesktop.org/releases/telepathy-qt/telepathy-qt-0.9.1.tar.gz
95 matches
Mail list logo
