[Sugar-devel] service_name and bundle_id... again
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 activity.info.
Existe alguno parche o alguna solución para evitar cambiar todos los
activity.info de las actividades?
"
Translation:
"When sugar changed the toolbar, or when changed to gtk3, background
compatibility
was maintained. But with the change to 0.98 several activities stoped
working because
have service_name instead of bundle_id in activity.info.
There are a patch or fix to avoid change the activity.info file in every
activity?"
Similar mails reporting errors in activities, and finally found the problem
is related to this
change are received regularly in support mailing lists as iaep or
support-gang.
I wanted try what is needed change to make that activities work, and the
change is really small. Attached is a patch to sugar-toolkit-gtk3. From my
part I think we have broken
compatibility without a good reason in this case, and should be solved.
What you think about include it in Sugar?
Gonzalo
From 5c8aead95135a9023041c1893661f42d872c9178 Mon Sep 17 00:00:00 2001
From: Gonzalo Odiard
Date: Wed, 30 Oct 2013 10:36:33 -0300
Subject: [PATCH] Workaround to enable start of activities still using
service_name
While we deprecated service_name a long time ago, still there are activities
using it, and is a source of frequent problems.
Signed-off-by: Gonzalo Odiard
---
src/sugar3/bundle/activitybundle.py | 12 +---
1 file changed, 9 insertions(+), 3 deletions(-)
diff --git a/src/sugar3/bundle/activitybundle.py b/src/sugar3/bundle/activitybundle.py
index 268092f..2695718 100644
--- a/src/sugar3/bundle/activitybundle.py
+++ b/src/sugar3/bundle/activitybundle.py
@@ -129,9 +129,15 @@ class ActivityBundle(Bundle):
if cp.has_option(section, 'bundle_id'):
self._bundle_id = cp.get(section, 'bundle_id')
else:
-raise MalformedBundleException(
-'Activity bundle %s does not specify a bundle id' %
-self._path)
+if cp.has_option(section, 'service_name'):
+self._bundle_id = cp.get(section, 'service_name')
+logging.error('ATENTION: service_name property in the '
+ 'activity.info file is deprecated, should be '
+ ' changed to bundle_id')
+else:
+raise MalformedBundleException(
+'Activity bundle %s does not specify a bundle id' %
+self._path)
if cp.has_option(section, 'name'):
self._name = cp.get(section, 'name')
--
1.8.1.4
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] New image to test sugar 0.100
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 control error. * Image do not have the Queensland connections profile. * Modem control panel do not open. * Sugar can't shutdown in some cases (by example when the Terminal activity is opened). This image include a candidate solution, we need check if works in all the cases, and if there are some additional issue. Please report. also, include all the fixes in sugar in the last weeks. Activities updated: TurtleArt, Paint, Fototoon New functionalities: * Harvest statistics service. (will upload statistics about usage weekly in a automatic way, or can be executed going to the web services section in the control panel) Gonzalo ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Have we achieved consensus among activite Sugar developers?
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 little more than a distraction without the accompanying code and credibility:( -- David Farning Activity Central: http://www.activitycentral.com ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] service_name and bundle_id... again
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 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 activity.info. > Existe alguno parche o alguna solución para evitar cambiar todos los > activity.info de las actividades? > > " > Translation: > "When sugar changed the toolbar, or when changed to gtk3, background > compatibility > was maintained. But with the change to 0.98 several activities stoped > working because > have service_name instead of bundle_id in activity.info. > There are a patch or fix to avoid change the activity.info file in every > activity?" > > Similar mails reporting errors in activities, and finally found the > problem is related to this > change are received regularly in support mailing lists as iaep or > support-gang. > > I wanted try what is needed change to make that activities work, and the > change is really small. Attached is a patch to sugar-toolkit-gtk3. From my > part I think we have broken > compatibility without a good reason in this case, and should be solved. > > What you think about include it in Sugar? > > Gonzalo > -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] service_name and bundle_id... again
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, Daniel Narvaez wrote: > 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 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 activity.info. >> Existe alguno parche o alguna solución para evitar cambiar todos los >> activity.info de las actividades? >> >> " >> Translation: >> "When sugar changed the toolbar, or when changed to gtk3, background >> compatibility >> was maintained. But with the change to 0.98 several activities stoped >> working because >> have service_name instead of bundle_id in activity.info. >> There are a patch or fix to avoid change the activity.info file in every >> activity?" >> >> Similar mails reporting errors in activities, and finally found the >> problem is related to this >> change are received regularly in support mailing lists as iaep or >> support-gang. >> >> I wanted try what is needed change to make that activities work, and the >> change is really small. Attached is a patch to sugar-toolkit-gtk3. From my >> part I think we have broken >> compatibility without a good reason in this case, and should be solved. >> >> What you think about include it in Sugar? >> >> Gonzalo >> > > > -- > Daniel Narvaez > > ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] service_name and bundle_id... again
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 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, Daniel Narvaez > > > wrote: > >> 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 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 >>> activity.info. >>> Existe alguno parche o alguna solución para evitar cambiar todos los >>> activity.info de las actividades? >>> >>> " >>> Translation: >>> "When sugar changed the toolbar, or when changed to gtk3, background >>> compatibility >>> was maintained. But with the change to 0.98 several activities stoped >>> working because >>> have service_name instead of bundle_id in activity.info. >>> There are a patch or fix to avoid change the activity.info file in >>> every activity?" >>> >>> Similar mails reporting errors in activities, and finally found the >>> problem is related to this >>> change are received regularly in support mailing lists as iaep or >>> support-gang. >>> >>> I wanted try what is needed change to make that activities work, and the >>> change is really small. Attached is a patch to sugar-toolkit-gtk3. From my >>> part I think we have broken >>> compatibility without a good reason in this case, and should be solved. >>> >>> What you think about include it in Sugar? >>> >>> Gonzalo >>> >> >> >> -- >> Daniel Narvaez >> >> > -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Have we achieved consensus among activite Sugar developers?
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 think it would be great if someone did. On Wednesday, 30 October 2013, 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 will be happy to answer any questions, but I would like to get to > work. Talk is little more than a distraction without the accompanying > code and credibility:( > > -- > David Farning > Activity Central: http://www.activitycentral.com > ___ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel > -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] service_name and bundle_id... again
Hi, 2013/10/30 Daniel Narvaez : > 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 of all, GTK2 activities should use sugar-toolkit, not sugar-toolkit-gtk3 . So this is not a bug. The 'service_name' is deprecated since six years ago, in old Sugar v0.70.2. I couldn't find release notes, but that's what git log says. When we did sugar-toolkit-gtk3 for the GTK3 port, we did a cleanup of deprecated API. Was about time. http://wiki.sugarlabs.org/go/Features/GTK3/Porting#Cleanup.2C_adopt_to_API_changes_in_sugar-toolkit-gtk3 By Sugar 0.84 - 0.86, all the core activities updated their activity.info . In Sugar 0.90, deprecation warning messages were added: http://wiki.sugarlabs.org/go/0.90/Notes#API I think these activities should just update their activity.info . > > On Wednesday, 30 October 2013, Gonzalo Odiard wrote: >> >> 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 activity.info. >> Existe alguno parche o alguna solución para evitar cambiar todos los >> activity.info de las actividades? >> >> " >> Translation: >> "When sugar changed the toolbar, or when changed to gtk3, background >> compatibility >> was maintained. But with the change to 0.98 several activities stoped >> working because >> have service_name instead of bundle_id in activity.info. >> There are a patch or fix to avoid change the activity.info file in every >> activity?" >> >> Similar mails reporting errors in activities, and finally found the >> problem is related to this >> change are received regularly in support mailing lists as iaep or >> support-gang. >> >> I wanted try what is needed change to make that activities work, and the >> change is really small. Attached is a patch to sugar-toolkit-gtk3. From my >> part I think we have broken >> compatibility without a good reason in this case, and should be solved. >> >> What you think about include it in Sugar? >> >> Gonzalo > > > > -- > Daniel Narvaez > > > ___ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel > -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] service_name and bundle_id... again
On Wed, Oct 30, 2013 at 1:51 PM, Manuel Quiñones wrote: > Hi, > > 2013/10/30 Daniel Narvaez : > > 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 of all, GTK2 activities should use sugar-toolkit, not > sugar-toolkit-gtk3 . > Wait. The problem is not gtk2 activities using sugar-toolkit-gtk3. The problem is, sugar is using sugar-toolkit-gtk3 to read the activity.infofile on old activities. Then, that activities can't start. We know service_name is deprecated. Also the old style toolbars, but we support activities using old toolbars. In the end, is a problem for the deployments, and we don't lost anything adding the workaround. You know I worked a lot updating core activities to solve this issue, but from the release of sugar 0.98 until today, I saw many problems related with this issue. Sadly, not all the activities are in ASLO, and breaking them without a real benefit is not a good strategy. Gonzalo > > So this is not a bug. The 'service_name' is deprecated since six > years ago, in old Sugar v0.70.2. I couldn't find release notes, but > that's what git log says. When we did sugar-toolkit-gtk3 for the GTK3 > port, we did a cleanup of deprecated API. Was about time. > > http://wiki.sugarlabs.org/go/Features/GTK3/Porting#Cleanup.2C_adopt_to_API_changes_in_sugar-toolkit-gtk3 > > By Sugar 0.84 - 0.86, all the core activities updated their activity.info. > > In Sugar 0.90, deprecation warning messages were added: > http://wiki.sugarlabs.org/go/0.90/Notes#API > > I think these activities should just update their activity.info . > > > > > > On Wednesday, 30 October 2013, Gonzalo Odiard wrote: > >> > >> 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 activity.info. > >> Existe alguno parche o alguna solución para evitar cambiar todos los > >> activity.info de las actividades? > >> > >> " > >> Translation: > >> "When sugar changed the toolbar, or when changed to gtk3, background > >> compatibility > >> was maintained. But with the change to 0.98 several activities stoped > >> working because > >> have service_name instead of bundle_id in activity.info. > >> There are a patch or fix to avoid change the activity.info file in > every > >> activity?" > >> > >> Similar mails reporting errors in activities, and finally found the > >> problem is related to this > >> change are received regularly in support mailing lists as iaep or > >> support-gang. > >> > >> I wanted try what is needed change to make that activities work, and the > >> change is really small. Attached is a patch to sugar-toolkit-gtk3. From > my > >> part I think we have broken > >> compatibility without a good reason in this case, and should be solved. > >> > >> What you think about include it in Sugar? > >> > >> Gonzalo > > > > > > > > -- > > Daniel Narvaez > > > > > > ___ > > Sugar-devel mailing list > > Sugar-devel@lists.sugarlabs.org > > http://lists.sugarlabs.org/listinfo/sugar-devel > > > > > > -- > .. manuq .. > ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] service_name and bundle_id... again
2013/10/30 Gonzalo Odiard : > > > On Wed, Oct 30, 2013 at 1:51 PM, Manuel Quiñones wrote: >> >> Hi, >> >> 2013/10/30 Daniel Narvaez : >> > 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 of all, GTK2 activities should use sugar-toolkit, not >> sugar-toolkit-gtk3 . > > > Wait. The problem is not gtk2 activities using sugar-toolkit-gtk3. > > The problem is, sugar is using sugar-toolkit-gtk3 to read the activity.info > file > on old activities. Then, that activities can't start. 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. Thanks, -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] sugar-web - API for storing data
2013/10/28 Daniel Narvaez > 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 forward. > * F20 Soas. See http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Beta . I've > not tested it personally but it should work. And if it doesn't we really > want to know it. > +1, let's try this next week, and will send you the result > > > On 24 October 2013 22:58, Code wrote: > >> Hello, list! >> I'm Ignacio Raguet (aka Code), a developer interested on web activities >> and I would like to help you. >> >> I have been testing the the Sugar HTML5 + JS framework by creating a >> proof of concept activity >> (https://github.com/code-sur/web-activity-POC). >> >> Now I'm heading to implement some activity state persistence in order to >> be able to resume from a journal entry... I will be happy to make some >> testing on it and give some feedback. >> >> >> To reduce confusion, is there an reference image or a set of RPMs on >> which I should base my work? >> >> >> After reading this article: "http://wiki.sugarlabs.org/go/0.100/Testing";, >> I'm currently using "a 13.2.0 image and installing rpms" and >> "sugar-build"... I have had better results with the former approach and >> that's why my question. >> >> >> Thanks, >> Code >> >> >> >> >> >> >> >> ___ >> Sugar-devel mailing list >> Sugar-devel@lists.sugarlabs.org >> http://lists.sugarlabs.org/listinfo/sugar-devel >> >> > > > -- > Daniel Narvaez > > ___ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel > > Thanks -- Roger. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] service_name and bundle_id... again
> 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 don't see your point. Look at the code. activitybundle.py do not have logic to recognize gtk2 or gtk3 activities. The patch is simple, why look for a more complicate logic, only to avoid new activities using service_name instead of bundle_id? We have a problem with old activities stopping working, not with new activities. Gonzalo > Thanks, > > -- > .. manuq .. > ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] service_name and bundle_id... again
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: Re: [Sugar-devel] service_name and bundle_id... again 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 don't see your point. Look at the code. activitybundle.py do not have logic to recognize gtk2 or gtk3activities. The patch is simple, why look for a more complicate logic, only to avoid new activities using service_name instead of bundle_id? We have a problem with old activities stopping working, not with new activities. Gonzalo Thanks, -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] service_name and bundle_id... again
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 > > -- > 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: Re: [Sugar-devel] service_name and bundle_id... again > > > > 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 don't see your point. > > Look at the code. activitybundle.py do not have logic to recognize gtk2 or > gtk3 > activities. The patch is simple, why look for a more complicate logic, > only to avoid new activities using service_name instead of bundle_id? > > We have a problem with old activities stopping working, not with new > activities. > > Gonzalo > > > > Thanks, > > -- > .. manuq .. > > > > ___ Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel > ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] service_name and bundle_id... again
>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; dwnarv...@gmail.com; sugar-devel@lists.sugarlabs.org 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 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: Re: [Sugar-devel] service_name and bundle_id... again 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 don't see your point. Look at the code. activitybundle.py do not have logic to recognize gtk2 or gtk3activities. The patch is simple, why look for a more complicate logic, only to avoid new activities using service_name instead of bundle_id? We have a problem with old activities stopping working, not with new activities. Gonzalo Thanks, -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] service_name and bundle_id... again
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?? > > > -- > 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; dwnarv...@gmail.com; sugar-devel@lists.sugarlabs.org > > > 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 > > > > > > -- > 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: Re: [Sugar-devel] service_name and bundle_id... again > > > > 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 don't see your point. > > Look at the code. activitybundle.py do not have logic to recognize gtk2 or > gtk3 > activities. The patch is simple, why look for a more complicate logic, > only to avoid new activities using service_name instead of bundle_id? > > We have a problem with old activities stopping working, not with new > activities. > > Gonzalo > > > > Thanks, > > -- > .. manuq .. > > > > ___ Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel > > > ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] service_name and bundle_id... again
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 solution Esteban. 2013/10/30 Alan Jhonn Aguiar Schwyn > I think that we must check the GTK-2 version of all activities and fix that > problem. > 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: Re: [Sugar-devel] service_name and bundle_id... again > > > > 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 don't see your point. > > Look at the code. activitybundle.py do not have logic to recognize gtk2 or > gtk3 > activities. The patch is simple, why look for a more complicate logic, > only to avoid new activities using service_name instead of bundle_id? > > We have a problem with old activities stopping working, not with new > activities. > > Gonzalo > > > > Thanks, > > -- > .. manuq .. > > > > ___ Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel > > ___ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel > > ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] service_name and bundle_id... again
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 From: gonz...@laptop.org To: alan...@hotmail.com CC: ma...@laptop.org; dwnarv...@gmail.com; sugar-devel@lists.sugarlabs.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 wrote: >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; dwnarv...@gmail.com; sugar-devel@lists.sugarlabs.org 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 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: Re: [Sugar-devel] service_name and bundle_id... again 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 don't see your point. Look at the code. activitybundle.py do not have logic to recognize gtk2 or gtk3activities. The patch is simple, why look for a more complicate logic, only to avoid new activities using service_name instead of bundle_id? We have a problem with old activities stopping working, not with new activities. Gonzalo Thanks, -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
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 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 > From: gonz...@laptop.org > To: alan...@hotmail.com > CC: ma...@laptop.org; dwnarv...@gmail.com; sugar-devel@lists.sugarlabs.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?? > > > -- > 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; dwnarv...@gmail.com; sugar-devel@lists.sugarlabs.org > > > 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 > > > > > > -- > 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: Re: [Sugar-devel] service_name and bundle_id... again > > > > 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 don't see your point. > > Look at the code. activitybundle.py do not have logic to recognize gtk2 or > gtk3 > activities. The patch is simple, why look for a more complicate logic, > only to avoid new activities using service_name instead of bundle_id? > > We have a problem with old activities stopping working, not with new > activities. > > Gonzalo > > > > Thanks, > > -- > .. manuq .. > > > > ___ Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel > > > > ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] service_name and bundle_id... again
>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 that are uploaded on SugarLabs site (aslo). From: ebor...@plan.ceibal.edu.uy Date: Wed, 30 Oct 2013 16:20:43 -0200 Subject: Re: [Sugar-devel] service_name and bundle_id... again To: alan...@hotmail.com CC: gonz...@laptop.org; ma...@laptop.org; dwnarv...@gmail.com; sugar-devel@lists.sugarlabs.org 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 solution Esteban. 2013/10/30 Alan Jhonn Aguiar Schwyn 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: Re: [Sugar-devel] service_name and bundle_id... again 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 don't see your point. Look at the code. activitybundle.py do not have logic to recognize gtk2 or gtk3activities. The patch is simple, why look for a more complicate logic, only to avoid new activities using service_name instead of bundle_id? We have a problem with old activities stopping working, not with new activities. Gonzalo Thanks, -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] service_name and bundle_id... again
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 make the patchs for the activities that have that problem.. Date: Wed, 30 Oct 2013 16:24:15 -0200 Subject: Re: [Sugar-devel] service_name and bundle_id... again From: gonz...@laptop.org To: alan...@hotmail.com CC: ma...@laptop.org; dwnarv...@gmail.com; sugar-devel@lists.sugarlabs.org 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 wrote: 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 From: gonz...@laptop.org To: alan...@hotmail.com CC: ma...@laptop.org; dwnarv...@gmail.com; sugar-devel@lists.sugarlabs.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 wrote: >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; dwnarv...@gmail.com; sugar-devel@lists.sugarlabs.org 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 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: Re: [Sugar-devel] service_name and bundle_id... again 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 don't see your point. Look at the code. activitybundle.py do not have logic to recognize gtk2 or gtk3activities. The patch is simple, why look for a more complicate logic, only to avoid new activities using service_name instead of bundle_id? We have a problem with old activities stopping working, not with new activities. Gonzalo Thanks, -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] service_name and bundle_id... again
>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: Ceibal does not have many applications, so the problem is not very serious .. The activities that are not in SugarLabs, (most) are sugarizations or Flash Games (created by the Community) (Sorry for my bad english) Saludos. Ignacio Rodríguez 2013/10/30 Alan Jhonn Aguiar Schwyn > >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 that are uploaded on SugarLabs site (aslo). > > -- > From: ebor...@plan.ceibal.edu.uy > Date: Wed, 30 Oct 2013 16:20:43 -0200 > > Subject: Re: [Sugar-devel] service_name and bundle_id... again > To: alan...@hotmail.com > CC: gonz...@laptop.org; ma...@laptop.org; dwnarv...@gmail.com; > sugar-devel@lists.sugarlabs.org > > > 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 > solution > > Esteban. > > > 2013/10/30 Alan Jhonn Aguiar Schwyn > > I think that we must check the GTK-2 version of all activities and fix that > problem. > 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: Re: [Sugar-devel] service_name and bundle_id... again > > > > 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 don't see your point. > > Look at the code. activitybundle.py do not have logic to recognize gtk2 or > gtk3 > activities. The patch is simple, why look for a more complicate logic, > only to avoid new activities using service_name instead of bundle_id? > > We have a problem with old activities stopping working, not with new > activities. > > Gonzalo > > > > Thanks, > > -- > .. manuq .. > > > > ___ Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel > > ___ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel > > > > ___ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel > > ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] service_name and bundle_id... again
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 with the old toolbars continue working. > If we change this again.. in wich sugar will be avaliable? Sugar 102? > I want include it in Sugar 0.100 > Personally, I update all my GTK-2 activities with bundle_id and exec some > time ago. > > I offer me to make the patchs for the activities that have that problem.. > > Ok, but this is bigger than you and me. We need think in the users, and make life easier to the deployments. I really don't understand what is the problem. Gonzalo > -- > Date: Wed, 30 Oct 2013 16:24:15 -0200 > > Subject: Re: [Sugar-devel] service_name and bundle_id... again > From: gonz...@laptop.org > To: alan...@hotmail.com > CC: ma...@laptop.org; dwnarv...@gmail.com; sugar-devel@lists.sugarlabs.org > > 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 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 > From: gonz...@laptop.org > To: alan...@hotmail.com > CC: ma...@laptop.org; dwnarv...@gmail.com; sugar-devel@lists.sugarlabs.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?? > > > -- > 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; dwnarv...@gmail.com; sugar-devel@lists.sugarlabs.org > > > 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 > > > > > > -- > 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: Re: [Sugar-devel] service_name and bundle_id... again > > > > 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 don't see your point. > > Look at the code. activitybundle.py do not have logic to recognize gtk2 or > gtk3 > activities. The patch is simple, why look for a more complicate logic, > only to avoid new activities using service_name instead of bundle_id? > > We have a problem with old activities stopping working, not with new > activities. > > Gonzalo > > > > Thanks, > > -- > .. manuq .. > > > > ___ Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel > > > > > ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] service_name and bundle_id... again
2013/10/30 Gonzalo Odiard > 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 does not work in the new one, which image will choose the children? Breaking compatibility without a good reason doesn't help to use the latest version of os. Cheers, Esteban. > > > > > 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 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 >> From: gonz...@laptop.org >> To: alan...@hotmail.com >> CC: ma...@laptop.org; dwnarv...@gmail.com; >> sugar-devel@lists.sugarlabs.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?? >> >> >> -- >> 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; dwnarv...@gmail.com; >> sugar-devel@lists.sugarlabs.org >> >> >> 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 >> >> >> >> >> >> -- >> 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: Re: [Sugar-devel] service_name and bundle_id... again >> >> >> >> 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 don't see your point. >> >> Look at the code. activitybundle.py do not have logic to recognize gtk2 >> or gtk3 >> activities. The patch is simple, why look for a more complicate logic, >> only to avoid new activities using service_name instead of bundle_id? >> >> We have a problem with old activities stopping working, not with new >> activities. >> >> Gonzalo >> >> >> >> Thanks, >> >> -- >> .. manuq .. >> >> >> >> ___ Sugar-devel mailing list >> Sugar-devel@lists.sugarlabs.org >> http://lists.sugarlabs.org/listinfo/sugar-devel >> >> >> >> > > ___ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel > > ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] service_name and bundle_id... again
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 change. If upstream is unwilling, then downstream may include it in packaging. -- James Cameron http://quozl.linux.org.au/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Have we achieved consensus among activite Sugar developers?
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 the discussion again; I couldn't see how your three phase approach answered Walter's question about your perception that Sugar Labs is not acting transparently. ;-) Regarding your need to rebuild trust on both sides; perhaps a quantitative approach; you could list the areas and extents in which Sugar Labs trusts Activity Central and Activity Central trusts Sugar Labs now. e.g. feature discussion, design review, patch review, go no-go release decisions, support for released code. Gain general agreement. Then do a diff against past and future. But this begins to sound like a developers' social contract, and not specific to Activity Central. My gut feel is that Sugar Labs treats all technical contributions fairly, regardless of funding source, and that promising funding gains no advantage except better phrasing of the responses; 'cause the funding bias is better understood to be present. However, looking carefully at your three phase approach on 29th October: 1. you are funding work; fine by me, thanks, expect some responses to these developers to be coloured by the awareness of funding, 2. you want more discussion about features and whether features as built are ready for release; fine by me, this is no material change to current process, 3. you speculate that there is a conflict between supporting existing deployments and developing the next releases; this doesn't fit with me, the two workloads are very different vectors in the phase space of possible work, and Sugar Labs primarily operates on only one of the vectors, solving support problems in the next release. -- Disclosure statement: the author provides consulting to OLPCA, and OLPCA does benefit from Sugar Labs releases. The author receives no direct funding from Sugar Labs or any deployment. -- James Cameron http://quozl.linux.org.au/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] service_name and bundle_id... again
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: Message: 3 Date: Thu, 31 Oct 2013 08:03:58 +1100 From: James Cameron To:sugar-devel@lists.sugarlabs.org Subject: Re: [Sugar-devel] service_name and bundle_id... again Message-ID:<20131030210358.gd20...@us.netrek.org> Content-Type: text/plain; charset=iso-8859-1 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 change. If upstream is unwilling, then downstream may include it in packaging. -- James Cameron http://quozl.linux.org.au/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] service_name and bundle_id... again
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 going to break it so badly. And all for what? What possible justification have we to insist on this breakage? (A rhetorical question.) On Wed, Oct 30, 2013 at 07:31:03PM -0400, Tony Anderson wrote: > 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: > >Message: 3 > >Date: Thu, 31 Oct 2013 08:03:58 +1100 > >From: James Cameron > >To:sugar-devel@lists.sugarlabs.org > >Subject: Re: [Sugar-devel] service_name and bundle_id... again > >Message-ID:<20131030210358.gd20...@us.netrek.org> > >Content-Type: text/plain; charset=iso-8859-1 > > > >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 change. > > > >If upstream is unwilling, then downstream may include it in packaging. > > > >-- James Cameron http://quozl.linux.org.au/ > > ___ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel -- James Cameron http://quozl.linux.org.au/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] service_name and bundle_id... again
2013/10/30 James Cameron : > 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 going to break it so badly. > > And all for what? What possible justification have we to insist on > this breakage? (A rhetorical question.) Thanks a lot James et all for the insightful feedback. Yes, let's fix this bug with the patch provided by Gonzalo, now that he said that is not possible to do it only for GTK2 activities. -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
