Re: [Sugar-devel] Hypothetical sugar-0.90 material, draft 1.

2010-06-12 Thread Simon Schampijer
On 06/11/2010 03:30 PM, Peter Robinson wrote: On Tue, Jun 8, 2010 at 5:54 AM, Michael Stonemich...@laptop.org wrote: Hi folks, Under the temporary working hypothesis that we want to make a Sugar release in a couple of months, I'd like to know more about what we might find ourselves

Re: [Sugar-devel] review process changes

2010-06-12 Thread Bernie Innocenti
El Thu, 03-06-2010 a las 12:19 +0200, Tomeu Vizoso escribió: Thanks, this is really useful. A few observations: - how to link tickets and patches? One way is to always end the commit message with a link to the bug: http://bugs.sugarlabs.org/ticket/1622 This is what git-bz does automatically.

Re: [Sugar-devel] [PATCH] fix trivial typo in extension loading exception

2010-06-12 Thread Bernie Innocenti
El Thu, 03-06-2010 a las 14:03 +0200, Tomeu Vizoso escribió: Well, but I guess we want to test a particular new process and for that, it needs to be written somewhere. Otherwise, each of us could end up testing a different process. Bernie was going to propose concrete changes but then got

Re: [Sugar-devel] ANNOUNCE: Sugar 0.88 for the XO-1

2010-06-12 Thread Bernie Innocenti
El Fri, 04-06-2010 a las 11:00 +1000, James Cameron escribió: Does this change fix the bug? No. (But it does fix the size of icons in the activity ring). BTW, a lot of testers told me that they like the small toolbar icons of the 72dpi mode more than the old big ones. I also think it

Re: [Sugar-devel] tuchpad revelde

2010-06-12 Thread Bernie Innocenti
El Thu, 03-06-2010 a las 15:46 -0600, Kevin Mauricio Benavides Castro escribió: Hola como estan a todos los de la lista tengo un problema en un colegio de una comunidad se entregaron XO y la mayoria de los casos de problemas tecnicos son de touchpad que es muy revelde para solucionar este

Re: [Sugar-devel] Hypothetical sugar-0.90 material, draft 1.

2010-06-12 Thread Bernie Innocenti
El Sat, 12-06-2010 a las 10:26 +0200, Simon Schampijer escribió: PS I'm sure Walter will back me up here! Can someone explain me what a development manager is? Didn't we talk about about Release Management? I hope people don't want to throw away what we have been establishing over the

Re: [Sugar-devel] Hypothetical sugar-0.90 material, draft 1.

2010-06-12 Thread Peter Robinson
On Sat, Jun 12, 2010 at 9:26 AM, Simon Schampijer si...@schampijer.de wrote: On 06/11/2010 03:30 PM, Peter Robinson wrote: On Tue, Jun 8, 2010 at 5:54 AM, Michael Stonemich...@laptop.org  wrote: Hi folks, Under the temporary working hypothesis that we want to make a Sugar release in a

Re: [Sugar-devel] Hypothetical sugar-0.90 material, draft 1.

2010-06-12 Thread Bernie Innocenti
El Sat, 12-06-2010 a las 01:15 -0400, Chris Ball escribió: Hi, Why it is just a pipe dream? 1. Python does not have anything like the DALVIK virtual machine so every Python process consumes a lot of memory. Because of this, implementing the above infrastructure would

Re: [Sugar-devel] Hypothetical sugar-0.90 material, draft 1.

2010-06-12 Thread Bernie Innocenti
El Thu, 10-06-2010 a las 14:24 -0400, Martin Langhoff escribió: On Thu, Jun 10, 2010 at 1:41 PM, Benjamin M. Schwartz bmsch...@fas.harvard.edu wrote: - Reworking the datastore... while I welcome efforts in a new datastore... _every Sugar release has a new DS implementation_ and they get

Re: [Sugar-devel] Hypothetical sugar-0.90 material, draft 1.

2010-06-12 Thread Benjamin M. Schwartz
On 06/12/2010 10:49 AM, Bernie Innocenti wrote: Besides, the assumption that VCS-style deltas will work well with the binary files stored by most Sugar activities is... wishful at best. It is one thing to say that we need a new datastore, and another to say what the new datastore should look

Re: [Sugar-devel] Datastore rewrite

2010-06-12 Thread Bernie Innocenti
El Sat, 12-06-2010 a las 11:40 -0400, Benjamin M. Schwartz escribió: It is one thing to say that we need a new datastore, and another to say what the new datastore should look like. I believe we have consensus on the first part, and I'm fairly sure we don't have consensus on the second. I

