John,
This week I finally got everything in sugar-jhbuild to compile. The
Browse activity is the only thing that doesn't work. It can't find a
Mozilla library file. In any case, I was able to get my Read Etexts
activity to share reliably. My activity saves the file to the journal
if it
Le mardi 25 mars 2008 à 16:02 -0400, Benjamin M. Schwartz a écrit :
This works, and will work for the proposed case. For the future, I see
file transfer as precisely the sort of thing that should be handled
internally to Telepathy. Perhaps Telepathy should implement XEP-0234
(file
On Wed, Mar 26, 2008 at 10:05:19AM -0600, Jameson Chema Quinn wrote:
I disagree with #2.
I disagree with both #1 and #2 and, as the current maintainer of
Rainbow, that should tell you something. More bluntly, please experiment
and please publish your work with a public solicitation of
As I said in my previous email, Bitfrost clearly states (correctly, in
my mind) that even justified belief that code originates from some known
individual implies no trust relationship with that code. Period. Use
isolation to make it safer to play with code and use signing to help
reduce
On Tue, 2008-03-25 at 13:46 -0400, Eben Eliason wrote:
Naturally, there are some security concerns, but those could be easily
addressed, I believe, with the usual signing mechanisms. Updates to
activities would only be transparent if the update was signed, etc.
I agree. For a first
I am trying to give Read Etexts the same sharing behavior that core Read
has, using mostly the same code. Until this week I didn't have a good
way to test sharing, but I have set up multiple instances of
sugar-jhbuild on one of my computers so now I can test sharing. My
sugar installation is
Hi James,
Another thing I remember reading is that if two kids share an activity
and one has an older version of the activity than the other, the older
version gets updated so they both have the newer version. This
doesn't
seem to be happening. I have two test machines, one running
It is a known problem that the Read activity doesn't automatically store
a copy of the shared document in the Journal.
Read has bigger problems. I haven't been able to get it to share
the document properly in test after test.
wad
On Mar 21, 2008, at 10:54 AM, James Simmons wrote:
I am
