<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p><br>
</p>
<br>
<div class="moz-cite-prefix">On 15/09/17 03:49, laurent bernabe
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAH8mndKp7i5rF5cMLPh4Oq5=jA-_J_tZDmFTsMmEOk20tHtkXA@mail.gmail.com">
<div>Indeed, I first cloned Sugarizer repository from Github,
copied activity template from inside it into the sugarizer
activities directory.</div>
<div>Then, as Sebastien Silva suggested me in order to correct a
problem with my activity icon (appearing all black), I replaced
the sugar-web folder with the one from Sugarizer top folder. <b>But
the icon problem stayed the same : so I plan to put back the
activity template version of sugar-web folder again.</b></div>
<div><b><br>
</b></div>
</blockquote>
Ah, mi recommendation was wrong then. I thought you had used the
Sugar-Web template as is documented here
(<a class="moz-txt-link-freetext" href="https://developer.sugarlabs.org/web-activity.md.html">https://developer.sugarlabs.org/web-activity.md.html</a>).<br>
<br>
Lionel, we should really unify instructions and make sure Sugarizer
Apps run as Sugar Activities, even with the WebKit2 backend (last
time I checked, it only worked with Webkit1 which is deprecated
everywhere and only active by default on XO laptops.)<br>
<br>
I have made a bug in Sugarizer for this in the past, <a
moz-do-not-send="true"
href="https://github.com/llaske/sugarizer/issues/116">https://github.com/llaske/sugarizer/issues/116</a>
and if there's anything you'd like to add to <i>sugar-web</i>, OLPC
(via James Cameron) has unilaterally declared feature freeze for
0.112, but it shouldn't be a problem since <i>sugar-web</i> is not
dinamically called but actually embedded in <i>every</i> activity.<br>
<br>
Laurent, if it is the same bug I reported, then your activity will
work fine in Sugarizer and if Lionel will test on an XO, it will
work fine in Sugar too, but it won't work in Sugar outside XO
because of the aforementioned issue with environment detection for
sugarizer's version of sugar-web which only detects Webkit1 as Sugar
otherwise just assumes Sugarizer style journale etc.<br>
<br>
Hope this helps,<br>
<br>
Regards,<br>
Sebastian<br>
</body>
</html>