On Thu, 28 Jun 2007 at 18:13:21 +0200, Simon Schamijer wrote:
the current telepathy-glib module does not build. Attached is the output.
Fixed (before I saw this mail, in fact).
Simon
___
Sugar mailing list
Sugar@lists.laptop.org
On Sat, 21 Jul 2007 at 13:50:27 +0200, J.M. Maurer wrote:
To the Tube guys:
Do you drop messages on your XMPP server? An AbiCollab packet that
contains an image never gets sent over, resulting in documents getting
out of sync (in fact, the PS seems to disconnect the buddy altogether
from
(Mailing this now while I remember, because this is something we need to
think about relatively soon after Trial 2, I think. Daf and I will be in
Boston on Monday, Tuesday and Wednesday trying to debug collaboration, so it'd
be great if we could talk to Ivan and Eben about this while we're
there.)
To use an m4 macro library you need three things:
* configure.ac mentions it (OK)
* autogen.sh mentions it (OK)
* Makefile.am mentions it (fixed by this patch)
Omission of the third part means that when you change configure.ac and run
make, ./configure is rebuilt without using the m4 directory,
A lot of this looks like a wishlist for the future rather than something
we can implement in the short term, I'm afraid... I think the only
user-visible feature we'll be adding in the near future is invitations.
We'll try to design in ways that don't prevent what you've asked for in
future.
On
On Tue, 07 Aug 2007 at 23:41:11 -0400, Eben Eliason wrote:
So... you want per-activity-instance icons? That's a requirement I've
never heard of: currently, the icon is 100% determined by the type (e.g.
Paint) and the color (i.e. it's the activity program's icon as it
appears in the donut
On Wed, 08 Aug 2007 at 11:41:55 -0400, Dan Williams wrote:
I think lag is more acceptable here since the data set is larger. We
may be able to do this as pull rather than push. I feel like photo
changes shouldn't really be pushes.
On XMPP avatars (photos) are semi-push - the SHA-1 of the
On Fri, 10 Aug 2007 at 20:46:01 +0100, Morgan Collett wrote:
* We'll have an API change for PS when the invitations stuff lands, as
instead of Share we'll have Invite and Advertise, to make the
distinction clear.
We also need Unadvertise() (suggestions for better verbs welcome).
Alternatively,
On Tue, 02 Oct 2007 at 17:43:41 -0400, Benjamin M. Schwartz wrote:
I used these to send arbitrary bytes over the Tube, which only supports utf8.
This isn't actually true. If a D-Bus method is declared with signature 's'
(string) it only supports unicode or UTF-8 str objects. If no signature is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Just a heads-up for anyone who isn't already aware:
We're replacing the Salut (link-local collaborative backend) rMulticast
protocol with a better version, over the next week or so (bug #4044). This is
an incompatible change; there may in fact be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
We still have one set of OLPC-specific patches to Salut (the link-local
collaboration backend) that has been rejected upstream, which is the one
that adds support for the deprecated ip4-address buddy property. This was
used during a transitional
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 25 Oct 2007 at 10:37:50 -0400, Benjamin M. Schwartz wrote:
Erik Blankinship wrote:
Record uses ip4-address, but we've just about completed Record Tubes
(and it is working great).
Should Activity developers assume that stream tubes will
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 25 Oct 2007 at 16:24:11 +0100, Simon McVittie wrote:
If you were previously using ip4-address, using the IPv4 socket type for
stream tubes will give you the nearest API match. I patched Read to use
stream tubes (patches are attached
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 26 Oct 2007 at 00:20:01 -0400, Giannis Galanis wrote:
The feature, although not usable by the activities, it has other benefits.
By observing the buddy list, you acquire instant information of the network
connection go the users:
when
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 26 Oct 2007 at 10:03:55 -0400, Michael Stone wrote:
The current process for RPMS already listed at that location is to
upload an RPM with a higher version number to ~/public_rpms/build on
dev.laptop.org.
It seems to work for me, but just
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sat, 27 Oct 2007 at 18:55:34 -0400, Michael Stone wrote:
Dear Sugar and Devel,
ChangeLogs in the format described on
http://wiki.laptop.org/go/Build_system#ChangeLog_Format
are now MANDATORY for package inclusion. Please write yours.
16 matches
Mail list logo
