Re: [Sugar-devel] [SoaS] [DESIGN] Restart

2010-07-17 Thread Bernie Innocenti
El Sat, 17-07-2010 a las 02:25 +0200, Sebastian Dziallas escribió:

> I think the last time I looked into this, olpc-switch-desktop depended
> on olpc-dm, which comes with the entire olpc-utils package. Hence,
> we're currently going with gdm. :)

Using gdm with autologin is probably ok, but you don't want to show the
regular GDM login screen before Sugar boots, do you?

We could slightly modify olpc-switch-desktop to create the file that gdm
looks for to choose the session. It could create _both_ files, so the
package could be shared between SoaS and OLPC builds.

Even better, it could do what the standard switchdesk package does:
create a ~/.Xclients and ~/.Xclients-default file, which should work
with any display manager as long as they execute xinit.

If olpc-dm does not execute xinit, it probably should.

-- 
   // 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] [DESIGN] Restart

2010-07-17 Thread pbrobin...@gmail.com
On Sat, Jul 17, 2010 at 1:39 PM, Bernie Innocenti  wrote:
> El Sat, 17-07-2010 a las 02:25 +0200, Sebastian Dziallas escribió:
>
>> I think the last time I looked into this, olpc-switch-desktop depended
>> on olpc-dm, which comes with the entire olpc-utils package. Hence,
>> we're currently going with gdm. :)
>
> Using gdm with autologin is probably ok, but you don't want to show the
> regular GDM login screen before Sugar boots, do you?

We use autologin.

> We could slightly modify olpc-switch-desktop to create the file that gdm
> looks for to choose the session. It could create _both_ files, so the
> package could be shared between SoaS and OLPC builds.
>
> Even better, it could do what the standard switchdesk package does:
> create a ~/.Xclients and ~/.Xclients-default file, which should work
> with any display manager as long as they execute xinit.
>
> If olpc-dm does not execute xinit, it probably should.
>
> --
>   // 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] [DESIGN] Restart

2010-07-17 Thread Bernie Innocenti
El Fri, 16-07-2010 a las 08:40 -0400, Paul Fox escribió:

> i'm was far more surprised by moving shutdown to the top of that
> menu (i use the control panel a lot more than shutdown) than i was
> by the removal of restart.

Yes, I don't like this change either... but I'll ask the users what they
think.


> are the releases you're user-testing running powerd?

Yes. (it works beautifully, btw)


> if so, it's the
> first large-scale usage of the new suspend-or-shutdown menu, so i'm
> interested in reaction to that.  for instance -- is shutdown really
> the most often used menu item, now that the machine can be shut down
> with the power button?  and i know you have idle suspend disabled
> otherwise i'd be interested in hearing about the timeouts associated
> with those.

One problem with asking for this sort of feedback is that, in the
schools I visit, children aren't used to get questions on their personal
opinion. Being a foreigner who talks funny does not help either.

Nevertheless, I will try to find out and report back.

Automatic power saving is still disabled in our builds even though the
issue with the libertas firmware resetting seems to be fixed. When we
had power management enabled, teachers complained that the touchpad was
hard to use. Observing them for a while, I realized that their problem
was the short glitch on resume. Since they had no clue that the CPU was
being turned off, they were blaming the touchpad instead.

Is it possible to speed up the resume path? Also, does the serial port
output significantly slow down resume?

If speeding up resume isn't possible, perhaps slightly dimming the
display backlight might help give them a hint.

-- 
   // 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] CIA bot disabled

2010-07-17 Thread Bernie Innocenti
El Fri, 16-07-2010 a las 10:52 +0200, Tomeu Vizoso escribió:
> have disabled again the CIA bot because it's reporting old commits
> when people merge.

Git does merges on the local clone, so it can't be it.

To avoid polluting the history with spurious merges, people should
rebase their patches on top of the remote branch before pushing them. 

sugar-jhbuild already does this on update (git pull --rebase). You can
also do it manually: git rebase origin/master. Add --interactive for
some fun.


> Please only activate it once uninteresting commits are filtered out.

The cia glue script for gitorious could be made a lot smarter, but I
have no time to look into it. Anyone else?

I suspect that many irc floods are caused by activity on clones. Perhaps
we could exclude those.

