Re: [Sugar-devel] [laptop-accessibility] screenreader for sugar

2011-09-02 Thread Tomeu Vizoso
On Tue, Aug 30, 2011 at 15:51, Esteban Arias ear...@plan.ceibal.edu.uy wrote:
 What should we change in sugar?

See these:

http://library.gnome.org/users/gnome-access-guide/stable/
http://library.gnome.org/devel/accessibility-devel-guide/stable/

Regards,

Tomeu

 2010/9/8 Tomeu Vizoso to...@sugarlabs.org

 On Tue, Sep 7, 2010 at 18:32, Peter Korn peter.k...@oracle.com wrote:
 
  Hi Tomeu, gang,
 
  [I'm cc-ing Joanie Diggs, co-maintainer of Orca]
 
  I believe there are 6 key things that need to be done in/for Sugar to
  enable use of the GNOME accessibility work for folks with vision
  impairments.  Others more expert in the specific details may correct/amend
  my comments.  I believe the 6 things are:
 
  The shift of AT-SPI from CORBA to DBUS (in process, not yet completed,
  but builds of at-spi2 are in the GNOME code repository and if someone would
  start playing and testing with it on the OLPC, that'd be great!)

 I tested the very recent bits of at-spi2 in sugar-jhbuild and they
 seemed to work fine in that accerciser was able to navigate through
 the controls of the desktop window and of activities (applications).

  Implementation of ATK by the Sugar UI components (this is the
  accessibility API that screen readers like Orca use)

 Accerciser showed that it could not go into the HippoCanvas widget
 that is used in some fundamental parts of the Sugar shell and also
 inside our browser. The browser is moving from xulrunner to webkitgtk+
 which I expect to fare much better there. About HippoCanvas, I have
 been experimenting with replacing it with custom GtkContainers and
 dropping Hippo completely seemed very doable.

  Creating / adapting a magnifier service on Sugar for Orca.  This may be
  a fairly trivial port of gnome-mag (non-COMPOSITE edition), or it may be a
  complete re-write

 I have no idea of what this entails, but as we have kept quite close
 to GNOME's architecture, I expect the fairly trivial port to suffice.

  Porting Orca to Sugar.  This may be fairly trivial, or it may involve a
  new Sugar-style GUI, etc.

 Tried out Orca in Sugar and it was able to read windows titles,
 buttons labels, etc. What GUI would it have other than a configuration
 parameter for starting it automatically at startup?

  Adding theme support go Sugar for vision impairments - things like a
  large-print theme, and inverse theme, etc.

 The Uruguayan deployment has customized their builds in this direction
 but I believe they need help upstreaming it.

  Ensure 100% keyboard operability of Sugar

 Hippo is also the roadblock here.

  Tomeu - are there folks in sugar-devel who have cycles to work on these
  things?

 No idea, I started this thread to find out :)

 Thanks a lot for the great insights!

 Tomeu

 
  Regards,
 
 
  Peter
 
  On 9/7/2010 12:49 AM, Tomeu Vizoso wrote:
 
  On Mon, Sep 6, 2010 at 20:15, Esteban Arias ear...@plan.ceibal.edu.uy
  wrote:
 
 
  no, I tested with gnome desktop.
 
 
  Ok, I can help you get in touch with the GNOME team that works on
  accessibility if you want. They are very dedicated, friendly and
  talented bunch. Collabora and other companies also provide services
  related to accessibility and GNOME.
 
  But nobody else than us is going to fix accessibility in Sugar so
  that's why I'm asking if anybody here has interest in working on this.
  The first need is finding someone who can tell us what needs to be
  improved in Sugar so it can be used by people with no or very low
  vision.
 
  Thanks,
 
  Tomeu
 
 
 
  2010/9/3 Tomeu Vizoso to...@sugarlabs.org
 
 
  On Thu, Sep 2, 2010 at 18:25, Esteban Arias ear...@plan.ceibal.edu.uy
  wrote:
 
 
  xo-1.0 | F11 | Dextrose version | Gnome desktop | orca 2.26.3
 
  If I set: run at startup
  orca run correctly.
 
 
  Hi Esteban,
 
  to clarify, you configure orca in some way so it runs when sugar
  starts up and it reads what is on the screen?
 
  Thanks,
 
  Tomeu
 
 
 
  If I excecute orca from Terminal, shows error:
  /usr/lib/python2.6/site-packages/orca/mouse_review.py:189: Warning:
  invalid
  uninstantiatable type `(null)' in cast to `GdkDisplayX11'
      self._mouseDwellTimeout(event.detail1, event.detail2)
 
  Displays Preferences dialog, but dont reads screen.
 
  Regards,
  Esteban Arias.
 
  2010/9/2 Tomeu Vizoso to...@sugarlabs.org
 
 
  On Wed, Sep 1, 2010 at 14:51, Esteban Arias ear...@plan.ceibal.edu.uy
  wrote:
 
 
  I install orca on xo 1.0 with gnome for f11.
  If I config to start session with orca, runs ok. But if I execute
  orca
  from
  terminal, dont run correctly:
 
 
  Hi Esteban,
 
  could be that your email arrived to us incomplete?
 
  Regards,
 
  Tomeu
 
 
 
  2010/9/1 pbrobin...@gmail.com pbrobin...@gmail.com
 
 
  On Wed, Sep 1, 2010 at 10:24 AM, Tomeu Vizoso to...@sugarlabs.org
  wrote:
 
 
  On Fri, Aug 20, 2010 at 14:10, Tomeu Vizoso to...@sugarlabs.org
  wrote:
 
 
  On Fri, Aug 20, 2010 at 14:08, Esteban Arias
  ear...@plan.ceibal.edu.uy wrote:
 
 
  hi,
  we can colaborate

[Sugar-devel] stepping down as maintainer

2010-10-19 Thread Tomeu Vizoso
Hi,

for personal reasons have to drastically reduce my involvement in the project.

Will be leaving maintenance of my modules and unsubscribing from the
mailing lists. My place on the board is vacant from now on and I'll be
adding to the wiki the new vacancies:
http://wiki.sugarlabs.org/go/Vacancies

Cheers and good luck,

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


[Sugar-devel] branching off sucrose-0.90

2010-10-15 Thread Tomeu Vizoso
Hi,

patches are accumulating as we wait for 0.90 branches in Pootle.

Anybody opposes to branching now in git?

I'm under the impression that this will mean that translators won't be
able to commit translations for 0.90 until such branches are created.

Sayamindu, do you think you could find some time to document how to
create branches in the Pootle backend?

Regards,

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


Re: [Sugar-devel] [PATCH] fix SL #2001 - Write does not pass parent window xid to ObjectChooser

2010-10-15 Thread Tomeu Vizoso
On Thu, Oct 14, 2010 at 20:09,  godi...@sugarlabs.org wrote:
 From: Gonzalo Odiard godi...@sugarlabs.org

 This is a regresion, probably introduced when changed the toolbar.
 May be pass self.abiword_canvas and self to ImageToolbar is not the smarter 
 option.

You are right, would be better if the activity listened to signals in
the toolbar and called methods on the canvas as a result.

But in this case, the toolbar can get a reference to the top level window with:

http://www.pygtk.org/docs/pygtk/class-gtkwidget.html#method-gtkwidget--get-toplevel

Btw, is Write maintained these days?

Regards,

Tomeu

 ---
  AbiWordActivity.py |    2 +-
  toolbar.py         |    5 +++--
  2 files changed, 4 insertions(+), 3 deletions(-)

 diff --git a/AbiWordActivity.py b/AbiWordActivity.py
 index f6c54fa..7deab8c 100644
 --- a/AbiWordActivity.py
 +++ b/AbiWordActivity.py
 @@ -110,7 +110,7 @@ class AbiWordActivity (activity.Activity):
         toolbar_box.toolbar.insert(list_toolbar, -1)

         insert_toolbar = ToolbarButton()
 -        insert_toolbar.props.page = InsertToolbar(self.abiword_canvas)
 +        insert_toolbar.props.page = InsertToolbar(self.abiword_canvas, self)
         insert_toolbar.props.icon_name = 'insert-table'
         insert_toolbar.props.label = _('Table')
         toolbar_box.toolbar.insert(insert_toolbar, -1)
 diff --git a/toolbar.py b/toolbar.py
 index 75243c7..a16803c 100644
 --- a/toolbar.py
 +++ b/toolbar.py
 @@ -176,10 +176,11 @@ class EditToolbar(gtk.Toolbar):
         tool_item.show()

  class InsertToolbar(gtk.Toolbar):
 -    def __init__(self, abiword_canvas):
 +    def __init__(self, abiword_canvas, parent):
         gtk.Toolbar.__init__(self)

         self._abiword_canvas = abiword_canvas
 +        self._parent = parent

         self._table = abiword.TableCreator()
         self._table.set_labels(_('Table'), _('Cancel'))
 @@ -234,7 +235,7 @@ class InsertToolbar(gtk.Toolbar):
         def cb(object):
             logging.debug('ObjectChooser: %r' % object)
             self._abiword_canvas.insert_image(object.file_path, True)
 -        chooser.pick(what=chooser.IMAGE, cb=cb)
 +        chooser.pick(parent=self._parent, what=chooser.IMAGE, cb=cb)

     def _table_cb(self, abi, rows, cols):
         self._abiword_canvas.insert_table(rows, cols)
 --
 1.7.2.3

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

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


Re: [Sugar-devel] [PATCH] fix SL #2001 - Write does not pass parent window xid to ObjectChooser

2010-10-15 Thread Tomeu Vizoso
On Fri, Oct 15, 2010 at 17:00, Gonzalo Odiard godi...@sugarlabs.org wrote:


 On Fri, Oct 15, 2010 at 8:36 AM, Tomeu Vizoso to...@sugarlabs.org wrote:

 On Thu, Oct 14, 2010 at 20:09,  godi...@sugarlabs.org wrote:
  From: Gonzalo Odiard godi...@sugarlabs.org
 
  This is a regresion, probably introduced when changed the toolbar.
  May be pass self.abiword_canvas and self to ImageToolbar is not the
  smarter option.

 You are right, would be better if the activity listened to signals in
 the toolbar and called methods on the canvas as a result.

 But in this case, the toolbar can get a reference to the top level window
 with:


 http://www.pygtk.org/docs/pygtk/class-gtkwidget.html#method-gtkwidget--get-toplevel


 Ok, i will redo the patch.


 Btw, is Write maintained these days?


 Good question :) You are one of the co-maintainers ;)
 http://wiki.sugarlabs.org/go/Development_Team/Release/Modules

I used to be just a peer until someone changed that page to say co-maintainer :)

Regards,

Tomeu

 Regards

 Gonzalo

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


Re: [Sugar-devel] [PATCH] Make sure the buddy palette is disposed after popdown #1742

2010-10-14 Thread Tomeu Vizoso
On Wed, Oct 13, 2010 at 18:29, Simon Schampijer si...@schampijer.de wrote:
 On 10/11/2010 11:35 AM, Tomeu Vizoso wrote:

 ---
  src/jarabe/view/buddyicon.py |    2 ++
  1 files changed, 2 insertions(+), 0 deletions(-)

 diff --git a/src/jarabe/view/buddyicon.py b/src/jarabe/view/buddyicon.py
 index 37b9167..15385bd 100644
 --- a/src/jarabe/view/buddyicon.py
 +++ b/src/jarabe/view/buddyicon.py
 @@ -28,6 +28,8 @@ class BuddyIcon(CanvasIcon):
          self._buddy.connect('notify::present',
 self.__buddy_notify_present_cb)
          self._buddy.connect('notify::color',
 self.__buddy_notify_color_cb)

 +        self.palette_invoker.transient = True
 +
          self._update_color()

      def create_palette(self):

 This does set it to transient for all the buddies palletes, as well the one
 from the owner. As the owner palette has no dynamic content I guess we don't
 need to.

It's no big deal, but I think we should stop caching as many palettes
as possible.

Regards,

Tomeu

 Regards,
   Simon
 ___
 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] [PATCH] Make sure the buddy palette is disposed after popdown #1742

2010-10-14 Thread Tomeu Vizoso
---
 src/jarabe/view/buddyicon.py |2 ++
 1 files changed, 2 insertions(+), 0 deletions(-)

diff --git a/src/jarabe/view/buddyicon.py b/src/jarabe/view/buddyicon.py
index 37b9167..332c0c8 100644
--- a/src/jarabe/view/buddyicon.py
+++ b/src/jarabe/view/buddyicon.py
@@ -28,6 +28,8 @@ class BuddyIcon(CanvasIcon):
 self._buddy.connect('notify::present', self.__buddy_notify_present_cb)
 self._buddy.connect('notify::color', self.__buddy_notify_color_cb)
 
+self.palette_invoker.cache_palette = False
+
 self._update_color()
 
 def create_palette(self):
-- 
1.7.2.3

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


[Sugar-devel] [PATCH] Add 'cache-palette' property to Invoker #1742

2010-10-14 Thread Tomeu Vizoso
Meaning that the palette will be cached after it's created.
---
 src/sugar/graphics/palette.py   |1 +
 src/sugar/graphics/palettewindow.py |   23 ---
 2 files changed, 21 insertions(+), 3 deletions(-)

diff --git a/src/sugar/graphics/palette.py b/src/sugar/graphics/palette.py
index d4632eb..d4f844c 100644
--- a/src/sugar/graphics/palette.py
+++ b/src/sugar/graphics/palette.py
@@ -158,6 +158,7 @@ class Palette(PaletteWindow):
 self.popdown(immediate=True)
 # Break the reference cycle. It looks like the gc is not able to free
 # it, possibly because gtk.Menu memory handling is very special.
+self.menu.disconnect_by_func(self.__menu_item_inserted_cb)
 self.menu = None
 
 def __show_cb(self, widget):
diff --git a/src/sugar/graphics/palettewindow.py 
b/src/sugar/graphics/palettewindow.py
index 22131c2..f51c938 100644
--- a/src/sugar/graphics/palettewindow.py
+++ b/src/sugar/graphics/palettewindow.py
@@ -179,6 +179,7 @@ class PaletteWindow(gtk.Window):
 
 def __destroy_cb(self, palette):
 self.set_group_id(None)
+self._mouse_detector.disconnect_by_func(self._mouse_slow_cb)
 
 def set_invoker(self, invoker):
 for hid in self._invoker_hids[:]:
@@ -457,6 +458,7 @@ class Invoker(gobject.GObject):
 self._cursor_x = -1
 self._cursor_y = -1
 self._palette = None
+self._cache_palette = True
 
 def attach(self, parent):
 self.parent = parent
@@ -639,18 +641,33 @@ class Invoker(gobject.GObject):
 def set_palette(self, palette):
 if self._palette is not None:
 self._palette.popdown(immediate=True)
-
-if self._palette:
 self._palette.props.invoker = None
+self._palette.destroy()
 
 self._palette = palette
 
-if self._palette:
+if self._palette is not None:
 self._palette.props.invoker = self
+self._palette.connect('popdown', self.__palette_popdown_cb)
 
 palette = gobject.property(
 type=object, setter=set_palette, getter=get_palette)
 
+def get_cache_palette(self):
+return self._cache_palette
+
+def set_cache_palette(self, cache_palette):
+self._cache_palette = cache_palette
+
+cache_palette = gobject.property(type=object, setter=set_cache_palette,
+ getter=get_cache_palette)
+Whether the invoker will cache the palette after its creation. Defaults
+to True.
+
+
+def __palette_popdown_cb(self, palette):
+if not self.props.cache_palette:
+self.set_palette(None)
 
 class WidgetInvoker(Invoker):
 
-- 
1.7.2.3

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


[Sugar-devel] [RELEASE] sugar-0.90.3

2010-10-14 Thread Tomeu Vizoso
== Source ==

http://download.sugarlabs.org/sources/sucrose/glucose/sugar/sugar-0.90.3.tar.bz2

== News ==

* Make sure the buddy palette is disposed after popdown #1742 (Tomeu Vizoso)
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


Re: [Sugar-devel] [PATCH] Title for 'Rectangular Marquee' tool changed to 'Select Area' (SL 2266)

2010-10-13 Thread Tomeu Vizoso
2010/10/12 Ayush Goyal ay...@seeta.in:
 From: Ayush Goyal ayush at seeta.in


 Signed-off-by: Ayush Goyal ayush at seeta.in
 ---
  po/Paint.pot |    2 +-
  po/af.po     |    2 +-
  po/am.po     |    2 +-
  po/ar.po     |    2 +-
  po/ay.po     |    2 +-
  po/bg.po     |    2 +-
  po/bi.po     |    2 +-
  po/bn.po     |    2 +-
  po/bn_IN.po  |    2 +-
  po/ca.po     |    2 +-
  po/cpp.po    |    2 +-
  po/cs.po     |    2 +-
  po/de.po     |    2 +-
  po/dz.po     |    2 +-
  po/el.po     |    2 +-
  po/en.po     |    2 +-
  po/es.po     |    2 +-
  po/fa.po     |    2 +-
  po/fa_AF.po  |    2 +-
  po/ff.po     |    2 +-
  po/fil.po    |    2 +-
  po/fr.po     |    2 +-
  po/gu.po     |    2 +-
  po/ha.po     |    2 +-
  po/he.po     |    2 +-
  po/hi.po     |    2 +-
  po/ht.po     |    2 +-
  po/hu.po     |    2 +-
  po/ig.po     |    2 +-
  po/is.po     |    2 +-
  po/it.po     |    2 +-
  po/ja.po     |    2 +-
  po/km.po     |    2 +-
  po/ko.po     |    2 +-
  po/ko_KO.po  |    2 +-
  po/kos.po    |    2 +-
  po/mg.po     |    2 +-
  po/mk.po     |    2 +-
  po/ml.po     |    2 +-
  po/mn.po     |    2 +-
  po/mr.po     |    2 +-
  po/ms.po     |    2 +-
  po/mvo.po    |    2 +-
  po/na.po     |    2 +-
  po/nb.po     |    2 +-
  po/ne.po     |    2 +-
  po/nl.po     |    2 +-
  po/pa.po     |    2 +-
  po/pap.po    |    2 +-
  po/pis.po    |    2 +-
  po/pl.po     |    2 +-
  po/ps.po     |    2 +-
  po/pseudo.po |    2 +-
  po/pt.po     |    2 +-
  po/pt_BR.po  |    2 +-
  po/qu.po     |    2 +-
  po/ro.po     |    2 +-
  po/ru.po     |    2 +-
  po/rw.po     |    2 +-
  po/sd.po     |    2 +-
  po/si.po     |    2 +-
  po/sk.po     |    2 +-
  po/sl.po     |    2 +-
  po/sq.po     |    2 +-
  po/sv.po     |    2 +-
  po/sw.po     |    2 +-
  po/ta.po     |    2 +-
  po/te.po     |    2 +-
  po/th.po     |    2 +-
  po/tpi.po    |    2 +-
  po/tr.po     |    2 +-
  po/tvl.po    |    2 +-
  po/tzo.po    |    2 +-
  po/ug.po     |    2 +-
  po/ur.po     |    2 +-
  po/vi.po     |    2 +-
  po/wa.po     |    2 +-
  po/yo.po     |    2 +-
  po/zh_CN.po  |    2 +-
  po/zh_TW.po  |    2 +-
  toolbox.py   |    2 +-

You should only need to change toolbox.py, the other files will be
updated when the maintainer makes a new release, or by Pootle.

Regards,

Tomeu

  81 files changed, 81 insertions(+), 81 deletions(-)

 diff --git a/po/Paint.pot b/po/Paint.pot
 index 6bbc6b4..f0d39df 100644
 --- a/po/Paint.pot
 +++ b/po/Paint.pot
 @@ -89,7 +89,7 @@ msgid Bucket
  msgstr 

  #: toolbox.py:365
 -msgid Rectangular Marquee
 +msgid Select Area
  msgstr 

  #: toolbox.py:417 toolbox.py:1049 toolbox.py:1412
 diff --git a/po/af.po b/po/af.po
 index 884b5f4..efc240b 100644
 --- a/po/af.po
 +++ b/po/af.po
 @@ -89,7 +89,7 @@ msgid Bucket
  msgstr 

  #: toolbox.py:365
 -msgid Rectangular Marquee
 +msgid Select Area
  msgstr 

  #: toolbox.py:417 toolbox.py:1049 toolbox.py:1412
 diff --git a/po/am.po b/po/am.po
 index 599b8e8..10dc4b7 100644
 --- a/po/am.po
 +++ b/po/am.po
 @@ -89,7 +89,7 @@ msgid Bucket
  msgstr 

  #: toolbox.py:365
 -msgid Rectangular Marquee
 +msgid Select Area
  msgstr 

  #: toolbox.py:417 toolbox.py:1049 toolbox.py:1412
 diff --git a/po/ar.po b/po/ar.po
 index d0d8609..2ae532d 100644
 --- a/po/ar.po
 +++ b/po/ar.po
 @@ -94,7 +94,7 @@ msgid Bucket
  msgstr محفظة

  #: toolbox.py:365
 -msgid Rectangular Marquee
 +msgid Select Area
  msgstr معلِّمة مربّعة

  #: toolbox.py:417 toolbox.py:1049 toolbox.py:1412
 diff --git a/po/ay.po b/po/ay.po
 index 599b8e8..10dc4b7 100644
 --- a/po/ay.po
 +++ b/po/ay.po
 @@ -89,7 +89,7 @@ msgid Bucket
  msgstr 

  #: toolbox.py:365
 -msgid Rectangular Marquee
 +msgid Select Area
  msgstr 

  #: toolbox.py:417 toolbox.py:1049 toolbox.py:1412
 diff --git a/po/bg.po b/po/bg.po
 index 7f45f15..ad8b3ae 100644
 --- a/po/bg.po
 +++ b/po/bg.po
 @@ -88,7 +88,7 @@ msgid Bucket
  msgstr Заливка

  #: toolbox.py:365
 -msgid Rectangular Marquee
 +msgid Select Area
  msgstr Правоъгълно маркиране

  #: toolbox.py:417 toolbox.py:1049 toolbox.py:1412
 diff --git a/po/bi.po b/po/bi.po
 index 884b5f4..efc240b 100644
 --- a/po/bi.po
 +++ b/po/bi.po
 @@ -89,7 +89,7 @@ msgid Bucket
  msgstr 

  #: toolbox.py:365
 -msgid Rectangular Marquee
 +msgid Select Area
  msgstr 

  #: toolbox.py:417 toolbox.py:1049 toolbox.py:1412
 diff --git a/po/bn.po b/po/bn.po
 index a163110..d6ac625 100644
 --- a/po/bn.po
 +++ b/po/bn.po
 @@ -88,7 +88,7 @@ msgid Bucket
  msgstr ঝুড়ি

  #: toolbox.py:365
 -msgid Rectangular Marquee
 +msgid Select Area
  msgstr চতুর্ভূজাকার মার্কিউই

  #: toolbox.py:417 toolbox.py:1049 toolbox.py:1412
 diff --git a/po/bn_IN.po b/po/bn_IN.po
 index 3af9f60..9cd9249 100644
 --- a/po/bn_IN.po
 +++ b/po/bn_IN.po
 @@ -90,7 +90,7 @@ msgid Bucket
  msgstr বাকেট

  #: toolbox.py:365
 -msgid Rectangular Marquee
 +msgid Select Area
  msgstr চতুর্ভূজাকার মার্কিউই

  #: toolbox.py:417 toolbox.py:1049 toolbox.py:1412
 diff --git a/po/ca.po b/po/ca.po
 index 175dc22..8585e5a 100644
 --- 

