Re: [Sugar-devel] Best Practices for setting font and widget size

Best practice is not hardcode, but measure the text and set the font size as needed. You can use Pango to measure the text. Example code in Memorize activity: https://github.com/godiard/memorize-activity/blob/master/svgcard.py#L303 On Sun, Jul 24, 2016 at 9:15 AM, Yash Agarwal

Re: [Sugar-devel] Thoughts on Collab

On Sun, Jul 24, 2016 at 9:35 PM, Tony Anderson wrote: I'm sorry. I don't understand you. Currently collaboration in locations with a school server is done by ejabberd. This resulted from the fact that the original mesh and later ad hoc networks did not support the

Re: [Sugar-devel] Thoughts on Collab

_tcp" >> 8080 "name=Sam P" "color=#fff,#000" "other_metadata=other_value" >> avahi-discover >> >> All of the backends could give us an ip and a port to reach the other >> person. For the avahi backend, this would be a direct connection

[Sugar-devel] Best Practices for setting font and widget size

Hello, In this pic

Re: [Sugar-devel] Thoughts on Collab

I'm sorry. I don't understand you. Currently collaboration in locations with a school server is done by ejabberd. This resulted from the fact that the original mesh and later ad hoc networks did not support the requirements of actual deployments. This means the software supports XMMP to

Re: [Sugar-devel] Thoughts on Collab

he other buddy. For the schoolserver, it would be proxied through the schoolserver. I'd love to hear your thoughts on the other problems, and on this problem to. Thanks, Sam -- next part -- An HTML attachment was scrubbed... URL: <http://

Re: [Sugar-devel] Thoughts on Collab

I actually don't want to use XMPP for the new collab system. I don't care how nice the library is. Telepathy isn't the best, maybe pyxmpp2 or nbxmpp are better. But xmpp is not the right protocol for sugar. Say you want to solve problem 2 and have a shared group channel. You could use

Re: [Sugar-devel] Thoughts on Collab

The 'patch' was essentially to place every ejabberd client in the same group. AFIK, there is no strong reason not to upgrade ejabberd on the server side to a current release. I don't have the information at hand but we were working with a group with focus on collaboration who implemented the

Re: [Sugar-devel] Thoughts on Collab

his would be a direct connection to > the other buddy. For the schoolserver, it would be proxied through the > schoolserver. > > I'd love to hear your thoughts on the other problems, and on this > problem to. > > Thanks, > Sam > -- next part -- > An HTML attac

Re: [Sugar-devel] Thoughts on Collab

> On July 23, 2016 at 5:36 PM sam@sam.today wrote: > > > Hi All, > > In the irc meeting 2 nights ago, we discussed adding collaberation to > the journal project feature. Abhijit has spent around 3 weeks working > on it. But we can't even get a text channel between the participants. >

Re: [Sugar-devel] Thoughts on Collab

XMPP is a standard protocol (originally called jabber). Currently, collaboration is supported on the schoolserver by ejabberd. This implementation has not been changed for years AFIK. In any case, implementation of collaboration probably should be XMPP compliant to maintain maximum

Re: [Sugar-devel] Thoughts on Collab

Currently I can use gajim to chat to Sugar users (it will trigger a Chat activity invitation). This is the level I meant when I said "backward compatible". I don't know if python-nbxmpp or python-farstream support some sort of tube, but for sure the api won't be the same as telepathy. Those are