...@laptop.org; sugar-devel@lists.sugarlabs.org;
walter.ben...@gmail.com; garycmar...@googlemail.com
Subject: Re: [Sugar-devel] We have a problem: activity._shared_activity
On Mon, Mar 4, 2013 at 2:47 PM, Alan Jhonn Aguiar Schwyn
wrote:
> Again GTK2, but it doesn't have any collaboration
On Mon, Mar 4, 2013 at 2:47 PM, Alan Jhonn Aguiar Schwyn <
alan...@hotmail.com> wrote:
> > Again GTK2, but it doesn't have any collaboration feature (yet), so
> you're likely just grepping something out of the old >olpcgames module that
> is not being used (there is work done to migrate to sugarga
On Mon, Mar 4, 2013 at 2:47 PM, Alan Jhonn Aguiar Schwyn
wrote:
>> Again GTK2, but it doesn't have any collaboration feature (yet), so you're
>> likely just grepping something out of the old >olpcgames module that is not
>> being used (there is work done to migrate to sugargame but that's on the
>
> Again GTK2, but it doesn't have any collaboration feature (yet), so you're
> likely just grepping something out of the old >olpcgames module that is not
> being used (there is work done to migrate to sugargame but that's on the
> back-burner just >now).
FYI: Physics has be ported to sugargam
Hi Gonzalo,
Thanks for the reminders :)
On 26 Feb 2013, at 19:08, Gonzalo Odiard wrote:
> After reading the information about Write ticket sl#4436 "Making
> collaboration work again"
> (Thanks Ajay!) I decided check what other activities use
> activity._shared_activity,
> and this is the lis
I found what is happening with distance, pippy and stopwatch. My mistake
was checkout from master branch,
where the maintainers are using the branch gtk3.
I see at least one problem with using a different branch: pootle push to
master.
Also is a nightmare for us identify what branch is using ever
On Sat, Mar 2, 2013 at 7:01 AM, Agustin Zubiaga Sanchez
wrote:
> Gonzalo,
>
> Maybe would be good to create also the _shared_activity variable, with the
> purpose to let the activities continue working while the developers change
> _shared_actvity by shared_activity.
>
> What do you think?
>
>
I d
Gonzalo,
Maybe would be good to create also the _shared_activity variable, with the
purpose to let the activities continue working while the developers change
_shared_actvity by shared_activity.
What do you think?
Regards,
aguz
2013/2/27 Gonzalo Odiard
> After more testing, I found the probl
After more testing, I found the problem is only with activities ported to
gtk3,
then the list of activities we need modify is reduced:
distance: (activity.py)
>
> pippy: groupthink/sugar_tools.py and pippy/mainline/pippy_app.py)
>
> portfolio: (PortfolioActivity.py) (already solved in git)
>
> sto
After reading the information about Write ticket sl#4436 "Making
collaboration work again"
(Thanks Ajay!) I decided check what other activities use
activity._shared_activity,
and this is the list:
[gonzalo@localhost honey]$ grep -r "\._shared_activity" * --include=*.py
calculate: (shareable_activ
10 matches
Mail list logo