Today I received this mail from Esteban Arias in Uruguay:
Cuando sugar cambió el toolbar, o cuando se pasó a gtk3, se mantuvo
compatibilidad hacia atrás.
Pero al pasar a sugar 0.98 varias de las actividades dejaron de funcionar
por tener *service_name* en lugar de* bundle_id *enel
This is images are candidates to be used in Australia deployment
if anybody want look and provide feedback, is welcomed:
http://wiki.sugarlabs.org/go/0.100/Testing#Testing_images
What is new:
Fixes for the following blockers:
* Teacher webservice can send only one file.
* Activity counter
Have we achieved general consensus that the three phase approach I
proposed earlier this week has the potential for establishing a
mutually beneficial relationship while progressively rebuilding trust
on both sides?
I will be happy to answer any questions, but I would like to get to
work. Talk is
This breaks gtk2 activities right? I think that should be considered a bug
and thus we should take the patch (I have not reviewed it). I would add a
comment though so that when we will finally drop gtk2 support we will
remove this too.
On Wednesday, 30 October 2013, Gonzalo Odiard wrote:
Today
Yes, all the affected activities are gtk2 activities.
We removed the code to support service_name in gtk3,
and did not affected the old activities until we ported sugar to gtk3.
About the comment you suggest, do we have any convention for this case?
Gonzalo
On Wed, Oct 30, 2013 at 12:44 PM,
For the comment I mean just something like This is necessary only to keep
gtk2 activities working. It's not obvious unless you know the whole
history of those properties.
On Wednesday, 30 October 2013, Gonzalo Odiard wrote:
Yes, all the affected activities are gtk2 activities.
We removed the
I think
Phase 1. We certainly need more hands.
Phase 2. We have been trying to do a bit of that with the features
discussion. We are going to bootstrap 0.102 very soon and there will be a
chance to improve on what we did for 0.100. I won't personally have time to
write down a specification but I
Hi,
2013/10/30 Daniel Narvaez dwnarv...@gmail.com:
This breaks gtk2 activities right? I think that should be considered a bug
and thus we should take the patch (I have not reviewed it). I would add a
comment though so that when we will finally drop gtk2 support we will remove
this too.
First
On Wed, Oct 30, 2013 at 1:51 PM, Manuel Quiñones ma...@laptop.org wrote:
Hi,
2013/10/30 Daniel Narvaez dwnarv...@gmail.com:
This breaks gtk2 activities right? I think that should be considered a
bug
and thus we should take the patch (I have not reviewed it). I would add a
comment though
2013/10/30 Gonzalo Odiard gonz...@laptop.org:
On Wed, Oct 30, 2013 at 1:51 PM, Manuel Quiñones ma...@laptop.org wrote:
Hi,
2013/10/30 Daniel Narvaez dwnarv...@gmail.com:
This breaks gtk2 activities right? I think that should be considered a
bug
and thus we should take the patch (I
2013/10/28 Daniel Narvaez dwnarv...@gmail.com
Hi,
this thread was also marked as spam by gmail :/ I can think of two
alternatives
yes =/ me too !...
* sugar-build, which you already tried. I'm pretty confident we can get it
to work on your system but it might require some back and
Oh, good Gonzalo, this is the bug to solve then. Your patch is in the
correct direction, but allows GTK3 activities to use service_name,
which I don't think is correct. The fix should allow only GTK2
activities to use service_name, and log a deprecation warning message,
as you did.
I
I think that we must check the GTK-2 version of all activities and fix
thatproblem.Gonzalo: you have the list of activities that need be fixed?
Date: Wed, 30 Oct 2013 15:41:56 -0200
From: gonz...@laptop.org
To: ma...@laptop.org
CC: dwnarv...@gmail.com; sugar-devel@lists.sugarlabs.org
Subject:
Gonzalo: you have the list of activities that need be fixed?
I have a list, but need do it again, because the process I used to
get the last version from aslo is wrong.
But anyway we have the problem of all the activities not available in aslo.
Gonzalo
--
But anyway we have the problem of all the activities not available in aslo.
Wich activities are not in aslo??
Date: Wed, 30 Oct 2013 16:02:25 -0200
Subject: Re: [Sugar-devel] service_name and bundle_id... again
From: gonz...@laptop.org
To: alan...@hotmail.com
CC: ma...@laptop.org;
All the Cazaproblemas, all the things done by Ceibal (like the Biblioteca)
at least.
Gonzalo
On Wed, Oct 30, 2013 at 3:10 PM, Alan Jhonn Aguiar Schwyn
alan...@hotmail.com wrote:
But anyway we have the problem of all the activities not available in
aslo.
Wich activities are not in aslo??
I think that it doesn't solve by fixing all activities. Anybody have an
exhaustive list of all the activities. For example, here in Uruguay have
many activities that kids are using and aren't in any OLPC/SugarLabs site.
I think maintain backward compatibility for gtk2 activities is the best
That is Ceibal problem.. not our problem..We mantain more than 700 activities
and all works.. if Ceibal want, their can fix very easy this problem(only
change 1 line in the activity.info !!! )
Date: Wed, 30 Oct 2013 16:12:31 -0200
Subject: Re: [Sugar-devel] service_name and bundle_id... again
Alan,
We don't maintain 700 and not all work.
Breaking compatibility without a good reason is not good for any platform.
Gonzalo
On Wed, Oct 30, 2013 at 3:22 PM, Alan Jhonn Aguiar Schwyn
alan...@hotmail.com wrote:
That is Ceibal problem.. not our problem..
We mantain more than 700
Uruguay have many activities that kids are using and aren't in any
OLPC/SugarLabs site
And where came from? spontaneous generation?We never will have control of the
activities that someone make and put in their own site.That is a problem of who
made the activity.
We only fix our activities: all
This is an old change.. since Sugar 0.96 we make the changes of service_name by
bundle_idand the class by exec sugar-activity..
If we change this again.. in wich sugar will be avaliable? Sugar 102?
Personally, I update all my GTK-2 activities with bundle_id and exec some time
ago.
I offer me to
Uruguay have many activities that kids are using and aren't in any
OLPC/SugarLabs site
That's true, but these activities are created by programmers, these
programmers should be informed about the change of the structure of the
activity. Reading the Sugar-Devel lists.. or SugarLabs Wiki.
I think:
On Wed, Oct 30, 2013 at 3:31 PM, Alan Jhonn Aguiar Schwyn
alan...@hotmail.com wrote:
This is an old change.. since Sugar 0.96 we make the changes of
service_name by bundle_id
and the class by exec sugar-activity..
Yes, and also we replaced the old toobars by the new toolbars,
but activities
2013/10/30 Gonzalo Odiard gonz...@laptop.org
Alan,
We don't maintain 700 and not all work.
Breaking compatibility without a good reason is not good for any platform.
+1
Ceibal can apply the patch in UY images, but this isn't the point. If an
Activity work in some image and the same activity
On Wed, Oct 30, 2013 at 12:27:57PM -0200, Gonzalo Odiard wrote:
What you think about include it in Sugar?
Yes, include it.
It has no effect unless it is necessary. (Small functional footprint).
It fixes an unnecessary incompatibility.
I have seen no significant evidence for excluding the
On Wed, Oct 30, 2013 at 10:28:35AM -0500, David Farning wrote:
Have we achieved general consensus that the three phase approach I
proposed earlier this week has the potential for establishing a
mutually beneficial relationship while progressively rebuilding trust
on both sides?
I got lost in
HI,
I suspect a 10 line python script could update activity-info.
It may be time to have two versions of each activity in ASLO. One
compatible
with 0.82 and the other with 0.100.
Keeping in mind that 0.82 0.100.
Tony
On 10/30/2013 05:04 PM, sugar-devel-requ...@lists.sugarlabs.org wrote:
Yes, it could, but tracking down every copy of every activity is
impractical for some deployments. Activities are shared around, on
school servers, by e-mail, by USB drive. Adding a needless
incompatibility breaks all this. May as well not have chosen .xo
format in the first place if we're
2013/10/30 James Cameron qu...@laptop.org:
Yes, it could, but tracking down every copy of every activity is
impractical for some deployments. Activities are shared around, on
school servers, by e-mail, by USB drive. Adding a needless
incompatibility breaks all this. May as well not have
29 matches
Mail list logo
