Yama,
(I privately replied earlier, but here it goes.)
Questions:
Do you know how far this can be done?
Are the numbers related to that radius?
These three numbers are channels. (Different frequency bands
around 2.4GHz, if I understand correctly).
Why do those XOs that are in one
On Fri, May 16, 2008 at 7:19 PM, Albert Cahalan [EMAIL PROTECTED] wrote:
On Fri, May 16, 2008 at 5:28 AM, Edward Cherlin [EMAIL PROTECTED] wrote:
On Thu, May 15, 2008 at 6:15 PM, Albert Cahalan [EMAIL PROTECTED] wrote:
Just look at the deal. Dual-boot costs $7 extra. Governments will
not pay
Hi,
On Tue, May 13, 2008 at 1:41 AM, Kim Quirk [EMAIL PROTECTED] wrote:
A high level view of this process:
1) Prioritize feature and bug fix requests from deployments, developers,
support, our sales/marketing group
2) Triage bugs to determine which bugs are critical to fix to meet the
On Fri, May 16, 2008 at 4:22 AM, Simon Schampijer [EMAIL PROTECTED] wrote:
Eben I only added a slider for the delay of the activation of the hot corners.
By default the delay is zero.
And since I wanted to test out how the warm edge works in general I added a
top
warm edge since I tapped
Tomeu Vizoso wrote:
On Fri, May 16, 2008 at 9:08 PM, Benjamin M. Schwartz
[EMAIL PROTECTED] wrote:
To resolve this, I am going to attempt to list a number of important,
distinct digital objects that this work has produced. I will also
introduce cutesy codenames. I hope that the Sugar
I've implemented some sort of collaboration on my activity. Code is in
the repository
(http://dev.laptop.org/git?p=activities/assimilate;a=summary)
Whenever users are collaborating, everything works more or less, signals
are send and received and all partners have the same content on their
On Sat, May 17, 2008 at 1:14 PM, Marco Pesenti Gritti
[EMAIL PROTECTED] wrote:
Changes I'd make to use Ben taxonomy:
* In the schedule section s/Sugar/Sucrose
Benjamin, you didn't make this change on the wiki. Intentional?
Marco
___
Sugar mailing
The prioritized list has been discussed in a number of venues, and has
general acceptance. Chuck is having regular management mtgs (weekly) so I
intend to put this priority list in front of this group every week to make
sure that this list is well communicated and if someone needs to bring up a
Kim Quirk wrote:
I don't believe this is a one person job.
+1
Here are some suggestions:
* Marco has led the sugar team bug priorities in the past (do you want
to do that again?).
Yup. Started to do some work on it last week.
Marco
___
Sugar
That's great that you're putting collaboration into Assimilate!
When a user joins an activity, they will have a brand new activity
instance. So there should be no merging of activity state needed.
Typically, you should just have joining users send a 'hello' message
when they establish a
Am 17.05.2008 um 04:47 schrieb Marco Pesenti Gritti [EMAIL PROTECTED]
:
Just a reminder that tomorrow is the last available day for the
proposals. So far they seem to be pretty much uncontroversial, except
for Develop which I'd like to discuss in detail next week.
Marco
Please consider
[In the 'On the Naming of Sugar' thread, 'Glucose' was proposed as
the name of the minimal system that must be added to a standard
Linux distribution in order to enable Activities to run, 'Fructose'
as the name of a set of (demonstration) Activities, and 'Sucrose' as
the name for a complete
Currently this interface definition consists of:
- A rough wiki page (http://wiki.laptop.org/go/Low-level_Activity_API)
- The source code to the Python modules in
/usr/share/python2.5/site-packages/sugar/
- The source code to the OLPC maintained activities (are there any anymore?).
I totally
13 matches
Mail list logo
