>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 <alan...@hotmail.com>





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

Reply via email to