[Sugar-devel] [ASLO] Release Measure-31
Activity Homepage: http://activities.sugarlabs.org/addon/4197 Sugar Platform: 0.82 - 0.88 Download Now: http://activities.sugarlabs.org/downloads/file/27000/measure-31.xo Release notes: Some minor bug fixes and enhancements: * avoid race condition that leads to image capture corruption (#2119) (thanks to quozl) * eliminate exception handler for tooltip text (#2121) * increment capture file id in Journal (#2120) * greatly simplified Journal interactions (#2124) * disabling sharing until sharing works again (#2123) Sugar Labs Activities http://activities.sugarlabs.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] activity record translate
On 26 July 2010 16:59, Esteban Arias ear...@plan.ceibal.edu.uy wrote: hi, Can you translate for the Cronometro and Duración combo values, the words seconds and minutes to spanish on activity Record. and add tilde on word Cronometro (-- Cronómetro) There was a problem with pootle but it has been fixed. You should be able to submit those translations there now. Thanks, Daniel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [DESIGN] Re: #1842 UNSP: Journal does not provide any error message on write errors
On Tue, Jul 13, 2010 at 12:32 AM, Anish Mangal
anishmangal2...@gmail.com wrote:
On Mon, Jul 12, 2010 at 7:53 PM, Aleksey Lim alsr...@member.fsf.org wrote:
On Mon, Jul 12, 2010 at 12:25:17PM +, Aleksey Lim wrote:
- Forwarded message from Sugar Labs Bugs
bugtracker-nore...@sugarlabs.org -
From: Sugar Labs Bugs bugtracker-nore...@sugarlabs.org
Subject: Re: #1842 UNSP: Journal does not provide any error message on write
errors
Cc: b...@lists.sugarlabs.org
Reply-To: sugar-devel@lists.sugarlabs.org
Date: Mon, 12 Jul 2010 12:23:33 -
#1842: Journal does not provide any error message on write errors
--+-
Reporter: bernie | Owner: alsroot
Type: defect | Status: assigned
Priority: Unspecified by Maintainer | Milestone: Unspecified by
Release Team
Component: sugar | Version: 0.84.x
Severity: Unspecified | Keywords: journal,
sugar-love, dev-love, r?
Distribution: Unspecified | Status_field: Needinfo
--+-
Changes (by alsroot):
* status_field: Unconfirmed = Needinfo
Comment:
Patch uses NotifyRedAlert but it is not part of sugar-toolkit i.e. code
won't work, what about just NotifyAlert and switch to red one later?
outdated, new patch[1] uses ErrorAlert
Just to add, ErrorAlert is made available using this patch[2]
Also, patch uses _('Alert') for alert title, could be not so informative
:), what about just Disk storage error?
outdated as well
volumestoolbar.py emits volume-error signal with error text taken from
exception, not sure if it is a good idea to pass it directly to user
visible message?
any ideas?
For IOError, its corresponding strerror is used. For ValueError
(which, amongst another scenarios can be raised in case there is no
file associated with a journal icon), the message in journal/model.py
isn't gettexed. Further, it doesn't seem that the ValueError messages
were meant to be displayed as GUI Alerts.
So given this, should one 're'-implement a similar check in
journal/volumestoolbar.py to ascertain the existence of any file
associated with the journal icon, or modify the ValueError messages.in
journal/model.py
What would be a plausible solution to this? Suggestions?
[1]
http://people.sugarlabs.org/anish/0001-Journal-show-error-message-on-write-failure-1842.patch
[2]
http://people.sugarlabs.org/anish/0001-Add-ErrorAlert-inherited-from-Alert.patch
--
Aleksey
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
--
Anish
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] How to copy something from the Journal to a pendrive?
Hi, Bernie just brought my XO-1 back from the dark ages (I was using 802) by passing me a pen-drive with build 300py (F11 + Sugar 0.88 if I'm not mistaken). Now playing around with it I realized that there was no menu option to copy something from the Journal onto a pendrive. Neither the popup menu over a Journal entry itself nor the copy-button on the details view offers such an option. Am I mistaken or did such an option exist in earlier builds? Thanks to the Uruguayan Sugar-devs in the room I learned that I could drag'n'drop a Journal entry right onto the pendrive icon. This surprised me quite a bit since I believe it's the first time I've seen drag'n'drop used in Sugar. Anyway, I'm thinking that adding a copy-to-pendrive option in the normal Journal menus (both the details view as well as the normal popup menu) would make sense since it's consistant with the rest of Sugar whereas drag'n'drop isn't really IMHO. Please let me know what you think. Thanks, Christoph -- Christoph Derndorfer co-editor, olpcnews url: www.olpcnews.com e-mail: christ...@olpcnews.com ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] How to copy something from the Journal to a pendrive?
Okay, we just discovered that it's apparently just my pendrive (8GB Cruzer) that's not showing up on the details view's copy-button palette. One way or another I think it would make sense to also offer such a copy option on the Journal list view itself as else copying multiple files from the Journal to a pendrive would be royal pain. Christoph On Tue, Jul 27, 2010 at 2:52 PM, Christoph Derndorfer christoph.derndor...@gmail.com wrote: Hi, Bernie just brought my XO-1 back from the dark ages (I was using 802) by passing me a pen-drive with build 300py (F11 + Sugar 0.88 if I'm not mistaken). Now playing around with it I realized that there was no menu option to copy something from the Journal onto a pendrive. Neither the popup menu over a Journal entry itself nor the copy-button on the details view offers such an option. Am I mistaken or did such an option exist in earlier builds? Thanks to the Uruguayan Sugar-devs in the room I learned that I could drag'n'drop a Journal entry right onto the pendrive icon. This surprised me quite a bit since I believe it's the first time I've seen drag'n'drop used in Sugar. Anyway, I'm thinking that adding a copy-to-pendrive option in the normal Journal menus (both the details view as well as the normal popup menu) would make sense since it's consistant with the rest of Sugar whereas drag'n'drop isn't really IMHO. Please let me know what you think. Thanks, Christoph -- Christoph Derndorfer co-editor, olpcnews url: www.olpcnews.com e-mail: christ...@olpcnews.com -- Christoph Derndorfer co-editor, olpcnews url: www.olpcnews.com e-mail: christ...@olpcnews.com ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [SoaS] sugar coating
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 This is probably something that would be of interest to sugar-devel as well. On 07/27/2010 03:11 PM, tom-ipp wrote: Hi, I wrote a small script in python which lets me sugarcoat linux application for sugar. In fact, you call the script with the name of an installed program (need the .desktop file) and it returns an activity directory - an icon appears in the home view to launch that program. The -l option will return you the programs installed in /usr/share/applications It looks for an svg icon, if not found the icon of the journal activity is used. It is based around the famous library libsugarize.so and the script found here : http://wiki.sugarlabs.org/go/Running_Linux_Applications_Under_Sugar Tested with fedora 13, for the application cheese, fedora-abe and fedora-supertux. You put the script simpleSugarCoater.py in your home directory, with the libsugarize.so. Morally, the sugar coating is not the best thing to promote the sugar platform. BUT we can't wait for the supertux developer to sugarize their application and we all need supertux. So... It's definitely a start, and better than having to leave Sugar entirely for such programs. Comments welcomed. Sincerely. Thomas The script: #!/usr/bin/env python # -*- coding: utf-8 -*- # # build activity directory for launching linux application from sugar # GNU General Public License v.3 # Author : Thomas Jacoviac # Contact : deve...@tom-ipp.info # import os import shutil import sys import getopt import xdg.DesktopEntry import xdg.IconTheme import xdg.BaseDirectory import mimetypes # == Declarations == activityPath = os.path.join(os.path.expanduser(~), Activities) #By default, the directory will be created in the user's Activities directory defaultIcon = /usr/share/icons/sugar/scalable/apps/activity-journal.svg # By default, this icon will be used for the application # == Internal functions == def sugarCoat(binary): global activityPath global defaultIcon iconName, execString = parseDesktopFile(binary) #Retrieve icon and exec from desktop file iconPath = locateIcon(iconName) createActivityDir(os.path.join(activityPath, binary + .activity)) # Create activity directory tree createInfoFile(activityPath, binary) # Create info file shutil.copy(iconPath, os.path.join(activityPath, binary + .activity, activity, icon.svg)) # Copy icon to activity directory if createLauncherFile(activityPath, binary, execString): sys.exit(Error with launcher creation) #Create launcher # Copy libsugarize.so in activity directory #TODO: More versatile location for distributing libsugarize.so shutil.copy(libsugarize.so, os.path.join(activityPath, binary + .activity, lib, libsugarize.so)) def parseDesktopFile(binary): dirs = xdg.BaseDirectory.xdg_data_dirs for dir in dirs: if os.path.isfile(os.path.join(dir + /applications/ + binary + .desktop)): desktopFileContent = xdg.DesktopEntry.DesktopEntry(filename = os.path.join(dir + /applications/ + binary + .desktop)) execString = desktopFileContent.getExec() iconName = desktopFileContent.getIcon() return iconName, execString sys.exit(No .desktop file for this application) def locateIcon(iconName): global defaultIcon iconPath = xdg.IconTheme.getIconPath(iconName, None, None, [svg]) #Get iconPath with xdg #TODO: Use xdg to magically find type, mimetypes is based on filename suffix if mimetypes.guess_type(iconPath)[0] != image/svg+xml: # Check if icon is svg file #From http://standards.freedesktop.org/icon-theme-spec/icon-theme-spec-latest.html #apps should look in $HOME/.icons, /usr/share/icons and /usr/share/pixmaps (in that order) dirs = [os.path.expanduser(~/.icons), /usr/share/icons, /usr/share/pixmaps] for dir in dirs: for root, ds, files in os.walk(dir): for file in files: if mimetypes.guess_type(file)[0] == image/svg+xml: if os.path.splitext(file)[0] == iconName: iconPath = os.path.join(root, file) return iconPath return defaultIcon # If no svg icon found, use default icon def createLauncherFile(activityPath, binary, execString): launcherFile = open(os.path.join(activityPath, binary + .activity, bin, launcher.sh), w) launcherFile.write(#!/bin/sh\n) launcherFile.write(# from http://wiki.sugarlabs.org/go/Running_Linux_Applications_Under_Sugar\n;) launcherFile.write(\n) launcherFile.write(while [ -n \$2\ ] ; do\n) launcherFile.write(case \$1\ in\n) launcherFile.write(-b | --bundle-id) export SUGAR_BUNDLE_ID=\$2\ ;;\n) launcherFile.write(-a | --activity-id) export SUGAR_ACTIVITY_ID=\$2\ ;;\n)
Re: [Sugar-devel] [SoaS] sugar coating
On Tue, Jul 27, 2010 at 4:15 PM, Luke Faraone l...@faraone.cc wrote: This is very good news. I am all for a Sugar wrapper to smooth things out for users. One quick comment however. For something that is meant to be a thin wrapper around other people's work, GPL is a bit of a thorny choice of license. Distributing this wrapper for use with sw with incompatible licenses would be a bit of a can of worms. Maybe that's what Thomas intends -- in that case, more power to him. OTOH, if he is happy to see wider use (and still wants GPL-style protection for his code) maybe something more like LGPL could be more appropriate. cheers, m -- martin.langh...@gmail.com mar...@laptop.org -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Journal and Updating Software Process
Maybe this topic was discussed before, teachers in Uruguay have reported as a bug this scenario: * The activities are updated * The user delete the journal entry with the activity bundle downloaded for this updating process. The result of this is that the activity is deleted from sugar This behavour is normal? Should I reported this as a bug? -- Ing. Daniel Castelo Plan Ceibal - Área Técnica Avda. Italia 6201 Montevideo - Uruguay. Tel.: 601.57.73 Interno 2228 E-mail : dcast...@plan.ceibal.edu.uy ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [SoaS] sugar coating
On Tue, 2010-07-27 at 15:15 -0400, Luke Faraone wrote: Morally, the sugar coating is not the best thing to promote the sugar platform. BUT we can't wait for the supertux developer to sugarize their application and we all need supertux. So... It's definitely a start, and better than having to leave Sugar entirely for such programs. libsugarize was a good hack to satisfy the requirements of Sugar's non-standard handshake protocol without touching the application. However, it lies to Sugar about several things and introduces needless complexity. All Linux desktops use a standard startup notification protocol that works with any application: http://www.freedesktop.org/software/startup-notification/ There's a library implementing this protocol which is already used by Gnome and KDE. I was hoping to get this done for F11-0.88, but there were too many other higher-priority things to do. Maybe we're still in time for 0.90. Before someone asks the standard rhetoric question [*]: following standards will make it easier to sugarize educational activities and improve the integration of existing non-native activities. [*] how does it help learning? -- // Bernie Innocenti - http://codewiz.org/ \X/ Sugar Labs - http://sugarlabs.org/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [SoaS] sugar coating
On Tue, Jul 27, 2010 at 5:39 PM, Bernie Innocenti ber...@codewiz.org wrote: On Tue, 2010-07-27 at 15:15 -0400, Luke Faraone wrote: Morally, the sugar coating is not the best thing to promote the sugar platform. BUT we can't wait for the supertux developer to sugarize their application and we all need supertux. So... It's definitely a start, and better than having to leave Sugar entirely for such programs. libsugarize was a good hack to satisfy the requirements of Sugar's non-standard handshake protocol without touching the application. However, it lies to Sugar about several things and introduces needless complexity. All Linux desktops use a standard startup notification protocol that works with any application: http://www.freedesktop.org/software/startup-notification/ There's a library implementing this protocol which is already used by Gnome and KDE. I was hoping to get this done for F11-0.88, but there were too many other higher-priority things to do. Maybe we're still in time for 0.90. h rejecting a fix/patch because you hope\intend to come up with a better solution in the future:( david Before someone asks the standard rhetoric question [*]: following standards will make it easier to sugarize educational activities and improve the integration of existing non-native activities. [*] how does it help learning? -- // Bernie Innocenti - http://codewiz.org/ \X/ Sugar Labs - http://sugarlabs.org/ ___ SoaS mailing list s...@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/soas ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Changing bundle_id and version scheme for Etoys
On Tue, Jul 27, 2010 at 5:14 PM, Bernie Innocenti ber...@codewiz.org wrote: The bundle base name (e.g Record) should be unique by itself, because you can't have two directories named Record.activity in your activities directory. This is, IMO, a bug. The directory should really be named after the bundle id. The bundle ID is not a dbus name, it just conforms to the character rules for dbus names. To quote http://wiki.laptop.org/go/Activity_bundles : -- begin quote -- This is the activity bundle identifier. It is required. The name should conform to the D-Bus spec - in particular, hyphens are not allowed (although this wasn't enforced in earlier builds, see Trac 6226). It is recommended that Java package naming conventions are used when chosing bundle identifiers, to ensure uniqueness. Briefly, your name should begin with the reversed domain name of an organization you belong to. The reversed domain name part is supposed to be rooted in some actual DNS-rooted namespace. You don't need to own this domain; you just need to have a reasonable claim on some unique name at that domain. There are several ways to derive one: If your email address is yourn...@somemailhost.com, then you could use com.somemailhost.yourname.YourActivity. You could set up a web page on a free hosting service with information about your activity, and use a name derived from its URL. For example, if you create a page at http://www.geocities.com/xotumusica for your activity, then com.geocities.www.xotumusica is a reasonable bundle_id. If nothing else is available, even org.laptop.wiki.YourActivityPageTitle is probably a reasonable bundle_id, provided that you create the YourActivityPageTitle page. Remember, bundle_ids should be unique, so you should double check that the YourActivityPageTitle page doesn't already exist (and then create it) before using this as your bundle_id. end quote This is a nicely decentralized mechanism for choosing identifiers which are guaranteed by construction never to conflict. Even if it were possible to install org.sugarlabs.Record and com.microsoft.Record in parallel, having two different activities with the same name would be confusing and almost never what the user expected. You're neglecting localization issues here. Perhaps there's still something we could do to simplify the design without breaking backwards compatibility: if an activity doesn't specify a bundle_id, its dbus name could be derived from the bundle name by pre-pending org.sugarlabs. (or org.laptop., it doesn't matter) to it. If sugarlabs is willing to maintain a mechanism for ensuring uniqueness, feel free to prepend org.sugarlabs to whatever activities you have registered. For all other purposes, the bundle_id is just a string which could contain anything. The bundle_id org.tuxpaint.sugar-is-lame worked flawlessly for all this time. Yes, this identifier is childish, but conforms precisely to the rules outlined above, which ensure its uniqueness. --scott -- ( http://cscott.net/ ) ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Changing bundle_id and version scheme for Etoys
On Tue, 2010-07-27 at 18:21 -0400, C. Scott Ananian wrote: This is a nicely decentralized mechanism for choosing identifiers which are guaranteed by construction never to conflict. It is indeed a simple and nice scheme, but why is such uniqueness a desiderable feature when developers can--and in fact *do*--often distribute forks of existing activities? Lucian has just created a fork of Browse and ParaguayEduca has a fork of XoIRC and VncLauncher on its wiki. In all cases, the bundle_id was intentionally left unmodified to ensure upgrades would work. (if the bundle_id were instead changed, funny things would happen when a user tries to install both bundles on the same machine). If sugarlabs is willing to maintain a mechanism for ensuring uniqueness, feel free to prepend org.sugarlabs to whatever activities you have registered. A good surrogate could be that no two activities with the same name can be uploaded to ASLO. Without a fancy scheme for signed bundles, nothing forbids people from distributing bundles with conflicting names from other sites, regardless of what uniqueness scheme gets chosen. For all other purposes, the bundle_id is just a string which could contain anything. The bundle_id org.tuxpaint.sugar-is-lame worked flawlessly for all this time. Yes, this identifier is childish, but conforms precisely to the rules outlined above, which ensure its uniqueness. It's not actually conforming, it has hyphens! ;-) -- // Bernie Innocenti - http://codewiz.org/ \X/ Sugar Labs - http://sugarlabs.org/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Evince browser plugin
Hi Lucian, sorry for the long delay, here is the git repository with the evince browser plugin. http://git.sugarlabs.org/projects/evince-browser-plugin The changes are on the plugin branch. It builds and seems to work fine for me in Lucid. Unfortunately it's still based on 2.25... I haven't tried rebasing to master, so I'm not sure how much work that would involve. Marco ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Changing bundle_id and version scheme for Etoys
On Tue, Jul 27, 2010 at 6:57 PM, Bernie Innocenti ber...@codewiz.org wrote: On Tue, 2010-07-27 at 18:21 -0400, C. Scott Ananian wrote: This is a nicely decentralized mechanism for choosing identifiers which are guaranteed by construction never to conflict. It is indeed a simple and nice scheme, but why is such uniqueness a desiderable feature when developers can--and in fact *do*--often distribute forks of existing activities? I think this is an orthogonal problem. I'm sure that some disagree. (if the bundle_id were instead changed, funny things would happen when a user tries to install both bundles on the same machine). Bug. If sugarlabs is willing to maintain a mechanism for ensuring uniqueness, feel free to prepend org.sugarlabs to whatever activities you have registered. A good surrogate could be that no two activities with the same name can be uploaded to ASLO. Translated name? English name? No Spanish name may conflict with a Portuguese or English name? Seems a bit strange to me. For all other purposes, the bundle_id is just a string which could contain anything. The bundle_id org.tuxpaint.sugar-is-lame worked flawlessly for all this time. Yes, this identifier is childish, but conforms precisely to the rules outlined above, which ensure its uniqueness. It's not actually conforming, it has hyphens! ;-) Oh, that's right, I *did* have a legit reason to dislike the name! ;-) --scott -- ( http://cscott.net/ ) ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Journal and Updating Software Process
On Tue, Jul 27, 2010 at 06:37:18PM -0300, Daniel Castelo wrote: * The activities are updated With Software update or manually using Browse? * The user delete the journal entry with the activity bundle downloaded for this updating process. The result of this is that the activity is deleted from sugar I've seen this on Sugar 0.84 if the activity was updated using Browse, but not if the activity was updated using Software update. This behavour is normal? Should I reported this as a bug? If you think it is a bug, then check for it in bugs.sugarlabs.org or report it there. I'm not sure what the behaviour should be. I'd be happy to see it fixed though, so that a user would have to both remove the download and remove the activity. -- 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] Journal and Updating Software Process
On Tue, Jul 27, 2010 at 9:37 PM, James Cameron qu...@laptop.org wrote: On Tue, Jul 27, 2010 at 06:37:18PM -0300, Daniel Castelo wrote: * The activities are updated With Software update or manually using Browse? * The user delete the journal entry with the activity bundle downloaded for this updating process. The result of this is that the activity is deleted from sugar I've seen this on Sugar 0.84 if the activity was updated using Browse, but not if the activity was updated using Software update. This behavour is normal? Should I reported this as a bug? If you think it is a bug, then check for it in bugs.sugarlabs.org See https://bugs.sugarlabs.org/ticket/1512 https://bugs.sugarlabs.org/ticket/1512 or report it there. I'm not sure what the behaviour should be. I'd be happy to see it fixed though, so that a user would have to both remove the download and remove the activity. -- James Cameron ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Sugar Digest 2010-07-28
==Sugar Digest== 1. Twitter-style: Hello from Squeakfest in Wilmington, North Carolina. We just had a demonstration of some Etoys projects done by 7th graders; pretty amazing. One student, when asked what she does to keep from getting frustrated said: Damn computer. But she is an accomplished problem solver. This is the first conference I have been to in years where the majority of presenters are ''not'' using PowerPoint. Naturally, by-in-large, they are using Etoys for their talks. It is great to see how teachers have incorporated the tool into their curriculum and the realities of school: even the kids built quizzes into their projects. But most of the learning is guided discovery. In many cases, kids use Etoys from a USB drive, so they could take their work home and turn in their homework. Bert Freudenberg showed an eloquent way to make animations in Etoys. I am inspired to finally add animation to my sprite library (the one I use for all of my activities: Turtle Art, Abacus, Visual Match, etc.) Simply a matter of adding paths and a timer. Yeah right. Avigail Snir, a teacher from Illinois showed a great example of exploring the modeling of gravity based on a simple basketball simulation. A remarkable thing was her use of a book to show the progress of her thinking along the path to discovery – the closest to a lab notebook as I have seen with Etoys (or any other learning program, for that matter). Lots more at [http://www.etoysillinois.org/]. Mahnaz Moallem talked about the challenges of making a transition from a well-defined, one best answer, discourage making mistakes classroom into an ill-defined, many answers, making mistakes and developing problem-solving skills classroom. She and her colleagues use extensive use of scaffolding and guiding to help kids stay motivated. Etoys Flaps are used for documenting what the kids have done. The consensus among North Carolina teachers at the conference is that there is terrible constraint in the schools in terms of tightly-scheduled problem-based requirements imposed on the teachers. Chandra Roughton posed a tough question: Is this a model or is it [just] a visualization? Etoys teachers think and do and demand a lot of each other and their students. What a breath of fresh air. ===In the community=== 2. There is a new and improved website describing teacher resources (in Spanish) here: http://wiki.laptop.org/go/Recursos_en_espanol 3. There will be a Turtle Art Day at the Arlington Career Center in Arlington Virginia on 7 August. ===Sugar Labs=== Gary Martin has generated SOMs from the past few weeks of discussion on the IAEP mailing list. http://wiki.sugarlabs.org/go/File:2010-July-10-16-som.jpg http://wiki.sugarlabs.org/go/File:2010-July-17-23-som.jpg Visit our [http://planet.sugarlabs.org planet] for more updates about Sugar and Sugar deployments. -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
