Re: [Sugar-devel] OT: Thesis: OLPC Evaluation with Usability Engineering
This is wonderful. I have been tackling the problem of Usability from a different direction, Discoverability, as you can see on my Wiki page http://wiki.sugarlabs.org/go/The_Undiscoverable. I am in the middle of greatly extending that study. I am also, unfortunately, in the middle of moving from California to Indiana, about 2,000 miles/3,000 km. I intend to sort the topics I find according to their dependencies, and work out how to introduce each idea in some context of interest in some subject matter area. I will need my work tested and improved by teachers and students. 2009/11/23 Carlos mauro unima...@gmail.com: Hi friend I invite you to attend the exposition of my thesis OLPC Evaluation with Usability Engineering (Evaluación de la OLPC con Ingeniería de Usabilidad). Tomorrow 24 November at 1pm or 13:00 (GMT -5). Blog: http://unimauro.blogspot.com/2009/11/sustentacion-de-tesis-en-vivo.html Streaming: http://www.ustream.tv/channel/unimauro Abstract: This thesis is a study of the Usability of Software Sugar from the OLPC project. The problem taken the negative expert opinion about the lack of usability studies of the interaction of Sugar with children, the procedure is to evaluate the Sugar, with the method of usability testing conducted at the National School Julio C Tello located in the district of San Juan de Lurigancho in Lima Peru to 12 children between 5 to 7 years in a period of eight months with collecting data from three versions of Sugar and five activities or programs. The revised thesis was with a multidisciplinary work, with elementary school teachers, statistical professionals, developers and virtual communities. The conclusions and recommendations can by cover the void of the lack of usability studies with the their target populations and their object the project: Integrating children excluded from the world by generating wealth from knowledge. Resumen: Esta tesis es un estudio de la usabilidad del software Sugar del proyecto OLPC. El problema tomó la opinión de los expertos negativos por la falta de estudios de usabilidad de la interacción de azúcar con los niños, el procedimiento consiste en evaluar el azúcar, con el método de las pruebas de usabilidad llevado a cabo en la Escuela Nacional de Julio C Tello, ubicado en el distrito de San Juan de Lurigancho en Lima, Perú a 12 niños de entre 5 a 7 años en un período de ocho meses con la recopilación de datos a partir de tres versiones de azúcar y cinco actividades o programas. La tesis fue revisada con un trabajo multidisciplinario, con los maestros de escuela primaria, profesionales de la estadística, los desarrolladores y las comunidades virtuales. Las conclusiones y recomendaciones puede cubrir el vacío de la falta de estudios de usabilidad con las poblaciones meta y objeto del proyecto: La integración de los niños excluidos del mundo mediante la generación de riqueza de conocimiento. -- http://forpapers.blogspot.com/ http://unimauro.blogspot.com/ Creemos en el amor de los Seres Humanos Carlos Mauro Cárdenas Fernández Egresado en Ingeniería de Sistemas 4582877 980525716 ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- Edward Mokurai (默雷/धर्ममेघशब्दगर्ज/دھرممیگھشبدگر ج) Cherlin Silent Thunder is my name, and Children are my nation. The Cosmos is my dwelling place, the Truth my destination. http://www.earthtreasury.org/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] .swf files visualization and bundling
Good question - the SWF author would have to manually add support for sharing to the activity. I believe Gnash has DBus bindings, so that might be a possibility. If there is interested by at least one SWF author, I could add support in the SWF framework for collaboration. Unless, Sugar had some sort of automatic collaboration, using VNC or the like, which didn't require custom programming in each activity, -Wade On Mon, Nov 23, 2009 at 11:08 PM, roshan karki ros...@olenepal.org wrote: nice, work. I can see that the activity can be shared as well. But unlike other shared activities I can't see any relation between two shared Cabeza activity. Though shared both activity are playing independently. Is it intentional ? What kind of work needs to be done so that a swf based activity can also be shared like 'write' activity ? On Tue, Nov 24, 2009 at 4:10 AM, Rafael Enrique Ortiz Guerrero raf...@sugarlabs.org wrote: Hi Wadeb and Tim Thanks for the suggestions. I followed eatboom skeleton and i got a working initial activity. http://people.sugarlabs.org/rafael/Cabeza.activity.xo obvioulsy i borrowed eatbom.svg (this mail is only for reporting the advance :)) Great work Wade!. Rafael Ortiz On Sun, Nov 22, 2009 at 7:44 AM, Wade Brainerd wad...@gmail.com wrote: Hey Rafael, Check out http://git.sugarlabs.org/projects/eatboom/repos/wadebs-clone. That project provides a template for making .SWF files into proper Sugar activities. The bundle is also available on ASLO here: http://activities.sugarlabs.org/en-US/sugar/addon/4225 EatBoom is pretty simplistic, but I'm working on porting a more advanced example. Let me know if you need any assistance with this. -Wade On Sun, Nov 22, 2009 at 2:11 AM, Rafael Enrique Ortiz Guerrero raf...@sugarlabs.org wrote: Hi. I have some educational content .swf files that i wish to visualize inside Sugar and also making a content bundle for them. What is the present way of doing so (both making the bundle and visualizing .swf files) ?, we have not talked in a while about content bundles at least that i remember ;), so please direct me to past conversations or links about it. Cheers and thanks in advance for your help. Rafael Ortiz ___ 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 ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Activity Versioning - Dotted Scheme
Hi, as a follow up on an older thread: http://lists.sugarlabs.org/archive/sugar-devel/2009-October/019939.html - we want to get the versioning sorted in 0.88 for real. So far we came up with these three options: a) The release cycle dependent one: Activities name their activity after the Sugar version they are developed against. If it was released during the 0.88 cycle and developed against 0.88, then it would be 0.88.x. b) MAJOR.MINOR (x.y): The new Browse activity for 0.88 would be 115.0. Fixes would go into 115.1, 115.2... c) MAJOR.MINOR.PATCH (x.y.z) The new Browse activity for 0.88 would be 115.0.0. Fixes would go into 115.1.0, 115.2.1... What do people like best? Thanks, Simon ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Activity Versioning - Dotted Scheme
Hi Simon, On 24 Nov 2009, at 11:20, Simon Schampijer wrote: Hi, as a follow up on an older thread: http://lists.sugarlabs.org/archive/sugar-devel/2009-October/019939.html - we want to get the versioning sorted in 0.88 for real. So far we came up with these three options: a) The release cycle dependent one: Activities name their activity after the Sugar version they are developed against. If it was released during the 0.88 cycle and developed against 0.88, then it would be 0.88.x. Should we also try and resolve the Fructose issue as well here? Is Fructose just a random grab bag of demo activities, or is it the set of activities that are dependant on a single specific release of Glucose? Right now it contains a mix of both. I'd be against including Sugar version numbers in activity version number (unless perhaps they fail to work in other sugar releases). Activity development should be as far removed from the Glucose development cycle as is feasibly possible. If Fructose becomes the set of Glucose dependent activities (like Browse), they could be the only ones that require special versioning support b) MAJOR.MINOR (x.y): The new Browse activity for 0.88 would be 115.0. Fixes would go into 115.1, 115.2... Yes, seems simple enough, but only if/when you have to support an activity that has to fork compatibility between Sugar releases. c) MAJOR.MINOR.PATCH (x.y.z) The new Browse activity for 0.88 would be 115.0.0. Fixes would go into 115.1.0, 115.2.1... Not sure this adds much to the above major.minor option. What do people like best? We need to keep in mind not breaking existing deployments. If I have to start releasing Moon-11.0.xo, Moon-11.1.xo, Moon-11.2.xo, I'd be really annoyed/frustrated if this broke things for our current user base – so I guess that means I'll be sticking with integer version numbers for all my activity work in the foreseeable future, which ever way this goes. Regards, --Gary ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Activity Versioning - Dotted Scheme
Hi Simon, a) The release cycle dependent one: Activities name their activity after the Sugar version they are developed against. If it was released during the 0.88 cycle and developed against 0.88, then it would be 0.88.x. I don't think it is a good idea that activities are developed against a specific version of Sugar. For example, right now in Uruguay we have 400.000 laptops with version 0.82. Updating to a new version is a very complex logistic problem. (Besides, as far as I know there is no XO image ready with a newer version of Sugar yet.) Legacy support can be painful but I think it is necessary. My wish is that as a rule all activities should be compatible with previous versions of Sugar and the Sugar API should try to remain as stable as possible. Regards, Gabriel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Activity Versioning - Dotted Scheme
On Tue, Nov 24, 2009 at 12:20:15PM +0100, Simon Schampijer wrote: Hi, as a follow up on an older thread: http://lists.sugarlabs.org/archive/sugar-devel/2009-October/019939.html - we want to get the versioning sorted in 0.88 for real. So far we came up with these three options: a) The release cycle dependent one: Activities name their activity after the Sugar version they are developed against. If it was released during the 0.88 cycle and developed against 0.88, then it would be 0.88.x. Most of activities are compatible with several release cycles, so using SP in activity versions adds only confusing b) MAJOR.MINOR (x.y): The new Browse activity for 0.88 would be 115.0. Fixes would go into 115.1, 115.2... c) MAJOR.MINOR.PATCH (x.y.z) The new Browse activity for 0.88 would be 115.0.0. Fixes would go into 115.1.0, 115.2.1... What do people like best? Thanks, Simon ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- Aleksey ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Activity Versioning - Dotted Scheme
On 11/24/2009 01:42 PM, Gary C Martin wrote: Hi Simon, On 24 Nov 2009, at 11:20, Simon Schampijer wrote: Hi, as a follow up on an older thread: http://lists.sugarlabs.org/archive/sugar-devel/2009-October/019939.html - we want to get the versioning sorted in 0.88 for real. So far we came up with these three options: a) The release cycle dependent one: Activities name their activity after the Sugar version they are developed against. If it was released during the 0.88 cycle and developed against 0.88, then it would be 0.88.x. Ok, I do not like that option neither. And the people that have replied, do not neither. Should we also try and resolve the Fructose issue as well here? Is Fructose just a random grab bag of demo activities, or is it the set of activities that are dependant on a single specific release of Glucose? Right now it contains a mix of both. I'd be against including Sugar version numbers in activity version number (unless perhaps they fail to work in other sugar releases). Activity development should be as far removed from the Glucose development cycle as is feasibly possible. If Fructose becomes the set of Glucose dependent activities (like Browse), they could be the only ones that require special versioning support Yes, good point. We should revisit the current activities in Fructose and think if it makes sense to keep them in Fructose. As you said, one point is if an activity has dependencies on the platform itself like Browse (Hulahop). I propose to go through all Fructose activities and see which one makes sense to keep in Fructose. b) MAJOR.MINOR (x.y): The new Browse activity for 0.88 would be 115.0. Fixes would go into 115.1, 115.2... Yes, seems simple enough, but only if/when you have to support an activity that has to fork compatibility between Sugar releases. Personally, I like this option best, for activities that needs that functionality (fructose mainly). c) MAJOR.MINOR.PATCH (x.y.z) The new Browse activity for 0.88 would be 115.0.0. Fixes would go into 115.1.0, 115.2.1... Not sure this adds much to the above major.minor option. What do people like best? We need to keep in mind not breaking existing deployments. If I have to start releasing Moon-11.0.xo, Moon-11.1.xo, Moon-11.2.xo, I'd be really annoyed/frustrated if this broke things for our current user base – so I guess that means I'll be sticking with integer version numbers for all my activity work in the foreseeable future, which ever way this goes. If we stick with option b, you would still be able to just use an integer. Internally in 0.88 it is just represented as a float (e.g. 10 - 10.0), but it allows for the activity to use a dotted scheme if necessary. Thanks, Simon ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Activity Versioning - Dotted Scheme
On 11/24/2009 02:00 PM, Gabriel Eirea wrote: Hi Simon, a) The release cycle dependent one: Activities name their activity after the Sugar version they are developed against. If it was released during the 0.88 cycle and developed against 0.88, then it would be 0.88.x. I don't think it is a good idea that activities are developed against a specific version of Sugar. For example, right now in Uruguay we have 400.000 laptops with version 0.82. Updating to a new version is a very complex logistic problem. (Besides, as far as I know there is no XO image ready with a newer version of Sugar yet.) Legacy support can be painful but I think it is necessary. My wish is that as a rule all activities should be compatible with previous versions of Sugar and the Sugar API should try to remain as stable as possible. Regards, Gabriel Of course, it makes sense to minimize dependencies wherever possible, and the API should try to stay as much stable as possible. Though changes like the new toolbar design must happen at some points. And of course having a lot of glue code is costly, too. For the versioning, I like the mayor-minor scheme best. Is easily added and people can keep the integer versioning if they like. Regards, Simon ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Activity Versioning - Dotted Scheme
On 11/24/2009 02:12 PM, Aleksey Lim wrote: On Tue, Nov 24, 2009 at 12:20:15PM +0100, Simon Schampijer wrote: Hi, as a follow up on an older thread: http://lists.sugarlabs.org/archive/sugar-devel/2009-October/019939.html - we want to get the versioning sorted in 0.88 for real. So far we came up with these three options: a) The release cycle dependent one: Activities name their activity after the Sugar version they are developed against. If it was released during the 0.88 cycle and developed against 0.88, then it would be 0.88.x. Most of activities are compatible with several release cycles, so using SP in activity versions adds only confusing Yup, agreed. Thanks, Simon ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Roadmap to 0.88 --- Proposal
On 11/20/2009 06:43 PM, Walter Bender wrote: Great job!! -walter Any more thoughts? Pros and Cons? Things I have overseen? Wishes? Otherwise I will set the roadmap in stone and move on with the process. Thanks, Simon ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] While checking the latest Soas image (soas05.iso) I realized that po.it file do not correspond to latest versions
Gary, I understood you're maintaining the Moon activity. A few days ago I realize thre where a little version mismatch in .po files (for italian) and filed a bug in launchpad (maybe it was the wrong place...) https://bugs.edge.launchpad.net/soas/+bug/484280 would it be possible for you to give a check to it? Thanks a lot ciao carlo attached: While checking the latest Soas image (soas05.iso) I realized that po.it file do not correspond to latest versions: po.it mo found in sugar (soas) as POT-Creation-Date: 2008-10-01 11:54-0400\n PO-Revision-Date: 2008-10-01 15:48-0400\n and has some errors the it.po in Git (http://git.sugarlabs.org/projects/moon/repos/mainline/blobs/master/po/it.po) POT-Creation-Date: 2008-10-01 11:54-0400\n PO-Revision-Date: 2009-05-12 12:49-0400\n the moon.po in pootle (http://translate.sugarlabs.org/it/honey/moon.po) POT-Creation-Date: 2008-10-01 11:54-0400\n PO-Revision-Date: 2009-05-12 12:49-0400\n ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] While checking the latest Soas image (soas05.iso) I realized that po.it file do not correspond to latest versions
Hi Carlo, On 24 Nov 2009, at 13:28, Carlo Falciola wrote: Gary, I understood you're maintaining the Moon activity. A few days ago I realize thre where a little version mismatch in .po files (for italian) and filed a bug in launchpad (maybe it was the wrong place...) https://bugs.edge.launchpad.net/soas/+bug/484280 would it be possible for you to give a check to it? Yes, Sebastian kindly floated the ticket up to http://bugs.sugarlabs.org/ticket/1574 so I could catch it :-) My trac comment: Thanks for the ping, I was hoping to add the new 0.86 toolbar support for the next release, and at least a new option to export the Moon image to the Journal for use in other activities. If I don't get time to work on it in the next day or two, I'll just go ahead and release the existing version with the updated translations. Hoping to give it a poke later today, perhaps also make the text window scrollable as workaround for text font size vs. low screen resolution on some laptops. Regards, --Gary ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Activity Versioning - Dotted Scheme
On Tue, Nov 24, 2009 at 02:21:09PM +0100, Simon Schampijer wrote: On 11/24/2009 01:42 PM, Gary C Martin wrote: Hi Simon, On 24 Nov 2009, at 11:20, Simon Schampijer wrote: Hi, as a follow up on an older thread: http://lists.sugarlabs.org/archive/sugar-devel/2009-October/019939.html - we want to get the versioning sorted in 0.88 for real. So far we came up with these three options: a) The release cycle dependent one: Activities name their activity after the Sugar version they are developed against. If it was released during the 0.88 cycle and developed against 0.88, then it would be 0.88.x. Ok, I do not like that option neither. And the people that have replied, do not neither. Should we also try and resolve the Fructose issue as well here? Is Fructose just a random grab bag of demo activities, or is it the set of activities that are dependant on a single specific release of Glucose? Right now it contains a mix of both. I'd be against including Sugar version numbers in activity version number (unless perhaps they fail to work in other sugar releases). Activity development should be as far removed from the Glucose development cycle as is feasibly possible. If Fructose becomes the set of Glucose dependent activities (like Browse), they could be the only ones that require special versioning support Yes, good point. We should revisit the current activities in Fructose and think if it makes sense to keep them in Fructose. As you said, one point is if an activity has dependencies on the platform itself like Browse (Hulahop). In mind thats wrong way, some activities have non-sugar SP dependencies and can work fine with several SP releases, I guess its better to not add additioanl complexity and use only one source for compatibility info - on ASLO(moreove we have fructose activities on ASLO). BTW for 0.88 can exclude fructose from core packages at all and let deployers decide what should be included to deployments. I propose to go through all Fructose activities and see which one makes sense to keep in Fructose. -- Aleksey ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Fructose - What is it? What should it be?
Hi, this came up several times now. People where wondering what Fructose is. From the definition it is: The Sugar developers will need some example set of activities with which to demonstrate Sugar. This set is Fructose. The packages in Fructose should be selected to make the resulting environment as impressive as possible for a potential client or user. Packages should therefore be stable, polished, and exercise the widest possible range of features. Fructose may also serve as an example for people constructing their own Activity sets. [1] The current list of activities can be found at [2]. The fructose activities follow the Sucrose development cycle (0.84, 0.86...). This means they follow the freezes, provide source tarballs, need a present maintainer etc. The duties are described at [3]. The activity gets noted in release notes, possibly more attention by the localization teams as revenue. In the end their are downsides and upsides to be part of Fructose. There were some arguing, that only system dependent activities should be part of it (e.g. Browse with the dependency on hulahop). There were some discussions that we would loose the show case activities when an activity would not be part of Fructose anymore. This comes down to packaging, as for rpm packaging one needs to provide the source tarballs and need to follow certain rules. Some distributors may ship the .xo bunles at one point, otherwise probably won't, so it is a good habit to do the source releases. Anyhow, this is a bit of the background. Let's think how we can move forward on this topic. We should do it quickly, to be able to keep the work on 0.88 going. Regards, Simon [1] http://wiki.sugarlabs.org/go/Taxonomy#Fructose:_The_set_of_demonstration_activities [2] http://wiki.sugarlabs.org/go/Development_Team/Release/Modules [3] http://wiki.sugarlabs.org/go/Development_Team/Release#New_modules_proposal ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Fructose - What is it? What should it be?
On Tue, Nov 24, 2009 at 8:57 AM, Simon Schampijer si...@schampijer.de wrote: Hi, this came up several times now. People where wondering what Fructose is. From the definition it is: The Sugar developers will need some example set of activities with which to demonstrate Sugar. This set is Fructose. The packages in Fructose should be selected to make the resulting environment as impressive as possible for a potential client or user. Packages should therefore be stable, polished, and exercise the widest possible range of features. Fructose may also serve as an example for people constructing their own Activity sets. [1] The current list of activities can be found at [2]. The fructose activities follow the Sucrose development cycle (0.84, 0.86...). This means they follow the freezes, provide source tarballs, need a present maintainer etc. The duties are described at [3]. The activity gets noted in release notes, possibly more attention by the localization teams as revenue. In practice, I haven't found that Fructose activities get more attention from the Localization teams :( In a separate thread, perhaps we can discuss how to best organize activities for localization efforts. But as a Fructose activity maintainer, it is nice to have the motivation and companionship from the freeze and release dates to keep me on schedule. In the end their are downsides and upsides to be part of Fructose. There were some arguing, that only system dependent activities should be part of it (e.g. Browse with the dependency on hulahop). There were some discussions that we would loose the show case activities when an activity would not be part of Fructose anymore. This comes down to packaging, as for rpm packaging one needs to provide the source tarballs and need to follow certain rules. Some distributors may ship the .xo bunles at one point, otherwise probably won't, so it is a good habit to do the source releases. Be nice to get feedback from the distros as to what would be of most use to them. Perhaps something as simple as a list of activities that are known to be working with a particular release, which ASLO already provides. Anyhow, this is a bit of the background. Let's think how we can move forward on this topic. We should do it quickly, to be able to keep the work on 0.88 going. Could be that Fructose is no longer necessary. Regards, Simon [1] http://wiki.sugarlabs.org/go/Taxonomy#Fructose:_The_set_of_demonstration_activities [2] http://wiki.sugarlabs.org/go/Development_Team/Release/Modules [3] http://wiki.sugarlabs.org/go/Development_Team/Release#New_modules_proposal ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- Walter Bender Sugar Labs http://www.sugarlabs.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Fructose - What is it? What should it be?
On Tue, Nov 24, 2009 at 02:57:16PM +0100, Simon Schampijer wrote: Hi, this came up several times now. People where wondering what Fructose is. From the definition it is: The Sugar developers will need some example set of activities with which to demonstrate Sugar. This set is Fructose. The packages in Fructose should be selected to make the resulting environment as impressive as possible for a potential client or user. Packages should therefore be stable, polished, and exercise the widest possible range of features. Fructose may also serve as an example for people constructing their own Activity sets. [1] The current list of activities can be found at [2]. The fructose activities follow the Sucrose development cycle (0.84, 0.86...). This means they follow the freezes, provide source tarballs, need a present maintainer etc. The duties are described at [3]. The activity gets noted in release notes, possibly more attention by the localization teams as revenue. In the end their are downsides and upsides to be part of Fructose. There were some arguing, that only system dependent activities should be part of it (e.g. Browse with the dependency on hulahop). There were some discussions that we would loose the show case activities when an activity would not be part of Fructose anymore. This comes down to packaging, as for rpm packaging one needs to provide the source tarballs and need to follow certain rules. Some distributors may ship the .xo bunles at one point, otherwise probably won't, so it is a good habit to do the source releases. Anyhow, this is a bit of the background. Let's think how we can move forward on this topic. We should do it quickly, to be able to keep the work on 0.88 going. In my mind, the best thing we can do is making clear definition: 1) we have core with strong release cycle * glucose(and its dependencies) * sugar platform(additional dependencies) (core) 2) various sugar activities (the rest of development community) 3) sugar users (the rest of community) Relations between 1) and 2) totally depends on sugar release cycles. Activity developers decide what release cycles they can/should/will support. For activities like Browse it will several activities versions per SP release. Most activities will support several SP release. Relations between 2) and 3) is task for various deployment methods. Since fructose makes sense mostly for users, its content should totally depends on deployers not core. So I can't see the 4rd place for fructose, only as a part of 2). -- Aleksey ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] [Feature] language and keyboard options for intro dialog
I've begun working on language and keyboard options for the Sugar intro dialog. More details can be found at: http://wiki.sugarlabs.org/go/Features/Feature_intro_language_keyboard_options Comments/feedback sought. -walter -- Walter Bender Sugar Labs http://www.sugarlabs.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Reminder please how to flash XO-1 NAND with soas05xo.iso
Sean DALY wrote: I did manage to generate the .img and .crc files with the live-iso-t-xo.sh script, but after successful nand-copy of soas05xo.img the XO-1 does not boot, freezes at avatar with no dots :-( Sorry for the late reply. I was a bit busy with writing docs and fixing bugs over the last days. I'm not sure why you're trying to use the livecd-iso-to-xo script, as we're providing .img and .crc files for the latest snapshots: http://download.sugarlabs.org/soas/snapshots/2/ To all: Any help with debugging issues, especially the critical ones, would be greatly appreciated: https://bugs.launchpad.net/soas/+bugs Oh, and just to make sure: SoaS is supposed to go GOLD this weekend! --Sebastian Sean On Tue, Nov 17, 2009 at 12:04 PM, Sean DALYsdaly...@gmail.com wrote: I found this post by Tomeu with instructions: http://lists.sugarlabs.org/archive/sugar-devel/2009-March/012521.html I burned the ISO file to a CD and found the livecd-iso-to-xo script on it. I will generate the .img and .crc files, if that works I will update the wiki with the step-by-step procedure. thanks Sean On Tue, Nov 17, 2009 at 10:39 AM, Peter Robinsonpbrobin...@gmail.com wrote: On Tue, Nov 17, 2009 at 9:33 AM, Sean DALYsdaly...@gmail.com wrote: Tomeu helped me with this at SugarCamp with the soas04xo image, but I didn't see what files were on his stick. I'd like to update an XO-1 to the soas05xo image, could someone please confirm this is the procedure? I'm confused that what should be an .img file seems to be an .iso file (found here: http://download.sugarlabs.org/soas/snapshots/2/ ). I'm willing to update http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Installation/OLPC Option 2 section More recent builds are better if this is indeed the procedure. thanks, Sean ** * Verify security is disabled (developer key valid). Boot into OpenFirmware ok prompt (hit Escape key - upper left with X - right after chime), type disable-security; response should be No wp tag. Obtain key otherwise as described here (usually takes 24 hours): http://wiki.laptop.org/go/Activation_and_developer_keys * Verify firmware version is Q2E41 ( http://wiki.laptop.org/go/OLPC_Firmware_q2e41 ). In Sugar, inspect Settings/About my Computer, alternatively boot banner above OpenFirmware ok prompt, or in Terminal Activity: cat /ofw/openprom/model * Remind XO-1 owner that all data will be completely erased. To back up existing nand image: save-nand u:\my-nand.img or save-nand sd:\my-nand.img * Shut down XO-1, insert USB stick or SD Card with soas05xo.iso file. Make sure battery is not discharged, better to have power plugged in * Boot to OFW ok prompt, type copy-nand u:\soas05xo.iso for USB stick or copy-nand sd:\soas05xo.iso for SD Card * After nand is written, reboot. That looks OK to me. You should have an img and a crc file so it looks like the image for the XO wasn't generated correctly. Cheers, Peter ___ 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] [Feature] language and keyboard options for intro dialog
On Tue, Nov 24, 2009 at 8:05 PM, Walter Bender walter.ben...@gmail.com wrote: I've begun working on language and keyboard options for the Sugar intro dialog. More details can be found at: http://wiki.sugarlabs.org/go/Features/Feature_intro_language_keyboard_options Comments/feedback sought. While the keyboard settings can be changed on the fly through either setxkbmap or the libxklavier python bindings - the language settings cannot be changed without a process restart. One possible solution is to conditionally run the introwindow as a separate process, and call the main sugar-session from that. (the display manager does the language choosing/setting for GNOME/KDE) Thanks, Sayamindu -- Sayamindu Dasgupta [http://sayamindu.randomink.org/ramblings] ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Reminder please how to flash XO-1 NAND with soas05xo.iso
On 24.11.2009, at 16:02, Sebastian Dziallas wrote: Sean DALY wrote: I did manage to generate the .img and .crc files with the live-iso-t-xo.sh script, but after successful nand-copy of soas05xo.img the XO-1 does not boot, freezes at avatar with no dots :-( Sorry for the late reply. I was a bit busy with writing docs and fixing bugs over the last days. I'm not sure why you're trying to use the livecd-iso-to-xo script, as we're providing .img and .crc files for the latest snapshots: http://download.sugarlabs.org/soas/snapshots/2/ there is no .img / .crc for soas05xo, only a .iso and a .tree. To all: Any help with debugging issues, especially the critical ones, would be greatly appreciated: https://bugs.launchpad.net/soas/+bugs Oh, and just to make sure: SoaS is supposed to go GOLD this weekend! --Sebastian Sounds great! If the XO is officially supported by this SoaS release, it would be good to update Etoys. See https://dev.laptop.org/ticket/9709 - Bert - ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Reminder please how to flash XO-1 NAND with soas05xo.iso
that's the thing, there are no .img and .crc files for soas05xo that I can find? thanks Sean On Tue, Nov 24, 2009 at 4:02 PM, Sebastian Dziallas sebast...@when.com wrote: Sean DALY wrote: I did manage to generate the .img and .crc files with the live-iso-t-xo.sh script, but after successful nand-copy of soas05xo.img the XO-1 does not boot, freezes at avatar with no dots :-( Sorry for the late reply. I was a bit busy with writing docs and fixing bugs over the last days. I'm not sure why you're trying to use the livecd-iso-to-xo script, as we're providing .img and .crc files for the latest snapshots: http://download.sugarlabs.org/soas/snapshots/2/ To all: Any help with debugging issues, especially the critical ones, would be greatly appreciated: https://bugs.launchpad.net/soas/+bugs Oh, and just to make sure: SoaS is supposed to go GOLD this weekend! --Sebastian Sean On Tue, Nov 17, 2009 at 12:04 PM, Sean DALYsdaly...@gmail.com wrote: I found this post by Tomeu with instructions: http://lists.sugarlabs.org/archive/sugar-devel/2009-March/012521.html I burned the ISO file to a CD and found the livecd-iso-to-xo script on it. I will generate the .img and .crc files, if that works I will update the wiki with the step-by-step procedure. thanks Sean On Tue, Nov 17, 2009 at 10:39 AM, Peter Robinsonpbrobin...@gmail.com wrote: On Tue, Nov 17, 2009 at 9:33 AM, Sean DALYsdaly...@gmail.com wrote: Tomeu helped me with this at SugarCamp with the soas04xo image, but I didn't see what files were on his stick. I'd like to update an XO-1 to the soas05xo image, could someone please confirm this is the procedure? I'm confused that what should be an .img file seems to be an .iso file (found here: http://download.sugarlabs.org/soas/snapshots/2/ ). I'm willing to update http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Installation/OLPC Option 2 section More recent builds are better if this is indeed the procedure. thanks, Sean ** * Verify security is disabled (developer key valid). Boot into OpenFirmware ok prompt (hit Escape key - upper left with X - right after chime), type disable-security; response should be No wp tag. Obtain key otherwise as described here (usually takes 24 hours): http://wiki.laptop.org/go/Activation_and_developer_keys * Verify firmware version is Q2E41 ( http://wiki.laptop.org/go/OLPC_Firmware_q2e41 ). In Sugar, inspect Settings/About my Computer, alternatively boot banner above OpenFirmware ok prompt, or in Terminal Activity: cat /ofw/openprom/model * Remind XO-1 owner that all data will be completely erased. To back up existing nand image: save-nand u:\my-nand.img or save-nand sd:\my-nand.img * Shut down XO-1, insert USB stick or SD Card with soas05xo.iso file. Make sure battery is not discharged, better to have power plugged in * Boot to OFW ok prompt, type copy-nand u:\soas05xo.iso for USB stick or copy-nand sd:\soas05xo.iso for SD Card * After nand is written, reboot. That looks OK to me. You should have an img and a crc file so it looks like the image for the XO wasn't generated correctly. Cheers, Peter ___ 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] [Feature] language and keyboard options for intro dialog
Hi Walter, On 24 Nov 2009, at 14:35, Walter Bender wrote: I've begun working on language and keyboard options for the Sugar intro dialog. More details can be found at: http://wiki.sugarlabs.org/go/Features/Feature_intro_language_keyboard_options Comments/feedback sought. I was initially worried that the language and keyboard buttons would be a distraction from the clean, simple first impression of the Sugar start-up; but I like your subtle placement for the two icon only buttons. Could we make them use the same dark grey vs. light grey colors with an outer stroke, as per the ( Next) button? Happy to clean up the icons (I see the keyboard graphic is using a nasty black fill instead of transparent). I'm assuming you plan to reuse the existing control panel language and keyboard modules so as to keep new code for the actual dialogues to a minimum? Regards, --Gary ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] [ANNOUNCE] development team meeting thursday at 14.00 UTC
Hi, the development team is going to meet next thursday to discuss this particular moment in the 0.88 release cycle, please add topics here: http://wiki.sugarlabs.org/go/Development_Team/Meetings#Upcoming_Meetings See you then, Tomeu -- «Sugar Labs is anyone who participates in improving and using Sugar. What Sugar Labs does is determined by the participants.» - David Farning ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Fructose - What is it? What should it be?
On 11/24/2009 03:18 PM, Aleksey Lim wrote: On Tue, Nov 24, 2009 at 02:57:16PM +0100, Simon Schampijer wrote: Hi, this came up several times now. People where wondering what Fructose is. From the definition it is: The Sugar developers will need some example set of activities with which to demonstrate Sugar. This set is Fructose. The packages in Fructose should be selected to make the resulting environment as impressive as possible for a potential client or user. Packages should therefore be stable, polished, and exercise the widest possible range of features. Fructose may also serve as an example for people constructing their own Activity sets. [1] The current list of activities can be found at [2]. The fructose activities follow the Sucrose development cycle (0.84, 0.86...). This means they follow the freezes, provide source tarballs, need a present maintainer etc. The duties are described at [3]. The activity gets noted in release notes, possibly more attention by the localization teams as revenue. In the end their are downsides and upsides to be part of Fructose. There were some arguing, that only system dependent activities should be part of it (e.g. Browse with the dependency on hulahop). There were some discussions that we would loose the show case activities when an activity would not be part of Fructose anymore. This comes down to packaging, as for rpm packaging one needs to provide the source tarballs and need to follow certain rules. Some distributors may ship the .xo bunles at one point, otherwise probably won't, so it is a good habit to do the source releases. Anyhow, this is a bit of the background. Let's think how we can move forward on this topic. We should do it quickly, to be able to keep the work on 0.88 going. In my mind, the best thing we can do is making clear definition: 1) we have core with strong release cycle * glucose(and its dependencies) * sugar platform(additional dependencies) (core) 2) various sugar activities (the rest of development community) 3) sugar users (the rest of community) Relations between 1) and 2) totally depends on sugar release cycles. Activity developers decide what release cycles they can/should/will support. For activities like Browse it will several activities versions per SP release. Most activities will support several SP release. Relations between 2) and 3) is task for various deployment methods. Since fructose makes sense mostly for users, its content should totally depends on deployers not core. So I can't see the 4rd place for fructose, only as a part of 2). So far, I conclude, that Fructose as we have it today is outdated. The tarball issue could be solved with adding for example a field to ASLO, to be able to upload a tarball too, when doing a release. As I think where to upload a tarball was one big issue back in the days. The packaging (rpm, xo, deb) and how you install/upgrade, where you install (system vs user space) is then up to the deployer. As the tarball is available, that should work out nicely. Activities that rest coupled to the Sucrose release would be Browse and Etoys as they have strong platform dependencies. Of course, activity authors are encouraged to follow the Sucrose release cycle, the point is: they don't have to. As Walter stated there is some benefit. Keeps you focused etc. More thoughts? Simon ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Roadmap to 0.88 --- Proposal
2009/11/25 Simon Schampijer si...@schampijer.de On 11/20/2009 06:43 PM, Walter Bender wrote: Great job!! -walter Any more thoughts? Pros and Cons? Things I have overseen? Wishes? Simon, et al This may be a SoaS issue, but I will press on nevertheless. I would like Fedora man pages included into Sugar. I see this as being a critical part of low floor, no ceiling. Decent documentation about the features the OS and how to run its advanced features is part of that. While I would like it to be on all Sugar installations, I think we have more flexibility with HDD space as deployers with SoaS. Any thoughts? @timClicks ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Roadmap to 0.88 --- Proposal
Be nice to go a step further and (optionally) put the entire Fedora source on the helper CD as well (if it will fit). -walter On Tue, Nov 24, 2009 at 2:13 PM, Tim McNamara paperl...@timmcnamara.co.nz wrote: 2009/11/25 Simon Schampijer si...@schampijer.de On 11/20/2009 06:43 PM, Walter Bender wrote: Great job!! -walter Any more thoughts? Pros and Cons? Things I have overseen? Wishes? Simon, et al This may be a SoaS issue, but I will press on nevertheless. I would like Fedora man pages included into Sugar. I see this as being a critical part of low floor, no ceiling. Decent documentation about the features the OS and how to run its advanced features is part of that. While I would like it to be on all Sugar installations, I think we have more flexibility with HDD space as deployers with SoaS. Any thoughts? @timClicks ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- Walter Bender Sugar Labs http://www.sugarlabs.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] 0depend feature request
Aleksey wrote:
To have some implementation mockups for next 0install debates,
I've coded how(I'm thinking) 0install integration could be implemented
in sugar[1]. To check existed code, pull sugar and sugar-toolkit cloned
repos[2] and follow simple test case[3].
[1] http://wiki.sugarlabs.org/go/Zero_Depend
[2] http://wiki.sugarlabs.org/go/Zero_Depend#Scope
[3] http://wiki.sugarlabs.org/go/Zero_Depend#How_To_Test
Aleksey,
I tried out your patches in a Debian Sid chroot with
zeroinstall-injector-0.42.1-1
installed and got the following exception in shell.log when running your test
case:
Traceback (most recent call last):
File /usr/lib/python2.5/site-packages/jarabe/desktop/favoritesview.py,
line 519, in __button_release_event_cb
self._activate()
File /usr/lib/python2.5/site-packages/jarabe/desktop/favoritesview.py,
line 531, in _activate
self._resume(self._journal_entries[0])
File /usr/lib/python2.5/site-packages/jarabe/desktop/favoritesview.py,
line 524, in _resume
shell.resume(journal_entry, self._activity_info.get_bundle_id())
File /usr/lib/python2.5/site-packages/jarabe/util/shell.py, line 222, in
resume
launch(bundle, handle, get_icon_color(metadata))
File /usr/lib/python2.5/site-packages/jarabe/util/shell.py, line 238, in
launch
launcher.add_launcher(bundle, activity_handle, color)
File /usr/lib/python2.5/site-packages/jarabe/view/launcher.py, line 185,
in add_launcher
zdepend.fetch(zfeed, progress, create_activity, cancel)
File /usr/lib/python2.5/site-packages/jarabe/util/zdepend.py, line 49,
in fetch
downloaded = policy.download_uncached_implementations()
File /usr/lib/python2.5/site-packages/zeroinstall/injector/policy.py,
line 393, in download_uncached_implementations
assert self.solver.ready, Solver is not ready!\n%s %
self.solver.selections
AssertionError: Solver is not ready!
{Interface http://rox.sourceforge.net/2005/interfaces/ROX-Lib: None,
Interface /home/sugar/Activities/Terminal.activity/activity/0depend.xml: v1
(/home/sugar/Activities/Terminal.activity/activity)}
The problem seems to be that you haven't told the policy object to solve the
feeds. You can do that with
policy.solve_with_downloads()
and maybe in other ways too.
Anyway, after teaching zdepend.py to solve the policy, I ran into into further
trouble because my zeroinstall trust-db doesn't contain the ROX keys.
To deal with this, I think you need to construct the policy object with a
Handler object
http://0install.net/python-api/html/zeroinstall.injector.handler.Handler-class.html
and override its confirm_keys method.
@Thomas, Rene: is this about right?
Michael
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] SoaS v2 approaching RC state
Hi all, with the next SoaS release coming up really soon (final image is supposed to be composed this weekend, release date is Dec 8), there's a new snapshot ready for you. It includes a lot of fixes and smaller adjustments. It's currently only available as a general .iso build, others will presumably follow later. You can get it from here: http://download.sugarlabs.org/soas/snapshots/2/soas06.iso Let us know how it goes and help us debugging and fixing the remaining bugs here: https://bugs.launchpad.net/soas/+bugs A last note, if anybody knows what's wrong with Record, Cairo and F12, please drop us a line! Thanks. --Sebastian ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Diapositivas de la Sustentación de Tesis
http://unimauro.blogspot.com/2009/11/diapositivas-de-la-sustentacion-de.html 1. RESUMEN 2. - La tesis es un estudio sobre la Usabilidad de la Plataforma de Software Sugar del proyecto Una Laptop Por Niño (OLPC) abordando la carencia de estudios de usabilidad de su software Sugar en niños, utilizando el método de pruebas de usabilidad, realizado en el Colegio Nacional Nro. 1173 Julio C Tello ubicado en el distrito de San Juan de Lurigancho en Lima Perú a 12 niños entre 5 a 7 años en un periodo de ocho meses recolectando datos de tres versiones de SUGAR y cinco actividades o programas. Dentro de unas horas la tesis y el video de expo juas -- http://forpapers.blogspot.com/ http://unimauro.blogspot.com/ Creemos en el amor de los Seres Humanos Carlos Mauro Cárdenas Fernández Egresado en Ingeniería de Sistemas 4582877 980525716 ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] OT: Thesis: OLPC Evaluation with Usability Engineering
My slice http://unimauro.blogspot.com/2009/11/diapositivas-de-la-sustentacion-de.html 2009/11/24 Edward Cherlin echer...@gmail.com This is wonderful. I have been tackling the problem of Usability from a different direction, Discoverability, as you can see on my Wiki page http://wiki.sugarlabs.org/go/The_Undiscoverable. I am in the middle of greatly extending that study. I am also, unfortunately, in the middle of moving from California to Indiana, about 2,000 miles/3,000 km. I intend to sort the topics I find according to their dependencies, and work out how to introduce each idea in some context of interest in some subject matter area. I will need my work tested and improved by teachers and students. 2009/11/23 Carlos mauro unima...@gmail.com: Hi friend I invite you to attend the exposition of my thesis OLPC Evaluation with Usability Engineering (Evaluación de la OLPC con Ingeniería de Usabilidad). Tomorrow 24 November at 1pm or 13:00 (GMT -5). Blog: http://unimauro.blogspot.com/2009/11/sustentacion-de-tesis-en-vivo.html Streaming: http://www.ustream.tv/channel/unimauro Abstract: This thesis is a study of the Usability of Software Sugar from the OLPC project. The problem taken the negative expert opinion about the lack of usability studies of the interaction of Sugar with children, the procedure is to evaluate the Sugar, with the method of usability testing conducted at the National School Julio C Tello located in the district of San Juan de Lurigancho in Lima Peru to 12 children between 5 to 7 years in a period of eight months with collecting data from three versions of Sugar and five activities or programs. The revised thesis was with a multidisciplinary work, with elementary school teachers, statistical professionals, developers and virtual communities. The conclusions and recommendations can by cover the void of the lack of usability studies with the their target populations and their object the project: Integrating children excluded from the world by generating wealth from knowledge. Resumen: Esta tesis es un estudio de la usabilidad del software Sugar del proyecto OLPC. El problema tomó la opinión de los expertos negativos por la falta de estudios de usabilidad de la interacción de azúcar con los niños, el procedimiento consiste en evaluar el azúcar, con el método de las pruebas de usabilidad llevado a cabo en la Escuela Nacional de Julio C Tello, ubicado en el distrito de San Juan de Lurigancho en Lima, Perú a 12 niños de entre 5 a 7 años en un período de ocho meses con la recopilación de datos a partir de tres versiones de azúcar y cinco actividades o programas. La tesis fue revisada con un trabajo multidisciplinario, con los maestros de escuela primaria, profesionales de la estadística, los desarrolladores y las comunidades virtuales. Las conclusiones y recomendaciones puede cubrir el vacío de la falta de estudios de usabilidad con las poblaciones meta y objeto del proyecto: La integración de los niños excluidos del mundo mediante la generación de riqueza de conocimiento. -- http://forpapers.blogspot.com/ http://unimauro.blogspot.com/ Creemos en el amor de los Seres Humanos Carlos Mauro Cárdenas Fernández Egresado en Ingeniería de Sistemas 4582877 980525716 ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- Edward Mokurai (默雷/धर्ममेघशब्दगर्ज/دھرممیگھشبدگر ج) Cherlin Silent Thunder is my name, and Children are my nation. The Cosmos is my dwelling place, the Truth my destination. http://www.earthtreasury.org/ -- http://forpapers.blogspot.com/ http://unimauro.blogspot.com/ Creemos en el amor de los Seres Humanos Carlos Mauro Cárdenas Fernández Egresado en Ingeniería de Sistemas 4582877 980525716 ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [Zero-install-devel] 0depend feature request
On Tue, Nov 24, 2009 at 10:20:27PM +, Thomas Leonard wrote:
2009/11/24 Michael Stone mich...@laptop.org:
Aleksey wrote:
To have some implementation mockups for next 0install debates,
I've coded how(I'm thinking) 0install integration could be implemented
in sugar[1]. To check existed code, pull sugar and sugar-toolkit cloned
repos[2] and follow simple test case[3].
[1] http://wiki.sugarlabs.org/go/Zero_Depend
[2] http://wiki.sugarlabs.org/go/Zero_Depend#Scope
[3] http://wiki.sugarlabs.org/go/Zero_Depend#How_To_Test
Aleksey,
I tried out your patches in a Debian Sid chroot with
zeroinstall-injector-0.42.1-1
installed and got the following exception in shell.log when running your
test
case:
AssertionError: Solver is not ready!
{Interface http://rox.sourceforge.net/2005/interfaces/ROX-Lib: None,
Interface /home/sugar/Activities/Terminal.activity/activity/0depend.xml:
v1 (/home/sugar/Activities/Terminal.activity/activity)}
The problem seems to be that you haven't told the policy object to solve the
feeds. You can do that with
policy.solve_with_downloads()
and maybe in other ways too.
That's right:
- need_download() will do a solve and return True if you're missing
feeds or implementations
- solve_with_downloads() will solve and download any extra feeds it
needs repeatedly until it has all the information it needs
- solve_and_download_impls() will additionally download the selected
implementations afterwards
I've just tried simple example[1] with simple feed[2] in system w/o
any 0install remains and it fails for the first time[3] but runs ok for 2nd.
I missed something in example code or its a unpredictable behaviour
(since [3] cailms for missed ROX-Lib dependensy but
solve_and_download_impls() should make all downloads)?
[1] http://pastebin.be/22131
[2] http://pastebin.be/22132
[3] http://pastebin.be/22133
--
Aleksey
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [SoaS] SoaS v2 approaching RC state
On Tue, Nov 24, 2009 at 9:13 PM, Sebastian Dziallas sebast...@when.com wrote: Hi all, with the next SoaS release coming up really soon (final image is supposed to be composed this weekend, release date is Dec 8), there's a new snapshot ready for you. It includes a lot of fixes and smaller adjustments. It's currently only available as a general .iso build, others will presumably follow later. You can get it from here: http://download.sugarlabs.org/soas/snapshots/2/soas06.iso Let us know how it goes and help us debugging and fixing the remaining bugs here: https://bugs.launchpad.net/soas/+bugs A last note, if anybody knows what's wrong with Record, Cairo and F12, Who is the maintainer of Record? It would be a pity to ship BB without that working as its one off the Activities that kids seem to love. What's the issue with Cairo? Peter ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [SoaS] SoaS v2 approaching RC state
On Tue, Nov 24, 2009 at 11:51:55PM +, Peter Robinson wrote: On Tue, Nov 24, 2009 at 9:13 PM, Sebastian Dziallas sebast...@when.com wrote: Hi all, with the next SoaS release coming up really soon (final image is supposed to be composed this weekend, release date is Dec 8), there's a new snapshot ready for you. It includes a lot of fixes and smaller adjustments. It's currently only available as a general .iso build, others will presumably follow later. You can get it from here: http://download.sugarlabs.org/soas/snapshots/2/soas06.iso Let us know how it goes and help us debugging and fixing the remaining bugs here: https://bugs.launchpad.net/soas/+bugs A last note, if anybody knows what's wrong with Record, Cairo and F12, Who is the maintainer of Record? It would be a pity to ship BB without that working as its one off the Activities that kids seem to love. What's the issue with Cairo? last time /me patched Record.. and looks like it doesn't work in 0.86 for a long time, so its the right moment to fix 0.86 issues then -- Aleksey ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] 0depend feature request
On Tue, Nov 24, 2009 at 03:01:07PM -0500, Michael Stone wrote:
Aleksey wrote:
To have some implementation mockups for next 0install debates,
I've coded how(I'm thinking) 0install integration could be implemented
in sugar[1]. To check existed code, pull sugar and sugar-toolkit cloned
repos[2] and follow simple test case[3].
[1] http://wiki.sugarlabs.org/go/Zero_Depend
[2] http://wiki.sugarlabs.org/go/Zero_Depend#Scope
[3] http://wiki.sugarlabs.org/go/Zero_Depend#How_To_Test
Aleksey,
I tried out your patches in a Debian Sid chroot with
zeroinstall-injector-0.42.1-1
installed and got the following exception in shell.log when running your test
case:
Traceback (most recent call last):
File /usr/lib/python2.5/site-packages/jarabe/desktop/favoritesview.py,
line 519, in __button_release_event_cb
self._activate()
File /usr/lib/python2.5/site-packages/jarabe/desktop/favoritesview.py,
line 531, in _activate
self._resume(self._journal_entries[0])
File /usr/lib/python2.5/site-packages/jarabe/desktop/favoritesview.py,
line 524, in _resume
shell.resume(journal_entry, self._activity_info.get_bundle_id())
File /usr/lib/python2.5/site-packages/jarabe/util/shell.py, line 222,
in resume
launch(bundle, handle, get_icon_color(metadata))
File /usr/lib/python2.5/site-packages/jarabe/util/shell.py, line 238,
in launch
launcher.add_launcher(bundle, activity_handle, color)
File /usr/lib/python2.5/site-packages/jarabe/view/launcher.py, line
185, in add_launcher
zdepend.fetch(zfeed, progress, create_activity, cancel)
File /usr/lib/python2.5/site-packages/jarabe/util/zdepend.py, line 49,
in fetch
downloaded = policy.download_uncached_implementations()
File /usr/lib/python2.5/site-packages/zeroinstall/injector/policy.py,
line 393, in download_uncached_implementations
assert self.solver.ready, Solver is not ready!\n%s %
self.solver.selections
AssertionError: Solver is not ready!
{Interface http://rox.sourceforge.net/2005/interfaces/ROX-Lib: None,
Interface /home/sugar/Activities/Terminal.activity/activity/0depend.xml: v1
(/home/sugar/Activities/Terminal.activity/activity)}
The problem seems to be that you haven't told the policy object to solve the
feeds. You can do that with
policy.solve_with_downloads()
and maybe in other ways too.
yeah, in my testing environment I have remains from previous 0install
sessions
Anyway, after teaching zdepend.py to solve the policy, I ran into into further
trouble because my zeroinstall trust-db doesn't contain the ROX keys.
To deal with this, I think you need to construct the policy object with a
Handler object
http://0install.net/python-api/html/zeroinstall.injector.handler.Handler-class.html
and override its confirm_keys method.
I've pushed new commits with fixed these issues and added cancel button
@Thomas, Rene: is this about right?
Michael
--
Aleksey
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] 0depend feature request
Aleksey wrote: yeah, in my testing environment I have remains from previous 0install sessions I've pushed new commits with fixed these issues and added cancel button Aleksey, Your test case passes on my system with these additional commits. Nice work, Michael ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] adding 3G support to Sugar (was Re: Sugarizing an application)
On 23/11/2009, at 7:18 AM, Peter Robinson wrote: On Sat, Nov 21, 2009 at 3:44 AM, Jonas Smedegaard d...@jones.dk wrote: On Sat, Nov 21, 2009 at 08:14:38AM +, Peter Robinson wrote: On Sat, Nov 21, 2009 at 12:10 AM, James Cameron qu...@laptop.org wrote: I think I've seen Ubuntu handling this UI design issue by building a data set of providers. It might be possible to piggy back on some of that work. Well NetworkManager in Fedora which we already use has all that support already so we don't need to piggy back off anything as the tools we use already support all of what we require. All that needs to be done is to extend the sugar interface to add the 3G support that's already in NM. If you want this for _Sugar_ then please do not just rely on a specific distro, but document in an INSTALL file what it is from that particular distro that you rely on - so that other distros can mimic that. If you are not targeting Sugar but just a specific distribution of it like, say, SoaS, then obviously you need not document anything. But it would be sad if you do not target Sugar globally. NetworkManager is distribution agnostic so its not targetted at specific distributions as NM support multiple distros undernearth. That's the advantage of it and one of the reasons its ued! I've just sat through a presentation on oFono by Denis Kenzior (Intel) at OSDC, and ConnMan is their chosen network management component for raising the interface for 3G modems. It was quite fascinating. I'm looking forward to it. We might want to consider it for OLPC due to the smaller footprint as compared to NetworkManager. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
