[Sugar-devel] [ASLO] Release Turtle Blocks-103
Activity Homepage: http://activities.sugarlabs.org/addon/4027 Sugar Platform: 0.82 - 0.90 Download Now: http://activities.sugarlabs.org/downloads/file/27100/turtle_art-103.xo Release notes: * sensor palette: sound, volume, pitch, resistance, voltage * menu cleanup: samples on import/export toolbar * error message when trying to mix and match incompatible blocks * new DE translations Sugar Labs Activities http://activities.sugarlabs.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] [PATCH] Adopt Updater to new activity version scheme
---
extensions/cpsection/updater/backends/aslo.py |9 ++---
extensions/cpsection/updater/model.py |4 +++-
extensions/cpsection/updater/view.py |2 +-
3 files changed, 10 insertions(+), 5 deletions(-)
diff --git a/extensions/cpsection/updater/backends/aslo.py
b/extensions/cpsection/updater/backends/aslo.py
index 5f257f9..3d63406 100644
--- a/extensions/cpsection/updater/backends/aslo.py
+++ b/extensions/cpsection/updater/backends/aslo.py
@@ -54,6 +54,9 @@ import traceback
import gio
+from sugar.bundle.bundleversion import NormalizedVersion
+from sugar.bundle.bundleversion import InvalidVersionError
+
from jarabe import config
_FIND_DESCRIPTION = \
@@ -127,10 +130,10 @@ class _UpdateFetcher(object):
size = None
else:
try:
-version = int(document.find(_FIND_VERSION).text)
-except ValueError:
+version = NormalizedVersion(document.find(_FIND_VERSION).text)
+except InvalidVersionError:
logging.error(traceback.format_exc())
-version = 0
+version = '0'
link = document.find(_FIND_LINK).text
diff --git a/extensions/cpsection/updater/model.py
b/extensions/cpsection/updater/model.py
index 9845371..d58e3bc 100755
--- a/extensions/cpsection/updater/model.py
+++ b/extensions/cpsection/updater/model.py
@@ -33,6 +33,7 @@ import gio
from sugar import env
from sugar.datastore import datastore
from sugar.bundle.activitybundle import ActivityBundle
+from sugar.bundle.bundleversion import NormalizedVersion
from jarabe.model import bundleregistry
@@ -83,7 +84,8 @@ class UpdateModel(gobject.GObject):
logging.error('Error getting update information from server:\n'
'%s' % error_message)
-if version is not None and version bundle.get_activity_version():
+if version is not None and \
+version NormalizedVersion(bundle.get_activity_version()):
self.updates.append(BundleUpdate(bundle, version, link, size))
if self._cancelling:
diff --git a/extensions/cpsection/updater/view.py
b/extensions/cpsection/updater/view.py
index 2164c0b..ce853fb 100644
--- a/extensions/cpsection/updater/view.py
+++ b/extensions/cpsection/updater/view.py
@@ -359,7 +359,7 @@ class UpdateListModel(gtk.ListStore):
row[self.SELECTED] = True
row[self.ICON_FILE_NAME] = bundle_update.bundle.get_icon()
-details = _('From version %(current)d to %(new)s (Size: %(size)s)')
+details = _('From version %(current)s to %(new)s (Size: %(size)s)')
details = details % \
{'current': bundle_update.bundle.get_activity_version(),
'new': bundle_update.version,
--
1.7.2.3
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] More new and revised chapters of Make Your Own Sugar Activities! ready for review, feedback
Aleksey, I've changed the paragraph in http://en.flossmanuals.net/bin/view/ActivitiesGuideSugar/SugarDebugging It is not published yet, but if you use the link above you can see it. If it looks OK to you I'll ask for the changes to be published. Thanks, James Simmons On Sat, Nov 6, 2010 at 9:11 PM, Aleksey Lim alsr...@member.fsf.org wrote: I've found minor issue on http://en.flossmanuals.net/ActivitiesGuideSugar/SugarDebugging You can also set the logging level outside your program code using an environment variable. For instance, in Sugar .82 and lower you can start sugar-emulator like this: SUGAR_LOGGER_LEVEL=debug sugar-emulator The way you accomplish the same thing in Sugar .84 and greater is to edit the file ~/.sugar/debug and uncomment the line that sets the SUGAR_LOGGER_LEVEL. SUGAR_LOGGER_LEVEL=debug sugar-emulator will will work in 0.84+ as well if ~/.sugar/debug doesn't reset SUGAR_LOGGER_LEVEL, i.e., ~/.sugar/debug just overrides current values right before launching sugar. -- Aleksey ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] ObjectChooser() Issue?
At Sasha's suggestion, I've arrived at the following code to send the filepath of a soundfile to Csound via its reference in the Journal. The filename (self.filename[0]) is being correctly passed: def choose1(self, widget): chooser = ObjectChooser(parent=self, what_filter=mime.GENERIC_TYPE_AUDIO) result = chooser.run() if result == gtk.RESPONSE_ACCEPT: jobject = chooser.get_selected_object() if jobject and jobject.file_path: self.filename[0] = str(jobject.file_path) # open(jobject.file_path).read() # open(self.filename[0]).read() else: self.filename[0] = 0 The problem is that the file cannot be opened by Csound - either via the above function as it stands, or by the addition of either line that is commented out. I receive this error message (from Csound): diskinfo can't open /home/olpc/.sugar/default/data/f70f03b1-fe40-44e6-9d75-5ef274cf0ad2.wav The filepath and name are correct, and the file can be played fine with either Browse or Jukebox. What must I do to make the referenced soundfile readable? Art Hunkins ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Sugar Digest 2010-11-08
==Sugar Digest== 1. After a long absence, Turtle Art with Sensors is back! The original fork was written by Arjun Sarwal when he was an intern at OLPC (See http://wiki.laptop.org/go/Turtle_Art_with_Sensors); however, when we migrated Sugar to non-XO platforms, we stopped supporting this fork due to problems with the alsaaudio library. With help from Tony Forster, Turtle Blocks (the mainline version of the project) has a sensor palette [http://wiki.sugarlabs.org/go/Activities/TurtleArt#Sensors_Palette] with blocks for sound (raw microphone input), volume, and pitch, and on OLPC XO hardware, resistance and voltage sensors. I used a Hall-effect sensor to build a bicycle odometer in Turtle Art. [http://wiki.sugarlabs.org/go/File:Bike_odometer.png] Tony has begun writing up a detailed description of the sensor input [http://wiki.sugarlabs.org/go/Activities/TurtleArt/Using_Turtle_Art_Sensors]. Claudia Urrea has documented how to build sensors [http://wiki.laptop.org/go/Making_XO_sensors] that work with the XO microphone input. Enjoy. Also note that the Butiá robot team [http://wiki.sugarlabs.org/go/Archive/Current_Events/2010-10-26] added Arduino support to a fork of Turtle Art. 2. There is growing interest in using Sugar as part of a computer-science curriculum. I have started to accumulate links to syllabi here: [http://wiki.sugarlabs.org/go/Activity_Team#Sugar_Activity_development_courses] ===In the community=== 3. I was in Lima last week where I got a chance to discuss some details of the Peru OLPC deployment with Oscar Becerra. We spent much of our time discussing how to better coordinate with community efforts in Peru. Oscar is organizing a meeting -- tentatively scheduled for mid-February -- which will hopefully serve as a vehicle for more cooperation. 4. DIGITAL CITIZENSHIP, an international forum on development and social inclusion through the use of ICT in Uruguay will be held on 29th and 30th November 2010 at the Uruguayan Laboratory of Technology (LATU) in Montevideo, Uruguay. ===Tech Talk=== 5. Aleksey Lim, Bernie Innocenti, et al. have been working on an upgrade to the Sugar Gitorious server. They have been running a test environment, jita.sugarlabs.org, with much success; git.sugarlabs.org will be switched to the new Gitorious code base soon. ===Sugar Labs=== Gary Martin has generated a SOM from the past few week of discussion on the IAEP mailing list. http://wiki.sugarlabs.org/go/File:2010-Oct-30-Nov-5-som.jpg (58 emails) Visit our planet [http://planet.sugarlabs.org] 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
Re: [Sugar-devel] More new and revised chapters of Make Your Own Sugar Activities! ready for review, feedback
On Mon, Nov 08, 2010 at 11:07:48AM -0600, James Simmons wrote: Aleksey, I've changed the paragraph in http://en.flossmanuals.net/bin/view/ActivitiesGuideSugar/SugarDebugging It is not published yet, but if you use the link above you can see it. If it looks OK to you I'll ask for the changes to be published. Looks fine to me, thanks. Thanks, James Simmons On Sat, Nov 6, 2010 at 9:11 PM, Aleksey Lim alsr...@member.fsf.org wrote: I've found minor issue on http://en.flossmanuals.net/ActivitiesGuideSugar/SugarDebugging You can also set the logging level outside your program code using an environment variable. For instance, in Sugar .82 and lower you can start sugar-emulator like this: SUGAR_LOGGER_LEVEL=debug sugar-emulator The way you accomplish the same thing in Sugar .84 and greater is to edit the file ~/.sugar/debug and uncomment the line that sets the SUGAR_LOGGER_LEVEL. SUGAR_LOGGER_LEVEL=debug sugar-emulator will will work in 0.84+ as well if ~/.sugar/debug doesn't reset SUGAR_LOGGER_LEVEL, i.e., ~/.sugar/debug just overrides current values right before launching sugar. -- Aleksey -- Aleksey ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [Alpha release] DevTutor activity
Manu, I just ran it on my XO laptop with runs the .84 release for Paraguay. Your Activity requires the new style toolbars, which .84 does not support. I realize that the purpose of your Activity is to demonstrate the use of Sugar API's, so full backward compatibility with graceful degradation may be unrealistic. However, supporting both new and old toolbars is not that difficult. I describe a workable method in Make Your Own Sugar Activities! Judging from the screenshots most of the API's you're demonstrating haven't changed much, so maybe you could implement at least part of functionality in .84, which might be the newest thing out in the field. I'll try out your Activity at home in my dev environment and let you know what I think. It sound pretty neat! Terrific job on the icon, by the way. James Simmons On Sun, Nov 7, 2010 at 4:30 PM, Manusheel Gupta m...@laptop.org wrote: Dear all, I am delighted to announce the alpha release of the DevTutor activity focused on understanding the Sugar API modules. Please visit - http://activities.sugarlabs.org/en-US/sugar/addon/4353 Many thanks to Kandarp Kaushik for his dedication and consistency during all the stages of the development; Ayush Goyal for designing the svg icon of the activity and Aleksey Lim for his continued guidance to the team. We look forward to hearing your feedback and experience with DevTutor activity. If you would like to put in a feature request, please do so at http://bugs.sugarlabs.org. Hope you find the activity useful. Regards, Manu ___ 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] [Election] Membership registration deadline in two days
Hi all, This is an informational mail; nothing has changed since my previous date announcement last month. By Wednesday, 2010-11-10 23:59 EST, all applications for membership must be submitted if they are to be considered valid for the upcoming election. On the 13th, all applications submitted before this deadline will be processed, and ballots will go out the next day. The voting period ends two weeks later, on the 28th. Please see http://wiki.sugarlabs.org/go/Sugar_Labs/Members#Applying_for_membership for information on how to apply. If you're not listed on http://wiki.sugarlabs.org/go/Sugar_Labs/Members/List, we don't know to send you a ballot! In addition, some people have no email address on file, noted by a red NO next to their name. If you are this person, or you know how we can contact them, let me know and I'll fix it in the database. Thanks, Luke Faraone Membership and Elections Committee Sugar Labs ✉: l...@sugarlabs.org I: lfaraone on irc.freenode.net signature.asc Description: OpenPGP digital signature ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Sugar UI Dictator
[cc += eben, cms] On Fri, 2010-10-29 at 10:02 +0100, Martin Dengler wrote: IMO a decent justification and a willingness to update the affected wiki pages - including the HIG - to a similar or better standard as what existed before should almost be enough for me. What I'm worried about is the HIG that exists - incomplete as it is - is being chipped away and we're left with UI that's justified by nothing but a patchwork of ad-hoc decisions made by very different people with very different users in mind. While I strongly believe in the power of loosely-managed volunteer-driven development, distributed authority doesn't seem to work equally well when it comes to human interface design. Good design implies one consistent vision, which is hard to obtain collaboratively. A case-by-case decision process results in either inconclusive discussions or UI inconsistency. It might work better if we agreed to delegate all design decisions to one clever dictator, in the style of Steve Jobs. In the early days of Sugar, Eben used to cover this role and many would probably agree that it worked very well. It's tempting to say that we already have a Design Team with a Coordinator, but today people proposing changes are supposed to follow a vague process which involves defending the proposal against a variety of alternatives, compromising with some of them in the hope to reach consensus soon or later. What I'm asking for is fundamentally different: there can still be a good public discussion, but in the end only one person would give a clear ACK or NAK within a finite amount of time and effort. At worse you could get a change this part and I will approve. Who should become the dictator could be decided by the currently active members of the design team. A truly great UI Dictator wouldn't undergo the annoying delay of democratic elections ;-) -- // 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] Request to review solution for SL #2464
Hello! I have uploaded a new xo to http://dev.laptop.org/~gonzalo/Paint-29.xo I don't have a 0.82 system, can anybody confirm if is working ok? Thanks! Gonzalo On Wed, Oct 20, 2010 at 11:25 AM, Gary Martin garycmar...@googlemail.comwrote: Hi Anurag/Gonzalo, On 19 Oct 2010, at 16:43, Anurag Chowdhury wrote: Gonzalo, I have run the chmod commands as suggested by Gary, and have uploaded Paint xo bundle at http://bugs.sugarlabs.org/ticket/2464. Kindly review it. Thanks, your test bundle installed and launched correctly on Sugar 0.82, I've updated the ticket with my comments: http://bugs.sugarlabs.org/ticket/2464 ...and added you to the cc: field – I'm just replying to your email here in case others are also interested in the ticket (usually I would just add my comments to the ticket and assume other interested parties were already following it). Regards, --Gary Regards, Anurag ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- Gonzalo Odiard ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [ANNOUCE] git.sugarlabs.org migration and downtime
On Sun, Nov 07, 2010 at 10:33:03PM +, Aleksey Lim wrote: Hi all, Thanks for testing new gitorious instance (if you didn't try yet, go to [1]). Since usual git.sugarlabs.org workflows looks good and since several people have ssh login issues (we are limitied in investigation these issues on current git.sugarlabs.org instance) and keeping im mind that [1] works for them, we are migrating git.sugarlabs.org to the new Gitorios code base and moving it to another host to make users support more responsive. git.sugarlabs.org will be inaccessible starting from 2010-11-09 01:00 UTC, for 2 hours. [1] http://jita.sugarlabs.org/ P.S. Previous request to test common SL login system was just a try to investigate this feature, git.sugarlabs.org will still use regular accounts after migration. New Gitorios is ready for using from regular http://git.sugarlabs.org. There are found isses that will be fixed soon: * HTTP cloning doesn't work * cgit.sugarlabs.org is useless * http://cia.vc plugin is inactive -- Aleksey ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