Re: [Sugar-devel] [PATCH] Keep aspect has been added in the Paint pot files (SL 2321)

2010-10-13 Thread Tomeu Vizoso
On Tue, Oct 12, 2010 at 20:05, SHACHI PAUL sha...@seeta.in wrote:
 The Keep aspect has now been added to the Paint pot files.

See http://en.wikipedia.org/wiki/GNU_gettext for an explanation of the
translation workflow. You should only need to modify the source code.

Regards,

Tomeu

 Signed-off-by: SHACHI PAUL sha...@seeta.in
 ---
  po/Paint.pot |    4 
  1 files changed, 4 insertions(+), 0 deletions(-)

 diff --git a/po/Paint.pot b/po/Paint.pot
 index 6bbc6b4..0ef3c2c 100644
 --- a/po/Paint.pot
 +++ b/po/Paint.pot
 @@ -116,6 +116,10 @@ msgstr 
  msgid Fill Color: 
  msgstr 

 +#: toolbox.py:531
 +msgid Keep aspect
 +msgstr 
 +
  #: toolbox.py:740
  msgid Fill Color
  msgstr 
 --
 1.7.0.4

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

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


Re: [Sugar-devel] [PATCH] add restart option configurable via gconf (#1206)

2010-10-13 Thread Tomeu Vizoso
On Tue, Oct 12, 2010 at 03:13, James Cameron qu...@laptop.org wrote:
 Nepal requested reordering and removal of restart, which was patched for
 them in 0.82 and implemented in 0.84.

 Paraguay and Uruguay detected the change in 0.84 and requested the
 restart option be restored.

 This patch restores the restart option as a configurable option, using
 the gconf key /desktop/sugar/show_restart, default true.

 Refer to http://bugs.sugarlabs.org/ticket/1206 for discussion.

Acked-by: Tomeu Vizoso tomeu.viz...@collabora.co.uk

But we cannot push it yet to master because we haven't branched yet.

We need someone to create the 0.90 branches in Pootle before we can
branch in git.

Regards,

Tomeu

 ---
  data/sugar.schemas.in        |   12 
  src/jarabe/view/buddymenu.py |    6 ++
  2 files changed, 18 insertions(+), 0 deletions(-)

 diff --git a/data/sugar.schemas.in b/data/sugar.schemas.in
 index cfa7edf..474753b 100644
 --- a/data/sugar.schemas.in
 +++ b/data/sugar.schemas.in
 @@ -192,6 +192,18 @@
     /schema

     schema
 +      key/schemas/desktop/sugar/show_restart/key
 +      applyto/desktop/sugar/show_restart/applyto
 +      ownersugar/owner
 +      typebool/type
 +      defaulttrue/default
 +      locale name=C
 +        shortShow Restart/short
 +        longIf TRUE, Sugar will show a Restart option./long
 +      /locale
 +    /schema
 +
 +    schema
       key/schemas/desktop/sugar/peripherals/keyboard/layouts/key
       applyto/desktop/sugar/peripherals/keyboard/layouts/applyto
       ownersugar/owner
 diff --git a/src/jarabe/view/buddymenu.py b/src/jarabe/view/buddymenu.py
 index 0ba6cc1..8ea2598 100644
 --- a/src/jarabe/view/buddymenu.py
 +++ b/src/jarabe/view/buddymenu.py
 @@ -86,6 +86,12 @@ class BuddyMenu(Palette):

         client = gconf.client_get_default()

 +        if client.get_bool('/desktop/sugar/show_restart'):
 +            item = MenuItem(_('Restart'), 'system-restart')
 +            item.connect('activate', self.__reboot_activate_cb)
 +            self.menu.append(item)
 +            item.show()
 +
         if client.get_bool('/desktop/sugar/show_logout'):
             item = MenuItem(_('Logout'), 'system-logout')
             item.connect('activate', self.__logout_activate_cb)
 --
 1.7.1

 --
 James Cameron
 http://quozl.linux.org.au/
 ___
 Sugar-devel mailing list
 Sugar-devel@lists.sugarlabs.org
 http://lists.sugarlabs.org/listinfo/sugar-devel

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


Re: [Sugar-devel] annotation support in abiword (was Fwd: uwog - r29358 - in abiword/trunk: . plugins/collab/backends/service/xp plugins/collab/core/packet/xp plugins/collab/core/plugin/xp plugins/col

2010-10-13 Thread Tomeu Vizoso
On Mon, Oct 11, 2010 at 14:51, Gary Martin garycmar...@googlemail.com wrote:
 Hi Tomeu,

 On 11 Oct 2010, at 09:25, Tomeu Vizoso to...@sugarlabs.org wrote:

 Hi,

 would be nice to add support for annotations in Write now that Abiword
 supports it.

 True, but only if you promise that the Write UI will get easier to use and 
 not more difficult ;) I think we're falling towards featureitus while not 
 managing complexity. Same thing is happening to Calculate.

When I give a talk about Sugar, one of its main features is Clarity.
The idea is to avoid saying simplicity because it may seem in
conflict with our goal of low floor, no ceiling.

I then explain that with clarity I mean that the features are layered
in such a way that it's clear to the user how to do what she wants to
do in each moment.

Regards,

Tomeu

 FWIW, in the Calculate case, I've been considering the need for a really 
 simple calculator activity called Sums, with a very minimal feature set**. 
 Perhaps we could do the same for Write and have a minimal feature set 
 activity called Note (or Text if you don't mind that modern verb usage)? It 
 would just be a simpler wrapper over the Abiword libs.

 Still not sure this is the right way to go to keep Sugar usable for our 
 younger learners (where I think Sugar is most ideally placed), as having 
 multiple Activities for the same activity does introduce additional 
 maintenance, and testing load.

 ** Ideally we should try harder to better layer complexity in the Write, 
 Calculate, et al UIs so that you need to drill down to the more complex 
 features while the common/novice features are exposed early at the top level 
 — but it seams there's only so far you can take this (Write and Calculate 
 being on the cusp of this cliff edge).

 Regards,
 --Gary

 Regards,

 Tomeu

 -- Forwarded message --
 From: J.M. Maurer u...@uwog.net
 Date: Sat, Oct 9, 2010 at 17:30
 Subject: Re: uwog - r29358 - in abiword/trunk: .
 plugins/collab/backends/service/xp plugins/collab/core/packet/xp
 plugins/collab/core/plugin/xp plugins/collab/core/session/xp
 plugins/opendocument plugins/opendocument/exp/xp
 plugins/opendocument/imp/xp src/af/gr/xp src/text/fmt/xp
 src/text/ptbl/xp src/wp/impexp/xp test/wp
 To: abiword-...@abisource.com


 Hi All!

 With this merge of Ben Martin's awesome work, AbiWord trunk (what will
 become AbiWord 2.9.0, the first 2.9 development release) has gained an
 awesome new feature: support for RDF. For those unfamiliar with RDF, you
 can read all about it on Wikipedia:

  http://en.wikipedia.org/wiki/Resource_Description_Framework

 It defines a metadata standard that AbiWord now supports. This means you
 can annotate pieces of content with generic metadata. For example you
 could attach contact data to a person who's name is mentioned in a text
 document.
 The use-cases are of course endless, so feel free to come up with cool
 use-cases, write patches, and we will gladly integrate them into AbiWord
 (or let you integrate them).

 A sample document containing RDF is attached. If you build AbiWord with
 debug support (--enable-debug) then you will find some fun RDF debugging
 menu items in the Collaborate menu (make sure to compile with
 --enable-plugins=collab). There is no particular reason why this in
 the Collaborate menu, it just had to go somewhere temporarily.

 There is full RDF support in AbiWord's internal model to hold the
 metadata. This work also supports reading and writing the metadata to
 AbiWord's native file format .abw and to OpenDocument .odt documents.
 Adding metadata to a document that is collaboratively being worked on
 will automatically synchronize the metadata as well.

 Surely there are certain bugs that need to be hashed out, but that's to
 be expected in a development release :)

 Cheers!
  Marc




 On Sat, 2010-10-09 at 17:06 +0200, c...@abisource.com wrote:
 Author: uwog
 Date: 2010-10-09 17:06:33 +0200 (Sat, 09 Oct 2010)
 New Revision: 29358

 Added:
    abiword/trunk/plugins/opendocument/exp/xp/ODe_RDFWriter.cpp
 [snip]
    abiword/trunk/src/wp/impexp/xp/ie_imp_XML.h
 Log:
 svn merge -r29073:29323 
 svn+ssh://svn.abisource.com/svnroot/abiword/branches/monkeyiqrdf/ .
 ___
 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] prerequisite skills for contributing code (was Re: [Dextrose] [PATCH v4 sugar] Pulsing icon delayed by 5 seconds or so SL#2080)

2010-10-13 Thread Tomeu Vizoso
On Tue, Oct 12, 2010 at 00:07, Bernie Innocenti ber...@codewiz.org wrote:
 On Mon, 2010-10-11 at 18:23 -0300, Gonzalo Odiard wrote:
 In my experience, it's easier start resolving tickets in activities
 than in the plataform.
 That worked for me:
 * start writing a new activity: you can do stupid things, while learn
 python and the interaction with the platform.
 * try t resolve easy tickets in activities: there are many in
 http://bugs.sugarlabs.org/ and http://dev.laptop.org/
 * next try to solve problems in Sugar.

 I completely agree with you.

This has been said several times to Seeta developers (and is valid for
everybody).

Manu, could you please explain what learning are doing Seeta
developers before they try to submit a contribution?

I'm under the strong impression that people are trying to play
football before learning to walk and this isn't helping nobody.

Thanks,

Tomeu

 --
   // 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 mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


Re: [Sugar-devel] A little change to www.sugarlabs.org

2010-10-13 Thread Tomeu Vizoso
[adding the IAEP, marketing and systems mailing lists]

On Mon, Oct 11, 2010 at 21:05,  nanon...@mediagala.com wrote:
Tomeu Vizoso wrote:
At least in not-ancient versions of Browse, popups open as new tabs.
 --




 Attached is the screen-shot that 400,000  children see in their own XO in
 Uruguay, using Browse v 101, when they want to download an Activity in
 SUGARLABS.ORG.

 Thks


 PAolo Benini
 Montevideo




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


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


Re: [Sugar-devel] changes in trac and others

2010-10-13 Thread Tomeu Vizoso
On Sat, Oct 9, 2010 at 08:46, Tabitha Roder tabi...@tabitha.net.nz wrote:
  What would be the difference between Owner and Developer then?


 I assumed that owner was the same as maintainer same as developer. Tom tells
 me that at his work the bug is assigned to an assignee or a team. In
 either case the team leader is officially the owner but often someone else
 takes on the owner duties that is not tracked. The other option at his
 work is cc list for those who want to know what happens.
 Language is complicated, and I speak English as a first language, must be
 hard for our friends who speak English as another language to work out what
 is going on with these titles.

Yes, all the webapps we use have different terms for the roles, I'm
afraid we cannot do much better than document it clearly in the wiki
or so unless we fork them.

Regards,

Tomeu

 Tabitha

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


Re: [Sugar-devel] prerequisite skills for contributing code (was Re: [Dextrose] [PATCH v4 sugar] Pulsing icon delayed by 5 seconds or so SL#2080)

2010-10-13 Thread Tomeu Vizoso
On Wed, Oct 13, 2010 at 11:59, Manusheel Gupta m...@seeta.in wrote:
 Tomeu,

 On Wed, Oct 13, 2010 at 2:18 PM, Tomeu Vizoso to...@sugarlabs.org wrote:

 On Tue, Oct 12, 2010 at 00:07, Bernie Innocenti ber...@codewiz.org
 wrote:
  On Mon, 2010-10-11 at 18:23 -0300, Gonzalo Odiard wrote:
  In my experience, it's easier start resolving tickets in activities
  than in the plataform.
  That worked for me:
  * start writing a new activity: you can do stupid things, while learn
  python and the interaction with the platform.
  * try t resolve easy tickets in activities: there are many in
  http://bugs.sugarlabs.org/ and http://dev.laptop.org/
  * next try to solve problems in Sugar.
 
  I completely agree with you.

 This has been said several times to Seeta developers (and is valid for
 everybody).

 Manu, could you please explain what learning are doing Seeta
 developers before they try to submit a contribution?

 Appreciate the feedback.
 Sure, SEETA developers are going through the following training and patch
 submission workflow -
 1. Revision/learning of Python, PyGTK skills through algorithms and
 programs;
 2. Studying Sugar manual, and getting familiar with using the emulator and
 jhbuild;
 3. James Simmon's guide on activity development (I do agree that this was
 not done for initial developers. But, every new developer is asked to study
 it);
 4. Patch workflow and documentation on code reviews;
 5. Asking the team members to go through certain patches accepted upstream,
 and submitted by Sascha, you and other team members;
 6. Assignment of bugs and initial discussion with Aleksey and Bernie;
 7. Submission of test patches in-house for peer review before submission to
 sugar-devel/dextrose/usr mailing lists;
 8. Final submission.
 Wish if you could provide feedback, and let us know if we are missing on any
 step.

If you provide links to the materials used in each step, people could
suggest additions, start a section in the wiki and maybe write a TODO
list of the material that needs to be added or improved.

Regards,

Tomeu

 Regards,
 Manu




 Thanks,

 Tomeu

  --
    // 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 mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


Re: [Sugar-devel] [Marketing] A little change to www.sugarlabs.org

2010-10-13 Thread Tomeu Vizoso
On Wed, Oct 13, 2010 at 12:57, Simon Schampijer si...@schampijer.de wrote:
 On 10/13/2010 10:49 AM, Tomeu Vizoso wrote:

 [adding the IAEP, marketing and systems mailing lists]

 Can someone that has access please just make this change. I already asked
 for that 1 or 2 years ago. Maybe the feedback from the field helps to
 actually make it happen.

Actually we already had feedback from the field more than a year ago:

http://lists.sugarlabs.org/archive/marketing/2009-April/000910.html

Regards,

Tomeu

 Regards,
   Simon

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


Re: [Sugar-devel] [PATCH] Title for 'Rectangular Marquee' tool changed to 'Select Area' (SL 2266)

2010-10-13 Thread Tomeu Vizoso
On Wed, Oct 13, 2010 at 13:44, Gonzalo Odiard godi...@gmail.com wrote:
 But in this case, the change is over a already translated text.
 The procedure is the same?

Yes, Pootle will generate a new .pot, will merge it into each existing
.po and will mark the changed strings as fuzzy so they get the
attention of translators.

Regards,

Tomeu

 Gonzalo

 You should only need to change toolbox.py, the other files will be
 updated when the maintainer makes a new release, or by Pootle.

 Regards,

 Tomeu

   #: toolbox.py:417 toolbox.py:1049 toolbox.py:1412
  diff --git a/toolbox.py b/toolbox.py
  index 90f664d..299181b 100644
  --- a/toolbox.py
  +++ b/toolbox.py
  @@ -434,7 +434,7 @@ class ToolsToolbar(gtk.Toolbar):
 
          
 
  -        self._tool_marquee_rectangular =
  DrawToolButton('tool-marquee-rectangular',activity.tool_group,_('Rectangular
  Marquee'))
  +        self._tool_marquee_rectangular =
  DrawToolButton('tool-marquee-rectangular',activity.tool_group,_('Select
  Area'))
          self.insert(self._tool_marquee_rectangular, -1)
          try:
              self._configure_palette(self._tool_marquee_rectangular,
  self._TOOL_MARQUEE_RECTANGULAR)
  --
  1.7.1
 
 
  ___
  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] Possible copyright infringement in activities.sl.o

2010-10-11 Thread Tomeu Vizoso
On Sat, Oct 9, 2010 at 15:09, Walter Bender walter.ben...@gmail.com wrote:
 On Sat, Oct 9, 2010 at 8:28 AM, Gabriel Eirea gei...@gmail.com wrote:
 Well, we have the same problem at ceibaljam.org.

 The thing is, these games are being uploaded by 13-yr old kids. They
 discovered how to package activities in two ways:

 1) using Pippy's export as .xo function. They download games from
 pygame.org and copy them at the right place in one of Pippy's
 generated xo files.

 2) using Flavio's flash wrapper
 (http://ceibaljam.org/drupal/sites/default/files/JAMactivityFlash.activity.xo).
 This simply requires putting swf files in a folder and zipping the xo
 file.

 I think it is a very interesting result, but I agree it is difficult
 to make them understand about licenses and such. We had to take down
 many projects from ceibaljam.org because of this. I contacted them and
 tried to explain the situation.

 ¿Anyone has any suggestion on how to proceed such that we don't
 discourage them to hack further?

 Maybe we should encourage them to set up their own hosting site and in
 the process establish their own guidelines for what they consider
 publishable. Having to be personally responsible for establishing such
 guidelines will be a great opportunity for them to learn. (In my
 experience it is often the case that when the children are in the
 position of establishing the rules, they end up with a very
 conservative framework.)

Sounds like a good idea, Google sites could work?

Regards,

Tomeu

 -walter

 Regards,

 Gabriel


 2010/10/9 Tim McNamara paperl...@timmcnamara.co.nz:
 Hi all,

 This morning, I tested juegos_flash-2. It's just a sample of free (no cost)
 flash games from the Internet. I don't think Sugar Labs is be allowed to
 distribute them.

 Apart from these legal concerns, I also have some ethical ones. The package
 includes a game that teaches users how to mix cocktails. Another one of the
 activities is called Smack your ex.

 Here are my raw notes from the session:

 ## juegos_flash-2
  - coloured icon
  - flash would wouldn't render the chess board at the start
  - seems to be a compilation of non-free flash games from various sites
  - gnash gave me English menus, everything else in Spanish

  - Penales
    - All rights reserved Flashfooty.com FTW
    - games failed to load after 20 secs

  - Penales2
   -  Games1.com Ad ??
   - in English
   - selecting a team didn't seem to do anything

  - EncontrarObjectos
    - failed to load in  20 secs on XO-1.5

  - Bar
    - Welcome to our pre-party cocktail mixing game for cocktail
  connoisseurs... or not as the case may be! - omg, it's actually
  a game about alcohol consumption
    - kinda cute, in it's own way. Provides instructions along the way,
  which is what I had expected from spirolaterals

  - Cocinarpizza
    - seemed unresponsive to the XO's mousepad

  - Ajedrez
    - argh, flashing chess game again

  - Futbal
    - ran very slowly
    - when missing a goal, the text is undefined

  - Tesoro
    - loaded well, a little slow on XO-1.5
    - teacher seemed to be silent

  - Pes2002
    - heavily screen flickering (gave up after 20sec)

  - Bolos
    - failed to load once Play was clicked

  - QueHariasConTuEx
    - from whackyourex.com
    - game does what it says



 Regards, Tim

 ___
 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




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

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


Re: [Sugar-devel] Status of Read activity (was: Re: Read Activity on Fedora 14 / SoaS v4)

2010-10-11 Thread Tomeu Vizoso
On Sat, Oct 9, 2010 at 15:01, Sascha Silbe
sascha-ml-reply-to-201...@silbe.org wrote:
 Excerpts from Lucian Branescu's message of Tue Sep 28 22:34:01 +0200 2010:

 Epub support is not complete, you can see epubs, but none of the
 toolbars work. [...]

 FWIW, I'd much rather see a working, but stripped-down Read upstream
 and in all distros than a working, stripped-down one in Fedora and a
 theoretically complete, but totally broken one everywhere else.

Totally agreed, it's fine to regress in some features if that is
needed in order to keep supporting the core features.

 Also, my work was on a somewhat old Read. I was hoping Read's
 maintainer would use my branch to port mainline, with whatever design
 for the epub view the maintainer considered a good idea.

 Who is the Read maintainer these days? AUTHORS still says Sayamindu,
 but AIUI he stopped working on Sugar stuff.

He still intends to keep involved as much as his studies allow, we
lost all contact for some weeks because of a technical issue.

That said, I think to remember he was looking for someone to take over
maintenance of Read.

Regards,

Tomeu

 Sascha

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

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


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


Re: [Sugar-devel] SL Bug #2063

2010-10-11 Thread Tomeu Vizoso
On Mon, Oct 11, 2010 at 09:57, Daniel Drake d...@laptop.org wrote:
 On 10 October 2010 20:14, Mukul Gupta mu...@seeta.in wrote:
 With reference to SL Bug # 2063 which deals with bringing some kind of
 notification alert whenever an unhandled python exception occurs, I had a
 few doubts. There are two approaches that I can think of.

 Neither of these sounds sensible.

 What's wrong with the obvious solution of popping up a dialog when the
 exception occurs?

 Technically the exceptions are not unhandled, if they were unhandled
 then sugar would crash. I guess we're referring to exceptions that are
 not handled gracefully and instead fall back to a catch-all handler
 which does not have the knowledge to act on them.

This is what abrt does with python (and other) processes, maybe we
could reuse it or at least steal some of the ideas:

https://fedorahosted.org/abrt/

Regards,

Tomeu


 Daniel
 ___
 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] annotation support in abiword (was Fwd: uwog - r29358 - in abiword/trunk: . plugins/collab/backends/service/xp plugins/collab/core/packet/xp plugins/collab/core/plugin/xp plugins/collab/

2010-10-11 Thread Tomeu Vizoso
Hi,

would be nice to add support for annotations in Write now that Abiword
supports it.

Regards,

Tomeu

-- Forwarded message --
From: J.M. Maurer u...@uwog.net
Date: Sat, Oct 9, 2010 at 17:30
Subject: Re: uwog - r29358 - in abiword/trunk: .
plugins/collab/backends/service/xp plugins/collab/core/packet/xp
plugins/collab/core/plugin/xp plugins/collab/core/session/xp
plugins/opendocument plugins/opendocument/exp/xp
plugins/opendocument/imp/xp src/af/gr/xp src/text/fmt/xp
src/text/ptbl/xp src/wp/impexp/xp test/wp
To: abiword-...@abisource.com


Hi All!

With this merge of Ben Martin's awesome work, AbiWord trunk (what will
become AbiWord 2.9.0, the first 2.9 development release) has gained an
awesome new feature: support for RDF. For those unfamiliar with RDF, you
can read all about it on Wikipedia:

 http://en.wikipedia.org/wiki/Resource_Description_Framework

It defines a metadata standard that AbiWord now supports. This means you
can annotate pieces of content with generic metadata. For example you
could attach contact data to a person who's name is mentioned in a text
document.
The use-cases are of course endless, so feel free to come up with cool
use-cases, write patches, and we will gladly integrate them into AbiWord
(or let you integrate them).

A sample document containing RDF is attached. If you build AbiWord with
debug support (--enable-debug) then you will find some fun RDF debugging
menu items in the Collaborate menu (make sure to compile with
--enable-plugins=collab). There is no particular reason why this in
the Collaborate menu, it just had to go somewhere temporarily.

There is full RDF support in AbiWord's internal model to hold the
metadata. This work also supports reading and writing the metadata to
AbiWord's native file format .abw and to OpenDocument .odt documents.
Adding metadata to a document that is collaboratively being worked on
will automatically synchronize the metadata as well.

Surely there are certain bugs that need to be hashed out, but that's to
be expected in a development release :)

Cheers!
 Marc




On Sat, 2010-10-09 at 17:06 +0200, c...@abisource.com wrote:
 Author: uwog
 Date: 2010-10-09 17:06:33 +0200 (Sat, 09 Oct 2010)
 New Revision: 29358

 Added:
    abiword/trunk/plugins/opendocument/exp/xp/ODe_RDFWriter.cpp
[snip]
    abiword/trunk/src/wp/impexp/xp/ie_imp_XML.h
 Log:
 svn merge -r29073:29323 
 svn+ssh://svn.abisource.com/svnroot/abiword/branches/monkeyiqrdf/ .
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


[Sugar-devel] [PATCH] Add 'transient' property to Invoker #1742

2010-10-11 Thread Tomeu Vizoso
Meaning that the palette will be disposed when it pops down.
---
 src/sugar/graphics/palette.py   |1 +
 src/sugar/graphics/palettewindow.py |   20 +---
 2 files changed, 18 insertions(+), 3 deletions(-)

diff --git a/src/sugar/graphics/palette.py b/src/sugar/graphics/palette.py
index d4632eb..d4f844c 100644
--- a/src/sugar/graphics/palette.py
+++ b/src/sugar/graphics/palette.py
@@ -158,6 +158,7 @@ class Palette(PaletteWindow):
 self.popdown(immediate=True)
 # Break the reference cycle. It looks like the gc is not able to free
 # it, possibly because gtk.Menu memory handling is very special.
+self.menu.disconnect_by_func(self.__menu_item_inserted_cb)
 self.menu = None
 
 def __show_cb(self, widget):
diff --git a/src/sugar/graphics/palettewindow.py 
b/src/sugar/graphics/palettewindow.py
index 22131c2..3c74662 100644
--- a/src/sugar/graphics/palettewindow.py
+++ b/src/sugar/graphics/palettewindow.py
@@ -179,6 +179,7 @@ class PaletteWindow(gtk.Window):
 
 def __destroy_cb(self, palette):
 self.set_group_id(None)
+self._mouse_detector.disconnect_by_func(self._mouse_slow_cb)
 
 def set_invoker(self, invoker):
 for hid in self._invoker_hids[:]:
@@ -457,6 +458,7 @@ class Invoker(gobject.GObject):
 self._cursor_x = -1
 self._cursor_y = -1
 self._palette = None
+self._transient = False
 
 def attach(self, parent):
 self.parent = parent
@@ -639,18 +641,30 @@ class Invoker(gobject.GObject):
 def set_palette(self, palette):
 if self._palette is not None:
 self._palette.popdown(immediate=True)
-
-if self._palette:
 self._palette.props.invoker = None
+self._palette.destroy()
 
 self._palette = palette
 
-if self._palette:
+if self._palette is not None:
 self._palette.props.invoker = self
+self._palette.connect('popdown', self.__palette_popdown_cb)
 
 palette = gobject.property(
 type=object, setter=set_palette, getter=get_palette)
 
+def get_transient(self):
+return self._transient
+
+def set_transient(self, transient):
+self._transient = transient
+
+transient = gobject.property(type=object, setter=set_transient,
+ getter=get_transient)
+
+def __palette_popdown_cb(self, palette):
+if self.props.transient:
+self.set_palette(None)
 
 class WidgetInvoker(Invoker):
 
-- 
1.7.2.3

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


[Sugar-devel] [PATCH] Make sure the buddy palette is disposed after popdown #1742

2010-10-11 Thread Tomeu Vizoso
---
 src/jarabe/view/buddyicon.py |2 ++
 1 files changed, 2 insertions(+), 0 deletions(-)

diff --git a/src/jarabe/view/buddyicon.py b/src/jarabe/view/buddyicon.py
index 37b9167..15385bd 100644
--- a/src/jarabe/view/buddyicon.py
+++ b/src/jarabe/view/buddyicon.py
@@ -28,6 +28,8 @@ class BuddyIcon(CanvasIcon):
 self._buddy.connect('notify::present', self.__buddy_notify_present_cb)
 self._buddy.connect('notify::color', self.__buddy_notify_color_cb)
 
+self.palette_invoker.transient = True
+
 self._update_color()
 
 def create_palette(self):
-- 
1.7.2.3

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


Re: [Sugar-devel] A little change to www.sugarlabs.org

2010-10-11 Thread Tomeu Vizoso
On Mon, Oct 11, 2010 at 16:21, Gonzalo Odiard gonz...@laptop.org wrote:
 Who can make a little change to the page www.sugarlabs.org?
 The links in the upper right zone (wiki / download / activities / donate)
 have a target=_blank attribute, and don't open in Browse.

Note that this has been reported before without much success, maybe
now we'll manage to change it.

At least in not-ancient versions of Browse, popups open as new tabs.

Regards,

Tomeu

 Regards

 Gonzalo

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


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


Re: [Sugar-devel] Memory leak in Sugar -- how to dump Py data structures?

2010-10-08 Thread Tomeu Vizoso
On Thu, Oct 7, 2010 at 22:01, Tim McNamara paperl...@timmcnamara.co.nz wrote:
 On 8 October 2010 03:34, Martin Langhoff martin.langh...@gmail.com wrote:

 See http://dev.laptop.org/ticket/10386 for details. The sugar-session
 process in 10.1.2 grows slowly...

 There's some form of leak somewhere. Maybe we are triggerin a real
 python leak, maybe we have reference loops. How do we trace this?

 This post seems pretty good [1]. It cites a tool that creates an object
 graph that visually represents what is happening in memory.[2]

 [1] http://www.lshift.net/blog/2008/11/14/tracing-python-memory-leaks
 [2] http://mg.pov.lt/blog/python-object-graphs.html

Those are good links, in this case I suspect those icons, or any other
object referenced inside a cycle that also contains an AP icon, are
listening for a signal in a longer-lived object, which prevents the
whole cycle to be freed. We need to either disconnect from that signal
when the icon is no longer needed, or use a weak reference.

I will be looking at a similar issue in the next few days but in 0.90,
I will know by then.

Regards,

Tomeu

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


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


Re: [Sugar-devel] changes in trac and others

2010-10-08 Thread Tomeu Vizoso
On Mon, Oct 4, 2010 at 19:49, Sascha Silbe
sascha-ml-reply-to-201...@silbe.org wrote:
 Excerpts from Frederick Grose's message of Mon Oct 04 18:09:18 +0200 2010:

 The SEETA Developer: field might better be adjusted to Developer:, and we
 could use a convention to tag the developer's name, such as, [SEETA] Ishan

 What would be the difference between Owner and Developer then?

My guess is that Seeta wants to track which of their developers may
work in a particular issue in the future, without actually taking
ownership of the issue. I interpret being the owner as I'm working on
this right now, so if you start working on it we may end up doing
duplicated work.

In any case, I think Seeta needs to explain what their intention was
with this change, and the other organizations that are as well putting
people to work on Sugar tickets are also welcome to do the same.

Regards,

Tomeu

 Sascha

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

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


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


Re: [Sugar-devel] Trac: added 1.0 milestone

2010-10-08 Thread Tomeu Vizoso
On Mon, Oct 4, 2010 at 14:10, Sascha Silbe
sascha-ml-reply-to-201...@silbe.org wrote:
 Hi!

 I just added a 1.0 milestone to Trac and used it for a ticket. The
 intended meaning is we should change (or at least look at) this before
 we declare the API 'stable' (whatever that means ;) ). If anyone has
 a better name for that milestone we can rename it.

