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 <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 
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

Reply via email to