Morgan,
This is *exactly* what I was looking for, thanks. As a bonus I can get
rid of the "keep" button as well, which is of no use to me.
James Simmons
Morgan Collett wrote:
On Tue, Feb 3, 2009 at 01:21, Wade Brainerd wrote:
There might be something in the Sugar Almanac,
see http://s
On Tue, Feb 3, 2009 at 01:21, Wade Brainerd wrote:
> There might be something in the Sugar Almanac,
> see http://sugarlabs.org/go/ActivityTeam/Resources for a link.
> Alternately, an example of how to disable sharing is here:
> http://git.sugarlabs.org/projects/math/repos/mainline/blobs/master/mat
On Mon, Feb 2, 2009 at 9:26 PM, Gary C Martin wrote:
> Happy to be proven wrong, and I guess it could be a Sugar feature not really
> intended for XOs.
Let's let the flowers bloom: I don't doubt that there are many ways to
make *better* collaboration, on an activity-by-activity basis. But
VNC is
Gary, I've used it for many years on machines much less powerful than the
XO, often for an sshable net meeting with multiple participants, and I think
you might need to do a few simple things to speed it up for yourself.
(Remove fancy graphic backdrop, try for a smaller palette). These things
are
On 3 Feb 2009, at 01:02, Benjamin M. Schwartz wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Eben Eliason wrote:
>> On Mon, Feb 2, 2009 at 7:33 PM, Benjamin M. Schwartz
>> wrote:
> In my mind, this would work perfectly with the above scheme,
> whereby
> any activity th
On Tue, Feb 3, 2009 at 1:33 PM, Benjamin M. Schwartz
wrote:
> OK, but as an Activity author I might like to specify that cap at runtime,
> depending on many things, such as the size of the document.
... start collaborating on an empty Write.xo doc, and shed
participants dynamically as the documen
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Eben Eliason wrote:
> On Mon, Feb 2, 2009 at 7:33 PM, Benjamin M. Schwartz
> wrote:
In my mind, this would work perfectly with the above scheme, whereby
any activity that already has max_participants in it could be viewed
in that manner
On Mon, Feb 2, 2009 at 7:33 PM, Benjamin M. Schwartz
wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Eben Eliason wrote:
>> I think that the addition of a new property in the activity.info file
>> would be logical here. Make it an integer indicating the maximum
>> number of supported
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Eben Eliason wrote:
> I think that the addition of a new property in the activity.info file
> would be logical here. Make it an integer indicating the maximum
> number of supported participants.
OK, but as an Activity author I might like to specify t
