Re: [Sugar-devel] FR: Feature for a.sl.o: global filter by Sugar version
On Mon, Nov 26, 2012 at 08:32:21AM +0100, Bastien wrote: Alan Jhonn Aguiar Schwyn alan...@hotmail.com writes: supposedly.. when you navigate from Browse Activity, the searchs on ASLO returns the latest for your sugar version.. Good if it is really so. Can someone confirm? Yes, I have seen this behaviour. It can be frustrating, because the concept of latest version is not common across all users. Two computers with different versions of Sugar can yield different answers. I don't think there's anything that tells the user that they are being given a variant of the truth. Then maybe the compatibility info for each activity is often wrong. Does any other users have problems with compatibility? I don't use activities.sugarlabs.org often enough to notice such problems. It loads too slowly for me. -- James Cameron http://quozl.linux.org.au/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] FR: Feature for a.sl.o: global filter by Sugar version
James Cameron qu...@laptop.org writes: I don't use activities.sugarlabs.org often enough to notice such problems. It loads too slowly for me. Well, a.sl.o is key in distributing Sugar and Sugar activities. Any progress on it will have a great impact on a large scale. I know Bernie has been working on it, maybe he needs some help? What about upgrading to a more recent version of the software? Would be nice to know how one can help here. Thanks! -- Bastien ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] FR: Feature for a.sl.o: global filter by Sugar version
Chris Leonard cjlhomeaddr...@gmail.com writes: I have found instances of bad compatibility info in ASLO. I asked the maintainer about it and they fixed it. This is also what I do. But we're not all hardcore geeks. Some teachers are being frustrated by this -- let's also think about normal users. Thanks, -- Bastien ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] FR: Feature for a.sl.o: global filter by Sugar version
On Mon, Nov 26, 2012 at 1:09 PM, Chris Leonard cjlhomeaddr...@gmail.comwrote: On Mon, Nov 26, 2012 at 2:32 AM, Bastien b...@laptop.org wrote: Then maybe the compatibility info for each activity is often wrong. Does any other users have problems with compatibility? I have found instances of bad compatibility info in ASLO. I asked the maintainer about it and they fixed it. I have also observed such behaviours, mainly in Software Update; there are times when the update_url is NULL for certain activities; while other activities are upgraded ok. cjl ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel Regards, Ajay Garg Dextrose Developer Activity Central: http://activitycentral.com ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] FR: Feature for a.sl.o: global filter by Sugar version
On Mon, Nov 26, 2012 at 4:53 AM, Bastien b...@laptop.org wrote: Chris Leonard cjlhomeaddr...@gmail.com writes: I have found instances of bad compatibility info in ASLO. I asked the maintainer about it and they fixed it. This is also what I do. But we're not all hardcore geeks. Some teachers are being frustrated by this -- let's also think about normal users. I was not suggesting that such errors were acceptable or to be considered normal, only confirming that they do occur and can be fixed. This sounds like an ideal set of QA task(s) to be written up for GCI. 1) Starting form a given version of Sugar, and given a provided list of activities as defined by ASLO links and version numbers), confirm compatibility as listed on ASLO and provide data for developing a compatibily matrix (version of Sugar versus release number of activity). 2) Highlight instances where the data provided in ASLO is wrong. 2) Define similar tasks for each of several (recent) releases of Sugar. Please write it up on the wiki and we will try to get some GCI contributors to work on it. http://wiki.sugarlabs.org/go/GoogleCodeIn2012/ http://wiki.sugarlabs.org/go/GoogleCodeIn2012/GCI2012_Brainstorming cjl ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] FR: Feature for a.sl.o: global filter by Sugar version
Chris Leonard cjlhomeaddr...@gmail.com writes: Please write it up on the wiki and we will try to get some GCI contributors to work on it. http://wiki.sugarlabs.org/go/GoogleCodeIn2012/GCI2012_Brainstorming Done on the page above as (9). -- Bastien ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] FR: Feature for a.sl.o: global filter by Sugar version
HiBastien,On 26 Nov 2012, at 07:32, Bastien b...@laptop.org wrote:Alan Jhonn Aguiar Schwyn alan...@hotmail.com writes:supposedly.. when you navigate from Browse Activity, the searchs onASLO returns the latest for your sugar version..Good if it is really so. Can someone confirm?Yes, http://activities.sugarlabs.org (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.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 differentarchitectures. 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.Then maybe the compatibility info for each activity is often wrong.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.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:Regards,--GaryDoes any other users have problems with compatibility?-- Bastien___Sugar-devel mailing listSugar-devel@lists.sugarlabs.orghttp://lists.sugarlabs.org/listinfo/sugar-devel___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] FR: Feature for a.sl.o: global filter by Sugar version
On Mon, Nov 26, 2012 at 9:44 AM, Bastien b...@laptop.org wrote: Chris Leonard cjlhomeaddr...@gmail.com writes: Please write it up on the wiki and we will try to get some GCI contributors to work on it. http://wiki.sugarlabs.org/go/GoogleCodeIn2012/GCI2012_Brainstorming Done on the page above as (9). -- Bastien We'll work on getting it posted as a task(s), but we will need mentors before posting. Any vols? cjl ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] FR: Feature for a.sl.o: global filter by Sugar version
Chris Leonard cjlhomeaddr...@gmail.com writes: We'll work on getting it posted as a task(s), but we will need mentors before posting. Any vols? I can't volunteer on this. PS: I mentored 3 Google Summer of Code students for free this summer, and while I enjoyed doing this a lot, I think the model is not well suited for small Orgs with no money. It is good for well-established Orgs like the Wikimedia Foundation and others, but not for small ones. -- Bastien ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] FR: Feature for a.sl.o: global filter by Sugar version
Hi Gary, thanks for your answer. Gary Martin garycmar...@googlemail.com writes: Yes, http://activities.sugarlabs.org (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. Yes. 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. Yes. This is a bit of a problem. For example, I encouraged the Kiwix developer to make Kiwix available for Sugar, which they did, and I now have to ask them to port it to the ARM architecture (as they had too few feedback on Kiwix, I doubt porting Kiwix on ARM is a high priority task.) 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. Using VirtualBox and Sugar on a Stick (Fedora-17-i686-Live-SoaS.iso), the Sugar File Manager does not launch. 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: [cid] Very useful, thanks! -- Bastien ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] FR: Feature for a.sl.o: global filter by Sugar version
Hi Bastien, On 26 Nov 2012, at 14:58, Bastien b...@laptop.org wrote: Hi Gary, thanks for your answer. Gary Martin garycmar...@googlemail.com writes: Yes, http://activities.sugarlabs.org (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. Yes. 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. Yes. This is a bit of a problem. For example, I encouraged the Kiwix developer to make Kiwix available for Sugar, which they did, and I now have to ask them to port it to the ARM architecture (as they had too few feedback on Kiwix, I doubt porting Kiwix on ARM is a high priority task.) 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. Using VirtualBox and Sugar on a Stick (Fedora-17-i686-Live-SoaS.iso), the Sugar File Manager does not launch. Aha, OK. So my first guess would be that the SOAS image is probably missing some dependency shipped in an OLPC build (or in a deployments customised build) that this activity depends on. I've not used this particular activity before (I try to use Sugar with the tools we ship by default so have a better idea what our users have access to), but if you wanted to help debug a little further (it might be something _really_ simple), start the Log activity and look in the log file called: org.ceibaljam.SugarFileManager Send me or copy/paste the log file if you wanted me to have a quick look. Regards, --Gary 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: [cid] Very useful, thanks! -- Bastien ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] FR: Feature for a.sl.o: global filter by Sugar version
Hi Gary, Gary Martin garycmar...@googlemail.com writes: Aha, OK. So my first guess would be that the SOAS image is probably missing some dependency shipped in an OLPC build (or in a deployments customised build) that this activity depends on. I've not used this particular activity before (I try to use Sugar with the tools we ship by default so have a better idea what our users have access to), but if you wanted to help debug a little further (it might be something _really_ simple), start the Log activity and look in the log file called: org.ceibaljam.SugarFileManager Send me or copy/paste the log file if you wanted me to have a quick look. My bad. I clicked on Ignore version check before downloading this Activity. I will report problems on other Activities when I encounter them. Thanks, -- Bastien ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] FR: Feature for a.sl.o: global filter by Sugar version
I often on an activity that is not compatible with the Sugar version running on the XO I'm using. This gives the impression that the whole system is unstable. Looking for compatibility info in each version is tedious, and looking on the wiki is even more haphazardous. It would be nice to have a field in the global search form which lets you filter the results by Sugar version. Is it something that is available somehow? Maybe create temporary collections of activities based on whether they are compatible with Sugar versions? Thanks, -- Bastien ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] FR: Feature for a.sl.o: global filter by Sugar version
supposedly.. when you navigate from Browse Activity, the searchs on ASLOreturns the latest for your sugar version.. Regards! Alan From: b...@laptop.org To: sugar-devel@lists.sugarlabs.org Date: Mon, 26 Nov 2012 08:05:00 +0100 Subject: [Sugar-devel] FR: Feature for a.sl.o: global filter by Sugar version I often on an activity that is not compatible with the Sugar version running on the XO I'm using. This gives the impression that the whole system is unstable. Looking for compatibility info in each version is tedious, and looking on the wiki is even more haphazardous. It would be nice to have a field in the global search form which lets you filter the results by Sugar version. Is it something that is available somehow? Maybe create temporary collections of activities based on whether they are compatible with Sugar versions? Thanks, -- Bastien ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] FR: Feature for a.sl.o: global filter by Sugar version
Alan Jhonn Aguiar Schwyn alan...@hotmail.com writes: supposedly.. when you navigate from Browse Activity, the searchs on ASLO returns the latest for your sugar version.. Good if it is really so. Can someone confirm? Then maybe the compatibility info for each activity is often wrong. Does any other users have problems with compatibility? -- Bastien ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] FR: Feature for a.sl.o: global filter by Sugar version
On Mon, Nov 26, 2012 at 2:32 AM, Bastien b...@laptop.org wrote: Then maybe the compatibility info for each activity is often wrong. Does any other users have problems with compatibility? I have found instances of bad compatibility info in ASLO. I asked the maintainer about it and they fixed it. cjl ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