Why a milestone and not a tag? The meaning we have been giving to
milestones doesn't seem to be exactly that.

Regards,

Tomeu

 Similarly, if we
 decided to call the next release (that would be 0.92) 1.0 because of
 the API break Gnome forced on us, we can rename it to 2.0.
 It's only meant to be used for things that affect API, especially
 activity API.

 Sascha

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

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


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


Re: [Sugar-devel] Freeing resources when switching away from activity (was: Re: [Bugs] #2413 UNSP: Hovering over the new activity toolbar activity icon so that sub toolbar appears triggers focus_out_e

2010-10-07 Thread Tomeu Vizoso
On Wed, Oct 6, 2010 at 20:51, Sascha Silbe
sascha-ml-reply-to-201...@silbe.org wrote:
 Excerpts from Sugar Labs Bugs's message of Wed Oct 06 18:16:49 UTC 2010:

  I decided to keep poking at this for Physics and there does seem to be an
  activity level fix. As per a long, long lost email from Tomeu (thanks
  Tomeu, only took me two years to re-investigate and take action). I'm
  connecting a callback to the visibility-notify-event and then testing if
  data.state == gtk.gdk.VISIBILITY_FULLY_OBSCURED. Took me ages to track
  this down, but seems to be working a treat, I'm about to test outside of
  my VM dev environment and onto an XO-1:

 FWIW, this is what I do in one of my activities (a simple digital wall
 clock):

 class BigDigiClockActivity(activity.Activity):

    def __init__(self, handle):
 [...]
        self.can_freeze = True
        self._freeze_scheduled = False
 [...]
        self.time_label.connect('size-allocate', self._size_allocate_cb)
        self._unmap_cb_handler = None
        self.time_label.connect('unmap-event', self._unmap_cb)
        self.set_canvas(self.time_label)
        self.time_label.show()

 [...]
    # for debug output only
    _vis_map = {
        gtk.gdk.VISIBILITY_UNOBSCURED: 'unobscured',
        gtk.gdk.VISIBILITY_PARTIAL: 'partial',
        gtk.gdk.VISIBILITY_FULLY_OBSCURED: 'fully obscured',
    }
    def _visibility_cb(self, widget, event, *args):
        X window has changed.
        logging.debug('visibility = %r', self._vis_map.get(event.state, 
 event.state))
        self._set_may_freeze(event.state == gtk.gdk.VISIBILITY_UNOBSCURED)

    def _unmap_cb(self, *args):
        X window has been unmapped (i.e. is invisible now).
        logging.debug('unmap')
        self._set_may_freeze(False)

    def _size_allocate_cb(self, widget, allocation, *args):
        Size for self.time_label has been (re)set.

        Recalculate font size if necessary.
 [...]
        if self._unmap_cb_handler is None:
            window = self.time_label.get_parent()
            self._unmap_cb_handler = window.connect('unmap-event',
                self._unmap_cb)
            window.connect('visibility-notify-event', self._visibility_cb)
            window.add_events(gtk.gdk.VISIBILITY_NOTIFY_MASK)

 [...]
    def _set_may_freeze(self, may_freeze):
        self._hide_cursor(may_freeze)
        self.may_freeze = may_freeze
        if may_freeze:
            self._schedule_freeze()
        else:
            self._set_dcon_freeze(False)


 For other activities there might be a better match than size-allocate
 for when to connect the callbacks to the window.

 Perhaps we could move some of this to sugar.activity.activity.Activity
 so activity authors could concentrate on the resource freeing part?
 Maybe even coupled with a timer to prevent us from slowing down quick
 activity switches (i.e. the user switching forth and back between two
 activities in quick succession).

Sounds like a very good idea to me.

Regards,

Tomeu

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

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


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


Re: [Sugar-devel] Ticket no #2210 words don't changed when language is changed

2010-10-07 Thread Tomeu Vizoso
On Thu, Oct 7, 2010 at 08:54, Ishan Bansal is...@seeta.in wrote:
 Hi

 I am working on the ticket http://bugs.sugarlabs.org/ticket/2210.

 To solve the above bug i am thinking of clearing the text in the text to be
 translate box when ever the language to be translated is being changed.
 Please provide suggestion on any better approach to deal with this bug.

 Please provide pointers on the following problems-

 1. Please explain me the code model, _iter = column.get_selected()

You should be able to find out by yourself, some references:

http://www.pygtk.org/pygtk2tutorial/index.html
http://www.pygtk.org/docs/pygtk/class-gtktreeselection.html#method-gtktreeselection--get-selected

Regards,

Tomeu

 2. How can i check when is the language to be translated is being changed.

 Regards

 ishan

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


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


Re: [Sugar-devel] Ticket no #2210 words don't changed when language is changed

2010-10-07 Thread Tomeu Vizoso
On Thu, Oct 7, 2010 at 20:08, David Farning dfarn...@gmail.com wrote:
 On Thu, Oct 7, 2010 at 1:54 AM, Ishan Bansal is...@seeta.in wrote:
 Hi

 I am working on the ticket http://bugs.sugarlabs.org/ticket/2210.

 To solve the above bug i am thinking of clearing the text in the text to be
 translate box when ever the language to be translated is being changed.
 Please provide suggestion on any better approach to deal with this bug.

 Over the last month this list has seen a significant increase in
 requests for pointers.

 Asking questions is an healthy part of learning, but asking for
 'pointers' is _not_ going to be particularly helpful.  It shifts the
 effort to the person answering the question rather then the person
 asking the question.  Effectively asking questions is an art.  Asking
 question is so important that Eric Raymond, author of the Cathedral
 and the Bazaar, has written and maintained an article about how to ask
 questions the smart way at
 http://www.catb.org/esr/faqs/smart-questions.html .

 I strongly suggest reading the article.  The time spent learning how
 to ask questions the smart way... and asking questions the smart way
 will pay for itself very quickly.  Questions asked the smart way will
 generally get quicker responses and better answers.

 Two additional points
  -- If you are new to the list please clearly describe 1) What you
 know, 2) What you don't know, 3) and what you think you have to learn
 to solve your problem.  This provides the person answering the
 question a sense of scope.

This is very well put, lately I have felt like I would need to explain
most I know about software engineering in order to give an useful
reply.

Regards,

Tomeu

 The answer someone provides is based on the
 knowledge and needs for the person asking the question.

 -- Answer as many questions as you ask.

 david


 Please provide pointers on the following problems-

 1. Please explain me the code model, _iter = column.get_selected()

 2. How can i check when is the language to be translated is being changed.

 Regards

 ishan

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


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

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


[Sugar-devel] multitouch on linux

2010-10-06 Thread Tomeu Vizoso
Hi,

this post makes very interesting points about multitouch UIs and its
implementation in X.

http://who-t.blogspot.com/2010/10/thoughts-on-linux-multitouch.html

Regards,

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


Re: [Sugar-devel] #1169 NORM: Drop down menus give no indication of their existence, also are too slow to load.

2010-10-05 Thread Tomeu Vizoso
On Sat, Oct 2, 2010 at 09:46, Shanjit Singh Jajmann
shan...@dev.seeta.in wrote:
 Hi,

 Appropriate changes have now been made to the issue and the patches have
 also been uploaded. Changes have been made as suggested by FGrose in his
 comment.

I see lots of related information in the bug tracker about this and
other proposals.

Can you make explicit why you have chosen to implement this particular solution?

Also, would be good to have a ticket for each issue that needs to be
addressed. Maybe we could have one for the general problem as
perceived by the user and then several subtickets for each of the
actions that can be taken to improve it.

For the others, please chime into this thread if you have any insight
on what the consensus is.

Thanks,

Tomeu

 Wish if the patch could be reviewed.


 Suggestions are welcome.


 regards
 Shan

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


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


Re: [Sugar-devel] Fwd: making patches and sending email using git-email

2010-10-05 Thread Tomeu Vizoso
On Sat, Oct 2, 2010 at 10:50, Sascha Silbe
sascha-ml-reply-to-201...@silbe.org wrote:
 Excerpts from Ishan Bansal's message of Fri Oct 01 19:58:23 +0200 2010:

 2. To do the git email configuration for your system refer to
 http://paste.ubuntu.com/488777/

Could we improve what we have in the wiki and refer people there?

I would add some more recommendations:

1. Introduce yourself to the community.
2. Don't leave questions without a reply.
3. Whenever you take a task that someone else was doing, mention it
explicitly so others aren't concerned about wasting efforts.
4. Ask when you don't understand.
5. Answer other people's questions when you can.

Regards,

