<div dir="ltr">Hello ,<br><br>I went through this <a href="https://github.com/sugarlabs/sugar-docs/blob/master/src/web-activity.md">https://github.com/sugarlabs/sugar-docs/blob/master/src/web-activity.md</a> and successfully run the basic activity on sugar desktop . But since the <i>ActivityTemplate </i>folder was copied from sugarizer repository , the activity ran using the sugar-web of sugarizer although the stop button in the frame didn't work (I saw this issue github) .<br><br>I am not able to find the way to run this activity using the sugar-web of sugarlabs so that I can find the error and compare two repositories(sugar-web of sugarlabs with that of sugar-web of sugarizer).<br>If you could help me to run the activity in <a href="https://github.com/sugarlabs/sugar-docs/blob/master/src/web-activity.md">this</a> tutorial using sugar-web of sugarlabs.<br><br>Thank You</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Apr 22, 2020 at 7:24 AM James Cameron <<a href="mailto:quozl@laptop.org">quozl@laptop.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">You asked if the sugar-web repository of Sugar Labs should be the same<br>
as that of Lionel, or the files inside Sugarizer.<br>
<br>
Yes, that would be ideal.  But it is not enough just to change the<br>
files.  The activities must use the files and must also work properly<br>
on Sugarizer and Sugar.<br>
<br>
You asked what the basis of testing an activity would be.  We have a<br>
checklist in our guide to contributing;<br>
<br>
<a href="https://github.com/sugarlabs/sugar-docs/blob/master/src/contributing.md#testing" rel="noreferrer" target="_blank">https://github.com/sugarlabs/sugar-docs/blob/master/src/contributing.md#testing</a><br>
<br>
The environment for testing would be Sugarizer and Sugar.  If you have<br>
not yet used and analysed these environments, please do so.<br>
<br>
An example of an activity being developed now which has been tested in<br>
both Sugarizer and Sugar, despite not being finished;<br>
<a href="https://github.com/llaske/sugarizer/pull/784" rel="noreferrer" target="_blank">https://github.com/llaske/sugarizer/pull/784</a><br>
<br>
Please also watch the repositories you mentioned, and review pull<br>
requests.<br>
<a href="https://github.com/sugarlabs/sugar-docs/blob/master/src/contributing.md#guide-for-reviewers" rel="noreferrer" target="_blank">https://github.com/sugarlabs/sugar-docs/blob/master/src/contributing.md#guide-for-reviewers</a><br>
<br>
On Tue, Apr 21, 2020 at 10:07:56PM +0530, Abhishek Tanwar wrote:<br>
> Hello,<br>
> Sorry for being away for some time from this topic as I was working on an<br>
> activity for sugarizer . Now I have the time to dedicate to this task. <br>
> <br>
> I am still not able to get a crystal clear image of the task. As originally I<br>
> proposed an activity for sugarizer and James suggested that I would be great if<br>
> the activity could work on both sugar and sugarizer which is actually really<br>
> good.<br>
> <br>
> I have two understanding of this task.<br>
> First one : Sugar-web repository of sugar labs is outdated and need to to<br>
> update to the level of sugar-web of sugarizer . OR Is it to update the<br>
> sugar-web of sugarizer to make it compatible with both sugar and sugarizer<br>
> Firstly,<br>
> I can find two sugar-web repositories one of sugar labs ([1]<a href="https://github.com/" rel="noreferrer" target="_blank">https://github.com/</a><br>
> sugarlabs/sugar-web) and one of sugarizer([2]<a href="https://github.com/llaske/" rel="noreferrer" target="_blank">https://github.com/llaske/</a><br>
> sugar-web) . What I understand is to bring the sugar web repository of sugar<br>
> labs to the save level as that of sugarizer . Am I correct?<br>
> <br>
> Secondly, here [3]<a href="https://github.com/sugarlabs/sugar-docs/blob/master/src/" rel="noreferrer" target="_blank">https://github.com/sugarlabs/sugar-docs/blob/master/src/</a><br>
> web-activity.md to run the basic activity of sugarizer on sugar (ubuntu) it is<br>
> using sugar-web of sugarizer ,which I think should not be the case . We should<br>
> be running it by updating the sugar-web of sugarlabs repository if I am<br>
> not mistaken.<br>
> <br>
> Lastly, what would be the basis to update the sugar-web of sugar labs I mean<br>
> what would be the basis of test?<br>
> <br>
> Thank You<br>
> On Tue, Apr 7, 2020 at 9:30 PM <[4]<a href="mailto:sugar-devel-request@lists.sugarlabs.org" target="_blank">sugar-devel-request@lists.sugarlabs.org</a>><br>
> wrote:<br>
> <br>
>     Send Sugar-devel mailing list submissions to<br>
>             [5]<a href="mailto:sugar-devel@lists.sugarlabs.org" target="_blank">sugar-devel@lists.sugarlabs.org</a><br>
> <br>
>     To subscribe or unsubscribe via the World Wide Web, visit<br>
>             [6]<a href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a><br>
>     or, via email, send a message with subject or body 'help' to<br>
>             [7]<a href="mailto:sugar-devel-request@lists.sugarlabs.org" target="_blank">sugar-devel-request@lists.sugarlabs.org</a><br>
> <br>
>     You can reach the person managing the list at<br>
>             [8]<a href="mailto:sugar-devel-owner@lists.sugarlabs.org" target="_blank">sugar-devel-owner@lists.sugarlabs.org</a><br>
> <br>
>     When replying, please edit your Subject line so it is more specific<br>
>     than "Re: Contents of Sugar-devel digest..."<br>
> <br>
>     Today's Topics:<br>
> <br>
>        1. Re: New Activity Proposal (Lionel Laské)<br>
> <br>
>     ----------------------------------------------------------------------<br>
> <br>
>     Message: 1<br>
>     Date: Tue, 7 Apr 2020 17:46:44 +0200<br>
>     From: Lionel Laské <[9]<a href="mailto:lionel.laske@gmail.com" target="_blank">lionel.laske@gmail.com</a>><br>
>     To: Sugar-dev Devel <[10]<a href="mailto:sugar-devel@lists.sugarlabs.org" target="_blank">sugar-devel@lists.sugarlabs.org</a>><br>
>     Subject: Re: [Sugar-devel] New Activity Proposal<br>
>     Message-ID:<br>
>             <CAA0v29AUnOX04HME306toqvZ-u4nEd4_PfEaYgBLcCrj=[11]<br>
>     <a href="mailto:fsuJg@mail.gmail.com" target="_blank">fsuJg@mail.gmail.com</a>><br>
>     Content-Type: text/plain; charset="utf-8"<br>
> <br>
>     Just few elements to give you some context.<br>
> <br>
>     Sugarizer was designed initially to host Sugar activities written with<br>
>     Sugar-Web. A brief history of Sugarizer is here:<br>
>     [12]<a href="https://github.com/llaske/sugarizer/blob/dev/docs/credits.md" rel="noreferrer" target="_blank">https://github.com/llaske/sugarizer/blob/dev/docs/credits.md</a><br>
>     So the Sugar-Web implementation in Sugarizer was compatible with Sugar.<br>
>     It's why today, the activity template to write a new Sugarizer activity (<br>
>     [13]<a href="https://github.com/llaske/sugarizer/tree/dev/activities/" rel="noreferrer" target="_blank">https://github.com/llaske/sugarizer/tree/dev/activities/</a><br>
>     ActivityTemplate)<br>
>     use in Sugarizer Development Tutorial, still include Python stuff.<br>
>     Just zip the content of your Sugarizer activities into a .xo file (explain<br>
>     here:<br>
>     [14]<a href="https://github.com/sugarlabs/sugar-docs/blob/master/src/web-activity.md" rel="noreferrer" target="_blank">https://github.com/sugarlabs/sugar-docs/blob/master/src/web-activity.md</a><br>
>     #ready-to-release)<br>
>     and you should be able to install it on Sugar and run it. At least,<br>
>     theoretically.<br>
> <br>
>     Unfortunately the compatibility between Sugarizer and Sugar-Web was lost<br>
>     during the development of Sugarizer. The Sugar-Web implementation in<br>
>     Sugarizer was never merged in Sugar-Web, Sugarizer added new features<br>
>     (presence, Journal chooser, ...) not directly compatible with Sugar and no<br>
>     one worked to maintain the compatibility.<br>
> <br>
>     BTW it will be interesting to retrieve this compatibility, even if some<br>
>     features are not directly mappable, at least to allow a Sugarizer activity<br>
>     to be launched on Sugar and run basic features of the activity.<br>
> <br>
>     It's not necessary a very complex task but it require rigor and patience.<br>
>     The thread here: [15]<a href="https://github.com/sugarlabs/sugar-web/pull/133" rel="noreferrer" target="_blank">https://github.com/sugarlabs/sugar-web/pull/133</a><br>
>     explain<br>
>     the process if you're volunteer to work on this task. Of course, both<br>
>     people from the Sugar side and from the Sugarizer side on this list will be<br>
>     able to help you.<br>
> <br>
>     Regards.<br>
> <br>
>               Lionel.<br>
> <br>
>     Le mar. 7 avr. 2020 à 15:56, <[16]<a href="mailto:sugar-devel-request@lists.sugarlabs.org" target="_blank">sugar-devel-request@lists.sugarlabs.org</a>><br>
>     a<br>
>     écrit :<br>
> <br>
>     > Date: Tue, 7 Apr 2020 13:14:28 +0530<br>
>     > From: Abhishek Tanwar <[17]<a href="mailto:abhishektanwar084@gmail.com" target="_blank">abhishektanwar084@gmail.com</a>><br>
>     > To: James Cameron <[18]<a href="mailto:quozl@laptop.org" target="_blank">quozl@laptop.org</a>><br>
>     > Cc: Sugar-dev Devel <[19]<a href="mailto:sugar-devel@lists.sugarlabs.org" target="_blank">sugar-devel@lists.sugarlabs.org</a>><br>
>     > Subject: Re: [Sugar-devel] New Activity Proposal<br>
>     > Message-ID:<br>
>     >         <<br>
>     > [20]<a href="mailto:CALhjuuh2VOWxmwB4Nmn9R8fUwOfAASSkSUZfm22Zge6kXhax2A@mail.gmail.com" target="_blank">CALhjuuh2VOWxmwB4Nmn9R8fUwOfAASSkSUZfm22Zge6kXhax2A@mail.gmail.com</a>><br>
>     > Content-Type: text/plain; charset="utf-8"<br>
>     ><br>
>     > Thanks for the clarification James.<br>
>     > What I am not able to understand is that if I make an activity by<br>
>     following<br>
>     > this [21]<a href="https://github.com/llaske/sugarizer/blob/master/docs/tutorial.md" rel="noreferrer" target="_blank">https://github.com/llaske/sugarizer/blob/master/docs/tutorial.md</a><br>
>     ,<br>
>     > how<br>
>     > will the activity work in both sugarizer as well as in sugar .<br>
>     > I have developed activities for sugarizer earlier and have decent<br>
>     > experience in it but I am not sure if I am correctly understanding what<br>
>     you<br>
>     > are looking for.<br>
>     > I have gone through the discussions in<br>
>     > [22]<a href="https://github.com/sugarlabs/sugar-web/issues/127" rel="noreferrer" target="_blank">https://github.com/sugarlabs/sugar-web/issues/127</a> and<br>
>     > [23]<a href="https://github.com/sugarlabs/sugar-web/pull/133" rel="noreferrer" target="_blank">https://github.com/sugarlabs/sugar-web/pull/133</a> . Sugarizer<br>
>     activities use<br>
>     > the sugar-web library , I can't find the relevant documentation for<br>
>     > developing activities for both sugar and sugarizer, if you could help me<br>
>     > with some documentation that would be great.<br>
>     ><br>
>     > Maybe I am not understanding what you intend to tell. Please let me know<br>
>     > what direction to head in.<br>
>     ><br>
>     > Thank You<br>
>     ><br>
>     > On Tue, Apr 7, 2020 at 3:42 AM James Cameron <[24]<a href="mailto:quozl@laptop.org" target="_blank">quozl@laptop.org</a>><br>
>     wrote:<br>
>     ><br>
>     > > Yes.  Sugar is a Linux environment that can run any language.<br>
>     > > Sugarizer is a JavaScript environment inside browser.  An activity can<br>
>     > > be written to run in both Sugar and Sugarizer.  The Sugar Web library<br>
>     > > facilitates that.  You will have seen the post here earlier about work<br>
>     > > on Sugar Web.<br>
>     > ><br>
>     > > On Tue, Apr 07, 2020 at 03:19:00AM +0530, Abhishek Tanwar wrote:<br>
>     > > > Hello ,<br>
>     > > > I did not quite understand everything .<br>
>     > > > By saying "include sugar as a platform for sugarizer activity" I did<br>
>     > not<br>
>     > > > understand what you are trying to say .<br>
>     > > > Are you saying to make mancala for both sugar and sugarizer?<br>
>     > > ><br>
>     > > > Thank you<br>
>     > > ><br>
>     > > > On Tue, 7 Apr, 2020, 3:10 am James Cameron, <[1][25]<a href="mailto:quozl@laptop.org" target="_blank">quozl@laptop.org</a>><br>
>     > wrote:<br>
>     > > ><br>
>     > > >     We have a Sugar activity for Mancala, written in Python.<br>
>     > > ><br>
>     > > >     [2][26]<a href="https://github.com/sugarlabs/mancala-activity" rel="noreferrer" target="_blank">https://github.com/sugarlabs/mancala-activity</a><br>
>     > > ><br>
>     > > >     License is GPLv3+, but Peter Hewitt has delegated an authority to<br>
>     > me<br>
>     > > >     to relicense his activities as we require.  Sugarizer activities<br>
>     > use<br>
>     > > a<br>
>     > > >     different license in order to maximise distribution.<br>
>     > > ><br>
>     > > >     Please do include Sugar as a platform for your JavaScript<br>
>     activity.<br>
>     > > ><br>
>     > > >     On Tue, Apr 07, 2020 at 02:11:21AM +0530, Abhishek Tanwar wrote:<br>
>     > > >     > Hello,<br>
>     > > >     ><br>
>     > > >     > I have been searching for games that could help the children to<br>
>     > > develop<br>
>     > > >     their<br>
>     > > >     > brains and work in teams as well to incorporate the values of a<br>
>     > > good team<br>
>     > > >     > player.<br>
>     > > >     ><br>
>     > > >     > Mancala(or Mangala) is one such game that I came<br>
>     > > across. [1]https://<br>
>     > > >     > [3][27]<a href="http://en.wikipedia.org/wiki/Mancala" rel="noreferrer" target="_blank">en.wikipedia.org/wiki/Mancala</a><br>
>     > > >     > [2][4][28]<a href="https://mancala.playdrift.com/" rel="noreferrer" target="_blank">https://mancala.playdrift.com/</a><br>
>     > > >     > Mancala on sugarizer can be played between computer vs player ,<br>
>     > > player vs<br>
>     > > >     > player (offline ),player vs player (online using presence).<br>
>     > > >     > I think this could be a good addition to sugarizer for children<br>
>     > of<br>
>     > > age 6<br>
>     > > >     and<br>
>     > > >     > above.<br>
>     > > >     > I want to make this game for sugarizer and would like the<br>
>     > > community to<br>
>     > > >     share<br>
>     > > >     > feedback on this if it would be good addition.<br>
>     > > >     ><br>
>     > > >     > Thank You<br>
>     > > >     ><br>
>     > > >     > References:<br>
>     > > >     ><br>
>     > > >     > [1] [5][29]<a href="https://en.wikipedia.org/wiki/Mancala" rel="noreferrer" target="_blank">https://en.wikipedia.org/wiki/Mancala</a><br>
>     > > >     > [2] [6][30]<a href="https://mancala.playdrift.com/" rel="noreferrer" target="_blank">https://mancala.playdrift.com/</a><br>
>     > > ><br>
>     > > >     > _______________________________________________<br>
>     > > >     > Sugar-devel mailing list<br>
>     > > >     > [7][31]<a href="mailto:Sugar-devel@lists.sugarlabs.org" target="_blank">Sugar-devel@lists.sugarlabs.org</a><br>
>     > > >     > [8][32]<a href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a><br>
>     > > ><br>
>     > > >     --<br>
>     > > >     James Cameron<br>
>     > > >     [9][33]<a href="http://quozl.netrek.org/" rel="noreferrer" target="_blank">http://quozl.netrek.org/</a><br>
>     > > ><br>
>     > > > References:<br>
>     > > ><br>
>     > > > [1] mailto:[34]<a href="mailto:quozl@laptop.org" target="_blank">quozl@laptop.org</a><br>
>     > > > [2] [35]<a href="https://github.com/sugarlabs/mancala-activity" rel="noreferrer" target="_blank">https://github.com/sugarlabs/mancala-activity</a><br>
>     > > > [3] [36]<a href="http://en.wikipedia.org/wiki/Mancala" rel="noreferrer" target="_blank">http://en.wikipedia.org/wiki/Mancala</a><br>
>     > > > [4] [37]<a href="https://mancala.playdrift.com/" rel="noreferrer" target="_blank">https://mancala.playdrift.com/</a><br>
>     > > > [5] [38]<a href="https://en.wikipedia.org/wiki/Mancala" rel="noreferrer" target="_blank">https://en.wikipedia.org/wiki/Mancala</a><br>
>     > > > [6] [39]<a href="https://mancala.playdrift.com/" rel="noreferrer" target="_blank">https://mancala.playdrift.com/</a><br>
>     > > > [7] mailto:[40]<a href="mailto:Sugar-devel@lists.sugarlabs.org" target="_blank">Sugar-devel@lists.sugarlabs.org</a><br>
>     > > > [8] [41]<a href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a><br>
>     > > > [9] [42]<a href="http://quozl.netrek.org/" rel="noreferrer" target="_blank">http://quozl.netrek.org/</a><br>
>     > ><br>
>     > > --<br>
>     > > James Cameron<br>
>     > > [43]<a href="http://quozl.netrek.org/" rel="noreferrer" target="_blank">http://quozl.netrek.org/</a><br>
>     > ><br>
>     > -------------- next part --------------<br>
>     > An HTML attachment was scrubbed...<br>
>     ><br>
>     -------------- next part --------------<br>
>     An HTML attachment was scrubbed...<br>
>     URL: <[44]<a href="http://lists.sugarlabs.org/archive/sugar-devel/attachments/" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/archive/sugar-devel/attachments/</a><br>
>     20200407/36d472d2/attachment-0001.htm><br>
> <br>
>     ------------------------------<br>
> <br>
>     Subject: Digest Footer<br>
> <br>
>     _______________________________________________<br>
>     Sugar-devel mailing list<br>
>     [45]<a href="mailto:Sugar-devel@lists.sugarlabs.org" target="_blank">Sugar-devel@lists.sugarlabs.org</a><br>
>     [46]<a href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a><br>
> <br>
>     ------------------------------<br>
> <br>
>     End of Sugar-devel Digest, Vol 138, Issue 8<br>
>     *******************************************<br>
> <br>
> References:<br>
> <br>
> [1] <a href="https://github.com/sugarlabs/sugar-web" rel="noreferrer" target="_blank">https://github.com/sugarlabs/sugar-web</a><br>
> [2] <a href="https://github.com/llaske/sugar-web" rel="noreferrer" target="_blank">https://github.com/llaske/sugar-web</a><br>
> [3] <a href="https://github.com/sugarlabs/sugar-docs/blob/master/src/web-activity.md" rel="noreferrer" target="_blank">https://github.com/sugarlabs/sugar-docs/blob/master/src/web-activity.md</a><br>
> [4] mailto:<a href="mailto:sugar-devel-request@lists.sugarlabs.org" target="_blank">sugar-devel-request@lists.sugarlabs.org</a><br>
> [5] mailto:<a href="mailto:sugar-devel@lists.sugarlabs.org" target="_blank">sugar-devel@lists.sugarlabs.org</a><br>
> [6] <a href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a><br>
> [7] mailto:<a href="mailto:sugar-devel-request@lists.sugarlabs.org" target="_blank">sugar-devel-request@lists.sugarlabs.org</a><br>
> [8] mailto:<a href="mailto:sugar-devel-owner@lists.sugarlabs.org" target="_blank">sugar-devel-owner@lists.sugarlabs.org</a><br>
> [9] mailto:<a href="mailto:lionel.laske@gmail.com" target="_blank">lionel.laske@gmail.com</a><br>
> [10] mailto:<a href="mailto:sugar-devel@lists.sugarlabs.org" target="_blank">sugar-devel@lists.sugarlabs.org</a><br>
> [11] mailto:<a href="mailto:fsuJg@mail.gmail.com" target="_blank">fsuJg@mail.gmail.com</a><br>
> [12] <a href="https://github.com/llaske/sugarizer/blob/dev/docs/credits.md" rel="noreferrer" target="_blank">https://github.com/llaske/sugarizer/blob/dev/docs/credits.md</a><br>
> [13] <a href="https://github.com/llaske/sugarizer/tree/dev/activities/ActivityTemplate" rel="noreferrer" target="_blank">https://github.com/llaske/sugarizer/tree/dev/activities/ActivityTemplate</a><br>
> [14] <a href="https://github.com/sugarlabs/sugar-docs/blob/master/src/web-activity.md#ready-to-release" rel="noreferrer" target="_blank">https://github.com/sugarlabs/sugar-docs/blob/master/src/web-activity.md#ready-to-release</a><br>
> [15] <a href="https://github.com/sugarlabs/sugar-web/pull/133" rel="noreferrer" target="_blank">https://github.com/sugarlabs/sugar-web/pull/133</a><br>
> [16] mailto:<a href="mailto:sugar-devel-request@lists.sugarlabs.org" target="_blank">sugar-devel-request@lists.sugarlabs.org</a><br>
> [17] mailto:<a href="mailto:abhishektanwar084@gmail.com" target="_blank">abhishektanwar084@gmail.com</a><br>
> [18] mailto:<a href="mailto:quozl@laptop.org" target="_blank">quozl@laptop.org</a><br>
> [19] mailto:<a href="mailto:sugar-devel@lists.sugarlabs.org" target="_blank">sugar-devel@lists.sugarlabs.org</a><br>
> [20] mailto:<a href="mailto:CALhjuuh2VOWxmwB4Nmn9R8fUwOfAASSkSUZfm22Zge6kXhax2A@mail.gmail.com" target="_blank">CALhjuuh2VOWxmwB4Nmn9R8fUwOfAASSkSUZfm22Zge6kXhax2A@mail.gmail.com</a><br>
> [21] <a href="https://github.com/llaske/sugarizer/blob/master/docs/tutorial.md" rel="noreferrer" target="_blank">https://github.com/llaske/sugarizer/blob/master/docs/tutorial.md</a><br>
> [22] <a href="https://github.com/sugarlabs/sugar-web/issues/127" rel="noreferrer" target="_blank">https://github.com/sugarlabs/sugar-web/issues/127</a><br>
> [23] <a href="https://github.com/sugarlabs/sugar-web/pull/133" rel="noreferrer" target="_blank">https://github.com/sugarlabs/sugar-web/pull/133</a><br>
> [24] mailto:<a href="mailto:quozl@laptop.org" target="_blank">quozl@laptop.org</a><br>
> [25] mailto:<a href="mailto:quozl@laptop.org" target="_blank">quozl@laptop.org</a><br>
> [26] <a href="https://github.com/sugarlabs/mancala-activity" rel="noreferrer" target="_blank">https://github.com/sugarlabs/mancala-activity</a><br>
> [27] <a href="http://en.wikipedia.org/wiki/Mancala" rel="noreferrer" target="_blank">http://en.wikipedia.org/wiki/Mancala</a><br>
> [28] <a href="https://mancala.playdrift.com/" rel="noreferrer" target="_blank">https://mancala.playdrift.com/</a><br>
> [29] <a href="https://en.wikipedia.org/wiki/Mancala" rel="noreferrer" target="_blank">https://en.wikipedia.org/wiki/Mancala</a><br>
> [30] <a href="https://mancala.playdrift.com/" rel="noreferrer" target="_blank">https://mancala.playdrift.com/</a><br>
> [31] mailto:<a href="mailto:Sugar-devel@lists.sugarlabs.org" target="_blank">Sugar-devel@lists.sugarlabs.org</a><br>
> [32] <a href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a><br>
> [33] <a href="http://quozl.netrek.org/" rel="noreferrer" target="_blank">http://quozl.netrek.org/</a><br>
> [34] mailto:<a href="mailto:quozl@laptop.org" target="_blank">quozl@laptop.org</a><br>
> [35] <a href="https://github.com/sugarlabs/mancala-activity" rel="noreferrer" target="_blank">https://github.com/sugarlabs/mancala-activity</a><br>
> [36] <a href="http://en.wikipedia.org/wiki/Mancala" rel="noreferrer" target="_blank">http://en.wikipedia.org/wiki/Mancala</a><br>
> [37] <a href="https://mancala.playdrift.com/" rel="noreferrer" target="_blank">https://mancala.playdrift.com/</a><br>
> [38] <a href="https://en.wikipedia.org/wiki/Mancala" rel="noreferrer" target="_blank">https://en.wikipedia.org/wiki/Mancala</a><br>
> [39] <a href="https://mancala.playdrift.com/" rel="noreferrer" target="_blank">https://mancala.playdrift.com/</a><br>
> [40] mailto:<a href="mailto:Sugar-devel@lists.sugarlabs.org" target="_blank">Sugar-devel@lists.sugarlabs.org</a><br>
> [41] <a href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a><br>
> [42] <a href="http://quozl.netrek.org/" rel="noreferrer" target="_blank">http://quozl.netrek.org/</a><br>
> [43] <a href="http://quozl.netrek.org/" rel="noreferrer" target="_blank">http://quozl.netrek.org/</a><br>
> [44] <a href="http://lists.sugarlabs.org/archive/sugar-devel/attachments/20200407/36d472d2/attachment-0001.htm" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/archive/sugar-devel/attachments/20200407/36d472d2/attachment-0001.htm</a><br>
> [45] mailto:<a href="mailto:Sugar-devel@lists.sugarlabs.org" target="_blank">Sugar-devel@lists.sugarlabs.org</a><br>
> [46] <a href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a><br>
<br>
-- <br>
James Cameron<br>
<a href="http://quozl.netrek.org/" rel="noreferrer" target="_blank">http://quozl.netrek.org/</a><br>
</blockquote></div>