[Sugar-devel] Revised hypothetical material for sugar-0.90

2010-06-12 Thread Michael Stone
First, thanks very much to everyone who commented on my previous thread about wild rumors for sugar-0.90. Your comments are very helpful to me because they inform my mental picture of what changes might be available within the next few months to be released. They are also valuable in their own

Re: [Sugar-devel] Hypothetical sugar-0.90 material, draft 1.

2010-06-12 Thread NoiseEHC
Besides, the assumption that VCS-style deltas will work well with the binary files stored by most Sugar activities is... wishful at best. A design working in real-world scenarios would probably require ad-hoc deltifiers for each file format, making it very complex, slow and fragile.

Re: [Sugar-devel] Hypothetical sugar-0.90 material, draft 1.

2010-06-12 Thread Bernie Innocenti
El Sat, 12-06-2010 a las 20:45 +0200, NoiseEHC escribió: Actually these are the exact same problems that could be solved much better with some kind of per activity DS (not the Android one, which would be a little bit overkill). I mean that even making or not making deltas is dependent on

Re: [Sugar-devel] Datastore rewrite

2010-06-12 Thread Frederick Grose
On Sat, Jun 12, 2010 at 12:57 PM, Bernie Innocenti ber...@codewiz.orgwrote: El Sat, 12-06-2010 a las 11:40 -0400, Benjamin M. Schwartz escribió: It is one thing to say that we need a new datastore, and another to say what the new datastore should look like. I believe we have consensus on

[Sugar-devel] Paint patch: fix #813 problem with clipboard OLPC #9022 also

2010-06-12 Thread Gonzalo Odiard
From 12ce2bb69724372132366afa7abf2d3a07be1537 Mon Sep 17 00:00:00 2001 From: Gonzalo Odiard godi...@gmail.com Date: Sat, 12 Jun 2010 18:08:08 -0300 Subject: [PATCH] fix #813 problem with clipboard , OLPC #9022 also This resolves pasting of a image from Browse to Paint or inside Paint Not resolves

Re: [Sugar-devel] ANNOUNCE: Sugar 0.88 for the XO-1

2010-06-12 Thread forster
Bernie 72 dpi icons looked good to me Maybe the logic of big icons was not eyesight but touchpad control? Though the target audience of the XO builds is still children 6-12, it doesnt have to restrict the audience of other Sugar builds. Sugarlabs can have a wider mission than OLPC. There

Re: [Sugar-devel] ANNOUNCE: Sugar 0.88 for the XO-1

2010-06-12 Thread Bernie Innocenti
El Sun, 13-06-2010 a las 08:40 +1000, fors...@ozonline.com.au escribió: 72 dpi icons looked good to me Maybe the logic of big icons was not eyesight but touchpad control? Though the target audience of the XO builds is still children 6-12, it doesnt have to restrict the audience of other

Re: [Sugar-devel] Revised hypothetical material for sugar-0.90

2010-06-12 Thread forster
Thanks Michael I am interested in what each of these changes means for the user experience. Is it possible to add a link to each of the listed changes so I (and maybe others) can read up a bit on them? Should this list be on the wiki? Maybe it is but I cant find it. Like

Re: [Sugar-devel] ANNOUNCE: Sugar 0.88 for the XO-1

2010-06-12 Thread Gary Martin
Hi guys, On 12 Jun 2010, at 23:53, Bernie Innocenti wrote: El Sun, 13-06-2010 a las 08:40 +1000, fors...@ozonline.com.au escribió: 72 dpi icons looked good to me Maybe the logic of big icons was not eyesight but touchpad control? Though the target audience of the XO builds is still

[Sugar-devel] Lost at sea, Calculate-31

2010-06-12 Thread Gary C Martin
Hi Guys, Was just having to re-installing activities to a fresh Sugar (trying to get to test recent Physics patches), and noticed that Calculate is only on ASLO up to version 30! Version 31 was the one supporting the new Sugar toolbars. I guess an official release of it must have slipped

[Sugar-devel] Fructose Dependencies?

2010-06-12 Thread Gary C Martin
Hi Guys, Should pygame be listed as an official Fructose Dependency (or even Glucose)? I can't find it referenced on the wiki road map pages. Only ask as have just installed Sugar as the desktop in a regular F13 install and it didn't pull in pygame as a dependency, so will cause failures for