<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi, Dave<br>
<br>
Its an educational project. An example is
<a class="moz-txt-link-freetext" href="https://github.com/ezequielpereira/Bridge">https://github.com/ezequielpereira/Bridge</a>. This version of the
Bridge-activity was developed as part of GCI. <br>
The zip downloaded from github is named Bridge-master.zip. I copied
the zip to an XO-1.75, unzipped, and ran setup.py dist_xo. The
result was a <br>
proper xo bundle which installed and ran. However, it failed to
start: import error lib/box2d_32/_Box2D.so.<br>
<br>
So setup.py solves the problem of the folder name. However, it does
suggest that we will need to upload xo bundles through a two step
process of <br>
downloading the zip and using it to create the bundle to be uploaded
to ASLO. <br>
<br>
On ASLO, this activity is shown as working on versions 0.82-0.104.
This is clearly not correct. I found in uploading helloweb that this
range is the default <br>
value. It is possible to set the lower end (e.g. 0.100 for
sugar-web-activities) but the upper end is 0.104 (0.106, 0.108 have
not been added to the widget).<br>
<br>
This import error raises again the issue that some dependencies will
be changed based on XO model and on 32 or 64 bit architechture.
During GCI, Walter set up a platform variable that activities can
test to determine the environment. This will become increasingly
important to developers.<br>
<br>
Tony<br>
<br>
<div class="moz-cite-prefix">On 05/18/2016 02:42 PM, Dave Crossland
wrote:<br>
</div>
<blockquote
cite="mid:CAEozd0zhW5DMqBFwmP-Fm7qsV2xk622ZivRiZukHCfMRNZRUTw@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra"><br>
<div class="gmail_quote">On 18 May 2016 at 08:18, Tony
Anderson <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:tony_anderson@usa.net" target="_blank">tony_anderson@usa.net</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">As I understand it,
what you are trying to do is make github the place where
Sugar activities are kept. </div>
</blockquote>
<div><br>
</div>
<div>The source code for activities has traditionally lived
on <a moz-do-not-send="true"
href="http://git.sugarlabs.org/projects">http://git.sugarlabs.org/projects</a>
but this is going to be shut down this year, because the
software is no longer maintained and each week it becomes
a bigger and bigger liability; meanwhile many activities
have already naturally found a home to live in on Github. <br>
</div>
<div> </div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">Currently, ASLO
provides for upload of an <br>
activity (new or new version) as an xo bundle from the
user's file system. </div>
</blockquote>
<div><br>
</div>
<div>This should not be a manual process in 2016 :)</div>
<div> </div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">What would be needed
is a way to release an xo bundle from the github
repository. </div>
</blockquote>
<div><br>
</div>
<div><a moz-do-not-send="true"
href="https://docs.travis-ci.com/user/deployment/">https://docs.travis-ci.com/user/deployment/</a></div>
<div> </div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">Experience in the
last GCI showed that the way Sugar activities are stored
in GitHub is not compatible with the requirements of an
xo bundle.<br>
For example, a Sugar activity must have a top-level
folder with the name xxxxx.activity.<br>
</div>
</blockquote>
<div><br>
</div>
<div>Please help me locate the discussion about this, the
assertion Github releases can't work with this requirement
seems totally incorrect to me. </div>
<div> </div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"> By custom, the
version is shown in the xo file name (e.g.
helloweb-3.xo) and should match the version number given
in <a moz-do-not-send="true"
href="http://activity.info" target="_blank">activity.info</a>.
However, this requires an act by the developer and is
not automatic.<br>
</div>
</blockquote>
<div><br>
</div>
<div>I am very confident I can automate this.</div>
<div> </div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"> So I think some
programming is required to release activities from
github to ASLO and to update the ASLO developer hub to
conform to the new requirements.<span class=""><font
color="#888888"><br>
</font></span></div>
</blockquote>
</div>
<br>
Sure! Its going to be great! :D<br clear="all">
<div><br>
</div>
-- <br>
<div class="gmail_signature">Cheers<br>
Dave</div>
</div>
</div>
</blockquote>
<br>
</body>
</html>