<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi Bastien,<div><br><div><div>On 26 Nov 2012, at 07:32, Bastien <<a href="mailto:bzg@laptop.org">bzg@laptop.org</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">Alan Jhonn Aguiar Schwyn <<a href="mailto:alanjas@hotmail.com">alanjas@hotmail.com</a>> writes:<br><br><blockquote type="cite">supposedly.. when you navigate from Browse Activity, the searchs on<br>ASLO returns the latest for your sugar version..<br></blockquote><br>Good if it is really so. Can someone confirm?<br></blockquote><div><br></div><div>Yes, <a href="http://activities.sugarlabs.org">http://activities.sugarlabs.org</a> (ASLO) picks up the browser client string from Browse that varies from Sugar release to Sugar release, and shows the latest Activity versions for that release of Sugar. It does assume some steps are correctly taken when a developer uploads a new version, they have to set which Sugar versions their activity is compatible with, or an editor/reviewer needs to be on the ball with re-testing the activity later. ASLO is also not just for longterm Sugar developers to distribute activities, but also to allow other third party developers to share their work as well, so the quality/robustness of activity code/design can vary.</div><div><br></div><div>The area we most often get caught out in Sugar is that we don't have good architecture variation support – XO hardware was x86 based (XO-1 XO 1.5) and more recent models are now ARM based (XO-1.75, XO-4), if an activity developer decides to include binary code/libraries within an activity, it is down to them to make sure they include support for different architectures. This is why we try and encourage developers to develop Python activities, built for the agreed Sugar platform dependancies, as this avoids hardware architecture issues.</div><br><blockquote type="cite">Then maybe the compatibility info for each activity is often wrong.<br></blockquote><div><br></div><div>If you have found one, please do let me know the activity name, version, the version of Sugar you tested, and what hardware type you were trying to get it to run on and I'll take a look and update the compatibility flags.</div><div><br></div><div>If you are downloading from a browser/device other than the Browse running on the XO you finally want to install the activity on, you can use the 'Advanced' search button on the main ASLO:</div><div><br></div><img id="b36d18d8-7864-4e32-b1d0-39af8bcc6a56" height="347" width="701" apple-width="yes" apple-height="yes" src="cid:735BB19E-ECB1-4605-8665-22E873581C04"></div><div>Regards,</div><div>--Gary</div><div><br><blockquote type="cite">Does any other users have problems with compatibility?<br><br>-- <br> Bastien<br>_______________________________________________<br>Sugar-devel mailing list<br><a href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.org</a><br>http://lists.sugarlabs.org/listinfo/sugar-devel<br></blockquote></div><br></div></body></html>