<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#ffffff" text="#000000"> Aleksey Lim wrote: <blockquote cite="mid:20100511192141.GB11991@antilopa-gnu" type="cite"> <pre wrap="">On Tue, May 11, 2010 at 05:37:52AM -0700, Thomas Gilliard wrote: </pre> <blockquote type="cite"> <pre wrap="">Is there anyway to tell what version (flavor) of sugar </pre> </blockquote> <pre wrap=""> It already works, ASLO can grab SP version from useragent string and provide appropriate activity versions for download buttons (full version list is still accessible on activity history page). </pre> </blockquote> I just finished updating ASLO for Mirabelle (0.88.0) compatability by activity This updated Spreadsheet reflects changes: <a class="moz-txt-link-freetext" href="http://people.sugarlabs.org/Tgillard/Activities-Index-Mirabell.ods">http://people.sugarlabs.org/Tgillard/Activities-Index-Mirabell.ods</a> "x 509 c" means it was changed in ASLO (Mirabelle should be entered in comments also) Tom Gilliard satellit <blockquote cite="mid:20100511192141.GB11991@antilopa-gnu" type="cite"> <pre wrap=""></pre> <blockquote type="cite"> <pre wrap="">(and hardware), </pre> </blockquote> <pre wrap=""> I guess we can grap x86/x86_64 info from useragent as well but not sure if it will help much since people just place binaries from their current distro to .xo thus there is not guaranty that it will work in other cases. It is fundamental issue w/ .xo, in my mind it is pretty useless to try to fix binaries issue and having only .xo deployment scheme at the same time. </pre> <blockquote type="cite"> <pre wrap="">a user is logging in with? If so, could this trigger a custom list of activities for his/her version to be listed? </pre> </blockquote> <pre wrap=""> It is not custom list but list of the same activities but some of them (incompatible with user's SP) have additional hints around/instead download button. </pre> <blockquote type="cite"> <pre wrap="">If not, maybe there should be a signature (cookie?) mechanism developed for sugar that ASLO could use to select the compatible activities to display. It works for browsers.... Tom Gilliard satellit Aleksey Lim wrote: </pre> <blockquote type="cite"> <pre wrap="">Hi all, The ASLO[1] is based on Sugar Platform[2] idea when if activity developer wants to be sure that activity will start, just declares Sugar Platform range e.g. 0.82-0.88. This scheme is simple - users need to know only SP range to judge will activity start or not. But it doesn't work in other cases like binaries, non-SP dependencies. These issues can't be solved within current ASLO (and current deployment scheme, "only .xo bundles"). But we can remove, inherited from AMO, practice when user should be logged in to download not public activities. So, it will look like: * featured activities(and collections) are blessed by ASLO editors will just work on declared sugars * activities that just work on declared sugars * experimental activities work in some cases e.g. dependencies exist, machine is x86 etc. In all cases, user should not be logged in to download all these activity types. Does it break someone's workflows ? [1] <a class="moz-txt-link-freetext" href="http://activities.sugarlabs.org/">http://activities.sugarlabs.org/</a> [2] <a class="moz-txt-link-freetext" href="http://wiki.sugarlabs.org/go/0.86/Platform_Components">http://wiki.sugarlabs.org/go/0.86/Platform_Components</a> </pre> </blockquote> </blockquote> <pre wrap=""> </pre> </blockquote> </body> </html>