-- 
   // 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] behaviour of F-keys on XO HS

2010-07-17 Thread Bernie Innocenti
El Thu, 15-07-2010 a las 23:08 -0400, Paul Fox escribió:
>  i think everyone (except
> apple, i'm learning tonight) agrees this is the correct setup
> when not in sugar.

Lenovo also seems to be switching to the Apple layout:

 http://www.blogcdn.com/www.engadget.com/media/2010/01/thinkpadedgepost16.jpg
 
http://www.thinkpads.com/wp-content/gallery/lenovo-thinkpad-edge-13-review/lenovo-thinkpad-edge-13-keyboard.jpg

Almost all the historic F-key mappings have an alternative CTRL+key or
ALT+key mapping in modern HIGs. Keys to control laptop volume and
brightness are accessed much more frequently, so it's foreseeable that
over time they will supplant the F-keys in PC keyboards.

-- 
   // 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] CIA bot disabled

2010-07-17 Thread Sascha Silbe
Excerpts from Bernie Innocenti's message of Sat Jul 17 13:10:01 + 2010:
> El Fri, 16-07-2010 a las 10:52 +0200, Tomeu Vizoso escribió:
> > have disabled again the CIA bot because it's reporting old commits
> > when people merge.
> Git does merges on the local clone, so it can't be it.
Actually it can be. Merges change the commit id, so "old" changes get reported 
as "new".
I partially worked around this by filtering out commits done by somebody else 
than me in "my" clones. This still spams the channel with commits from me that 
made it into mainline. I usually deactivate CIA while I push those merges, but 
often forget to do so.

> To avoid polluting the history with spurious merges, people should
> rebase their patches on top of the remote branch before pushing them. 
That only works if the changes are local - i.e. not if you've published them on 
gitorious clone.

> > Please only activate it once uninteresting commits are filtered out.
> The cia glue script for gitorious could be made a lot smarter, but I
> have no time to look into it. Anyone else?
I finally changed it to add the name of the repository (e.g. "mainline") so we 
can now do some filtering on it. 

> I suspect that many irc floods are caused by activity on clones. Perhaps
> we could exclude those.
Perhaps we should for the time being. While clones contain interesting activity 
as well (IMO even more interesting than mainline), I have no idea how we could 
filter out the merge spam. I already filter out the merge commits themselves 
for my clone, but filtering the "merged" commits is beyond my git foo.

Sascha

--
http://sascha.silbe.org/
http://www.infra-silbe.de/


signature.asc
Description: PGP signature
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


Re: [Sugar-devel] Fwd: [somos-azucar] instalar sugar en usb

2010-07-17 Thread KonS
Carlos mauro  gmail.com> writes:

> Una orientación amigos...
> -- Mensaje reenviado --De: VICTOR HUGO 
gmail.com>
> Fecha: 11 de julio de 2010 13:45Asunto: [somos-azucar] instalar sugar en
usbPara: somosazucar  lists.sugarlabs.orghola podrian orientarme en como
instalar sugar en una memoria usb yo
> 
> uso como sistema principal ubuntu remix en mi netbook, no uso windows.
> gracias
> ___
Buenas, yo tambien uso debian/ubuntu en mi caso lucid, estaba buscando la forma
de instalar sugar en esta distro y me tope contigo.

Yo voy a usar esta herramienta "unetbootin" ( apt-get install unetbootin ) la
cual es para poner iso's en usb's. miraba antes por la red, por si acaso..

Un saludo y suerte


Mi web

http://konsserver.no-ip.info/web





___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


Re: [Sugar-devel] Problem with Jhbuild and Fedora 11

2010-07-17 Thread Bernie Innocenti
El Thu, 15-07-2010 a las 11:38 -0300, Daniel Castelo escribió:
> 
> Sascha is the sugar-jhbuild maintainer, so if he says that we
> should
> drop F11 and you want to keep using it, then either you make a
> deal
> with him or you will have to maintain your own fork of it.
> 
>  
> No problem. As soon as possible I move to a next version.
> Thanks for all.

I would like to keep F11 support around a little longer too.

If no supported distribution requires building metacity from source,
maybe we could drop it?

BTW: what's the status of dropping GConf-dbus? Besides being
unmaintained, it makes Metacity crash and other evil things. There's an
easy alternative of running multiple user accounts. The recipe is quite
simple.

We should strive for *zero* external modules built from sources. They
cause all sort of build problems that are very hard to diagnose for a
typical Sugar developer who has no knowledge of the lower OS layers.

It's quite obvious to me that we're loosing contributions because
building Sugar is unnecessarily harder than building the Linux kernel or
gcc.

-- 
   // 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] behaviour of F-keys on XO HS

2010-07-17 Thread Bert Freudenberg

On 17.07.2010, at 09:31, Bernie Innocenti wrote:

> El Thu, 15-07-2010 a las 23:08 -0400, Paul Fox escribió:
>> i think everyone (except
>> apple, i'm learning tonight) agrees this is the correct setup
>> when not in sugar.
> 
> Lenovo also seems to be switching to the Apple layout:
> 
> http://www.blogcdn.com/www.engadget.com/media/2010/01/thinkpadedgepost16.jpg
> http://www.thinkpads.com/wp-content/gallery/lenovo-thinkpad-edge-13-review/lenovo-thinkpad-edge-13-keyboard.jpg
> 
> Almost all the historic F-key mappings have an alternative CTRL+key or
> ALT+key mapping in modern HIGs. Keys to control laptop volume and
> brightness are accessed much more frequently, so it's foreseeable that
> over time they will supplant the F-keys in PC keyboards.

+1

IMHO pressing "fn" to get "f1" to "f10" makes sense. In my daily routine I much 
more often change volume or brightness than use the numbered F keys.

Looking at this again

http://wiki.laptop.org/go/OLPC_Spanish_Non-membrane_Keyboard

I propose:

f1-f8 produce F key codes both with and without the fn key
f9-f12 produce F codes only with fn, and volume/brightness events 
without fn.

So holding down fn always gets you the F key codes, you can change 
volume/brightness without modifier, and as a bonus you can use the first eight 
F keys even without the fn key.

This mapping should work both in Sugar and outside. 

- Bert -


___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


[Sugar-devel] [PATCH] Help needed adding microformat support to the activity updater

2010-07-17 Thread akashg1611
1.Testing:  For testing purposes I replaced the call to aslo.py with my 
implemtation of the
  microformat, microformat.fetch_info()
2.Results: For the first time it starts a bit late and the checking stops at 
the first activity,
  ie. Image Viewer. On closing the software update panel now, and restarting it 
I get this error:
  raise RuntimeError('Multiple simultaneous requests are not supported')
  What does that mean, is it to prevent undefined behavious from the previously 
failed software
  updates? I am guessing here, as I just implemented the microformat 
parser(which seemed to work fine)
  and am now trying to modify it to sync with current backend.
3.Also if I comment out the raised exception above in the code, the software 
updater panel starts,
  but it hangs on the first activty ie. ImageViewer everytime.
4.As for microformat parser it fetches the activities information from the 
webpage and gets it into
  a dictionary with the activity_id as it's key, and each key corresponding to 
a two valued tuple
  (activity_version, activity_url)

I hope this provides enough information. Thanks!
---
 extensions/cpsection/updater/backends/Makefile.am  |3 +-
 .../cpsection/updater/backends/microformat.py  |  124 
 extensions/cpsection/updater/model.py  |4 +-
 3 files changed, 128 insertions(+), 3 deletions(-)
 mode change 100644 => 100755 extensions/cpsection/updater/backends/aslo.py
 create mode 100644 extensions/cpsection/updater/backends/microformat.py
 mode change 100644 => 100755 extensions/cpsection/updater/view.py

diff --git a/extensions/cpsection/updater/backends/Makefile.am 
b/extensions/cpsection/updater/backends/Makefile.am
index e280a07..6ed79cb 100644
--- a/extensions/cpsection/updater/backends/Makefile.am
+++ b/extensions/cpsection/updater/backends/Makefile.am
@@ -2,4 +2,5 @@ sugardir = $(pkgdatadir)/extensions/cpsection/updater/backends
 
 sugar_PYTHON = \
aslo.py \
-   __init__.py
+   __init__.py \
+microformat.py
diff --git a/extensions/cpsection/updater/backends/aslo.py 
b/extensions/cpsection/updater/backends/aslo.py
old mode 100644
new mode 100755
diff --git a/extensions/cpsection/updater/backends/microformat.py 
b/extensions/cpsection/updater/backends/microformat.py
new file mode 100644
index 000..edeb9f1
--- /dev/null
+++ b/extensions/cpsection/updater/backends/microformat.py
@@ -0,0 +1,124 @@
+#!/usr/bin/python
+# Copyright (C) 2009, Sugar Labs
+#
+# This program is free software; you can redistribute it and/or modify
+# it under the terms of the GNU General Public License as published by
+# the Free Software Foundation; either version 2 of the License, or
+# (at your option) any later version.
+#
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+# GNU General Public License for more details.
+#
+# You should have received a copy of the GNU General Public License
+# along with this program; if not, write to the Free Software
+# Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA  02110-1301 USA
+
+'''Sugar Microformat Parser.
+
+This module implements the microformat parser for the
+activity updater.
+'''
+from HTMLParser import HTMLParser
+from urllib2 import urlopen, URLError
+
+dic = {}
+
+_fetcher = None
+
+
+class _Microformat_UpdateFetcher(object):
+
+def __init__(self, bundle, completion_cb):
+
+
_MicroformatParser('http://wiki.paraguayeduca.org/index.php/Actividades_y_contenidos')
+self._completion_cb = completion_cb
+self._bundle = bundle
+self._get_updated_info()
+
+def _get_updated_info(self):
+try:
+version, link = dic[self._bundle.get_bundle_id()]
+except KeyError:
+print "No bundle with this id"
+   return
+else:
+size = 0
+global _fetcher
+_fetcher = None
+self._completion_cb(self._bundle, version, link, size, None)
+
+class _MicroformatParser(HTMLParser):
+
+   '''Microformat parser for the activity updater'''
+
+   def __init__(self,url):
+   HTMLParser.__init__(self)
+   self._activity_id = ''
+   self._activity_url = ''
+   self._activity_version = ''
+   self._inside_activity_version = False
+   self._inside_activity_id = False
+   self._inside_activity_url = False
+
+   try:
+   req = urlopen(url)
+   except URLError, e:
+   if hasattr(e, 'reason'):
+   print 'you failed to reach a server.'
+   print 'Reason: ', e.reason
+   elif hasattr(e, 'code'):
+   print 'The server couldn\'t fulfill the 
request.'
+   

[Sugar-devel] Sugar Digest 2010-07-17

2010-07-17 Thread Walter Bender
==Sugar Digest==

1. Over the past month I have had the pleasure of visiting Sugar/OLPC
deployments in Paraguay, Uruguay, Argentina, Nicaragua, and Peru. Each
has been different from the next, but all share a common goal of
bringing the opportunity for learning to the children of their
communities. I've gotten to spend time with the local deployment
teams, teachers, trainers, technicians, government officials,
children, and even some parents. Sugar, GNU/Linux and OLPC volunteers
and community members has also been present everywhere I have gone.

I cannot begin to describe the dedication and energy I have observed
and what it means to me to see the efforts of countless thousands of
volunteers being put into practice.

In Nicaragua, the deployment is being run by Grupo Financiero LAFISE
BANCENTRO. They are focusing their efforts on the Atlantic Coast,
where the needs are greatest. Daniel Drake, who deserves to be
knighted for his tireless efforts – he has volunteered in Ethiopia,
Nigeria, Nepal, Argentina, Paraguay, and Peru – was in Managua,
helping yet another technical team get on top of all of the issues
they face in scaling up a deployment. Claudia Urea led a series of
discussions with the pedagogical team and I had a chance to hold a
workshop on hacking Sugar with the local GNU/Linux community; we
covered a lot of ground and managed to submit a patch by the end of
evening.

In Peru, I spent time at the ministry of education, giving them an
update on the latest from Sugar Labs and discussing with them a
strategy for upgrading their XO 1.0 computers while phasing in XO 1.5
machines as well as Sugar on a Stick. The highlight of the trip was a
day-long seminar with 1000 teachers from schools in the Lima region.
(These teachers will be working with Sugar in the next phase of the
Peru deployment.) I gave two presentations: a morning talk on Sugar
and pedagogy and an after-lunch demonstration of Sugar (we ate chifa).
I had a very good reception, but I was out-staged by the presentation
by Sdenka Salas, a teacher from Puno, a city on the shore of Lake
Titikaka. Sdenka, as you may recall, wrote a book about Sugar for
teachers, ''La Laptop XO en el Aula''. She also hosted Sebastian Silva
at a recent Sugar Camp in Puno that made major inroads into
translating Sugar into Quechua and Aymara. As usual, I gave my
presentation using Turtle Art. Sdenka used Etoys for her talk.
Needless to say, the teachers were blown away by seeing the
accomplishments of one of their own. It was breathtaking. Victor
Castillo ended the meeting with a call for more regional autonomy and
sharing among them – a great directive.

2. While in Lima, I got my first look at the OLPC "High School"
machine. It is a blue XO 1.5 with a "standard" non-membrane keyboard.
The keyboard exceeded my expectations. I am guessing that it will be
quite popular with deployments.

===In the community===

3. Squeakfest will be held in Wilmington, North Carolina on the
26th–28th of July. [http://www.squeakland.org/squeakfest/about/].

4. There will be a Turtle Art Day at the Arlington Career Center in
Arlington Virginia on 7 August. Jeff Elkner's team will be showing off
the activity portal they have build for uploading and sharing Turtle
Art projects. (It could serve as a prototype for a general Sugar
project portal.)

===Tech talk===

5. Chris Ball announced the release of build os206 as the final 10.1.1
release build for XO-1.5 laptops. Release notes are available at
[http://wiki.laptop.org/go/Release_notes/10.1.1]. Instructions for
installing the release can be found at
[http://wiki.laptop.org/go/Release_notes/10.1.1#Installation].

===Sugar Labs===

Gary Martin has generated SOMs from the past few weeks of discussion
on the IAEP mailing list.

2010 July 3rd-9th (38 emails)  [File:2010-July-3-9-som.jpg]

Visit our planet for more updates about Sugar and Sugar deployments.
[http://planet.sugarlabs.org]

-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] [DESIGN] Restart

2010-07-17 Thread Paul Fox
bernie wrote:
 > El Fri, 16-07-2010 a las 08:40 -0400, Paul Fox escribió:
 > > if so, it's the
 > > first large-scale usage of the new suspend-or-shutdown menu, so i'm
 > > interested in reaction to that.  for instance -- is shutdown really
 > > the most often used menu item, now that the machine can be shut down
 > > with the power button?  and i know you have idle suspend disabled
 > > otherwise i'd be interested in hearing about the timeouts associated
 > > with those.
 > 
 > One problem with asking for this sort of feedback is that, in the
 > schools I visit, children aren't used to get questions on their personal
 > opinion. Being a foreigner who talks funny does not help either.
 > 
 > Nevertheless, I will try to find out and report back.

well, if they're not complaining, and not confused, that's the main
thing.  :-)

 > 
 > Automatic power saving is still disabled in our builds even though the
 > issue with the libertas firmware resetting seems to be fixed. When we
 > had power management enabled, teachers complained that the touchpad was
 > hard to use. Observing them for a while, I realized that their problem
 > was the short glitch on resume. Since they had no clue that the CPU was
 > being turned off, they were blaming the touchpad instead.

ah -- good observation!

 > 
 > Is it possible to speed up the resume path? Also, does the serial port
 > output significantly slow down resume?

i don't believe it does.  resume certainly hasn't gotten faster on
XO-1, and the resume delay has always been a concern.

 > If speeding up resume isn't possible, perhaps slightly dimming the
 > display backlight might help give them a hint.

dimming after 15 seconds?  perhaps.  or maybe we should simply make
the time-to-suspend quite a bit longer on XO-1.  (a minute?  two?)

paul
=-
 paul fox, p...@laptop.org
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


Re: [Sugar-devel] [DESIGN] Restart

2010-07-17 Thread Bernie Innocenti
El Sat, 17-07-2010 a las 20:00 -0400, Paul Fox escribió:

> dimming after 15 seconds?  perhaps.  or maybe we should simply make
> the time-to-suspend quite a bit longer on XO-1.  (a minute?  two?)

I'm not a fan of adding obscure configuration knobs for everything, but
this seems one of those cases in which users may want to choose. At the
UI level, it's more like replacing a binary switch with an analog slider
going from "10 seconds" to "Never".

-- 
   // 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] Pulsing icons don't stop

2010-07-17 Thread Gonzalo Odiard
I am using systemtap in F13 to try to know what is doing sugar.
In my first test I found the pulsing icon in launcher.py never stop.
To monitor sugar-sesion I have a script stap-sugar-session.sh:

[gonz...@aronax sugar-jhbuild]$ cat stap-sugar-session.sh
SUGAR_SESSION_PID=`ps ax | grep sugar-session | grep -v grep | awk
'{printf("%s",$1)}'`
stap -t /usr/share/doc/python-libs-2.6.4/systemtap-sugar-3.stp -x
$SUGAR_SESSION_PID

The file /usr/share/doc/python-libs-2.6.4/systemtap-sugar-3.stp is a
modification of /usr/share/doc/python-libs-2.6.4/systemtap-example.stp, but
you can use it also.

If I start sugar-emulator and execute stap-sugar-session.sh I can see after
start a activity and stop the activity, the pulsing icon continue for ever.
It can be resolved applying the following patch, but I don't know if it's
the right solution. May be it's anything wrong with the properties.


 [gonz...@aronax view]$ diff -u launcher.py launcher.py.new
--- launcher.py2010-07-18 01:39:20.436252902 -0300
+++ launcher.py.new2010-07-17 01:25:42.893632264 -0300
@@ -122,7 +122,7 @@
 self.connect('destroy', self.__destroy_cb)

 def __destroy_cb(self, box):
-self._activity_icon.pulsing = False
+self._activity_icon.set_paused(True)
 self._home.disconnect_by_func(self.__active_activity_changed_cb)

 def zoom_in(self):
@@ -133,13 +133,13 @@
   style.STANDARD_ICON_SIZE,
   style.XLARGE_ICON_SIZE))
 self._animator.start()
-self._activity_icon.pulsing = True
+self._activity_icon.set_paused(False)

 def __active_activity_changed_cb(self, model, activity):
 if activity.get_activity_id() == self._activity_id:
-self._activity_icon.paused = False
+self._activity_icon.set_paused(False)
 else:
-self._activity_icon.paused = True
+self._activity_icon.set_paused(False)


 class _Animation(animator.Animation):

There are other files using the same properties.

[gonz...@aronax site-packages]$ pwd
/home/gonzalo/sugar-jhbuild/install/lib/python2.6/site-packages
[gonz...@aronax site-packages]$ grep -r props.pause *
jarabe/view/launcher.py.ori:self._activity_icon.props.paused =
False
jarabe/view/launcher.py.ori:self._activity_icon.props.paused =
True
jarabe/desktop/meshbox.py:net.props.paused = True
jarabe/desktop/meshbox.py:net.props.paused = False
[gonz...@aronax site-packages]$ grep -r props.pulsing *
jarabe/view/launcher.py.ori:self._activity_icon.props.pulsing =
False
jarabe/view/launcher.py.ori:self._activity_icon.props.pulsing = True
jarabe/frame/notification.py:self._icon.props.pulsing = True
jarabe/frame/notification.py:self._icon.props.pulsing = False
jarabe/frame/activitiestray.py:self._icon.props.pulsing = True
jarabe/frame/activitiestray.py:self._icon.props.pulsing = False
jarabe/desktop/meshbox.py:self.props.pulsing = True
jarabe/desktop/meshbox.py:self.props.pulsing = False
jarabe/desktop/meshbox.py:self.props.pulsing = False
jarabe/desktop/meshbox.py:self.props.pulsing = False
jarabe/desktop/meshbox.py:self.props.pulsing = True
jarabe/desktop/meshbox.py:self.props.pulsing = False
jarabe/desktop/meshbox.py:self.props.pulsing = False

I can put the instructions to use systemtap with sugar in the wiki if
anybody think its useful.
-- 
Gonzalo Odiard
SugarLabs Argentina
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel