Re: [IAEP] Turtle Blocks question
On Sat, Oct 6, 2012 at 1:27 AM, Alan Jhonn Aguiar Schwyn alan...@hotmail.com wrote: I think that you cannot check what sensor is connected.. Butia have hotplug and show instantly that a sensor is connect. Lego not have that, and the only check possible: get a value, if no gives errors, maybe there are a sensor of that type connected.. The usual approach would be to add a device input to the blocks... device 1, device 2, device 3 That can works, but I don't like it taking into consideration that you have put the port where each sensor/motor is connected. I think in a special block that sets the brick that you want to use. For example: - you have 2 bricks connected -if you want to: read color sensor from brick 1 in port 1 -turn motor in port b of brcik 2 with power 100 The code will be: select brick (1) read sensor (color, port 1) select brcik (2) turn motor (port b, 100) See that all the blocks no have changes, only uses the select brick to set in the system, which brick get the next functions. The important of this change: when you have only 1 brick, the code no have changes! Opinions? Regards! Alan From: gerald.ard...@gmail.com Date: Fri, 5 Oct 2012 14:45:48 -0400 To: walter.ben...@gmail.com CC: alan...@hotmail.com; iaep@lists.sugarlabs.org; support-g...@laptop.org Subject: Re: [IAEP] Turtle Blocks question Walter, Agreed. I am happy to continuing working with you on this. Gerald On Fri, Oct 5, 2012 at 2:36 PM, Walter Bender walter.ben...@gmail.com wrote: On Fri, Oct 5, 2012 at 2:30 PM, Dr. Gerald Ardito gerald.ard...@gmail.com wrote: Walter, if we are crossing devices? Egon Spengler: Don't cross the streams. The usual approach would be to add a device input to the blocks... device 1, device 2, device 3... But also, I should do a better job of autodetecting which sensors are available. The whole thing should be more dynamic. -walter -- Walter Bender Sugar Labs http://www.sugarlabs.org ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep Attached is a BETA version of a new WeDo plugin that supports multiple devices. It follows a schema similar to what Alan proposes above. I only have one device, so it is not tested for multiple devices, however, it seems to work for one device and includes a new feature which tests for devices before each start, rather than just at launch, so devices and be plugged in and unplugged without having to restart Turtle Art. Feedback greatly appreciated. regards. -walter -- Walter Bender Sugar Labs http://www.sugarlabs.org wedo.tar.gz Description: GNU Zip compressed data ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] Turtle Blocks question
Kids from Bukokholo School Acted Out a One Laptop Per Child Promo for Kenyan Kids. Watch the beginning and the end of this clip : It is charming, funny and a great ad for OLPC In Kenya! This was done by the Small Solutions partner Hands of Charity. http://youtu.be/-ip8UP4RtTs On Sat, Oct 6, 2012 at 6:46 PM, Walter Bender walter.ben...@gmail.com wrote: On Sat, Oct 6, 2012 at 1:27 AM, Alan Jhonn Aguiar Schwyn alan...@hotmail.com wrote: I think that you cannot check what sensor is connected.. Butia have hotplug and show instantly that a sensor is connect. Lego not have that, and the only check possible: get a value, if no gives errors, maybe there are a sensor of that type connected.. The usual approach would be to add a device input to the blocks... device 1, device 2, device 3 That can works, but I don't like it taking into consideration that you have put the port where each sensor/motor is connected. I think in a special block that sets the brick that you want to use. For example: - you have 2 bricks connected -if you want to: read color sensor from brick 1 in port 1 -turn motor in port b of brcik 2 with power 100 The code will be: select brick (1) read sensor (color, port 1) select brcik (2) turn motor (port b, 100) See that all the blocks no have changes, only uses the select brick to set in the system, which brick get the next functions. The important of this change: when you have only 1 brick, the code no have changes! Opinions? Regards! Alan From: gerald.ard...@gmail.com Date: Fri, 5 Oct 2012 14:45:48 -0400 To: walter.ben...@gmail.com CC: alan...@hotmail.com; iaep@lists.sugarlabs.org; support-g...@laptop.org Subject: Re: [IAEP] Turtle Blocks question Walter, Agreed. I am happy to continuing working with you on this. Gerald On Fri, Oct 5, 2012 at 2:36 PM, Walter Bender walter.ben...@gmail.com wrote: On Fri, Oct 5, 2012 at 2:30 PM, Dr. Gerald Ardito gerald.ard...@gmail.com wrote: Walter, if we are crossing devices? Egon Spengler: Don't cross the streams. The usual approach would be to add a device input to the blocks... device 1, device 2, device 3... But also, I should do a better job of autodetecting which sensors are available. The whole thing should be more dynamic. -walter -- Walter Bender Sugar Labs http://www.sugarlabs.org ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep Attached is a BETA version of a new WeDo plugin that supports multiple devices. It follows a schema similar to what Alan proposes above. I only have one device, so it is not tested for multiple devices, however, it seems to work for one device and includes a new feature which tests for devices before each start, rather than just at launch, so devices and be plugged in and unplugged without having to restart Turtle Art. Feedback greatly appreciated. regards. -walter -- Walter Bender Sugar Labs http://www.sugarlabs.org ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep -- Sandra Thaxter san...@smallsolutionsbigideas.org san...@thaxter.net (617) 320-1098 www.smallsolutonsbigideas.org. ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] Turtle Blocks question
On Sat, Oct 6, 2012 at 2:08 PM, Dr. Gerald Ardito gerald.ard...@gmail.com wrote: Walter, I have been testing it out this afternoon. It works really well. I only have one We Do here, so I can't test out if it sees different devices. There is one quirky thing. When the script is running a motor, the Stop icon disappears. Then, if you use ctrl-s to stop the script, the blocks disappear. You could just keep a motor=0 block around... I suppose I could auto-stop the motor when the program stops executing, but I think that might limit the utility somewhat. (The Stop Button is for the Turtle Art program, not the WeDo motor.) And a question, how do you reverse the direction of the motor? Should reverse with a negative number. enjoy. -walter Thanks. Gerald On Sat, Oct 6, 2012 at 11:46 AM, Walter Bender walter.ben...@gmail.com wrote: On Sat, Oct 6, 2012 at 1:27 AM, Alan Jhonn Aguiar Schwyn alan...@hotmail.com wrote: I think that you cannot check what sensor is connected.. Butia have hotplug and show instantly that a sensor is connect. Lego not have that, and the only check possible: get a value, if no gives errors, maybe there are a sensor of that type connected.. The usual approach would be to add a device input to the blocks... device 1, device 2, device 3 That can works, but I don't like it taking into consideration that you have put the port where each sensor/motor is connected. I think in a special block that sets the brick that you want to use. For example: - you have 2 bricks connected -if you want to: read color sensor from brick 1 in port 1 -turn motor in port b of brcik 2 with power 100 The code will be: select brick (1) read sensor (color, port 1) select brcik (2) turn motor (port b, 100) See that all the blocks no have changes, only uses the select brick to set in the system, which brick get the next functions. The important of this change: when you have only 1 brick, the code no have changes! Opinions? Regards! Alan From: gerald.ard...@gmail.com Date: Fri, 5 Oct 2012 14:45:48 -0400 To: walter.ben...@gmail.com CC: alan...@hotmail.com; iaep@lists.sugarlabs.org; support-g...@laptop.org Subject: Re: [IAEP] Turtle Blocks question Walter, Agreed. I am happy to continuing working with you on this. Gerald On Fri, Oct 5, 2012 at 2:36 PM, Walter Bender walter.ben...@gmail.com wrote: On Fri, Oct 5, 2012 at 2:30 PM, Dr. Gerald Ardito gerald.ard...@gmail.com wrote: Walter, if we are crossing devices? Egon Spengler: Don't cross the streams. The usual approach would be to add a device input to the blocks... device 1, device 2, device 3... But also, I should do a better job of autodetecting which sensors are available. The whole thing should be more dynamic. -walter -- Walter Bender Sugar Labs http://www.sugarlabs.org ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep Attached is a BETA version of a new WeDo plugin that supports multiple devices. It follows a schema similar to what Alan proposes above. I only have one device, so it is not tested for multiple devices, however, it seems to work for one device and includes a new feature which tests for devices before each start, rather than just at launch, so devices and be plugged in and unplugged without having to restart Turtle Art. Feedback greatly appreciated. regards. -walter -- Walter Bender Sugar Labs http://www.sugarlabs.org -- Walter Bender Sugar Labs http://www.sugarlabs.org ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
[IAEP] Sugar Digest 2012-10-06
== Sugar Digest == 1. Assessment is a topic that comes up again and again in discussions of Sugar. While there are several efforts under way to gather statistics about activity usage (See [1, 2] and [3], for example), most of those efforts are in service of everyone except the learner. In the spirit of making learning visible, I modified an existing activity, Analyze Journal [4], written by Agustin Zubiaga Sanchez, in order give the Sugar user some feedback about their activity usage. Agustin had written the original activity to show free space in the Journal. I added two more views: one that displays a list of activities sorted by frequency of use; and one that shows statistics about block usage in Turtle Art activities. (The latter is based on a rubric developed jointly with Pacita Pena from Paraguayu Educa and Claudia Urrea from OLPC.) I am hoping that Analyze Journal and Portfolio (a previous effort to make learning visible) inspire the Sugar community to put more effort not just into gathering data for school administrators, but also in making reflection by the learners themselves part of the Sugar experience. One further note regarding Analyze Journal. I'd blogged recently about how youths who had grown up with Sugar were beginning to submit patches. In this case, the roles have reversed completely: I submitted the patch to Agustin. 2. In the keeping with spirit of the above discussion, a new datastore metadata tag [5] has landed in Sugar 0.98. The launch-times tag is updated whenever an activity is launched. This will enable the learner to answer questions such as how often have I used this activity?; do I use it in class, at home, or both? Again, the goal is not to subsume the functionality potentially provided by [2], but to make the data available within Sugar itself more rich. 3. There has been a discussion on the IAEP list [6] about various strategies for using Turtle Blocks in support of robotics. The LEGO WeDo was discussed as one of several options currently available. It got me thinking that it may be time to finally add support for multiple WeDo devices. It is still beta, but please test the latest wedo_plugin [7]. In addition to supporting multiple devices, it also is a bit more robust in regard to plugging in and removing devices while the program is running. (In the first version of the code, the device had to be plugged in when Turtle Blocks launched. Now devices can be added and removed while Turtle Blocks is running.) === In the community === 4. There are plans to hold the next OLPC SF summit in San Francisco the weekend of October 19-21. We are holding a Sugar Camp ''following'' the summit (Oct 22-24). Please register at [8]. === Sugar Labs === Visit our planet [9] for more updates about Sugar and Sugar deployments. -walter -- Walter Bender Sugar Labs http://www.sugarlabs.org [1] http://git.sugarlabs.org/desktop/stats [2] http://wiki.sugarlabs.org/go/Platform_Team/Usage_Statistics [3] http://git.sugarlabs.org/ds-analysis-scripts [4] http://wiki.sugarlabs.org/go/Activities/Analyze_Journal [5] http://git.sugarlabs.org/sugar-toolkit-gtk3/sugar-toolkit-gtk3/commit/2a15fbc0f2269b1d61e5fa8ea723cb4848a8ee74 [6] http://lists.sugarlabs.org/archive/iaep/2012-October/015642.html [7] http://wiki.sugarlabs.org/images/0/00/Wedo_plugin_2.tar.gz [8] http://wiki.sugarlabs.org/go/Sugarcamp_SF_2012 [9] http://planet.sugarlabs.org ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] Turtle Blocks question
Hello all. Thanks for all the support with this project. At Tony's suggestion, I downgraded the XO-1 to build 883 (11.3.0), and the the We Do works fine in TurtleBots. Walter shared his new We Do plug in, which worked fine with Turtle Art 160. Thanks. Gerald On Sat, Oct 6, 2012 at 2:18 PM, Walter Bender walter.ben...@gmail.comwrote: On Sat, Oct 6, 2012 at 2:08 PM, Dr. Gerald Ardito gerald.ard...@gmail.com wrote: Walter, I have been testing it out this afternoon. It works really well. I only have one We Do here, so I can't test out if it sees different devices. There is one quirky thing. When the script is running a motor, the Stop icon disappears. Then, if you use ctrl-s to stop the script, the blocks disappear. You could just keep a motor=0 block around... I suppose I could auto-stop the motor when the program stops executing, but I think that might limit the utility somewhat. (The Stop Button is for the Turtle Art program, not the WeDo motor.) And a question, how do you reverse the direction of the motor? Should reverse with a negative number. enjoy. -walter Thanks. Gerald On Sat, Oct 6, 2012 at 11:46 AM, Walter Bender walter.ben...@gmail.com wrote: On Sat, Oct 6, 2012 at 1:27 AM, Alan Jhonn Aguiar Schwyn alan...@hotmail.com wrote: I think that you cannot check what sensor is connected.. Butia have hotplug and show instantly that a sensor is connect. Lego not have that, and the only check possible: get a value, if no gives errors, maybe there are a sensor of that type connected.. The usual approach would be to add a device input to the blocks... device 1, device 2, device 3 That can works, but I don't like it taking into consideration that you have put the port where each sensor/motor is connected. I think in a special block that sets the brick that you want to use. For example: - you have 2 bricks connected -if you want to: read color sensor from brick 1 in port 1 -turn motor in port b of brcik 2 with power 100 The code will be: select brick (1) read sensor (color, port 1) select brcik (2) turn motor (port b, 100) See that all the blocks no have changes, only uses the select brick to set in the system, which brick get the next functions. The important of this change: when you have only 1 brick, the code no have changes! Opinions? Regards! Alan From: gerald.ard...@gmail.com Date: Fri, 5 Oct 2012 14:45:48 -0400 To: walter.ben...@gmail.com CC: alan...@hotmail.com; iaep@lists.sugarlabs.org; support-g...@laptop.org Subject: Re: [IAEP] Turtle Blocks question Walter, Agreed. I am happy to continuing working with you on this. Gerald On Fri, Oct 5, 2012 at 2:36 PM, Walter Bender walter.ben...@gmail.com wrote: On Fri, Oct 5, 2012 at 2:30 PM, Dr. Gerald Ardito gerald.ard...@gmail.com wrote: Walter, if we are crossing devices? Egon Spengler: Don't cross the streams. The usual approach would be to add a device input to the blocks... device 1, device 2, device 3... But also, I should do a better job of autodetecting which sensors are available. The whole thing should be more dynamic. -walter -- Walter Bender Sugar Labs http://www.sugarlabs.org ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep Attached is a BETA version of a new WeDo plugin that supports multiple devices. It follows a schema similar to what Alan proposes above. I only have one device, so it is not tested for multiple devices, however, it seems to work for one device and includes a new feature which tests for devices before each start, rather than just at launch, so devices and be plugged in and unplugged without having to restart Turtle Art. Feedback greatly appreciated. regards. -walter -- Walter Bender Sugar Labs http://www.sugarlabs.org -- Walter Bender Sugar Labs http://www.sugarlabs.org ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] Turtle Blocks question
Hello all. Thanks for all the support with this project. At Tony's suggestion, I downgraded the XO-1 to build 883 (11.3.0), and the the We Do works fine in TurtleBots. Walter shared his new We Do plug in, which worked fine with Turtle Art 160. Thanks. Gerald Hi Maybe though, the Sugar version is not the problem. I am very happy you have it working though. Just tested Turtlebots Wedo OK on 13.1.0 XO-1.75 Tony ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] Turtle Blocks question
Date: Sat, 6 Oct 2012 14:18:10 -0400 Subject: Re: [IAEP] Turtle Blocks question From: walter.ben...@gmail.com To: gerald.ard...@gmail.com CC: alan...@hotmail.com; iaep@lists.sugarlabs.org; support-g...@laptop.org; davidson.i...@gmail.com; fors...@ozonline.com.au On Sat, Oct 6, 2012 at 2:08 PM, Dr. Gerald Ardito gerald.ard...@gmail.com wrote: Walter, I have been testing it out this afternoon. It works really well. I only have one We Do here, so I can't test out if it sees different devices. There is one quirky thing. When the script is running a motor, the Stop icon disappears. Then, if you use ctrl-s to stop the script, the blocks disappear. You could just keep a motor=0 block around... I suppose I could auto-stop the motor when the program stops executing, but I think that might limit the utility somewhat. (The Stop Button is for the Turtle Art program, not the WeDo motor.) In the Nxt Plugin (and the Butia) I add the stop motors in the stop of the Turtle.When the robot is crazy and you want to stop it, the best way (beyond turn off) isclick on the stop button off the Turtle. The WeDo plugin have the stop motors function: when you click on the stopof the turtle, the WeDo motor is stopped?? And a question, how do you reverse the direction of the motor? Should reverse with a negative number. enjoy. -walter Thanks. Gerald On Sat, Oct 6, 2012 at 11:46 AM, Walter Bender walter.ben...@gmail.com wrote: On Sat, Oct 6, 2012 at 1:27 AM, Alan Jhonn Aguiar Schwyn alan...@hotmail.com wrote: I think that you cannot check what sensor is connected.. Butia have hotplug and show instantly that a sensor is connect. Lego not have that, and the only check possible: get a value, if no gives errors, maybe there are a sensor of that type connected.. The usual approach would be to add a device input to the blocks... device 1, device 2, device 3 That can works, but I don't like it taking into consideration that you have put the port where each sensor/motor is connected. I think in a special block that sets the brick that you want to use. For example: - you have 2 bricks connected -if you want to: read color sensor from brick 1 in port 1 -turn motor in port b of brcik 2 with power 100 The code will be: select brick (1) read sensor (color, port 1) select brcik (2) turn motor (port b, 100) See that all the blocks no have changes, only uses the select brick to set in the system, which brick get the next functions. The important of this change: when you have only 1 brick, the code no have changes! Opinions? Regards! Alan From: gerald.ard...@gmail.com Date: Fri, 5 Oct 2012 14:45:48 -0400 To: walter.ben...@gmail.com CC: alan...@hotmail.com; iaep@lists.sugarlabs.org; support-g...@laptop.org Subject: Re: [IAEP] Turtle Blocks question Walter, Agreed. I am happy to continuing working with you on this. Gerald On Fri, Oct 5, 2012 at 2:36 PM, Walter Bender walter.ben...@gmail.com wrote: On Fri, Oct 5, 2012 at 2:30 PM, Dr. Gerald Ardito gerald.ard...@gmail.com wrote: Walter, if we are crossing devices? Egon Spengler: Don't cross the streams. The usual approach would be to add a device input to the blocks... device 1, device 2, device 3... But also, I should do a better job of autodetecting which sensors are available. The whole thing should be more dynamic. -walter -- Walter Bender Sugar Labs http://www.sugarlabs.org ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep Attached is a BETA version of a new WeDo plugin that supports multiple devices. It follows a schema similar to what Alan proposes above. I only have one device, so it is not tested for multiple devices, however, it seems to work for one device and includes a new feature which tests for devices before each start, rather than just at launch, so devices and be plugged in and unplugged without having to restart Turtle Art. Feedback greatly appreciated. regards. -walter -- Walter Bender Sugar Labs http://www.sugarlabs.org -- Walter Bender Sugar Labs http://www.sugarlabs.org ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