Tomeu

 From there:

 17 git send-email --to sugar-devel@lists.sugarlabs.org patchname.patch

 FWIW, you don't need to create the patch (using format-patch) first,
 git-send-email can do that for you:

 git send-email HEAD^..HEAD

 You can configure the destination address so you don't need to specify
 it manually every time:

 git config sendemail.to sugar-devel sugar-devel@lists.sugarlabs.org

 You need to do this for each of the repositories you are working on
 (e.g. sugar + sugar-toolkit).

 Sascha

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

 ___
 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] coping with the traffic in sugar-devel (was Re: Replacing Illegal character ':' in username (SL #2152))

2010-10-05 Thread Tomeu Vizoso
On Sun, Oct 3, 2010 at 21:23, Bernie Innocenti ber...@codewiz.org wrote:
 If you want to ensure that I read a message intended for me, you'd
 better keep me on cc. I don't read every single post sent to
 sugar-devel.

What about marking in some way those incoming emails that belong to a
thread that has included the word 'bernie'?

There's also the option of just going through the subjects, read the
threads that look interesting then marking all of them as read when
finished.

I'm starting a new thread about this because I often hear from people
who have missed important developments because cannot cope with the
traffic.

I'm also on way more lists that I can read, but with a bit of
automatic labelling and organization I think I manage to miss little
of the relevant info.

Any other tips?

Regards,

Tomeu

 On Sun, 2010-10-03 at 00:12 +0530, Dipankar Patro wrote:
 I am currently facing some problem with XS setup. I downloaded the
 image and installed it on VMware. But that did not work.

 What failed exactly?


 Bernie,
 Since the school server setup may take up a day or two, I can
 definitely work on the bug #1976 in the meantime. I will send the
 patch as soon as it is ready and tested.

 Thanks. Please make sure that, in the default case when nothing is
 configured, the behavior on the XO-1 stays the same as before.


 Sascha,
 I agree with you, there should be ready-made Live CD kind of thing for
 XS. Just plug and test! :-)

 The current installation CD is supposed to perform an almost 100%
 automated installation.

 --
   // 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 mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


Re: [Sugar-devel] Pointers required for SL#1742 (after adding a friend the palette doesn't change) ,

2010-10-05 Thread Tomeu Vizoso
On Fri, Oct 1, 2010 at 20:06, Anurag Chowdhury anu...@seeta.in wrote:
 What I figured out for this bug is that the bug could be solved only if the
 shell service has a D-Bus API for buddies. Untill then even the present
 scenario of one time update during system restart has also been applied
 through a hack place in sync_friends () in the jarabe.model.friends.py
 module
 this bug will get wrapped itself when the said api for shell service will
 get designed
 then even this sync_friends function would be removed.

 But I would need some pointers on how to create this dbus api for the
 present scenario and how will that work through the process to solve this
 defect.

Replied in the ticket, I'm curious about why you have reached the
conclusion that D-Bus is needed.

Regards,

Tomeu

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


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


Re: [Sugar-devel] [PATCH] Bug #630:Modal Dialog Fix and Journal Memory Full Alert added

2010-10-05 Thread Tomeu Vizoso
On Fri, Sep 24, 2010 at 16:46, Mukul Gupta mu...@seeta.in wrote:
 Modal Dialog should be displayed only once at startup if free
 memory is less than 50MB but greater than 10MB. Instead, for every
 redundant Modal Dialog Display, an Alert in the Journal signifying
 Low Memory is displayed.But when free memory reaches a critical
 limit(ie. 10MB) Modal Dialog is displayed repeatedly asking the
 user to delete some data in the Journal along with an alert in the
 Journal

How can I know if this change is desired? The comments in #630 suggest
a different approach.

Or maybe you are addressing another issue instead of #630?

Regards,

Tomeu

 ---
  src/jarabe/journal/journalactivity.py |   22 ++
  1 files changed, 14 insertions(+), 8 deletions(-)

 diff --git a/src/jarabe/journal/journalactivity.py 
 b/src/jarabe/journal/journalactivity.py
 index 44cc018..aa4001b 100644
 --- a/src/jarabe/journal/journalactivity.py
 +++ b/src/jarabe/journal/journalactivity.py
 @@ -49,7 +49,7 @@ J_DBUS_SERVICE = 'org.laptop.Journal'
  J_DBUS_INTERFACE = 'org.laptop.Journal'
  J_DBUS_PATH = '/org/laptop/Journal'

 -_SPACE_TRESHOLD = 52428800
 +_SPACE_THRESHOLD = 52428800
  _BUNDLE_ID = 'org.laptop.JournalActivity'

  class JournalActivityDBusService(dbus.service.Object):
 @@ -116,7 +116,7 @@ class JournalActivity(Window):
         self._main_toolbox = None
         self._detail_toolbox = None
         self._volumes_toolbar = None
 -
 +       self.modal_already_shown=False
         self._setup_main_view()
         self._setup_secondary_view()

 @@ -139,7 +139,7 @@ class JournalActivity(Window):

         self._critical_space_alert = None
         self._check_available_space()
 -
 +
     def __volume_error_cb(self, gobject, message, severity):
         alert = ErrorAlert(title=severity, msg=message)
         alert.connect('response', self.__alert_response_cb)
 @@ -337,11 +337,17 @@ class JournalActivity(Window):
             return
         stat = os.statvfs(env.get_profile_path())
         free_space = stat[statvfs.F_BSIZE] * stat[statvfs.F_BAVAIL]
 -        if free_space  _SPACE_TRESHOLD:
 -            self._critical_space_alert = ModalAlert()
 -            self._critical_space_alert.connect('destroy',
 -                                               self.__alert_closed_cb)
 -            self._critical_space_alert.show()
 +       if free_space  _SPACE_THRESHOLD:
 +           if self.modal_already_shown==False or free_space  
 _SPACE_THRESHOLD/5:
 +               self._critical_space_alert = ModalAlert()
 +               self._critical_space_alert.connect('destroy',
 +                                                  self.__alert_closed_cb)
 +               self._critical_space_alert.show()
 +               self.modal_already_shown=True
 +               alert = ErrorAlert(title=Journal Almost Full, msg=Please 
 delete some data from journal)
 +               alert.connect('response', self.__alert_response_cb)
 +               self.add_alert(alert)
 +               alert.show()

     def __alert_closed_cb(self, data):
         self.show_main_view()
 --
 1.7.0.4

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

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


Re: [Sugar-devel] [PATCH v3 sugar] Run Sugar-Emulator in fullscreen by default if the screen is =800x600 (SL #2180)

2010-10-05 Thread Tomeu Vizoso
On Mon, Sep 27, 2010 at 20:35, Dipankar Patro dipan...@seeta.in wrote:
 Previously some bottom part of sugar emulator window was pushed out of 
 viewing area at 800x600 system resolution.
 The patch opens Sugar-emulator in fullscreen mode by default for resolutions 
 = 800x600 to avoid the above mentioned situation.

Thanks,

will push once we branch, please ping if I forget about it.

Regards,

Tomeu

 ---
  src/jarabe/util/emulator.py |    2 +-
  1 files changed, 1 insertions(+), 1 deletions(-)

 v2 was Reviewed-By Tomeu Vizoso to...@sugarlabs.org
 v2-v3 : Changed commit message for proper description of patch.

 diff --git a/src/jarabe/util/emulator.py b/src/jarabe/util/emulator.py
 index 6a43044..cc112c9 100644
 --- a/src/jarabe/util/emulator.py
 +++ b/src/jarabe/util/emulator.py
 @@ -42,7 +42,7 @@ def _run_xephyr(display, dpi, dimensions, fullscreen):
     screen_size = (gtk.gdk.screen_width(), gtk.gdk.screen_height())

     if (not dimensions) and (fullscreen is None) and \
 -       (screen_size  default_dimensions) :
 +       (screen_size = default_dimensions) :
         # no forced settings, screen too small = fit screen
         fullscreen = True
     elif (not dimensions) :
 --
 1.7.0.4

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

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


Re: [Sugar-devel] Fwd: making patches and sending email using git-email

2010-10-05 Thread Tomeu Vizoso
On Tue, Oct 5, 2010 at 11:09, Tomeu Vizoso to...@sugarlabs.org wrote:
 On Sat, Oct 2, 2010 at 10:50, Sascha Silbe
 sascha-ml-reply-to-201...@silbe.org wrote:
 Excerpts from Ishan Bansal's message of Fri Oct 01 19:58:23 +0200 2010:

 2. To do the git email configuration for your system refer to
 http://paste.ubuntu.com/488777/

 Could we improve what we have in the wiki and refer people there?

 I would add some more recommendations:

 1. Introduce yourself to the community.
 2. Don't leave questions without a reply.
 3. Whenever you take a task that someone else was doing, mention it
 explicitly so others aren't concerned about wasting efforts.
 4. Ask when you don't understand.
 5. Answer other people's questions when you can.

Just one more :)

6. Don't take things off-list unless it's a personal matter.

Well, the last:

7. Read all messages sent to the mailing list.

Regards,

Tomeu

 Regards,

 Tomeu

 From there:

 17 git send-email --to sugar-devel@lists.sugarlabs.org patchname.patch

 FWIW, you don't need to create the patch (using format-patch) first,
 git-send-email can do that for you:

 git send-email HEAD^..HEAD

 You can configure the destination address so you don't need to specify
 it manually every time:

 git config sendemail.to sugar-devel sugar-devel@lists.sugarlabs.org

 You need to do this for each of the repositories you are working on
 (e.g. sugar + sugar-toolkit).

 Sascha

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

 ___
 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] [PATCH] Fix running multiple instances of Browse by adapting to API changes #2404

2010-10-05 Thread Tomeu Vizoso
* sugar/presence/presenceservice.py: Specify the D-Bus interface when
  calling ActivityProperties.GetActivity
* sugar/activity/main.py: Set a default for the --invite option and
  make the create() D-Bus method accept a{sv} so we can pass the
  boolean value.
---
 src/sugar/activity/main.py|7 ---
 src/sugar/presence/presenceservice.py |6 +-
 2 files changed, 9 insertions(+), 4 deletions(-)

diff --git a/src/sugar/activity/main.py b/src/sugar/activity/main.py
index 3a3950d..c04257a 100644
--- a/src/sugar/activity/main.py
+++ b/src/sugar/activity/main.py
@@ -56,7 +56,7 @@ class SingleProcess(dbus.service.Object):
 object_path = get_single_process_path(name_service)
 dbus.service.Object.__init__(self, bus_name, object_path)
 
-@dbus.service.method(org.laptop.SingleProcess, in_signature=a{ss})
+@dbus.service.method(org.laptop.SingleProcess, in_signature=a{sv})
 def create(self, handle_dict):
 handle = activityhandle.create_from_dict(handle_dict)
 create_activity_instance(self.constructor, handle)
@@ -76,7 +76,7 @@ def main():
   action='store_true',
   help='start all the instances in the same process')
 parser.add_option('-i', '--invited', dest='invited',
-  action='store_true',
+  action='store_true', default=False,
   help='the activity is being launched for handling an '
'invite from the network')
 (options, args) = parser.parse_args()
@@ -146,7 +146,8 @@ def main():
 SingleProcess(service_name, activity_constructor)
 else:
 single_process = sessionbus.get_object(service_name, service_path)
-single_process.create(activity_handle.get_dict())
+single_process.create(activity_handle.get_dict(),
+  dbus_interface='org.laptop.SingleProcess')
 
 print 'Created %s in a single process.' % service_name
 sys.exit(0)
diff --git a/src/sugar/presence/presenceservice.py 
b/src/sugar/presence/presenceservice.py
index 862d6d0..51d8625 100644
--- a/src/sugar/presence/presenceservice.py
+++ b/src/sugar/presence/presenceservice.py
@@ -42,6 +42,8 @@ _logger = logging.getLogger('sugar.presence.presenceservice')
 ACCOUNT_MANAGER_SERVICE = 'org.freedesktop.Telepathy.AccountManager'
 ACCOUNT_MANAGER_PATH = '/org/freedesktop/Telepathy/AccountManager'
 
+CONN_INTERFACE_ACTIVITY_PROPERTIES = 'org.laptop.Telepathy.ActivityProperties'
+
 class PresenceService(gobject.GObject):
 Provides simplified access to the Telepathy framework to activities
 __gsignals__ = {
@@ -80,7 +82,9 @@ class PresenceService(gobject.GObject):
 continue
 logging.debug(Calling GetActivity on %s, account_path)
 try:
-room_handle = 
connection.connection.GetActivity(activity_id)
+room_handle = connection.connection.GetActivity(
+activity_id,
+dbus_interface=CONN_INTERFACE_ACTIVITY_PROPERTIES)
 except dbus.exceptions.DBusException, e:
 name = 'org.freedesktop.Telepathy.Error.NotAvailable'
 if e.get_dbus_name() == name:
-- 
1.7.2.3

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


Re: [Sugar-devel] any patches for 0.90.1?

2010-10-05 Thread Tomeu Vizoso
On Mon, Oct 4, 2010 at 21:05, Sascha Silbe
sascha-ml-reply-to-201...@silbe.org wrote:
 Excerpts from Tomeu Vizoso's message of Mon Oct 04 19:48:36 +0200 2010:

 Can submitters reply to their own messages for those that are intended
 to go in before we branch?

 This patch of mine is a bug fix and should go into 0.90.1:

 [sugar] fix recognition of JEBs outside of data store [1]

 These patches fix breakages on a HAL-free system (does F14 still ship
 HAL?):

 [sugar] battery frame device: replace HAL with UPower [2]
 [Read] don't break if HAL is not available [3]

We don't have tickets for any of these? I think at this point we
should be still focusing on fixing regressions. If they are
enhancements or fixes for things that had already been broken, then I
think they could land in 0.90 just after we make the first bugfix
release.

 If you'd like I can bump the threads, but maybe you like Patchwork
 even better. ;)

Actually, the value I saw in Patchwork was submitters (and others)
helping me manage my queue by assigning me patches to review, but that
doesn't seem going to happen :(

Regards,

Tomeu

 All other patches I posted are for 0.92.

 Sascha

 [1] https://patchwork.sugarlabs.org/patch/169/
 [2] https://patchwork.sugarlabs.org/patch/134/
 [3] https://patchwork.sugarlabs.org/patch/27/

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

 ___
 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] [RELEASE] sugar-0.90.2

2010-10-05 Thread Tomeu Vizoso
== Source ==

http://download.sugarlabs.org/sources/sucrose/glucose/sugar/sugar-0.90.2.tar.bz2

== News ==

* Don't emit buddy-removed if we don't know yet its contact-id #2402 (Tomeu 
Vizoso)
* Don't emit buddy-removed and activity-removed before they have announced 
#2401 (Tomeu Vizoso)
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


[Sugar-devel] changes in trac and others

2010-10-04 Thread Tomeu Vizoso
Hi,

have seen that recently some changes have been made to trac outside
the normal adding of users and components.

I would like to request that when making those changes, that the list
was notified, if the change is presumed uncontroversial. If the change
has a broader effect (such as adding a field), please ask in
sugar-devel first for opinions.

A change that I think can be made without asking first is the addition
of the 1.0 milestone, but I think we still need to agree on the
meaning of moving a ticket to that milestone.

The addition of Seeta-specific fields needs to be discussed before,
because we have other organizations working together in Sugar Labs and
some amount of coordination is needed.

Note that mentioning it in #sugar is not enough because not everybody
is always present and because the channel is not logged.

For other services, please notify the list as well when your changes
will affect the other people's work.

Regards,

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


[Sugar-devel] [PATCH] Don't emit buddy-removed if we don't know yet its contact-id #2402

2010-10-04 Thread Tomeu Vizoso
Otherwise the owner icon is removed from the neighborhood view
---
 src/jarabe/model/neighborhood.py |3 ++-
 1 files changed, 2 insertions(+), 1 deletions(-)

diff --git a/src/jarabe/model/neighborhood.py b/src/jarabe/model/neighborhood.py
index 478ee46..91dd059 100644
--- a/src/jarabe/model/neighborhood.py
+++ b/src/jarabe/model/neighborhood.py
@@ -283,7 +283,8 @@ class _Account(gobject.GObject):
 self.emit('connected')
 else:
 for contact_handle, contact_id in self._buddy_handles.items():
-self.emit('buddy-removed', contact_id)
+if contact_id is not None:
+self.emit('buddy-removed', contact_id)
 
 for room_handle, activity_id in self._activity_handles.items():
 self.emit('activity-removed', activity_id)
-- 
1.7.2.3

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


[Sugar-devel] [PATCH] Don't emit buddy-removed and activity-removed before they have announced #2401

2010-10-04 Thread Tomeu Vizoso
Otherwise we'll get some tracebacks from the listeners of those
signals because they still don't know about those buddies or activities.
---
 src/jarabe/model/neighborhood.py |8 ++--
 1 files changed, 6 insertions(+), 2 deletions(-)

diff --git a/src/jarabe/model/neighborhood.py b/src/jarabe/model/neighborhood.py
index ed23f7f..478ee46 100644
--- a/src/jarabe/model/neighborhood.py
+++ b/src/jarabe/model/neighborhood.py
@@ -858,7 +858,9 @@ class Neighborhood(gobject.GObject):
 
 buddy = self._buddies[contact_id]
 del self._buddies[contact_id]
-self.emit('buddy-removed', buddy)
+
+if buddy.props.key is not None:
+self.emit('buddy-removed', buddy)
 
 def __activity_added_cb(self, account, room_handle, activity_id):
 logging.debug('__activity_added_cb %r %r', room_handle, activity_id)
@@ -902,7 +904,9 @@ class Neighborhood(gobject.GObject):
 return
 activity = self._activities[activity_id]
 del self._activities[activity_id]
-self.emit('activity-removed', activity)
+
+if activity.props.bundle is not None:
+self.emit('activity-removed', activity)
 
 def __current_activity_updated_cb(self, account, contact_id, activity_id):
 logging.debug('__current_activity_updated_cb %r %r', contact_id,
-- 
1.7.2.3

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


[Sugar-devel] any patches for 0.90.1?

2010-10-04 Thread Tomeu Vizoso
Hi,

there are several patches awaiting commit and review, but I don't
think all of them are intended to go into 0.90.

Can submitters reply to their own messages for those that are intended
to go in before we branch?

Thanks,

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


Re: [Sugar-devel] [PATCH] Don't emit buddy-removed if we don't know yet its contact-id #2402

2010-10-04 Thread Tomeu Vizoso
On Mon, Oct 4, 2010 at 19:42, Tomeu Vizoso tomeu.viz...@collabora.co.uk wrote:
 Otherwise the owner icon is removed from the neighborhood view

Requesting inclusion in 0.90.

Thanks,

Tomeu

 ---
  src/jarabe/model/neighborhood.py |    3 ++-
  1 files changed, 2 insertions(+), 1 deletions(-)

 diff --git a/src/jarabe/model/neighborhood.py 
 b/src/jarabe/model/neighborhood.py
 index 478ee46..91dd059 100644
 --- a/src/jarabe/model/neighborhood.py
 +++ b/src/jarabe/model/neighborhood.py
 @@ -283,7 +283,8 @@ class _Account(gobject.GObject):
             self.emit('connected')
         else:
             for contact_handle, contact_id in self._buddy_handles.items():
 -                self.emit('buddy-removed', contact_id)
 +                if contact_id is not None:
 +                    self.emit('buddy-removed', contact_id)

             for room_handle, activity_id in self._activity_handles.items():
                 self.emit('activity-removed', activity_id)
 --
 1.7.2.3

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

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


Re: [Sugar-devel] [PATCH] Don't emit buddy-removed and activity-removed before they have announced #2401

2010-10-04 Thread Tomeu Vizoso
On Mon, Oct 4, 2010 at 19:44, Tomeu Vizoso tomeu.viz...@collabora.co.uk wrote:
 Otherwise we'll get some tracebacks from the listeners of those
 signals because they still don't know about those buddies or activities.

Requesting inclusion in 0.90.

Thanks,

Tomeu

 ---
  src/jarabe/model/neighborhood.py |    8 ++--
  1 files changed, 6 insertions(+), 2 deletions(-)

 diff --git a/src/jarabe/model/neighborhood.py 
 b/src/jarabe/model/neighborhood.py
 index ed23f7f..478ee46 100644
 --- a/src/jarabe/model/neighborhood.py
 +++ b/src/jarabe/model/neighborhood.py
 @@ -858,7 +858,9 @@ class Neighborhood(gobject.GObject):

         buddy = self._buddies[contact_id]
         del self._buddies[contact_id]
 -        self.emit('buddy-removed', buddy)
 +
 +        if buddy.props.key is not None:
 +            self.emit('buddy-removed', buddy)

     def __activity_added_cb(self, account, room_handle, activity_id):
         logging.debug('__activity_added_cb %r %r', room_handle, activity_id)
 @@ -902,7 +904,9 @@ class Neighborhood(gobject.GObject):
             return
         activity = self._activities[activity_id]
         del self._activities[activity_id]
 -        self.emit('activity-removed', activity)
 +
 +        if activity.props.bundle is not None:
 +            self.emit('activity-removed', activity)

     def __current_activity_updated_cb(self, account, contact_id, activity_id):
         logging.debug('__current_activity_updated_cb %r %r', contact_id,
 --
 1.7.2.3

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

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


Re: [Sugar-devel] #2389 resolution set to notsugar, fixed upstream

2010-10-01 Thread Tomeu Vizoso
On Thu, Sep 30, 2010 at 18:25, Simon Schampijer si...@schampijer.de wrote:
 Hi,

 is that the first sign [1] that Killing the PS was the right choice? :)

Could be, let's see :)

Regards,

Tomeu

 Regards,
    Simon

 [1] http://bugs.sugarlabs.org/ticket/2389#comment:2
 ___
 Sugar-devel mailing list
 Sugar-devel@lists.sugarlabs.org
 http://lists.sugarlabs.org/listinfo/sugar-devel

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


Re: [Sugar-devel] favorite_activities bug or feature?

2010-10-01 Thread Tomeu Vizoso
On Thu, Sep 30, 2010 at 19:13, Gonzalo Odiard gonz...@laptop.org wrote:
 When I update a activity present in the favorite_activities file, in the
 file appears a new line with the activity and the new version number.
 I have tested it in 0.84 and sugar-jhbuild.
 I think it is a bug, but there any reason for this?

Part of the activity mechanisms can deal with several versions of an
activity installed at the same time. There was the intention to
support that in the UI as well, but a blocker was found with the
activity version not being transmitted across the network when
advertising an activity or inviting.

Regards,

Tomeu

 Thanks

 Gonzalo


 ___
 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] [RELEASE] Image Viewer-15

2010-09-30 Thread Tomeu Vizoso
== Source ==

http://download.sugarlabs.org/sources/sucrose/fructose/Image 
Viewer/ImageViewer-15.tar.bz2

== News ==

* Release 15 (Tomeu Vizoso)
* Commit from Sugar Labs: Translation System by user mschlager.: 11 of 11 
messages translated (0 fuzzy). (Pootle daemon)
* Commit from Sugar Labs: Translation System by user thangam.ar...@gmail.com.: 
11 of 11 messages translated (0 fuzzy). (Pootle daemon)
* Commit from Sugar Labs: Translation System by user Myckel.: 11 of 11 messages 
translated (0 fuzzy). (Pootle daemon)
* Commit from Sugar Labs: Translation System by user anderson861.: 11 of 12 
messages translated (0 fuzzy). (Pootle daemon)
* Commit from Sugar Labs: Translation System by user mschlager.: 11 of 11 
messages translated (0 fuzzy). (Pootle daemon)
* Commit from Sugar Labs: Translation System by user mschlager.: 11 of 11 
messages translated (0 fuzzy). (Pootle daemon)
* Commit from Sugar Labs: Translation System by user carlo.: 11 of 11 messages 
translated (0 fuzzy). (Pootle daemon)
* Commit from Sugar Labs: Translation System by user cjl.: 11 of 11 messages 
translated (0 fuzzy). (Pootle daemon)
* Commit from Sugar Labs: Translation System by user carlo.: 11 of 11 messages 
translated (0 fuzzy). (Pootle daemon)
* Commit from Sugar Labs: Translation System by user sayamindu.: 11 of 11 
messages translated (0 fuzzy). (Pootle daemon)
* Commit from Sugar Labs: Translation System by user YuanChao.: 11 of 11 
messages translated (0 fuzzy). (Pootle daemon)
* Commit from Sugar Labs: Translation System by user korakurider.: 11 of 11 
messages translated (0 fuzzy). (Pootle daemon)
* Commit from Sugar Labs: Translation System by user sayamindu.: 11 of 11 
messages translated (0 fuzzy). (Pootle daemon)
* Adding language tvl via Pootle (Pootle daemon)
* Adding language fil via Pootle (Pootle daemon)
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


Re: [Sugar-devel] [Systems] updating pootle and creating branches

2010-09-29 Thread Tomeu Vizoso
On Wed, Sep 29, 2010 at 08:37, Bernie Innocenti ber...@codewiz.org wrote:
 On 09/28/10 18:21, Tomeu Vizoso wrote:
 On Tue, Sep 28, 2010 at 15:43, Sayamindu Dasgupta sayami...@gmail.com 
 wrote:
 On Tue, Sep 28, 2010 at 9:17 AM, Tomeu Vizoso to...@sugarlabs.org wrote:
 On Tue, Sep 28, 2010 at 15:07, Chris Leonard cjlhomeaddr...@gmail.com 
 wrote:
 Bernie,

 I will continue to to the work I do as a Pootle admin (as time allows), 
 but
 as we've discussed before, we need someone from the Systems group to 
 handle
 back-end things like project versioning and git connections.  I do what I
 can via the Pootle administrative interface, but that is limited to adding
 new language admins, new language set up, adding existing projects to new
 languages, and the like.

 That's great, I'm now working on fixing pushing to git and then will
 do branches. Will try to write down processes for the next admin.


 Hi guys,
 Apologies for disappearing. Here are the details you may require:
 Documentation of the helper scripts:
 http://git.sugarlabs.org/projects/pootle-helpers/repos/mainline/blobs/master/README
 Updater stuff (look at the cronjobs for Pootle - they ensure the VCS
 stuff remain in sync).
 SSH keys (/var/lib/pootle/.ssh)
 Let me know if you need any more help.
 If it makes sense - I can participate in a Skype/IRC meeting to guide
 you through the process.

 Can you check when you have time if what I added to the wiki is true
 and if there's any big omission?

 http://wiki.sugarlabs.org/go/Service/translate#Notes

 Thanks for writing this excellent documentation.

 I added an administrative contact translate AT sugarlabs DOT org. It
 forwards to sayamindu, cjl, tomeu and bernie.

 There's also pootle AT sugarlabs DOT org, which seems to be used for
 bounces of email sent out by pootle.

 If you want, I could route pootle's cron output to one of these in
 addition to systems-logs. In case of trouble, it may send you plenty of
 spam.

I would be interested in getting those for a short period from now.

Thanks,

Tomeu


 --
   // 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] [Localization] 0.90 localization

2010-09-29 Thread Tomeu Vizoso
On Tue, Sep 28, 2010 at 20:34, Chris Leonard cjlhomeaddr...@gmail.com wrote:


 On Tue, Sep 28, 2010 at 12:59 PM, Tomeu Vizoso to...@sugarlabs.org wrote:


 Ok, what was happening is that Walter was checking the Spanish .po for
 TurtleArt and it had not been merged from the templates.

 Language administrators need to do so from time to time by clicking
 the update the files from templates link in the Files tab.

 Btw, do we have documented somewhere what language admins need to do?



 There is a page that needs some improvement and updating that would be the
 appropriate place to document the update templates task for lang admins.

 http://wiki.sugarlabs.org/go/Translation_Team/Administration_QuickStart

Have added this section:

http://wiki.sugarlabs.org/go/Translation_Team/Administration_QuickStart#Catching_up_with_new_strings_to_translate

Would be good if language admins could do what is said there so they
get the latest strings from 0.90.

And also, if someone could double check that what is said is true and
cannot cause harm.

Regards,

Tomeu



 cjl

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


Re: [Sugar-devel] Queries regarding Sugar Sharp assembly on Mono

2010-09-28 Thread Tomeu Vizoso
On Tue, Sep 28, 2010 at 02:57, Harpreet Sareen author.blog...@gmail.com wrote:
 Hi,
 Thanks for the reply. I have quite a bit of experience in Windows
 development and I specifically wanted to use C# to open the entrances for
 everyone to contribute in for the OLPC. Although the hardest part is done, I
 would like to know about how can I add the core features of collaboration in
 developing activities by C#. Please guide me along the process.

I agree with what Bert said. If you really want to create a framework
that makes easier developing activities with C# and are ready to make
the effort required, then you will need to slowly learn the basics and
go up step by step.

A good starting point is to follow these tutorials/guides:

http://en.flossmanuals.net/ActivitiesGuideSugar
http://dbus.freedesktop.org/doc/dbus-tutorial.html
http://www.ndesk.org/DBus_Documentation

You will also need to be willing to read quite a bit of Python and C code.

Regards,

Tomeu

 Thanks
 --Harpreet

 On Tue, Sep 28, 2010 at 12:19 AM, Bert Freudenberg b...@freudenbergs.de
 wrote:

 On 27.09.2010, at 20:05, Harpreet Sareen wrote:

 Hi Tomeu,

 You can access the Telepathy API through DBus# and the Telepathy DBus
  spec:
 
 http://www.ndesk.org/DBusSharp
 http://telepathy.freedesktop.org/spec/
 

 Thanks for your response. I came to know about developing activities for
 Sugar throug C# from this link.
 http://www.codeproject.com/KB/cross-platform/monosugar.aspx?display=Print
 I am not a pro developer. Is there a tutorial available on how to use the
 telepathy API for mesh networking in my activity as it is normally available
 for Python etc. while developing an activity. I would be obliged for the
 same.

 They are normal Gtk widgets, you can see how to construct them in the
 sugar-toolkit code:
 

  http://git.sugarlabs.org/projects/sugar-toolkit/repos/mainline/blobs/master/src/sugar/activity/widgets.py#line326

 I am sorry I didn't refer to using C# here. How can I make the Activity
 Toolbar or these widgets in my activity using C#?

 3) I want to use the Text to Speech mechanism in my activity similar to
  eSpeak. How's that done in Mono?I think you have two options:
  
 - DBus# to interface with speech-dispatcher
 - http://wiki.sugarlabs.org/go/Activity_Team/gst-plugins-espeak

 Since I am a new learner, I would really appreciate a sample or a tutorial
 on how do the same(using C# here).
 I would be really indebted for help. Thanks a lot!

 If you are just learning to program, writing your Sugar activity in Python
 would save you loads of trouble.
 It is possible to write an activity in any language (I know, because I did
 it) but you do have to be proficient in the language you want to use, and be
 able to map general advice into working code.
 For C#, the framework that Lionel's tutorial describes already goes a long
 way, the hardest part is done. But extending it to fully support a
 Sugar-like GUI and collaboration is going to be your problem, since you are
 one of the very few (if not the only one) who want to write an activity in
 C#.
 - Bert -


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



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


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


Re: [Sugar-devel] Mesh networking not working in my XO's

2010-09-28 Thread Tomeu Vizoso
On Tue, Sep 28, 2010 at 04:13, Harpreet Sareen author.blog...@gmail.com wrote:
 Hi,
 I have tow XO laptops (XO 1 and XO 1.5) which I want to connect together
 through mesh networking. I currently don't use WiFi hotspot/Access
 Point/Wired Network for the internet rather 3G EVDO. So, unfortunately, I
 cannot connect both these XO's through the XO -- AP -- XO. I had to consider
 the XO -- XO mesh for networking.
 XO 1 shows only one dot in the Neighbourhood named as olpc-mesh and XO 1.5
 shows three dots namely, MeshNetwork1, MeshNetwork6 and MeshNetwork11
 in the Neighbourhood. I tried sharing the Record activity between the XO's
 by starting the activity on XO 1.5 but XO 1.5 is not discovered in the
 neighbourhood of XO 1.0.
 What could be the problem or how it could be troubleshooted? Why isn't the
 laptop being discovered int the neghbourhood?

First thing you need to do is to say which OS versions you are running
on each machine.

Regards,

Tomeu

 Regards
 Harpreet
 ___
 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] updating pootle and creating branches

2010-09-28 Thread Tomeu Vizoso
Hi,

time is getting tight and we need to release 0.90.0 and branch so
development can continue.

Can we put together in this thread all the knowledge we have available
about how to do that? Links to the wiki are best, but anything will be
useful.

To be specific, what we need to do is:

- update the Glucose and Fructose projects by pulling from git,
- create Glucose and Fructose branches for 0.86, 0.88 and 0.90.

One of the most urgent things is getting shell access to
translate.sugarlabs.org, can someone add my public ssh key to it?

Thanks,

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


Re: [Sugar-devel] updating pootle and creating branches

2010-09-28 Thread Tomeu Vizoso
On Tue, Sep 28, 2010 at 10:12, Tomeu Vizoso to...@sugarlabs.org wrote:
 Hi,

 time is getting tight and we need to release 0.90.0 and branch so
 development can continue.

 Can we put together in this thread all the knowledge we have available
 about how to do that? Links to the wiki are best, but anything will be
 useful.

 To be specific, what we need to do is:

 - update the Glucose and Fructose projects by pulling from git,

Looks like the git checkouts were almost up to date. What remained to
be done was regenerating the .pot files and having each language
update their templates.

Will be updating the wiki with what I discover.

 - create Glucose and Fructose branches for 0.86, 0.88 and 0.90.

 One of the most urgent things is getting shell access to
 translate.sugarlabs.org, can someone add my public ssh key to it?

Bernie has given me all required access to the server.

Thanks,

Tomeu

 Thanks,

 Tomeu

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


Re: [Sugar-devel] Introduction

2010-09-28 Thread Tomeu Vizoso
On Tue, Sep 28, 2010 at 12:46, Steven Parrish smparr...@gmail.com wrote:
 Some of you may have already heard that I have accepted a position
 with ActivityCentral to be the project manager for Dextrose.  It feels
 like I have come full circle as I started out as a volunteer
 maintaining the F11 for the XO-1 builds for the past 18 months.
 That work was very rewarding and I was glad to see OLPC step in and
 release official builds based on my work.  The F11 for the XO-1 was
 also a starting point for the original Dextrose system, which Bernie
 Innocenti brought to fruition.

 Now we will be taking the original Dextrose and expanding upon it.
 Dextrose2 will be the result.  Based on Fedora11 and Sugar 0.88 it
 will strive for stability, while providing deployments with a
 customizable product.  I have already started creating builds for the
 new system with additional language support, and they can be found at
 http://wiki.sugarlabs.org/go/Dextrose .  The builds will be for both
 the XO-1 and XO-1.5 and will be available both with Gnome and without.

 We have a team of developers at SEETA who will be working on this with
 us.  Many of them are already known to the community and more will
 become known as they join the effort.

 I have already started going over the outstanding issues and know that
 with everyone's help we can make Dextrose the Premier system for XO
 deployments.

 The issues that need to be worked on can be found at:

 http://bugs.sugarlabs.org/query?status=acceptedstatus=assignedstatus=newstatus=reopenedorder=prioritycol=idcol=summarycol=statuscol=typecol=prioritycol=milestonecol=componentkeywords=$love

 and

 http://bugs.sugarlabs.org/query?status=acceptedstatus=assignedstatus=newstatus=reopenedorder=prioritycol=idcol=summarycol=componentcol=statuscol=typecol=prioritycol=milestonekeywords=$extrose

 If you are already working on any of these tickets please send me a
 quick note as to which tickets you are working on and what the status
 is.

 I look forward to working with everyone.

I'm very happy to read this, look forward to work further with you.

It would be very helpful if any new contributors could take the time
to present themselves and their plans as you have done.

Regards,

Tomeu

 Steven Parrish
 smparr...@gmail.com
 ___
 Sugar-devel mailing list
 Sugar-devel@lists.sugarlabs.org
 http://lists.sugarlabs.org/listinfo/sugar-devel

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


Re: [Sugar-devel] Queries regarding Sugar Sharp assembly on Mono

2010-09-28 Thread Tomeu Vizoso
On Tue, Sep 28, 2010 at 13:55, Harpreet Sareen author.blog...@gmail.com wrote:
 The Sugar-Sharp assembly doesn't include today the binding for the Telepathy
 Framework so we can't communicate with Sugar for networking operation.

If you have DBus bindings, you can use the whole Telepathy framework.

 By the way, there is already a Telepathy-Sharp that exists here: Link.
 If somebody already has used Telepathy sharp earlier and/or knows about the
 working of Telepathy and how it is interoperable with Sugar, then the person
 could integrate TelepathySharp in his project and do the right call to
 communicate with Sugar.

I have heard that TelepathySharp is pretty much incomplete and
unmaintained and that it's better to use Telepathy via DBus.

Regards,

Tomeu


 Regards
 Harpreet

 On Tue, Sep 28, 2010 at 5:05 PM, Harpreet Sareen author.blog...@gmail.com
 wrote:

 Hi,

 No problem. I'll get back with more specific queries related to C#
 activities.
 Thanks for the links!

 Regards
 Harpreet

 On Tue, Sep 28, 2010 at 12:57 PM, Tomeu Vizoso to...@sugarlabs.org
 wrote:

 On Tue, Sep 28, 2010 at 02:57, Harpreet Sareen author.blog...@gmail.com
 wrote:
  Hi,
  Thanks for the reply. I have quite a bit of experience in Windows
  development and I specifically wanted to use C# to open the entrances
  for
  everyone to contribute in for the OLPC. Although the hardest part is
  done, I
  would like to know about how can I add the core features of
  collaboration in
  developing activities by C#. Please guide me along the process.

 I agree with what Bert said. If you really want to create a framework
 that makes easier developing activities with C# and are ready to make
 the effort required, then you will need to slowly learn the basics and
 go up step by step.

 A good starting point is to follow these tutorials/guides:

 http://en.flossmanuals.net/ActivitiesGuideSugar
 http://dbus.freedesktop.org/doc/dbus-tutorial.html
 http://www.ndesk.org/DBus_Documentation

 You will also need to be willing to read quite a bit of Python and C
 code.

 Regards,

 Tomeu

  Thanks
  --Harpreet
 
  On Tue, Sep 28, 2010 at 12:19 AM, Bert Freudenberg
  b...@freudenbergs.de
  wrote:
 
  On 27.09.2010, at 20:05, Harpreet Sareen wrote:
 
  Hi Tomeu,
 
  You can access the Telepathy API through DBus# and the Telepathy
   DBus
   spec:
  
  http://www.ndesk.org/DBusSharp
  http://telepathy.freedesktop.org/spec/
  
 
  Thanks for your response. I came to know about developing activities
  for
  Sugar throug C# from this link.
 
  http://www.codeproject.com/KB/cross-platform/monosugar.aspx?display=Print
  I am not a pro developer. Is there a tutorial available on how to use
  the
  telepathy API for mesh networking in my activity as it is normally
  available
  for Python etc. while developing an activity. I would be obliged for
  the
  same.
 
  They are normal Gtk widgets, you can see how to construct them in
   the
  sugar-toolkit code:
  
 
  
