<html> <head> <meta content="text/html; charset=utf-8" http-equiv="Content-Type"> </head> <body bgcolor="#FFFFFF" text="#000000"> Speaking only for myself. In origin, Sugar was the software provided with the OLPC laptop. It has become obvious that in the long run, Sugar must be able to serve more than the XO platform. I suspect Sugar will need to be viewed as a software project which supports multiple platforms including the XO. Because Sugar is based on Python, the Android form may need to be Sugarizer. Sebastian Silva has just given us a way to leverage the library of Sugar activities outside of Sugar, another way to extend the benefits of the Sugar community. Tony <div class="moz-cite-prefix">On 04/20/2016 09:30 AM, Justin Overton wrote: </div> <blockquote cite="mid:CAMNWm9+exg+2oZB=ZwGKtDP_8Ao9nK0Do1JTRo-tGBe=tw1kmg@mail.gmail.com" type="cite"> I have some questio s about the vision of sugar after reading another thread about the conference. I like the idea of sugar as a platform, but I'm curious about how tied it is to OLPC hardware. Is there a larger vision to create a platform that can be used in a more widespread fashion? I discovered this project after getting tired of all the freemium apps that trick my young kids into buying things. I love the idea of sugar, but it's been around a while and the it still seems a bit esoteric. I'd be more than happy to start cranking out code if I can see the bigger picture. In the meantime I'm trying to find a way to target sugar and Android without duplicating core logic. <fieldset class="mimeAttachmentHeader"></fieldset> <pre wrap="">_______________________________________________ Sugar-devel mailing list <a class="moz-txt-link-abbreviated" href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.org</a> <a class="moz-txt-link-freetext" href="http://lists.sugarlabs.org/listinfo/sugar-devel">http://lists.sugarlabs.org/listinfo/sugar-devel</a> </pre> </blockquote> </body> </html>