http://git.sugarlabs.org/projects/sugar-toolkit/repos/mainline/blobs/master/src/sugar/activity/widgets.py#line326
 
  I am sorry I didn't refer to using C# here. How can I make the
  Activity
  Toolbar or these widgets in my activity using C#?
 
  3) I want to use the Text to Speech mechanism in my activity similar
   to
   eSpeak. How's that done in Mono?I think you have two options:
   
  - DBus# to interface with speech-dispatcher
  - http://wiki.sugarlabs.org/go/Activity_Team/gst-plugins-espeak
 
  Since I am a new learner, I would really appreciate a sample or a
  tutorial
  on how do the same(using C# here).
  I would be really indebted for help. Thanks a lot!
 
  If you are just learning to program, writing your Sugar activity in
  Python
  would save you loads of trouble.
  It is possible to write an activity in any language (I know, because I
  did
  it) but you do have to be proficient in the language you want to use,
  and be
  able to map general advice into working code.
  For C#, the framework that Lionel's tutorial describes already goes a
  long
  way, the hardest part is done. But extending it to fully support a
  Sugar-like GUI and collaboration is going to be your problem, since
  you are
  one of the very few (if not the only one) who want to write an
  activity in
  C#.
  - Bert -
 
 
  ___
  Sugar-devel mailing list
  Sugar-devel@lists.sugarlabs.org
  http://lists.sugarlabs.org/listinfo/sugar-devel
 
 
 
  ___
  Sugar-devel mailing list
  Sugar-devel@lists.sugarlabs.org
  http://lists.sugarlabs.org/listinfo/sugar-devel
 
 



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


Re: [Sugar-devel] updating pootle and creating branches

2010-09-28 Thread Tomeu Vizoso
On Tue, Sep 28, 2010 at 12:55, Tomeu Vizoso to...@sugarlabs.org wrote:
 On Tue, Sep 28, 2010 at 10:12, Tomeu Vizoso to...@sugarlabs.org wrote:
 Hi,

 time is getting tight and we need to release 0.90.0 and branch so
 development can continue.

 Can we put together in this thread all the knowledge we have available
 about how to do that? Links to the wiki are best, but anything will be
 useful.

 To be specific, what we need to do is:

 - update the Glucose and Fructose projects by pulling from git,

 Looks like the git checkouts were almost up to date. What remained to
 be done was regenerating the .pot files and having each language
 update their templates.

The current roadblock is pushing to gitorious, we would need to either
find out the keys for the pootle user or change them.

Regards,

Tomeu

 Will be updating the wiki with what I discover.

 - create Glucose and Fructose branches for 0.86, 0.88 and 0.90.

 One of the most urgent things is getting shell access to
 translate.sugarlabs.org, can someone add my public ssh key to it?

 Bernie has given me all required access to the server.

 Thanks,

 Tomeu

 Thanks,

 Tomeu


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


Re: [Sugar-devel] Mesh networking not working in my XO's

2010-09-28 Thread Tomeu Vizoso
On Tue, Sep 28, 2010 at 14:08, Harpreet Sareen author.blog...@gmail.com wrote:
 Hi,
 Here's the info about OS versions on my XO laptops.

 XO 1:
 Build: 201 customised
 Sugar: 0.84.2
 Firmware: Q3A36
 Wireless Firmware: 9.70.7.p0

 XO 1.5
 Build: 802
 Sugar: 0.32.1
 Firmware: Q2E41
 Strange, there's no wireless firmware listed here unlike the XO 1.0
 What to do?

I think this should be enough. Someone here or in
http://lists.laptop.org/listinfo/devel will be able to tell you if
those versions should be able to create a network without
infrastructure.

Regards,

Tomeu

 Regards
 Harpreet


 On Tue, Sep 28, 2010 at 12:58 PM, Tomeu Vizoso to...@sugarlabs.org wrote:

 On Tue, Sep 28, 2010 at 04:13, Harpreet Sareen author.blog...@gmail.com
 wrote:
  Hi,
  I have tow XO laptops (XO 1 and XO 1.5) which I want to connect together
  through mesh networking. I currently don't use WiFi hotspot/Access
  Point/Wired Network for the internet rather 3G EVDO. So, unfortunately,
  I
  cannot connect both these XO's through the XO -- AP -- XO. I had to
  consider
  the XO -- XO mesh for networking.
  XO 1 shows only one dot in the Neighbourhood named as olpc-mesh and XO
  1.5
  shows three dots namely, MeshNetwork1, MeshNetwork6 and
  MeshNetwork11
  in the Neighbourhood. I tried sharing the Record activity between the
  XO's
  by starting the activity on XO 1.5 but XO 1.5 is not discovered in the
  neighbourhood of XO 1.0.
  What could be the problem or how it could be troubleshooted? Why isn't
  the
  laptop being discovered int the neghbourhood?

 First thing you need to do is to say which OS versions you are running
 on each machine.

 Regards,

 Tomeu

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



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


Re: [Sugar-devel] Mesh networking not working in my XO's

2010-09-28 Thread Tomeu Vizoso
On Tue, Sep 28, 2010 at 14:53, Harpreet Sareen author.blog...@gmail.com wrote:
 Hi,
 I was discussing here about using Telepathy Framework with DBus bindings i.e
 collaboration on XO's using C#.
 If I am able to do that, will the solution be the same for Mesh networking
 and Ad-hoc networking or would I have to concentrate on any one of them
 first?

Should be the same.

Regards,

Tomeu

 Regards
 Harpreet

 On Tue, Sep 28, 2010 at 6:04 PM, Simon Schampijer si...@schampijer.de
 wrote:

 On 09/28/2010 02:26 PM, Harpreet Sareen wrote:

 Hi,
 To share between XO-1s and XO-1.5s you have to use Ad-hoc networks. You
 can
 create one by using the option in the frame wireless device.
 Could you please explain that in detail?
 Thanks!


 --Harpreet--


 http://wiki.sugarlabs.org/go/0.86/Notes#Ad_hoc_Networking

 Regards,
   Simon


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


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


Re: [Sugar-devel] [Systems] updating pootle and creating branches

2010-09-28 Thread Tomeu Vizoso
On Tue, Sep 28, 2010 at 15:43, Sayamindu Dasgupta sayami...@gmail.com wrote:
 On Tue, Sep 28, 2010 at 9:17 AM, Tomeu Vizoso to...@sugarlabs.org wrote:
 On Tue, Sep 28, 2010 at 15:07, Chris Leonard cjlhomeaddr...@gmail.com 
 wrote:
 Bernie,

 I will continue to to the work I do as a Pootle admin (as time allows), but
 as we've discussed before, we need someone from the Systems group to handle
 back-end things like project versioning and git connections.  I do what I
 can via the Pootle administrative interface, but that is limited to adding
 new language admins, new language set up, adding existing projects to new
 languages, and the like.

 That's great, I'm now working on fixing pushing to git and then will
 do branches. Will try to write down processes for the next admin.


 Hi guys,
 Apologies for disappearing. Here are the details you may require:
 Documentation of the helper scripts:
 http://git.sugarlabs.org/projects/pootle-helpers/repos/mainline/blobs/master/README
 Updater stuff (look at the cronjobs for Pootle - they ensure the VCS
 stuff remain in sync).

Thanks for the pointers!

 SSH keys (/var/lib/pootle/.ssh)

Hmm, that dir only contains known_hosts, then there's:

poo...@pootle:~$ ls -l .ssh*
.ssh:
total 4
-rw-r--r-- 1 pootle pootle 2652 2010-09-28 08:05 known_hosts

.ssh_nothanks:
total 16
-rw-r--r-- 1 pootle pootle  808 2010-01-14 12:51 authorized_keys
-rw--- 1 pootle pootle 1675 2009-03-25 13:56 id_rsa
-rw-r--r-- 1 pootle pootle  412 2009-03-25 13:56 id_rsa.pub
-rw-r--r-- 1 pootle pootle 2210 2009-04-22 15:57 known_hosts

Tried with using .ssh_nothanks but it still cannot push to gitorious.

 Let me know if you need any more help.
 If it makes sense - I can participate in a Skype/IRC meeting to guide
 you through the process.

Will be great, we may have found a candidate for the job.

Thanks,

Tomeu

 -sdg-


 Thanks,

 Tomeu

 cj;

 On Tue, Sep 28, 2010 at 5:52 AM, Bernie Innocenti ber...@codewiz.org
 wrote:

 On 09/28/10 10:12, Tomeu Vizoso wrote:
  Can we put together in this thread all the knowledge we have available
  about how to do that? Links to the wiki are best, but anything will be
  useful.

 I've started a wiki page to collect information on the translation
 service:

  http://wiki.sugarlabs.org/go/Service/translate

 In the event we can't get back in touch with Sayamindu, is there any
 volunteer who would like to step forward to help maintaining Pootle?

 --
   // Bernie Innocenti - http://codewiz.org/
  \X/  Sugar Labs       - http://sugarlabs.org/
 ___
 Systems mailing list
 syst...@lists.sugarlabs.org
 http://lists.sugarlabs.org/listinfo/systems


 ___
 Systems mailing list
 syst...@lists.sugarlabs.org
 http://lists.sugarlabs.org/listinfo/systems




 --
 Sayamindu Dasgupta
 [http://sayamindu.randomink.org/ramblings]

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


Re: [Sugar-devel] [Systems] updating pootle and creating branches

2010-09-28 Thread Tomeu Vizoso
On Tue, Sep 28, 2010 at 15:48, Tomeu Vizoso to...@sugarlabs.org wrote:
 On Tue, Sep 28, 2010 at 15:43, Sayamindu Dasgupta sayami...@gmail.com wrote:
 On Tue, Sep 28, 2010 at 9:17 AM, Tomeu Vizoso to...@sugarlabs.org wrote:
 On Tue, Sep 28, 2010 at 15:07, Chris Leonard cjlhomeaddr...@gmail.com 
 wrote:
 Bernie,

 I will continue to to the work I do as a Pootle admin (as time allows), but
 as we've discussed before, we need someone from the Systems group to handle
 back-end things like project versioning and git connections.  I do what I
 can via the Pootle administrative interface, but that is limited to adding
 new language admins, new language set up, adding existing projects to new
 languages, and the like.

 That's great, I'm now working on fixing pushing to git and then will
 do branches. Will try to write down processes for the next admin.


 Hi guys,
 Apologies for disappearing. Here are the details you may require:
 Documentation of the helper scripts:
 http://git.sugarlabs.org/projects/pootle-helpers/repos/mainline/blobs/master/README
 Updater stuff (look at the cronjobs for Pootle - they ensure the VCS
 stuff remain in sync).

 Thanks for the pointers!

 SSH keys (/var/lib/pootle/.ssh)

 Hmm, that dir only contains known_hosts, then there's:

 poo...@pootle:~$ ls -l .ssh*
 .ssh:
 total 4
 -rw-r--r-- 1 pootle pootle 2652 2010-09-28 08:05 known_hosts

 .ssh_nothanks:
 total 16
 -rw-r--r-- 1 pootle pootle  808 2010-01-14 12:51 authorized_keys
 -rw--- 1 pootle pootle 1675 2009-03-25 13:56 id_rsa
 -rw-r--r-- 1 pootle pootle  412 2009-03-25 13:56 id_rsa.pub
 -rw-r--r-- 1 pootle pootle 2210 2009-04-22 15:57 known_hosts

 Tried with using .ssh_nothanks but it still cannot push to gitorious.

Bernie tried and it worked, so I guess we can push now.

Regards,

Tomeu

 Let me know if you need any more help.
 If it makes sense - I can participate in a Skype/IRC meeting to guide
 you through the process.

 Will be great, we may have found a candidate for the job.

 Thanks,

 Tomeu

 -sdg-


 Thanks,

 Tomeu

 cj;

 On Tue, Sep 28, 2010 at 5:52 AM, Bernie Innocenti ber...@codewiz.org
 wrote:

 On 09/28/10 10:12, Tomeu Vizoso wrote:
  Can we put together in this thread all the knowledge we have available
  about how to do that? Links to the wiki are best, but anything will be
  useful.

 I've started a wiki page to collect information on the translation
 service:

  http://wiki.sugarlabs.org/go/Service/translate

 In the event we can't get back in touch with Sayamindu, is there any
 volunteer who would like to step forward to help maintaining Pootle?

 --
   // Bernie Innocenti - http://codewiz.org/
  \X/  Sugar Labs       - http://sugarlabs.org/
 ___
 Systems mailing list
 syst...@lists.sugarlabs.org
 http://lists.sugarlabs.org/listinfo/systems


 ___
 Systems mailing list
 syst...@lists.sugarlabs.org
 http://lists.sugarlabs.org/listinfo/systems




 --
 Sayamindu Dasgupta
 [http://sayamindu.randomink.org/ramblings]


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


Re: [Sugar-devel] [Systems] updating pootle and creating branches

2010-09-28 Thread Tomeu Vizoso
On Tue, Sep 28, 2010 at 15:43, Sayamindu Dasgupta sayami...@gmail.com wrote:
 On Tue, Sep 28, 2010 at 9:17 AM, Tomeu Vizoso to...@sugarlabs.org wrote:
 On Tue, Sep 28, 2010 at 15:07, Chris Leonard cjlhomeaddr...@gmail.com 
 wrote:
 Bernie,

 I will continue to to the work I do as a Pootle admin (as time allows), but
 as we've discussed before, we need someone from the Systems group to handle
 back-end things like project versioning and git connections.  I do what I
 can via the Pootle administrative interface, but that is limited to adding
 new language admins, new language set up, adding existing projects to new
 languages, and the like.

 That's great, I'm now working on fixing pushing to git and then will
 do branches. Will try to write down processes for the next admin.


 Hi guys,
 Apologies for disappearing. Here are the details you may require:
 Documentation of the helper scripts:
 http://git.sugarlabs.org/projects/pootle-helpers/repos/mainline/blobs/master/README
 Updater stuff (look at the cronjobs for Pootle - they ensure the VCS
 stuff remain in sync).
 SSH keys (/var/lib/pootle/.ssh)
 Let me know if you need any more help.

We're getting close, now I'm receiving this error when trying to merge
the new .pot into the Etoys .po:

An error has occurred. Thank you for your patience.

Error accessing
/var/lib/pootle/translations/etoys_new/templates/DrGeoII-Etoys.pot,
Filesystem sent error: No such file or directory

Any ideas how to fix it?

Thanks,

Tomeu

 If it makes sense - I can participate in a Skype/IRC meeting to guide
 you through the process.
 -sdg-


 Thanks,

 Tomeu

 cj;

 On Tue, Sep 28, 2010 at 5:52 AM, Bernie Innocenti ber...@codewiz.org
 wrote:

 On 09/28/10 10:12, Tomeu Vizoso wrote:
  Can we put together in this thread all the knowledge we have available
  about how to do that? Links to the wiki are best, but anything will be
  useful.

 I've started a wiki page to collect information on the translation
 service:

  http://wiki.sugarlabs.org/go/Service/translate

 In the event we can't get back in touch with Sayamindu, is there any
 volunteer who would like to step forward to help maintaining Pootle?

 --
   // Bernie Innocenti - http://codewiz.org/
  \X/  Sugar Labs       - http://sugarlabs.org/
 ___
 Systems mailing list
 syst...@lists.sugarlabs.org
 http://lists.sugarlabs.org/listinfo/systems


 ___
 Systems mailing list
 syst...@lists.sugarlabs.org
 http://lists.sugarlabs.org/listinfo/systems




 --
 Sayamindu Dasgupta
 [http://sayamindu.randomink.org/ramblings]

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


[Sugar-devel] 0.90 localization

2010-09-28 Thread Tomeu Vizoso
Hi,

as far as I know language administrators and translators should be
able now to keep doing their work as usual.

Would be great if you could try to get Fructose and Glucose translated
and report any problems you may find.

I'm not sure if we should delay the 0.90.0 release so it gets better
translations, or release as-is so the translations will go in a future
release. Opinions?

Regards,

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


Re: [Sugar-devel] [Systems] updating pootle and creating branches

2010-09-28 Thread Tomeu Vizoso
On Tue, Sep 28, 2010 at 15:43, Sayamindu Dasgupta sayami...@gmail.com wrote:
 On Tue, Sep 28, 2010 at 9:17 AM, Tomeu Vizoso to...@sugarlabs.org wrote:
 On Tue, Sep 28, 2010 at 15:07, Chris Leonard cjlhomeaddr...@gmail.com 
 wrote:
 Bernie,

 I will continue to to the work I do as a Pootle admin (as time allows), but
 as we've discussed before, we need someone from the Systems group to handle
 back-end things like project versioning and git connections.  I do what I
 can via the Pootle administrative interface, but that is limited to adding
 new language admins, new language set up, adding existing projects to new
 languages, and the like.

 That's great, I'm now working on fixing pushing to git and then will
 do branches. Will try to write down processes for the next admin.


 Hi guys,
 Apologies for disappearing. Here are the details you may require:
 Documentation of the helper scripts:
 http://git.sugarlabs.org/projects/pootle-helpers/repos/mainline/blobs/master/README
 Updater stuff (look at the cronjobs for Pootle - they ensure the VCS
 stuff remain in sync).
 SSH keys (/var/lib/pootle/.ssh)
 Let me know if you need any more help.
 If it makes sense - I can participate in a Skype/IRC meeting to guide
 you through the process.

Can you check when you have time if what I added to the wiki is true
and if there's any big omission?

http://wiki.sugarlabs.org/go/Service/translate#Notes

Thanks,

Tomeu

 -sdg-


 Thanks,

 Tomeu

 cj;

 On Tue, Sep 28, 2010 at 5:52 AM, Bernie Innocenti ber...@codewiz.org
 wrote:

 On 09/28/10 10:12, Tomeu Vizoso wrote:
  Can we put together in this thread all the knowledge we have available
  about how to do that? Links to the wiki are best, but anything will be
  useful.

 I've started a wiki page to collect information on the translation
 service:

  http://wiki.sugarlabs.org/go/Service/translate

 In the event we can't get back in touch with Sayamindu, is there any
 volunteer who would like to step forward to help maintaining Pootle?

 --
   // Bernie Innocenti - http://codewiz.org/
  \X/  Sugar Labs       - http://sugarlabs.org/
 ___
 Systems mailing list
 syst...@lists.sugarlabs.org
 http://lists.sugarlabs.org/listinfo/systems


 ___
 Systems mailing list
 syst...@lists.sugarlabs.org
 http://lists.sugarlabs.org/listinfo/systems




 --
 Sayamindu Dasgupta
 [http://sayamindu.randomink.org/ramblings]

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


Re: [Sugar-devel] 0.90 localization

2010-09-28 Thread Tomeu Vizoso
On Tue, Sep 28, 2010 at 18:29, Walter Bender walter.ben...@gmail.com wrote:
 On Tue, Sep 28, 2010 at 12:18 PM, Tomeu Vizoso to...@sugarlabs.org wrote:
 Hi,

 as far as I know language administrators and translators should be
 able now to keep doing their work as usual.

 Would be great if you could try to get Fructose and Glucose translated
 and report any problems you may find.

 I still don't see the most recent POT file for Turtle Art in Fructose
 reflected in the workflow.

How do you check that?

Thanks,

Tomeu

 -walter

 I'm not sure if we should delay the 0.90.0 release so it gets better
 translations, or release as-is so the translations will go in a future
 release. Opinions?

 Regards,

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




 --
 Walter Bender
 Sugar Labs
 http://www.sugarlabs.org

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


Re: [Sugar-devel] 0.90 localization

2010-09-28 Thread Tomeu Vizoso
On Tue, Sep 28, 2010 at 18:45, Tomeu Vizoso to...@sugarlabs.org wrote:
 On Tue, Sep 28, 2010 at 18:29, Walter Bender walter.ben...@gmail.com wrote:
 On Tue, Sep 28, 2010 at 12:18 PM, Tomeu Vizoso to...@sugarlabs.org wrote:
 Hi,

 as far as I know language administrators and translators should be
 able now to keep doing their work as usual.

 Would be great if you could try to get Fructose and Glucose translated
 and report any problems you may find.

 I still don't see the most recent POT file for Turtle Art in Fructose
 reflected in the workflow.

 How do you check that?

Ok, what was happening is that Walter was checking the Spanish .po for
TurtleArt and it had not been merged from the templates.

Language administrators need to do so from time to time by clicking
the update the files from templates link in the Files tab.

Btw, do we have documented somewhere what language admins need to do?

Regards,

Tomeu

 Thanks,

 Tomeu

 -walter

 I'm not sure if we should delay the 0.90.0 release so it gets better
 translations, or release as-is so the translations will go in a future
 release. Opinions?

 Regards,

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




 --
 Walter Bender
 Sugar Labs
 http://www.sugarlabs.org


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


Re: [Sugar-devel] Accessing hidden SSIDs

2010-09-27 Thread Tomeu Vizoso
On Mon, Sep 27, 2010 at 01:56, Tim McNamara paperl...@timmcnamara.co.nz wrote:
 Is it possible to access hidden SSIDs via the Neighbourhood View?

Nope, guess we could grow an option in the wifi device icon.

Regards,

Tomeu

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


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


Re: [Sugar-devel] Weekly test request reminders? (was Re: Priorities for testing)

2010-09-27 Thread Tomeu Vizoso
On Sun, Sep 26, 2010 at 22:04, Tim McNamara paperl...@timmcnamara.co.nz wrote:

 On 25 September 2010 21:07, Sascha Silbe
 sascha-ml-reply-to-201...@silbe.org wrote:

 Excerpts from Tim McNamara's message of Fri Sep 24 22:37:18 +0200 2010:

  The New Zealand testing groups will be operating in a few hours. If you
  have
  any requests for things to be explored, please respond within 5 hours.

 That was a bit short notice.

 Sorry about that Sascha. We meet every weekend (Friday evening in Europe,
 Friday afternoon USA) , but haven't received many direct requests in a
 while.
 If it would be worthwhile, I can send out reminders in the middle of the
 week asking for things that are worthwhile to be manually tested. Do people
 think that would be excessive?

I think it would be very appropriate. Thanks for the great work!

Tomeu

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


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


Re: [Sugar-devel] Bug 2323

2010-09-27 Thread Tomeu Vizoso
On Sat, Sep 25, 2010 at 19:28, Kandarp Kaushik kand...@seeta.in wrote:
 Hello,
 I was working on bug #2323 but do not have much knowledge on how to use the
 clipboard.

 Please provide some pointers on it.

http://www.pygtk.org/pygtk2tutorial/ch-NewInPyGTK2.2.html
http://www.pygtk.org/docs/pygtk/class-gtkclipboard.html
http://wiki.sugarlabs.org/go/Development_Team/Almanac/GTK%27s_Clipboard_Module

Regards,

Tomeu

 Regards,
 Kandarp

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


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


Re: [Sugar-devel] [PATCH v2 sugar] Shutdown and Logout menu items should activate the buzzy cursor (SL#2151)

2010-09-27 Thread Tomeu Vizoso
On Sat, Sep 25, 2010 at 23:29, Anurag Chowdhury anu...@seeta.in wrote:
 Shutdown (and Logout) menu items should activate the buzzy cursor (or provide 
 some other visual feedback, perhaps dimming/locking the UI from use).

Hi Anurag, could you explain what you have changed since the last
revision and why?

With the information you have made available I would have to guess too much.

Thanks,

Tomeu

 ---
  src/jarabe/view/buddymenu.py |   42 
 ++
  1 files changed, 34 insertions(+), 8 deletions(-)

 v1 was Reviewed-By: James Cameron quozl at laptop.org
 v1-v2: Set the cursor in its appropriate window

 diff --git a/src/jarabe/view/buddymenu.py b/src/jarabe/view/buddymenu.py
 index 0ba6cc1..7135d9e 100644
 --- a/src/jarabe/view/buddymenu.py
 +++ b/src/jarabe/view/buddymenu.py
 @@ -21,6 +21,8 @@ from gettext import gettext as _
  import gtk
  import gconf
  import dbus
 +import jarabe
 +import glib

  from sugar.graphics.palette import Palette
  from sugar.graphics.menuitem import MenuItem
 @@ -98,16 +100,40 @@ class BuddyMenu(Palette):
         item.show()

     def __logout_activate_cb(self, menu_item):
 -        session_manager = get_session_manager()
 -        session_manager.logout()
 +        def update_cur(window):
 +            window.get_window().set_cursor(gtk.gdk.Cursor(gtk.gdk.WATCH))
 +            return False
 +        def shut(self, menu_item):
 +            session_manager = get_session_manager()
 +            session_manager.logout()
 +        window = jarabe.desktop.homewindow.get_instance()
 +        glib.timeout_add(3, update_cur, window)
 +        glib.idle_add(shut,self,menu_item)
 +        gtk.main()

     def __reboot_activate_cb(self, menu_item):
 -        session_manager = get_session_manager()
 -        session_manager.reboot()
 -
 -    def __shutdown_activate_cb(self, menu_item):
 -        session_manager = get_session_manager()
 -        session_manager.shutdown()
 +        def update_cur(window):
 +            window.get_window().set_cursor(gtk.gdk.Cursor(gtk.gdk.WATCH))
 +            return False
 +        def shut(self, menu_item):
 +            session_manager = get_session_manager()
 +            session_manager.reboot()
 +        window = jarabe.desktop.homewindow.get_instance()
 +        glib.timeout_add(3, update_cur, window)
 +        glib.idle_add(shut,self,menu_item)
 +        gtk.main()
 +
 +    def __shutdown_activate_cb(self, menu_item):
 +        def update_cur(window):
 +            window.get_window().set_cursor(gtk.gdk.Cursor(gtk.gdk.WATCH))
 +            return False
 +        def shut(self, menu_item):
 +            session_manager = get_session_manager()
 +            session_manager.shutdown()
 +        window = jarabe.desktop.homewindow.get_instance()
 +        glib.timeout_add(3, update_cur, window)
 +        glib.idle_add(shut,self,menu_item)
 +        gtk.main()

     def __controlpanel_activate_cb(self, menu_item):
         panel = ControlPanel()
 --
 1.7.2.2

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

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


Re: [Sugar-devel] [PATCH v2 sugar] Work around for fullscreen bug (SL #2180)

2010-09-27 Thread Tomeu Vizoso
On Sat, Sep 25, 2010 at 17:06, Dipankar Patro dipan...@seeta.in wrote:
 Previously some bottom part of sugar emulator window was pushed out
 of viewing area at 800x600 system resolution.
 Modified the code to include the resolution 800x600 for fullscreen
 execution, since we cannot predict the space of different OS task
 pannels/bars/ window title bars.

Patch looks good to me, please send it again with a commit message
that describes what the patch is for (for example: open sugar-emulator
in fullscreen mode by default if the screen is = 800x600).

Also please ask for submittal once we have branched 0.90, it will be
in a few days from now and will be announced in sugar-devel.

Thanks,

Tomeu

 ---
  src/jarabe/util/emulator.py |    2 +-
  1 files changed, 1 insertions(+), 1 deletions(-)

 v1-v2: Rebased on current mainline/master

 diff --git a/src/jarabe/util/emulator.py b/src/jarabe/util/emulator.py
 index 6a43044..cc112c9 100644
 --- a/src/jarabe/util/emulator.py
 +++ b/src/jarabe/util/emulator.py
 @@ -42,7 +42,7 @@ def _run_xephyr(display, dpi, dimensions, fullscreen):
     screen_size = (gtk.gdk.screen_width(), gtk.gdk.screen_height())

     if (not dimensions) and (fullscreen is None) and \
 -       (screen_size  default_dimensions) :
 +       (screen_size = default_dimensions) :
         # no forced settings, screen too small = fit screen
         fullscreen = True
     elif (not dimensions) :
 --
 1.7.0.4

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

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


Re: [Sugar-devel] Bug 2318

2010-09-27 Thread Tomeu Vizoso
On Fri, Sep 24, 2010 at 19:56, Dipankar Patro dipan...@seeta.in wrote:
 Hi all,

 I am working on the bug : http://bugs.sugarlabs.org/ticket/2318

 I tried changing the class JournalButton in jarabe/journal/volumestoolbar.py
 as follows
 http://paste.ubuntu.com/499852/
 It seems that the volume info still does not appear.

Can you send a diff instead? It's hard to see what you have changed.

It would be good as well if you could explain in words how do you plan
to fix the issue.

Thanks,

Tomeu

 I think it is somewhat related to right click key handler, because in other
 places (frame, home view) the volume info appears as a right click popup.

 Would be great if you some could provide some pointers on the views above.

 Regards,
 Dipankar

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


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


Re: [Sugar-devel] Unintentional data store reindexing on sugar-emulator restart (was: Re: Some questions concerning saving methods on sugar)

2010-09-27 Thread Tomeu Vizoso
On Fri, Sep 24, 2010 at 19:22, Sascha Silbe
sascha-ml-reply-to-201...@silbe.org wrote:
 Excerpts from Tomeu Vizoso's message of Fri Sep 24 15:10:07 +0200 2010:

  It could be that the Journal is reindexing. (For a large Journal, this
  sometimes has the appearance of an empty or nearly empty Journal.) If
  you wait for the indexing to complete, everything reappears as normal.

 But why would it be reindexing? Are people getting their journals
 reindexed from time to time?

 This happened to me a few times during the last few days, each time
 after I restarted Sugar rather quickly. There's an exception in the log:

 1285265788.580216 DEBUG root: max_versions=0
 1285265788.604839 ERROR root: Failed to open index, will rebuild
 Traceback (most recent call last):
  File 
 /home/sascha.silbe/sugar-jhbuild/install/lib/python2.6/site-packages/carquinyol/datastore.py,
  line 275, in __init__
    self._index_store.open_index()
  File 
 /home/sascha.silbe/sugar-jhbuild/install/lib/python2.6/site-packages/carquinyol/indexstore.py,
  line 246, in open_index
    self._database = WritableDatabase(index_path, xapian.DB_CREATE_OR_OPEN)
  File /usr/lib/python2.6/dist-packages/xapian/__init__.py, line 4059, in 
 __init__
    _xapian.WritableDatabase_swiginit(self,_xapian.new_WritableDatabase(*args))
 DatabaseLockError: Unable to get write lock on 
 /home/sascha.silbe/.sugar/default/datastore/index: already locked
 1285265789.971570 DEBUG root: Going to update the index with object_ids 
 [('15947ca6-a018-47d0-9c09-f58c12e6cf82'
 [...]


 My guess is that the old sugar-datastore instance still has the index
 open. We don't have API for stopping sugar-datastore and instead rely
 on dbus-daemon to stop it when it gets stopped itself. I've noticed that
 when using --exit-with-session dbus-launch and dbus-daemon often continue
 to run for several seconds after a session has ended and returned.

 So this is just another way to trigger SL#1257 [1].

Have just added a comment that hopefully will make easier to see what
needs to be done.

 It might be even easier to trigger if you're running sugar-emulator from
 a GUI menu on a slow system as the user assumes it to be finished as
 soon as the Xephyr window is closed, not when sugar-emulator (the
 script) stops.

That's a good point, now I understand why we cannot rely on the usual
D-Bus mechanisms.

Regards,

Tomeu

 Sascha

 [1] https://bugs.sugarlabs.org/ticket/1257
 --
 http://sascha.silbe.org/
 http://www.infra-silbe.de/

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


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


Re: [Sugar-devel] Bug No. #398

2010-09-27 Thread Tomeu Vizoso
On Mon, Sep 27, 2010 at 16:36, Shanjit Singh Jajmann
shan...@dev.seeta.in wrote:
 Team,

 I am working on http://bugs.sugarlabs.org/ticket/398  : Regarding the search
 box, i have tried to introduce the same functionality as in the 'Log'
 activity, in the toolbar of viewsource (jarabe/view/viewscreen.py), however
 i have run into some searching and highlighting issues regarding working

Without knowing which are the issues is a bit hard to know how to
help. Can you be more explicit and also post the patch?

Regards,

Tomeu

 with gtksourceview used in the sourceview function of the same file. Could
 you please provide some pointers on how to achieve the searching and
 highlighting ? (i could not get the bounds of the buffer created, start,end
 . The highlight function has me confused as it isn't working) or any other
 approach if possible.

 Regards
 Shan

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


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


Re: [Sugar-devel] [PATCH v3 sugar] Work around for fullscreen bug (SL #2180)

2010-09-27 Thread Tomeu Vizoso
On Mon, Sep 27, 2010 at 16:48, Dipankar Patro dipan...@seeta.in wrote:
 Previously some bottom part of sugar emulator window was pushed out of 
 viewing area at 800x600 system resolution.
 The patch opens Sugar-emulator in fullscreen mode for resolutions = 800x600 
 to avoid the above mentioned situation.

I meant changing the _Subject_ line of the patch describe what the
patch does in less than 80 chars. Sometimes is hard but is very
important to try.

Right now it is:

Subject: [Sugar-devel] [PATCH v3 sugar] Work around for fullscreen bug
(SL #2180)

I'm saying this because often when going through the history people
will only see the subject line.

Thanks,

Tomeu

 ---
  src/jarabe/util/emulator.py |    2 +-
  1 files changed, 1 insertions(+), 1 deletions(-)

 v2 was Reviewed by Tomeu Vizoso
 v2-v3 : Changed commit message for proper description of patch.

 diff --git a/src/jarabe/util/emulator.py b/src/jarabe/util/emulator.py
 index 6a43044..cc112c9 100644
 --- a/src/jarabe/util/emulator.py
 +++ b/src/jarabe/util/emulator.py
 @@ -42,7 +42,7 @@ def _run_xephyr(display, dpi, dimensions, fullscreen):
     screen_size = (gtk.gdk.screen_width(), gtk.gdk.screen_height())

     if (not dimensions) and (fullscreen is None) and \
 -       (screen_size  default_dimensions) :
 +       (screen_size = default_dimensions) :
         # no forced settings, screen too small = fit screen
         fullscreen = True
     elif (not dimensions) :
 --
 1.7.0.4

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

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


Re: [Sugar-devel] Queries regarding Sugar Sharp assembly on Mono

2010-09-27 Thread Tomeu Vizoso
On Mon, Sep 27, 2010 at 14:50, Harpreet Sareen author.blog...@gmail.com wrote:
 Hi,
 1) Usually the activity interface has different tabs on the top such as
 shown in this screenshot for Record activity.
 http://img163.imageshack.us/img163/7580/542record1.png[^]
 Sugar-Sharp assembly doesn't include the binding for the Telepathy
 Framework. I would be greatful if you could that to make the networking
 operation possible.
 Mesh Networking is a major requirement for XO laptops as the activities have
 to collaborate. Please Please Please help !!

You can access the Telepathy API through DBus# and the Telepathy DBus spec:

http://www.ndesk.org/DBusSharp
http://telepathy.freedesktop.org/spec/

 What do I have to do to make those tabs in Mono i.e to share my activities
 with the neighborhood?

They are normal Gtk widgets, you can see how to construct them in the
sugar-toolkit code:

http://git.sugarlabs.org/projects/sugar-toolkit/repos/mainline/blobs/master/src/sugar/activity/widgets.py#line326

 2) I haven't noticed dialogue boxes coming up in Sugar. Are they possible in
 Sugar?

They are possible but not recommended, consider using an inline Alert instead:

http://git.sugarlabs.org/projects/sugar-toolkit/repos/mainline/blobs/master/src/sugar/graphics/alert.py

 3) I want to use the Text to Speech mechanism in my activity similar to
 eSpeak. How's that done in Mono?

I think you have two options:

- DBus# to interface with speech-dispatcher
- http://wiki.sugarlabs.org/go/Activity_Team/gst-plugins-espeak

Regards,

Tomeu

 Thanks for help!

 Regards
 Harpreet

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


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


Re: [Sugar-devel] Some questions concerning saving methods on sugar

2010-09-24 Thread Tomeu Vizoso
On Thu, Sep 23, 2010 at 00:58, Alberto Arruda de Oliveira
alberto.a.o...@gmail.com wrote:
 Hello,

 First of all, thanks for all the answers!

 I decided to follow your advices and implement the saving feature of my
 activity through the journal.

 Although it's not working perfectly yet, I hope it will be soon. I'm just
 having a little problem with the keep button. My activity creates the
 journal entry like it should when I exit through the close button, but when
 I press the keep button, it doesn't create the entry. Is there any big
 differences in how the keep and close button access the journal to save the
 state of the activity?

 Also, related to the sugar-emulator, sometimes, when I close it, all the
 journal entries are wiped. I suspect this is an emulator problem ( because
 not only it happened with my activity, but also with other activities ), but
 I'd like to be sure I'm not doing anything wrong!

Haven't seen it happening myself. Can you tell us specific versions of
Sugar and any tips for reproducing it?

Thanks,

Tomeu

 Thanks again,

 Alberto Arruda de Oliveira

 2010/9/20 Alberto Arruda de Oliveira alberto.a.o...@gmail.com

 Hello,

 I've been adapting an application to use as an activity, and I have some
 questions about the way to save on sugar.

 At first, I tried to just create a directory inside my Activity folder
 especially made for saving files, but it did not work, because of the access
 permissions to it, and, although we could simply manually change the folder
 permission for writing on that folder, we would have to do it for every
 single OLPC we installed our activity into and we didn't want that.

 Then, we started trying with the journal. Everything was going fine, until
 we discovered that another sugar activity, Scratch, implemented saving and
 loading on a similar fashion we previously wanted. It has a folder inside
 it's Activity directory with subdirectories related to each kind of Scratch
 project. Also, Scratch's Activity directory has the same access permission
 as any other sugar Activity installed.

 So, my question is, does anyone knows how Scratch implements it's save /
 loading method? is there any guide explaining how to do it without using the
 journal? Keep in mind that we do know that there are other directories we
 could use to save our files, but we would like to use our Activity directory
 if possible.

 Thanks in advance ( and sorry for any english mistakes :] ),

 Alberto Arruda de Oliveira


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


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


Re: [Sugar-devel] 0.90 Exception: Activities list view and Journal view crashes in Arabic

2010-09-24 Thread Tomeu Vizoso
On Wed, Sep 22, 2010 at 18:06, Simon Schampijer si...@schampijer.de wrote:
 Hi,

 I am asking for an exception for [1] 0.90. Originally discovered on 0.84
 this is also present on 0.90. The patch [2] has been reviewed by Sascha
 and Tomeu already and it is low risk. Otherwise Arabic will be unusable
 as this effects the Journal and the Activities list view.

I think there should be a big FIXME comment with a reference to a
ticket in trac because it's a hack and because we really need to find
an appropriate fix in the near future.

Also, we don't have plurals in any other place?

Regards,

Tomeu

 Regards,
    Simon

 [1] http://bugs.sugarlabs.org/ticket/2354
 [2] Patch: http://bugs.sugarlabs.org/ticket/2354#comment:3
 ___
 Sugar-devel mailing list
 Sugar-devel@lists.sugarlabs.org
 http://lists.sugarlabs.org/listinfo/sugar-devel

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


Re: [Sugar-devel] Unicode and input method menu in gtk inputs

2010-09-24 Thread Tomeu Vizoso
On Wed, Sep 22, 2010 at 13:58, Gonzalo Odiard godi...@sugarlabs.org wrote:
 In all the gtk inputs we display in Sugar there are a menu when we the
 options Cut, Copy,Paste,Select all and the Input method and unicode menu
 menus.
 The last two menus are optional and by default not showed  in Gnome.
 You can use gconf to change the visibility of the menus
 Gconf settings
 /desktop/gnome/interface/show_unicode_menu
 /desktop/gnome/interface/show_input_method_menu

 I tried to change the values in gconf or in .gtkrc-2.0 or in
 /etc/gtk-2.0/gtkrc but Sugar ignores the settings.
 I have a simple pygtk test program with a entry. If I run it from the gnome
 terminal doesn't show the menus, if I run it from Sugar Terminal show the
 menus.

 Anybody knows if this is a bug in the theme engine or where I set the menus
 visibility?

Which gconf database and gtkrc file will be used is defined by the
environment on which Sugar is running.

To make sure you are modifying the Sugar GConf, run gconftool-2 or
gconf-editor from inside the terminal activity.

Sugar installs its own gtkrc files, called sugar-72.gtkrc or sugar-100.gtkrc.

Regards,

Tomeu

 --
 Gonzalo Odiard
 SugarLabs Argentina


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


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


Re: [Sugar-devel] Some questions concerning saving methods on sugar

2010-09-24 Thread Tomeu Vizoso
On Fri, Sep 24, 2010 at 14:41, Walter Bender walter.ben...@gmail.com wrote:
 On Fri, Sep 24, 2010 at 4:02 AM, Tomeu Vizoso to...@sugarlabs.org wrote:
 On Thu, Sep 23, 2010 at 00:58, Alberto Arruda de Oliveira
 alberto.a.o...@gmail.com wrote:
 Hello,

 First of all, thanks for all the answers!

 I decided to follow your advices and implement the saving feature of my
 activity through the journal.

 Although it's not working perfectly yet, I hope it will be soon. I'm just
 having a little problem with the keep button. My activity creates the
 journal entry like it should when I exit through the close button, but when
 I press the keep button, it doesn't create the entry. Is there any big
 differences in how the keep and close button access the journal to save the
 state of the activity?

 Also, related to the sugar-emulator, sometimes, when I close it, all the
 journal entries are wiped. I suspect this is an emulator problem ( because
 not only it happened with my activity, but also with other activities ), but
 I'd like to be sure I'm not doing anything wrong!

 It could be that the Journal is reindexing. (For a large Journal, this
 sometimes has the appearance of an empty or nearly empty Journal.) If
 you wait for the indexing to complete, everything reappears as normal.

But why would it be reindexing? Are people getting their journals
reindexed from time to time?

Regards,

Tomeu

 -walter

 Haven't seen it happening myself. Can you tell us specific versions of
 Sugar and any tips for reproducing it?

 Thanks,

 Tomeu

 Thanks again,

 Alberto Arruda de Oliveira

 2010/9/20 Alberto Arruda de Oliveira alberto.a.o...@gmail.com

 Hello,

 I've been adapting an application to use as an activity, and I have some
 questions about the way to save on sugar.

 At first, I tried to just create a directory inside my Activity folder
 especially made for saving files, but it did not work, because of the 
 access
 permissions to it, and, although we could simply manually change the folder
 permission for writing on that folder, we would have to do it for every
 single OLPC we installed our activity into and we didn't want that.

 Then, we started trying with the journal. Everything was going fine, until
 we discovered that another sugar activity, Scratch, implemented saving and
 loading on a similar fashion we previously wanted. It has a folder inside
 it's Activity directory with subdirectories related to each kind of Scratch
 project. Also, Scratch's Activity directory has the same access permission
 as any other sugar Activity installed.

 So, my question is, does anyone knows how Scratch implements it's save /
 loading method? is there any guide explaining how to do it without using 
 the
 journal? Keep in mind that we do know that there are other directories we
 could use to save our files, but we would like to use our Activity 
 directory
 if possible.

 Thanks in advance ( and sorry for any english mistakes :] ),

 Alberto Arruda de Oliveira


 ___
 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




 --
 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] Some questions concerning saving methods on sugar

2010-09-24 Thread Tomeu Vizoso
On Fri, Sep 24, 2010 at 15:25, Walter Bender walter.ben...@gmail.com wrote:
 On Fri, Sep 24, 2010 at 9:10 AM, Tomeu Vizoso to...@sugarlabs.org wrote:
 On Fri, Sep 24, 2010 at 14:41, Walter Bender walter.ben...@gmail.com wrote:
 On Fri, Sep 24, 2010 at 4:02 AM, Tomeu Vizoso to...@sugarlabs.org wrote:
 On Thu, Sep 23, 2010 at 00:58, Alberto Arruda de Oliveira
 alberto.a.o...@gmail.com wrote:
 Hello,

 First of all, thanks for all the answers!

 I decided to follow your advices and implement the saving feature of my
 activity through the journal.

 Although it's not working perfectly yet, I hope it will be soon. I'm just
 having a little problem with the keep button. My activity creates the
 journal entry like it should when I exit through the close button, but 
 when
 I press the keep button, it doesn't create the entry. Is there any big
 differences in how the keep and close button access the journal to save 
 the
 state of the activity?

 Also, related to the sugar-emulator, sometimes, when I close it, all the
 journal entries are wiped. I suspect this is an emulator problem ( because
 not only it happened with my activity, but also with other activities ), 
 but
 I'd like to be sure I'm not doing anything wrong!

 It could be that the Journal is reindexing. (For a large Journal, this
 sometimes has the appearance of an empty or nearly empty Journal.) If
 you wait for the indexing to complete, everything reappears as normal.

 But why would it be reindexing? Are people getting their journals
 reindexed from time to time?

 Not sure why, but in sugar-jhbuild, where I do most of my work, it
 seems to reindex fairly often (~1 out of every 30-40 sessions
 launched). one trigger *seems to be* changing the display size, e.g.,
 if I use 1200x900 sessions for a while and then switch to 800x600, it
 will often reindex. (Likely nothing causal there.)

It could be very interesting to look at the logs of the session when
reindexing starts and also of the session just before that.

Regards,

Tomeu

 -walter

 Regards,

 Tomeu

 -walter

 Haven't seen it happening myself. Can you tell us specific versions of
 Sugar and any tips for reproducing it?

 Thanks,

 Tomeu

 Thanks again,

 Alberto Arruda de Oliveira

 2010/9/20 Alberto Arruda de Oliveira alberto.a.o...@gmail.com

 Hello,

 I've been adapting an application to use as an activity, and I have some
 questions about the way to save on sugar.

 At first, I tried to just create a directory inside my Activity folder
 especially made for saving files, but it did not work, because of the 
 access
 permissions to it, and, although we could simply manually change the 
 folder
 permission for writing on that folder, we would have to do it for every
 single OLPC we installed our activity into and we didn't want that.

 Then, we started trying with the journal. Everything was going fine, 
 until
 we discovered that another sugar activity, Scratch, implemented saving 
 and
 loading on a similar fashion we previously wanted. It has a folder inside
 it's Activity directory with subdirectories related to each kind of 
 Scratch
 project. Also, Scratch's Activity directory has the same access 
 permission
 as any other sugar Activity installed.

 So, my question is, does anyone knows how Scratch implements it's save /
 loading method? is there any guide explaining how to do it without using 
 the
 journal? Keep in mind that we do know that there are other directories we
 could use to save our files, but we would like to use our Activity 
 directory
 if possible.

 Thanks in advance ( and sorry for any english mistakes :] ),

 Alberto Arruda de Oliveira


 ___
 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




 --
 Walter Bender
 Sugar Labs
 http://www.sugarlabs.org





 --
 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] bug #305

2010-09-24 Thread Tomeu Vizoso
On Fri, Sep 24, 2010 at 15:26, Ishan Bansal is...@seeta.in wrote:
 Hi

 I had made the patch for the Bug #305.

 http://lists.sugarlabs.org/archive/sugar-devel/2010-September/026732.html

 Please review the patch and provide suggestions on any change required.

Looks good to me, but we have to wait until we branch 0.90 before we
can commit. Can you ask benzea in #sugar if he has time to give it a
look?

Regards,

Tomeu

 regards

 ishan

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


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


Re: [Sugar-devel] bug #2170

2010-09-24 Thread Tomeu Vizoso
On Fri, Sep 24, 2010 at 15:28, Ishan Bansal is...@seeta.in wrote:
 Hi

 I had made the patch for the Bug #2170.

 http://lists.sugarlabs.org/archive/sugar-devel/2010-September/026963.html

 Please review the patch and provide suggestions on any change required.

The patch has been reviewed already IIRC, but I'm not sure if
Sayamindu has time to keep maintaining Read. If not, we need to find a
new maintainer.

Regards,

Tomeu

 regards

 ishan

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


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


Re: [Sugar-devel] 0.90 Exception: Activities list view and Journal view crashes in Arabic

2010-09-24 Thread Tomeu Vizoso
On Fri, Sep 24, 2010 at 16:10, Simon Schampijer si...@schampijer.de wrote:
 On 09/24/2010 10:06 AM, Tomeu Vizoso wrote:

 On Wed, Sep 22, 2010 at 18:06, Simon Schampijersi...@schampijer.de
  wrote:

 Hi,

 I am asking for an exception for [1] 0.90. Originally discovered on 0.84
 this is also present on 0.90. The patch [2] has been reviewed by Sascha
 and Tomeu already and it is low risk. Otherwise Arabic will be unusable
 as this effects the Journal and the Activities list view.

 I think there should be a big FIXME comment with a reference to a
 ticket in trac because it's a hack and because we really need to find
 an appropriate fix in the near future.

 Also, we don't have plurals in any other place?

 Regards,

 Tomeu

 http://bugs.sugarlabs.org/attachment/ticket/2354/0001-If-the-string-does-not-contain-a-conversion-specifie.patch

 The latest patch does add the comment.

Sorry, I was referring to a ticket about correctly translating strings
with plurals. If you want to use the same ticket, at least it should
be clear that it is about a proper solution and not just about the
crash. It also helps if it starts with FIXME.

 I will check if there are other plurals at other places - none I am aware of
 for now.

I have only found the activity updater.

Regards,

Tomeu

 Regards,
   Simon

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


Re: [Sugar-devel] Managing own patches on patchwork (was: Re: [PATCH] Announce file transfer capabilities #1603)

2010-09-24 Thread Tomeu Vizoso
On Tue, Sep 21, 2010 at 02:14, James Cameron qu...@laptop.org wrote:
 On Mon, Sep 20, 2010 at 10:57:49PM +0200, Sascha Silbe wrote:
 BTW, it would be nice if patch submitters would update the state of their
 own patches on patchwork [1], especially if they get superseded by newer
 patch versions or accepted into mainline.
 This is entirely optional, but helps reducing the load on maintainers.

 Neat.  Didn't know I could do that.

 Advice for others: get an account if you don't have one yet, log in,
 look in the patches list, identify those that are superceded, click on
 them, update the state and optionally click on archived, then update.

Just did it for the patches I submitted, if others could do the same
would be great.

Thanks,

Tomeu

 --
 James Cameron
 http://quozl.linux.org.au/
 ___
 Sugar-devel mailing list
 Sugar-devel@lists.sugarlabs.org
 http://lists.sugarlabs.org/listinfo/sugar-devel

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


Re: [Sugar-devel] Sugar on Fedora and Sugar on a Stick QA Processes Announcement

2010-09-23 Thread Tomeu Vizoso
On Wed, Sep 22, 2010 at 10:50, Peter Robinson pbrobin...@gmail.com wrote:
 Hi All,

 As some of you know I was at FUDCon Zurich last weekend. I took the
 opportunity to sit down with Adam Williamson who is in charge of the
 Fedora QA team and process to discuss how we could incorporate Sugar
 and SoaS testing into the QA process.

 Adam agreed that we would be able to incorporate Sugar into the
 Desktop QA which will expand our testing massively as Fedora has a
 great QA team. It will also have the ability to allow us to block a
 release if there is things broken. That is a double edged sword as if
 its broken we'll also need to pull out all stops to ensure it is fixed
 as well, but overall I believe that is positive!

 In the short term this won't affect this release too much but I will
 be spending some time to define the criteria for Alpha, Beta and Final
 releases. It will also mean we have official spins for each of the
 Alpha, Beta as well as the usual Final releases. While we will see the
 start of the benefits for the home run this will really start to kick
 in for the SoaSv5 release process.

 Overall I think this is a massively positive opportunity for Sugar as
 it opens it out more to the wider Fedora community and allows us to
 get involved in the Fedora QA more and define what is important for us
 for our releases and allows us to ride on the coattails and gain the
 benefit of the awesome work that Adam and his team are doing upstream.

Sounds really excellent, congratulations. Please ping me when you need
anything from upstream.

There's a lot of value for Sugar upstream in our releases getting
packaged so quickly in Fedora and the testing will have as well a big
impact.

Regards,

Tomeu

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

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


Re: [Sugar-devel] [SoaS] Sugar on Fedora and Sugar on a Stick QA Processes Announcement

2010-09-23 Thread Tomeu Vizoso
On Wed, Sep 22, 2010 at 20:07, David Farning dfarn...@gmail.com wrote:
 On Wed, Sep 22, 2010 at 3:50 AM, Peter Robinson pbrobin...@gmail.com wrote:
 Hi All,

 As some of you know I was at FUDCon Zurich last weekend. I took the
 opportunity to sit down with Adam Williamson who is in charge of the
 Fedora QA team and process to discuss how we could incorporate Sugar
 and SoaS testing into the QA process.

 Adam agreed that we would be able to incorporate Sugar into the
 Desktop QA which will expand our testing massively as Fedora has a
 great QA team. It will also have the ability to allow us to block a
 release if there is things broken. That is a double edged sword as if
 its broken we'll also need to pull out all stops to ensure it is fixed
 as well, but overall I believe that is positive!

 In the short term this won't affect this release too much but I will
 be spending some time to define the criteria for Alpha, Beta and Final
 releases. It will also mean we have official spins for each of the
 Alpha, Beta as well as the usual Final releases. While we will see the
 start of the benefits for the home run this will really start to kick
 in for the SoaSv5 release process.

 Overall I think this is a massively positive opportunity for Sugar as
 it opens it out more to the wider Fedora community and allows us to
 get involved in the Fedora QA more and define what is important for us
 for our releases and allows us to ride on the coattails and gain the
 benefit of the awesome work that Adam and his team are doing upstream.

 That is excellent news.  That will make my life much easier as I work
 to get Ubuntu Sugar Remix approved as a official Ubuntu release.  We
 are targeting the 11.04 release for inclusion.

 I hope we can contribute as much back to the ecosystem as the SoaS has
 contributed:)  I am hoping to start by engaging the ubuntu translation
 community.

Sounds very good, looking forward to work more closely with the Ubuntu
community.

Regards,

Tomeu

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

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


Re: [Sugar-devel] [PATCH] implements http://bugs.sugarlabs.org/ticket/1106 - Browse: No preview in Journal for downloaded image

2010-09-23 Thread Tomeu Vizoso
On Wed, Sep 22, 2010 at 17:44,  godi...@sugarlabs.org wrote:
 From: Gonzalo Odiard godi...@sugarlabs.org

 this patch adressed comments from silbe about segregate the check of a image 
 mime type and use of sugar.style constant colors
 now opens the image in the original size because we don't want scale up small 
 images

Just two small remarks:

- the commit subject line should be short but tell enough of the
commit to spot most things easily. Just appending #1234 at the end may
be enough.

- the rest of the commit message should be addressed to someone
reading git log in the future. So it should be about the commit as a
whole and not about a particular revision of it.

If there's anything specific to the proposed patch you want to note
when sending it, you can use the --compose arg to git-send-email.

Regards,

Tomeu

 ---
  downloadmanager.py |   46 ++
  1 files changed, 46 insertions(+), 0 deletions(-)

 diff --git a/downloadmanager.py b/downloadmanager.py
 index 3eec649..ed68d82 100644
 --- a/downloadmanager.py
 +++ b/downloadmanager.py
 @@ -35,6 +35,7 @@ from sugar.datastore import datastore
  from sugar import profile
  from sugar import mime
  from sugar.graphics.alert import Alert, TimeoutAlert
 +from sugar.graphics import style
  from sugar.graphics.icon import Icon
  from sugar.activity import activity

 @@ -192,12 +193,57 @@ class Download:
                 sniffed_mime_type = mime.get_for_file(self._target_file.path)
                 self.dl_jobject.metadata['mime_type'] = sniffed_mime_type

 +            if self._check_image_mime_type():
 +                self.dl_jobject.metadata['preview'] = 
 self._get_preview_image()
 +
             datastore.write(self.dl_jobject,
                             transfer_ownership=True,
                             reply_handler=self._internal_save_cb,
                             error_handler=self._internal_save_error_cb,
                             timeout=360 * 
 DBUS_PYTHON_TIMEOUT_UNITS_PER_SECOND)

 +
 +    def _check_image_mime_type(self):
 +        pixbuf_mime_types = []
 +        for pixbuf_format in gtk.gdk.pixbuf_get_formats():
 +            pixbuf_mime_types.extend(pixbuf_format['mime_types'])
 +
 +        return self._mime_type in pixbuf_mime_types
 +
 +    def _get_preview_image(self):
 +        preview_width, preview_height = style.zoom(300), style.zoom(225)
 +
 +        pixbuf = gtk.gdk.pixbuf_new_from_file(self._target_file.path)
 +        width, height = pixbuf.get_width(), pixbuf.get_height()
 +
 +
 +        if (width  preview_width) or (height  preview_height):
 +            scale_x = float(width) / preview_width
 +            scale_y = float(height) / preview_height
 +            scale = max(scale_x,scale_y)
 +
 +            pixbuf = pixbuf.scale_simple(float(width) / scale, height / 
 scale,
 +                                     gtk.gdk.INTERP_BILINEAR)
 +
 +        width, height = pixbuf.get_width(), pixbuf.get_height()
 +
 +        pixbuf2 = gtk.gdk.Pixbuf(gtk.gdk.COLORSPACE_RGB, 
 pixbuf.get_has_alpha(),
 +            pixbuf.get_bits_per_sample(), preview_width, preview_height)
 +
 +        pixbuf2.fill(style.COLOR_WHITE.get_int())
 +
 +        margin_x, margin_y = (preview_width - width) / 2, (preview_height - 
 height) / 2
 +
 +        pixbuf.copy_area(0, 0, width, height, pixbuf2, margin_x, margin_y)
 +
 +        preview_data = []
 +        def save_func(buf, data):
 +            data.append(buf)
 +
 +        pixbuf2.save_to_callback(save_func, 'png', user_data=preview_data)
 +        preview_data = ''.join(preview_data)
 +        return dbus.ByteArray(preview_data)
 +
     def __start_response_cb(self, alert, response_id):
         global _active_downloads
         if response_id is gtk.RESPONSE_CANCEL:
 --
 1.7.2.3

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

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


Re: [Sugar-devel] Bug #1742

2010-09-22 Thread Tomeu Vizoso
On Tue, Sep 21, 2010 at 20:21, Dipankar Patro dipan...@seeta.in wrote:

 Hi,

 I am working on the bug : http://bugs.sugarlabs.org/ticket/1742

 I investigated a bit and found that the BuddyMenu in Neighbourhood view is
 not getting updated without restart.
 It would be helpful to get some pointers on how to update the buddy status
 without restarting in BuddyMenu.

I see two options:

1. Make the palette listen for friends changes
2. See why the palette is not being disposed when it pops down

Ideally we would make both 1 and 2 but I think just 2 is the most
appropriate course of action.

You may need to read about reference counting and garbage collection
in Python in order to understand what's going on.

Regards,

Tomeu

 Regards,
 Dipankar


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


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


Re: [Sugar-devel] SL bug #1520

2010-09-22 Thread Tomeu Vizoso
On Tue, Sep 21, 2010 at 20:50, Sascha Silbe
sascha-ml-reply-to-201...@silbe.org wrote:
 Excerpts from Mukul Gupta's message of Tue Sep 21 20:06:11 +0200 2010:

 I had a word with Bernie regarding the issue and he says that probably newer
 versions of the X server actually implement XUngrabKey() with keycode= Any
 Key as specified in the man-page. He said he had seen the source code and
 someone (whot) reworked that function sometime back, probably fixing up the
 bug.

 What component (package) is that in and which version fixed it? Or which
 source file and function contains the change so I can try scanning the
 repo?

The most relevant changes I have found are:

commit ff1d6244eba8367a8d50601ca393e951c60c94b6
Author: Peter Hutterer peter.hutte...@who-t.net
Date:   Mon Jun 1 12:14:52 2009 +1000

input: add support for XIAnyModifier in passive XI2 grabs.

commit 80ea32ad4f1440d068e18db65830f45498703b09
Author: Peter Hutterer peter.hutte...@who-t.net
Date:   Mon Jun 1 12:06:55 2009 +1000

dix: switch grab checking from unsigned shorts to unsigned ints

XIAnyModifier is outside of the unsigned short range.

Signed-off-by: Peter Hutterer peter.hutte...@who-t.net

Regards,

Tomeu

 Sascha

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

 ___
 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] [PATCH] Don't miss early nick updates from our contacts #2355

2010-09-22 Thread Tomeu Vizoso
We were receiving the nick before the BuddyModel for that contact
had been created, so we were failing to store it. This means we
create the BuddyModel as soon as we have a contact-id but Neighborhood
defers buddy-added emission until we have gotten the key property.
---
 src/jarabe/model/neighborhood.py |   26 --
 1 files changed, 16 insertions(+), 10 deletions(-)

diff --git a/src/jarabe/model/neighborhood.py b/src/jarabe/model/neighborhood.py
index fc7a0f1..ed23f7f 100644
--- a/src/jarabe/model/neighborhood.py
+++ b/src/jarabe/model/neighborhood.py
@@ -160,8 +160,7 @@ class _Account(gobject.GObject):
 'activity-removed': (gobject.SIGNAL_RUN_FIRST,
  gobject.TYPE_NONE, ([object])),
 'buddy-added':  (gobject.SIGNAL_RUN_FIRST,
- gobject.TYPE_NONE,
- ([object, object, object, object])),
+ gobject.TYPE_NONE, ([object, object, 
object])),
 'buddy-updated':(gobject.SIGNAL_RUN_FIRST,
  gobject.TYPE_NONE, ([object, object])),
 'buddy-removed':(gobject.SIGNAL_RUN_FIRST,
@@ -536,8 +535,6 @@ class _Account(gobject.GObject):
 
 def __got_buddy_info_cb(self, handle, nick, properties):
 logging.debug('_Account.__got_buddy_info_cb %r', handle)
-self.emit('buddy-added', self._buddy_handles[handle], nick,
-  properties.get('key', None), handle)
 self.emit('buddy-updated', self._buddy_handles[handle], properties)
 
 def __get_contact_attributes_cb(self, attributes):
@@ -587,8 +584,8 @@ class _Account(gobject.GObject):
 error_handler=partial(self.__error_handler_cb,
   'BuddyInfo.GetCurrentActivity'),
 timeout=_QUERY_DBUS_TIMEOUT)
-else:
-self.emit('buddy-added', contact_id, nick, None, handle)
+
+self.emit('buddy-added', contact_id, nick, handle)
 
 def __got_activities_cb(self, buddy_handle, activities):
 logging.debug('_Account.__got_activities_cb %r %r', buddy_handle,
@@ -811,7 +808,7 @@ class Neighborhood(gobject.GObject):
 if needs_reconnect:
 account.Reconnect()
 
-def __buddy_added_cb(self, account, contact_id, nick, key, handle):
+def __buddy_added_cb(self, account, contact_id, nick, handle):
 logging.debug('__buddy_added_cb %r', contact_id)
 
 if contact_id in self._buddies:
@@ -822,12 +819,9 @@ class Neighborhood(gobject.GObject):
 nick=nick,
 account=account.object_path,
 contact_id=contact_id,
-key=key,
 handle=handle)
 self._buddies[contact_id] = buddy
 
-self.emit('buddy-added', buddy)
-
 def __buddy_updated_cb(self, account, contact_id, properties):
 logging.debug('__buddy_updated_cb %r', contact_id)
 if contact_id is None:
@@ -840,9 +834,21 @@ class Neighborhood(gobject.GObject):
 return
 
 buddy = self._buddies[contact_id]
+
+is_new = buddy.props.key is None and 'key' in properties
+
 if 'color' in properties:
 buddy.props.color = XoColor(properties['color'])
 
+if 'key' in properties:
+buddy.props.key = properties['key']
+
+if 'nick' in properties:
+buddy.props.nick = properties['nick']
+
+if is_new:
+self.emit('buddy-added', buddy)
+
 def __buddy_removed_cb(self, account, contact_id):
 logging.debug('Neighborhood.__buddy_removed_cb %r', contact_id)
 if contact_id not in self._buddies:
-- 
1.7.2.3

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


Re: [Sugar-devel] [PATCH] Pass the contact-id to the buddy-removed signal instead of the handle #2349

2010-09-21 Thread Tomeu Vizoso
On Mon, Sep 20, 2010 at 22:39, Sascha Silbe
sascha-ml-reply-to-201...@silbe.org wrote:
 Excerpts from Tomeu Vizoso's message of Mon Sep 20 14:56:04 +0200 2010:

 ---

 Would have been nice to note that this is a regression and callers
 expect the contact_id instead of the handle. At first I was worried that
 this might break other code, but the patch actually makes the listeners
 work again.

Seems like this bug has been there since the signal was added, but
indeed I can make explicit that I'm not changing the signal signature
but passing the expected argument.

Thanks,

Tomeu

 Reviewed-By: Sascha Silbe sascha-...@silbe.org

 Sascha

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

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


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


Re: [Sugar-devel] [PATCH] Added busy cursor when we open any section in control panel. (Ticket #245)

2010-09-21 Thread Tomeu Vizoso
On Mon, Sep 20, 2010 at 22:33, Sascha Silbe
sascha-ml-reply-to-201...@silbe.org wrote:
 Excerpts from Ishan Bansal's message of Mon Sep 20 17:36:03 +0200 2010:

 The sections in control panel should activate busy cursor so that user could 
 be given a impression that their request is in progress.

 Like for the other patch, please wrap lines so they fit into 80 columns
 (70-75 for the subject).

 [src/jarabe/controlpanel/gui.py]
 @@ -214,11 +214,14 @@ class ControlPanel(gtk.Window):
                           globals(), locals(), ['model'])
          model = ModelWrapper(mod)


 +        self.get_window().set_cursor(gtk.gdk.Cursor(gtk.gdk.WATCH))
 +
          self._section_view = view_class(model,
                                          self._options[option]['alerts'])

          self._set_canvas(self._section_view)
          self._section_view.show()
 +        self.get_window().set_cursor(None)

 The cursor shape is global state, so it should be reset in a finally:
 clause with everything between the two set_cursor() calls in the try:
 block.

There's also the question of which window we want the cursor to be
changed. As the CP is modal, would we want it to be on the whole
screen?

If so, we could add a public method on HomeWindow which would be used
here and in the other places where we are changing the cursor.

It could also prove handy in debugging wtf the cursor is not coming
back to the default shape in the future.

Regards,

Tomeu

 Sascha

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

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


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


Re: [Sugar-devel] [PATCH] Pass the contact-id to the buddy-removed signal instead of the handle #2349

2010-09-21 Thread Tomeu Vizoso
Hi,

I'm proposing this patch for inclusion in master during the hard code
freeze period as per
http://wiki.sugarlabs.org/go/0.90/Roadmap#Schedule

The benefit is a more consistent neighborhood view and the risk is very low.

Thanks,

Tomeu

On Mon, Sep 20, 2010 at 14:56, Tomeu Vizoso
tomeu.viz...@collabora.co.uk wrote:
 ---
  src/jarabe/model/neighborhood.py |    3 ++-
  1 files changed, 2 insertions(+), 1 deletions(-)

 diff --git a/src/jarabe/model/neighborhood.py 
 b/src/jarabe/model/neighborhood.py
 index 76a0a7d..9d82db3 100644
 --- a/src/jarabe/model/neighborhood.py
 +++ b/src/jarabe/model/neighborhood.py
 @@ -387,8 +387,9 @@ class _Account(gobject.GObject):
             if handle in self._buddy_handles:
                 presence_type, status_, message_ = presence
                 if presence_type == CONNECTION_PRESENCE_TYPE_OFFLINE:
 +                    contact_id = self._buddy_handles[handle]
                     del self._buddy_handles[handle]
 -                    self.emit('buddy-removed', handle)
 +                    self.emit('buddy-removed', contact_id)

     def __buddy_info_updated_cb(self, handle, properties):
         logging.debug('_Account.__buddy_info_updated_cb %r', handle)
 --
 1.7.2.3

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

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


Re: [Sugar-devel] [PATCH] Make sure we don't change the owner's colors because of a network event #2348

2010-09-21 Thread Tomeu Vizoso
On Mon, Sep 20, 2010 at 22:45, Sascha Silbe
sascha-ml-reply-to-201...@silbe.org wrote:
 Excerpts from Tomeu Vizoso's message of Mon Sep 20 14:55:28 +0200 2010:

 ---
  src/jarabe/model/neighborhood.py |    2 +-
  1 files changed, 1 insertions(+), 1 deletions(-)

 diff --git a/src/jarabe/model/neighborhood.py 
 b/src/jarabe/model/neighborhood.py
 index b808e12..76a0a7d 100644
 --- a/src/jarabe/model/neighborhood.py
 +++ b/src/jarabe/model/neighborhood.py
 @@ -829,7 +829,7 @@ class Neighborhood(gobject.GObject):

      def __buddy_updated_cb(self, account, contact_id, properties):
          logging.debug('__buddy_updated_cb %r', contact_id)
 -        if contact_id not in self._buddies:
 +        if contact_id is None or contact_id not in self._buddies:
              logging.debug('__buddy_updated_cb Unknown buddy with contact_id 
 %r',
                            contact_id)
              return


 I guess this is the correct change, but we should note exactly when
 contact_id is None and why we simply ignore that case. At least to me
 it isn't obvious from the code. It feels strange to receive an update
 for Buddy None.

Agreed, the history behind is that we may get presence updates for
contacts from which we haven't gotten their contact-ids nor other info
yet. I have plans to fix it in tp-gabble because it also gives us an
opportunity for reducing the bandwidth used, but it will take a bit
more time.

I'm going to make it clearer in the code and repost the patch.

Regards,

Tomeu

 Sascha

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

 ___
 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] [PATCH] Make sure we don't change the owner's colors because of a network event #2348

2010-09-21 Thread Tomeu Vizoso
Because the owner is stored in Neighborhood._buddies in the key None.
---
 src/jarabe/model/neighborhood.py |4 
 1 files changed, 4 insertions(+), 0 deletions(-)

diff --git a/src/jarabe/model/neighborhood.py b/src/jarabe/model/neighborhood.py
index b808e12..ff973fd 100644
--- a/src/jarabe/model/neighborhood.py
+++ b/src/jarabe/model/neighborhood.py
@@ -829,6 +829,10 @@ class Neighborhood(gobject.GObject):
 
 def __buddy_updated_cb(self, account, contact_id, properties):
 logging.debug('__buddy_updated_cb %r', contact_id)
+if contact_id is None:
+# Don't know the contact-id yet, will get the full state later
+return
+
 if contact_id not in self._buddies:
 logging.debug('__buddy_updated_cb Unknown buddy with contact_id 
%r',
   contact_id)
-- 
1.7.2.3

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


  1   2   3   4   5   6   7   8   9   10   >