Re: [Sugar-devel] porting Gstreamer Activities to PYGobject and Gstreamer 1.0

2012-08-01 Thread Daniel Narvaez
You mean the activity or gst-plugin-speak?

On Thursday, 2 August 2012, Flavio Danesse wrote:

> Speak is almost completely ported to gtk and GStreamer 1.0, there are only
> a few corrections.
>
>
> 2012/8/1 Daniel Narvaez 
>
> No, it needs to be ported to 1.0. The configure.ac currently links to
> 0.10 and I suppose there might be API changes we need to adapt to.
>
> On 1 August 2012 22:55, Gonzalo Odiard  wrote:
> > Thanks!
> > Do you know if the gstreamer-espeak plugin works?
> >
> > Gonzalo
> >
> >
> > On Wed, Aug 1, 2012 at 5:39 PM, Daniel Narvaez 
> wrote:
> >>
> >> Hello,
> >>
> >> I added Gstreamer 1.0 to sugar-build. I tested with a sample video
> >> player and it seems to work fine, no additional script is required.
> >>
> >> If you are using a plugin which is not built, please let me know and
> >> I'll add the required system dependencies.
> >>
> >> On 31 July 2012 01:40, Simon Schampijer  wrote:
> >> > Hey Activity team,
> >> >
> >> > so in the last days we have been looking here at Gstreamer and the
> >> > situation
> >> > in regards to Pygobject and GTK+ 3.
> >> >
> >> > All in all in order to use Gstreamer with introspection we have to use
> >> > Gstreamer 1.0 (0.12). Version 0.10 is dead, and will never really work
> >> > with
> >> > introspection (see [1] and what we know as well from talking with the
> >> > Gstreamer devs).
> >> >
> >> > I talked to Peter and Gstreamer-1.0 should be packaged with F18, see
> >> > recent
> >> > discussions [2].
> >> >
> >> > In the meantime when you port your activity you can build Gstreamer on
> >> > your
> >> > system and use a script to point your activity to the new Gstreamer
> >> > version
> >> > [3][4].
> >> >
> >> > If you are stuck while poring you can have a look at the Pitivi
> porting
> >> > branch [5].
> >> >
> >> > Regards,
> >> >Simon
> >> >
> >> > [1] https://wiki.ubuntu.com/Novacut/GStreamer1.0#Python_Porting_Guide
> >> > [2] http://www.spinics.net/lists/fedora-desktop/msg07545.html
> >> > [3]
> >> >
> >> >
> http://gstreamer.freedesktop.org/data/doc/gstreamer/head/faq/html/chapter-git.html#git-anon
> >> > [4]
> >> >
> >> >
> http://gstreamer.freedesktop.org/data/doc/gstreamer/head/faq/html/chapter-developing.html#developing-uninstalled-gstreamer
> >> > [5] https://github.com/nekohayo/pitivi/tree/pygi
> >> > ___
> >> > Sugar-devel mailing list
> >> > Sugar-devel@lists.sugarlabs.org
> >> > http://lists.sugarlabs.org/listinfo/sugar-devel
> >>
> >>
> >>
> >> --
> >> Daniel Narvaez
> >> ___
> >> Sugar-devel mailing list
> >> Sugar-devel@lists.sugarlabs.org
> >> http://lists.sugarlabs.org/listinfo/sugar-devel
> >
> >
>
>
>
> --
> Daniel Narvaez
> ___
> Sugar-devel mailing list
> Sugar-deve
>
>

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


Re: [Sugar-devel] [DESIGN] Proposal: Lease expiry information display in My Settings -> About My Computer

2012-08-01 Thread James Cameron
On Thu, Aug 02, 2012 at 12:55:23AM +0530, Anish Mangal wrote:
> Your probably right. IIRC the idea was to make that information
> visible alongside the Serial Number.

And what I'm saying is that the lease expiry does in no way identify a
system, so it should not be in a section with a title "Identity".

> Does it make sense to move it to Software?

No.

> I don't want to rename the sections because this feature should only
> be visible when the lease file is actually present.

In other words, you do not want to fix the problems with the section
titles.  I understand that.  But you did ask for review.

Looking again at the About my Computer panel, there are other
inconsistencies:

- the Build in the Software section shows the hardware model,
  (hardware model should not be in a Software section),

- the Build shows both the OLPC OS version _and_ the build number,

- the version of Fedora is not shown,

I think the Identity section might change to Hardware, and move the
hardware model up there from Build.

Here's a suggested layout:

Hardware
Manufacturer: OLPC
Model: XO-1.5
Serial Number: SHC952A

Firmware:
System: Q3C09   Wireless: 9.70.20.p0

Software:
Release: 12.1.0 Build: 18
Distribution: FedoraVersion: 17
Sugar: 0.96.2

The panel already has a scroll bar to fit the "Fill license" item in.

On Thu, Aug 02, 2012 at 12:00:19AM +0100, Gary Martin wrote:
> If it moves to Software, perhaps it should go below the Firmware
> line? James is that more inkeeping with the implementation? The
> other option is for a new Lease section below the Identity section.

It need not be in keeping with the implementation, that was my
original point.

-- 
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] [PATCH sugar-toolkit (gtk2)] props.accelerator available at ToggleToolButton SL#3774

2012-08-01 Thread Daniel Francis
Signed-off-by: Daniel Francis 
---
 src/sugar/graphics/toggletoolbutton.py | 40 ++
 1 file changed, 40 insertions(+)

diff --git a/src/sugar/graphics/toggletoolbutton.py 
b/src/sugar/graphics/toggletoolbutton.py
index 012c2b0..63d843f 100644
--- a/src/sugar/graphics/toggletoolbutton.py
+++ b/src/sugar/graphics/toggletoolbutton.py
@@ -19,6 +19,8 @@
 STABLE.
 """
 
+import logging
+
 import gobject
 import gtk
 
@@ -26,6 +28,34 @@ from sugar.graphics.icon import Icon
 from sugar.graphics.palette import Palette, ToolInvoker
 
 
+def _add_accelerator(tool_button):
+if not tool_button.props.accelerator or not tool_button.get_toplevel() or \
+not tool_button.child:
+return
+
+# TODO: should we remove the accelerator from the prev top level?
+
+accel_group = tool_button.get_toplevel().get_data('sugar-accel-group')
+if not accel_group:
+logging.warning('No gtk.AccelGroup in the top level window.')
+return
+
+keyval, mask = gtk.accelerator_parse(tool_button.props.accelerator)
+# the accelerator needs to be set at the child, so the gtk.AccelLabel
+# in the palette can pick it up.
+tool_button.child.add_accelerator('clicked', accel_group, keyval, mask,
+  gtk.ACCEL_LOCKED | gtk.ACCEL_VISIBLE)
+
+
+def _hierarchy_changed_cb(tool_button, previous_toplevel):
+_add_accelerator(tool_button)
+
+
+def setup_accelerator(tool_button):
+_add_accelerator(tool_button)
+tool_button.connect('hierarchy-changed', _hierarchy_changed_cb)
+
+
 class ToggleToolButton(gtk.ToggleToolButton):
 
 __gtype_name__ = 'SugarToggleToolButton'
@@ -72,6 +102,16 @@ class ToggleToolButton(gtk.ToggleToolButton):
 def set_tooltip(self, text):
 self.set_palette(Palette(text))
 
+def set_accelerator(self, accelerator):
+self._accelerator = accelerator
+setup_accelerator(self)
+
+def get_accelerator(self):
+return self._accelerator
+
+accelerator = gobject.property(type=str, setter=set_accelerator,
+getter=get_accelerator)
+
 def do_expose_event(self, event):
 allocation = self.get_allocation()
 child = self.get_child()
-- 
1.7.11.2

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


[Sugar-devel] [PATCH sugar-toolkit-gtk3] props.accelerator available at ToggleToolButton SL#3774

2012-08-01 Thread Daniel Francis
Signed-off-by: Daniel Francis 

---
 src/sugar3/graphics/toggletoolbutton.py | 39 +
 1 file changed, 39 insertions(+)

diff --git a/src/sugar3/graphics/toggletoolbutton.py 
b/src/sugar3/graphics/toggletoolbutton.py
index 94cc6ae..f3a9c57 100644
--- a/src/sugar3/graphics/toggletoolbutton.py
+++ b/src/sugar3/graphics/toggletoolbutton.py
@@ -19,6 +19,8 @@
 STABLE.
 """
 
+import logging
+
 from gi.repository import GObject
 from gi.repository import Gtk
 
@@ -26,6 +28,33 @@ from sugar3.graphics.icon import Icon
 from sugar3.graphics.palette import Palette, ToolInvoker
 
 
+def _add_accelerator(tool_button):
+if not tool_button.props.accelerator or not tool_button.get_toplevel() or \
+not tool_button.get_child():
+return
+
+# TODO: should we remove the accelerator from the prev top level?
+if not hasattr(tool_button.get_toplevel(), 'sugar_accel_group'):
+logging.warning('No Gtk.AccelGroup in the top level window.')
+return
+
+accel_group = tool_button.get_toplevel().sugar_accel_group
+keyval, mask = Gtk.accelerator_parse(tool_button.props.accelerator)
+# the accelerator needs to be set at the child, so the Gtk.AccelLabel
+# in the palette can pick it up.
+tool_button.get_child().add_accelerator('clicked', accel_group, keyval, 
mask,
+  Gtk.AccelFlags.LOCKED | 
Gtk.AccelFlags.VISIBLE)
+
+
+def _hierarchy_changed_cb(tool_button, previous_toplevel):
+_add_accelerator(tool_button)
+
+
+def setup_accelerator(tool_button):
+_add_accelerator(tool_button)
+tool_button.connect('hierarchy-changed', _hierarchy_changed_cb)
+
+
 class ToggleToolButton(Gtk.ToggleToolButton):
 
 __gtype_name__ = 'SugarToggleToolButton'
@@ -72,6 +101,16 @@ class ToggleToolButton(Gtk.ToggleToolButton):
 def set_tooltip(self, text):
 self.set_palette(Palette(text))
 
+def set_accelerator(self, accelerator):
+self._accelerator = accelerator
+setup_accelerator(self)
+
+def get_accelerator(self):
+return self._accelerator
+
+accelerator = GObject.property(type=str, setter=set_accelerator,
+getter=get_accelerator)
+
 def do_expose_event(self, event):
 allocation = self.get_allocation()
 child = self.get_child()
-- 
1.7.11.2

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


Re: [Sugar-devel] [DESIGN] Proposal: Lease expiry information display in My Settings -> About My Computer

2012-08-01 Thread Anish Mangal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Thursday 02 August 2012 04:30 AM, Gary Martin wrote:
> On 1 Aug 2012, at 20:25, Anish Mangal  wrote:
>
>>
> On Friday 20 July 2012 04:05 AM, James Cameron wrote:
> >>> I don't think it should be in a section titled "Identity", because it
> >>> isn't an identifier, and is only related to serial number because of
> >>> implementation details.
>
> Your probably right. IIRC the idea was to make that information visible
> alongside the Serial Number.
>
> Does it make sense to move it to Software?
>
> > I don't have a strong objection to it being in Identity, but then
again, I am not aware of many of the implementation details of the code
behind it – also likely true for most folks reading it in the field.
>
> > If it moves to Software, perhaps it should go below the Firmware
line? James is that more inkeeping with the implementation? The other
option is for a new Lease section below the Identity section.
>
> I don't want to rename the sections because this feature should only be
> visible when the lease file is actually present.
>
> > On this point, the code seems to not behave you describe above.
Testing on an XO-1, the DX3 build 143 International, I see an item in
the Identity section saying "Lease: Not available". The wording "Not
available" suggests something is missing from my XO when actually this
machine does not need a lease, and is unsecured, this line of
information should not be displayed at all to the user.
>

Yes, that is correct. That change will be made when the code is ported
over to mainline.

> > Regards,
> > --Gary
>
>
> >>>
> >>> I don't wish to constrain your creativity by saying how to fix that
> >>> though. I'm sure you can imagine many alternatives.
> >>>
>
>
>>
>> ___
>> 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

- -- 
Anish Mangal
Sugar Labs
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJQGdpRAAoJEBoxUdDHDZVpQYIH/11UXRL+4PY23ijV9CoL0Ph6
7vexudcSbOrVNSnPCzFOaKpu9tYxSP8nYmv4S0X8KEGi4PbyAJG5O2vDb67A71SK
TgbGXPqdx6FIa/i+n0axl46DAn21vQLzUQp+wFT9GvgtiBqVJW8iM/T9PlRD8phP
RldsRei0jbA4AdxSHLhjyQypiE7Lcnio6FYAhrW0sYeydVLyXOpCSkv4XyQFcL5t
/liB5bKs1YX9EirFJPJURuKKGWmQ/GC//uk3vmWKV+KaBJwE9koirNU4OvjSwNVX
g51nmt1LwXbmYDtDWgYeUm+5hUPWbjxsFRskgW1Zgedo44XSpYz5r0DVhFzbT6I=
=Xr6U
-END PGP SIGNATURE-

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


Re: [Sugar-devel] [DESIGN] Proposal: Contol-Panel packaging

2012-08-01 Thread Sridhar Dhanapalan
On 30 July 2012 23:26, Jerry Vonau  wrote:
> The idea works well for users of Dextrose where OLPC-AU as a deployment
> could omit features that are still under development and not show the
> icon the control-panel at all. I'm not asking for anything to be
> removed, just packaged and made available separately.
>
> Once the spec file is altered OOB users would state which of the applets
> to install or substitute their own. The one rub would be having to alter
> the sugar-desktop group definition available from fedora's repos.
>
> Just trying to ease the burden on some of us deployments.

This feature would make maintenance of code and updates in the field
much easier for us.

As a deployment, we would like the choice of which CP applets to
include, or even make substitutions if need be. We don't want to be
making unnecessary patches or building our own Sugar RPM just for
this. That would in effect be a fork of Sugar and become a maintenance
burden for us.

We use yum to provide automatic updates to our XOs in the field, and
we must be mindful that large RPMs can have an impact on the school's
Internet connection. If 400 XOs need to download a ~800KB Sugar RPM,
that's 320MB being downloaded, potentially at the same time.

Sridhar


Sridhar Dhanapalan
Engineering Manager
One Laptop per Child Australia
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


Re: [Sugar-devel] porting Gstreamer Activities to PYGobject and Gstreamer 1.0

2012-08-01 Thread Flavio Danesse
Speak is almost completely ported to gtk and GStreamer 1.0, there are only
a few corrections.


2012/8/1 Daniel Narvaez 

> No, it needs to be ported to 1.0. The configure.ac currently links to
> 0.10 and I suppose there might be API changes we need to adapt to.
>
> On 1 August 2012 22:55, Gonzalo Odiard  wrote:
> > Thanks!
> > Do you know if the gstreamer-espeak plugin works?
> >
> > Gonzalo
> >
> >
> > On Wed, Aug 1, 2012 at 5:39 PM, Daniel Narvaez 
> wrote:
> >>
> >> Hello,
> >>
> >> I added Gstreamer 1.0 to sugar-build. I tested with a sample video
> >> player and it seems to work fine, no additional script is required.
> >>
> >> If you are using a plugin which is not built, please let me know and
> >> I'll add the required system dependencies.
> >>
> >> On 31 July 2012 01:40, Simon Schampijer  wrote:
> >> > Hey Activity team,
> >> >
> >> > so in the last days we have been looking here at Gstreamer and the
> >> > situation
> >> > in regards to Pygobject and GTK+ 3.
> >> >
> >> > All in all in order to use Gstreamer with introspection we have to use
> >> > Gstreamer 1.0 (0.12). Version 0.10 is dead, and will never really work
> >> > with
> >> > introspection (see [1] and what we know as well from talking with the
> >> > Gstreamer devs).
> >> >
> >> > I talked to Peter and Gstreamer-1.0 should be packaged with F18, see
> >> > recent
> >> > discussions [2].
> >> >
> >> > In the meantime when you port your activity you can build Gstreamer on
> >> > your
> >> > system and use a script to point your activity to the new Gstreamer
> >> > version
> >> > [3][4].
> >> >
> >> > If you are stuck while poring you can have a look at the Pitivi
> porting
> >> > branch [5].
> >> >
> >> > Regards,
> >> >Simon
> >> >
> >> > [1] https://wiki.ubuntu.com/Novacut/GStreamer1.0#Python_Porting_Guide
> >> > [2] http://www.spinics.net/lists/fedora-desktop/msg07545.html
> >> > [3]
> >> >
> >> >
> http://gstreamer.freedesktop.org/data/doc/gstreamer/head/faq/html/chapter-git.html#git-anon
> >> > [4]
> >> >
> >> >
> http://gstreamer.freedesktop.org/data/doc/gstreamer/head/faq/html/chapter-developing.html#developing-uninstalled-gstreamer
> >> > [5] https://github.com/nekohayo/pitivi/tree/pygi
> >> > ___
> >> > Sugar-devel mailing list
> >> > Sugar-devel@lists.sugarlabs.org
> >> > http://lists.sugarlabs.org/listinfo/sugar-devel
> >>
> >>
> >>
> >> --
> >> Daniel Narvaez
> >> ___
> >> Sugar-devel mailing list
> >> Sugar-devel@lists.sugarlabs.org
> >> http://lists.sugarlabs.org/listinfo/sugar-devel
> >
> >
>
>
>
> --
> Daniel Narvaez
> ___
> 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] [DESIGN] Proposal: Lease expiry information display in My Settings -> About My Computer

2012-08-01 Thread Gary Martin
On 1 Aug 2012, at 20:25, Anish Mangal  wrote:

> 
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> 
> On Friday 20 July 2012 04:05 AM, James Cameron wrote:
>> I don't think it should be in a section titled "Identity", because it
>> isn't an identifier, and is only related to serial number because of
>> implementation details.
> 
> Your probably right. IIRC the idea was to make that information visible
> alongside the Serial Number.
> 
> Does it make sense to move it to Software?

I don't have a strong objection to it being in Identity, but then again, I am 
not aware of many of the implementation details of the code behind it – also 
likely true for most folks reading it in the field.

If it moves to Software, perhaps it should go below the Firmware line? James is 
that more inkeeping with the implementation? The other option is for a new 
Lease section below the Identity section.

> I don't want to rename the sections because this feature should only be
> visible when the lease file is actually present.

On this point, the code seems to not behave you describe above. Testing on an 
XO-1, the DX3 build 143 International, I see an item in the Identity section 
saying "Lease: Not available". The wording "Not available" suggests something 
is missing from my XO when actually this machine does not need a lease, and is 
unsecured, this line of information should not be displayed at all to the user.

Regards,
--Gary

> 
>> 
>> I don't wish to constrain your creativity by saying how to fix that
>> though. I'm sure you can imagine many alternatives.
>> 
> 
> 
> - -- 
> Anish Mangal
> Sugar Labs
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.4.12 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
> 
> iQEcBAEBAgAGBQJQGYKjAAoJEBoxUdDHDZVpA+cH/2tT8rDzqoN3GPZbJhrU+fvR
> bRMw2sDwi+GHw+57WikzKygjeBBiEriKITO9gCtzyNgrQDz6leYTh4RHV2Iva5XK
> r+XGHIs1g1UN66aM6KicdocEEJzAX8ClE44uvyli1bc+q4D2dXtHyHguMeEc+H+0
> n+LQAiaR3HeBSx2bCwvXIchwJvIvIj0+GDYCCfbE2yMCzUI1yuVSUx/f880Ucvod
> 8+fa9Q4d3CATcHdz0wgpGcKw2By2ETjSlMkMuMeJbgivFh7OdMvu3T/4IBi0wz2O
> q94j6gKpEAIDHGn7UeYYFU7W9UebtRRcgg1VEy58w8fa4lrl0ySxd/mZkTnyCUY=
> =iZ6m
> -END PGP SIGNATURE-
> 
> ___
> 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] porting Gstreamer Activities to PYGobject and Gstreamer 1.0

2012-08-01 Thread Daniel Narvaez
No, it needs to be ported to 1.0. The configure.ac currently links to
0.10 and I suppose there might be API changes we need to adapt to.

On 1 August 2012 22:55, Gonzalo Odiard  wrote:
> Thanks!
> Do you know if the gstreamer-espeak plugin works?
>
> Gonzalo
>
>
> On Wed, Aug 1, 2012 at 5:39 PM, Daniel Narvaez  wrote:
>>
>> Hello,
>>
>> I added Gstreamer 1.0 to sugar-build. I tested with a sample video
>> player and it seems to work fine, no additional script is required.
>>
>> If you are using a plugin which is not built, please let me know and
>> I'll add the required system dependencies.
>>
>> On 31 July 2012 01:40, Simon Schampijer  wrote:
>> > Hey Activity team,
>> >
>> > so in the last days we have been looking here at Gstreamer and the
>> > situation
>> > in regards to Pygobject and GTK+ 3.
>> >
>> > All in all in order to use Gstreamer with introspection we have to use
>> > Gstreamer 1.0 (0.12). Version 0.10 is dead, and will never really work
>> > with
>> > introspection (see [1] and what we know as well from talking with the
>> > Gstreamer devs).
>> >
>> > I talked to Peter and Gstreamer-1.0 should be packaged with F18, see
>> > recent
>> > discussions [2].
>> >
>> > In the meantime when you port your activity you can build Gstreamer on
>> > your
>> > system and use a script to point your activity to the new Gstreamer
>> > version
>> > [3][4].
>> >
>> > If you are stuck while poring you can have a look at the Pitivi porting
>> > branch [5].
>> >
>> > Regards,
>> >Simon
>> >
>> > [1] https://wiki.ubuntu.com/Novacut/GStreamer1.0#Python_Porting_Guide
>> > [2] http://www.spinics.net/lists/fedora-desktop/msg07545.html
>> > [3]
>> >
>> > http://gstreamer.freedesktop.org/data/doc/gstreamer/head/faq/html/chapter-git.html#git-anon
>> > [4]
>> >
>> > http://gstreamer.freedesktop.org/data/doc/gstreamer/head/faq/html/chapter-developing.html#developing-uninstalled-gstreamer
>> > [5] https://github.com/nekohayo/pitivi/tree/pygi
>> > ___
>> > Sugar-devel mailing list
>> > Sugar-devel@lists.sugarlabs.org
>> > http://lists.sugarlabs.org/listinfo/sugar-devel
>>
>>
>>
>> --
>> Daniel Narvaez
>> ___
>> Sugar-devel mailing list
>> Sugar-devel@lists.sugarlabs.org
>> http://lists.sugarlabs.org/listinfo/sugar-devel
>
>



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


Re: [Sugar-devel] porting Gstreamer Activities to PYGobject and Gstreamer 1.0

2012-08-01 Thread Gonzalo Odiard
Thanks!
Do you know if the gstreamer-espeak plugin works?

Gonzalo

On Wed, Aug 1, 2012 at 5:39 PM, Daniel Narvaez  wrote:

> Hello,
>
> I added Gstreamer 1.0 to sugar-build. I tested with a sample video
> player and it seems to work fine, no additional script is required.
>
> If you are using a plugin which is not built, please let me know and
> I'll add the required system dependencies.
>
> On 31 July 2012 01:40, Simon Schampijer  wrote:
> > Hey Activity team,
> >
> > so in the last days we have been looking here at Gstreamer and the
> situation
> > in regards to Pygobject and GTK+ 3.
> >
> > All in all in order to use Gstreamer with introspection we have to use
> > Gstreamer 1.0 (0.12). Version 0.10 is dead, and will never really work
> with
> > introspection (see [1] and what we know as well from talking with the
> > Gstreamer devs).
> >
> > I talked to Peter and Gstreamer-1.0 should be packaged with F18, see
> recent
> > discussions [2].
> >
> > In the meantime when you port your activity you can build Gstreamer on
> your
> > system and use a script to point your activity to the new Gstreamer
> version
> > [3][4].
> >
> > If you are stuck while poring you can have a look at the Pitivi porting
> > branch [5].
> >
> > Regards,
> >Simon
> >
> > [1] https://wiki.ubuntu.com/Novacut/GStreamer1.0#Python_Porting_Guide
> > [2] http://www.spinics.net/lists/fedora-desktop/msg07545.html
> > [3]
> >
> http://gstreamer.freedesktop.org/data/doc/gstreamer/head/faq/html/chapter-git.html#git-anon
> > [4]
> >
> http://gstreamer.freedesktop.org/data/doc/gstreamer/head/faq/html/chapter-developing.html#developing-uninstalled-gstreamer
> > [5] https://github.com/nekohayo/pitivi/tree/pygi
> > ___
> > Sugar-devel mailing list
> > Sugar-devel@lists.sugarlabs.org
> > http://lists.sugarlabs.org/listinfo/sugar-devel
>
>
>
> --
> Daniel Narvaez
> ___
> 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] [DESIGN] Proposal: Lease expiry information display in My Settings -> About My Computer

2012-08-01 Thread Ian MacArthur

On 1 Aug 2012, at 20:14, Anish Mangal wrote:

> On Thursday 19 July 2012 08:26 PM, Samuel Greenfeld wrote:
>> Personally I think this would be a reasonable feature.  But prior
>> to this discussion I have never heard of the word "expiry" before.
>> 
>> In US English the synonym "expiration" tends to be used much more 
>> often.  I do not know what the preferred international form is.
>> 
> 
> I don't really know what the correct English would be, but expiration
> sounds okay to me too. In India, we often use the word expiry, but
> could be a common mistake :-)

FWIW (which isn't much) I think "expiry" is the normal British English usage, 
and "expiration" sounds odd.
The British English form is still pretty common in other dialects, particularly 
where the British influence continued past (say) 1776 or thereabouts...
Which is more common I could not say. I imagine both forms are understood...



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


Re: [Sugar-devel] porting Gstreamer Activities to PYGobject and Gstreamer 1.0

2012-08-01 Thread Daniel Narvaez
Hello,

I added Gstreamer 1.0 to sugar-build. I tested with a sample video
player and it seems to work fine, no additional script is required.

If you are using a plugin which is not built, please let me know and
I'll add the required system dependencies.

On 31 July 2012 01:40, Simon Schampijer  wrote:
> Hey Activity team,
>
> so in the last days we have been looking here at Gstreamer and the situation
> in regards to Pygobject and GTK+ 3.
>
> All in all in order to use Gstreamer with introspection we have to use
> Gstreamer 1.0 (0.12). Version 0.10 is dead, and will never really work with
> introspection (see [1] and what we know as well from talking with the
> Gstreamer devs).
>
> I talked to Peter and Gstreamer-1.0 should be packaged with F18, see recent
> discussions [2].
>
> In the meantime when you port your activity you can build Gstreamer on your
> system and use a script to point your activity to the new Gstreamer version
> [3][4].
>
> If you are stuck while poring you can have a look at the Pitivi porting
> branch [5].
>
> Regards,
>Simon
>
> [1] https://wiki.ubuntu.com/Novacut/GStreamer1.0#Python_Porting_Guide
> [2] http://www.spinics.net/lists/fedora-desktop/msg07545.html
> [3]
> http://gstreamer.freedesktop.org/data/doc/gstreamer/head/faq/html/chapter-git.html#git-anon
> [4]
> http://gstreamer.freedesktop.org/data/doc/gstreamer/head/faq/html/chapter-developing.html#developing-uninstalled-gstreamer
> [5] https://github.com/nekohayo/pitivi/tree/pygi
> ___
> Sugar-devel mailing list
> Sugar-devel@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel



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


Re: [Sugar-devel] [DESIGN] Proposal: Lease expiry information display in My Settings -> About My Computer

2012-08-01 Thread Anish Mangal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Friday 20 July 2012 04:05 AM, James Cameron wrote:
> I don't think it should be in a section titled "Identity", because it
> isn't an identifier, and is only related to serial number because of
> implementation details.

Your probably right. IIRC the idea was to make that information visible
alongside the Serial Number.

Does it make sense to move it to Software?

I don't want to rename the sections because this feature should only be
visible when the lease file is actually present.

>
> I don't wish to constrain your creativity by saying how to fix that
> though. I'm sure you can imagine many alternatives.
>


- -- 
Anish Mangal
Sugar Labs
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJQGYKjAAoJEBoxUdDHDZVpA+cH/2tT8rDzqoN3GPZbJhrU+fvR
bRMw2sDwi+GHw+57WikzKygjeBBiEriKITO9gCtzyNgrQDz6leYTh4RHV2Iva5XK
r+XGHIs1g1UN66aM6KicdocEEJzAX8ClE44uvyli1bc+q4D2dXtHyHguMeEc+H+0
n+LQAiaR3HeBSx2bCwvXIchwJvIvIj0+GDYCCfbE2yMCzUI1yuVSUx/f880Ucvod
8+fa9Q4d3CATcHdz0wgpGcKw2By2ETjSlMkMuMeJbgivFh7OdMvu3T/4IBi0wz2O
q94j6gKpEAIDHGn7UeYYFU7W9UebtRRcgg1VEy58w8fa4lrl0ySxd/mZkTnyCUY=
=iZ6m
-END PGP SIGNATURE-

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


Re: [Sugar-devel] [DESIGN] Proposal: Lease expiry information display in My Settings -> About My Computer

2012-08-01 Thread Anish Mangal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Thursday 19 July 2012 08:26 PM, Samuel Greenfeld wrote:
> Personally I think this would be a reasonable feature.  But prior
> to this discussion I have never heard of the word "expiry" before.
> 
> In US English the synonym "expiration" tends to be used much more 
> often.  I do not know what the preferred international form is.
> 

I don't really know what the correct English would be, but expiration
sounds okay to me too. In India, we often use the word expiry, but
could be a common mistake :-)

- --
Anish

> --- SJG
> 
> 
> On Thu, Jul 19, 2012 at 10:40 AM, Rafael Ortiz 
> mailto:raf...@activitycentral.com>>
> wrote:
> 
> 
> 
> On Wed, Jul 18, 2012 at 1:07 PM, Anish Mangal 
> mailto:an...@activitycentral.com>>
> wrote:
> 
> Hi,
> 
> I would like to propose a feature for discussion and inclusion in
> the 0.98 cycle.
> 
> http://wiki.sugarlabs.org/go/Features/Lease_Information_Display
> 
> This feature, which has been tested to work on 0.94 based
> dextrose-3 builds, displays information relating to lease expiry in
> the about my computer section in the my settings menu.
> 
> This feature is valuable for support staff in deployments which
> use OLPC's security system built on the XO laptops, and was
> specifically requested by the OLPC deployment in Paraguay.
> 
> Please go through the feature page for a more in-depth explanation
> and a screenshot. Looking forward to discussion and answering
> queries.
> 
> 
>> +1 to me, it's been used in dextrose w/o problems.
> 
> 
> 
> Cheers, Anish ___ 
> 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
> 
> 
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJQGYAWAAoJEBoxUdDHDZVpWecH/25z/7nHa74cK6CZTiS4CU9h
oVWrv1Y1qmXE1sEZ0/0Tri4zfcrQxq/zIxLxfAKLziVbTtwB1PxGo+E3z2o0CoIH
wNhOB+vFVXeRxlttCzhqoKujenGvWM7DY5EZHcV5tt3gOuctflVlD3j/7aw+lO+u
GeThh+lyMFz1vLvHc3BaQdTQUldx36an5CB8QAqL3gIWeKX+9uXW8UcGu4AUT+p2
U+hv/X/ANPIKqgA8NLAKSWkWLqDMQXB6DqKPHRzp9UM4jFcPB29WUBlq1K77GAFh
GwSYVVBxi9uQOcKrA+JjXV7k+uVTjrcGCa7crLPhLPg5UlJDlYlIYRbYOYnNmqs=
=vhzJ
-END PGP SIGNATURE-
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


Re: [Sugar-devel] [DESIGN] Proposal: Lease expiry information display in My Settings -> About My Computer

2012-08-01 Thread Anish Mangal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Wednesday 25 July 2012 10:46 PM, Daniel Drake wrote:
> On Wed, Jul 18, 2012 at 12:07 PM, Anish Mangal 
>  wrote:
>> I would like to propose a feature for discussion and inclusion in
>> the 0.98 cycle.
>> 
>> http://wiki.sugarlabs.org/go/Features/Lease_Information_Display
>> 
>> This feature is valuable for support staff in deployments which
>> use OLPC's security system built on the XO laptops, and was
>> specifically requested by the OLPC deployment in Paraguay.
> 
> I read the feature page, and I don't really understand the use case
> or problem that needs to be solved. I'm not convinced that changing
> sugar is the right answer, especially when this only affects
> support staff, not regular users.
> 

Well, in a sense, the support staff support our users, so taking care
of them is also important. This might be useful info. for kids in some
cases too (explained later in the email)

> The feature page discusses the case when the lease has expired,
> but this seems like quite the corner case to me. Assuming that XO
> laptops are booted and shutdown on a daily basis, this bit of
> information would only be shown when the following happens:

This information shows the number of days to lease expiration, not
after the lease has expired, and is always shown.

> - The XO is booted in the morning - The lease expires shortly after
> boot - A support staff member happens to pick up that laptop that
> same day, before the laptop gets shut down, and opens "About my
> computer"
> 

One problem they were also trying to get around in Paraguay is that
during vacations, the kids don't go to the schools and hence the
leases expire. If the kids also know about this information, then they
can easily make sure that they don't get 'locked out'

> Any member of support staff that deals with leases is going to need
> to be a little bit familiar with the lease.sig format and
> location. So running "cat /security/lease.sig" at the terminal can
> show the same information - its a little bit technical, but again,
> familiarity is required for this role anyway.

This is EXACTLY what we are trying to get around here. We should not
expect everyone in the support staff (or the kids themselves) to be
proficient enough to open the terminal, type commands, understand
encoded formats etc.

> For the rare occasions when leases need to be checked, running this
> command at a terminal suffices here in Nicaragua at least.
> 

It doesn't in Paraguay, that's why they asked us for this information
to be present in the About my computer section for Dextrose-2.


> It is harder to read the expiry of a sig02 lease from catting the 
> file, but as far as I know those aren't used in Paraguay. If the 
> format is too difficult then perhaps a command line tool in
> bitfrost would be a better solution.
> 
> From a technical perspective, the implementation would need to
> either be quite hacky (parsing lease.sig directly) or use bitfrost.
> Using bitfrost libraries would be OK but the feature page should
> note that this now becomes a dependency of sugar.
> 

Since this feature is only relevant for the XO at the moment, making
use of the bitfrost API would be acceptable to me, but I don't see a
lot wrong here by parsing the lease.sig directly. This file is
supposed to be automatically generated/updated in normal use cases.

> Daniel
> 


- -- 
Anish

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJQGX+oAAoJEBoxUdDHDZVpJfoH/AxBZPrjgQOzvedLVafFggXp
L2JbZnULYBkAz9767CQrlIcLydSWlwry3e8gFKRICcRN/H4Hg8wQnzxNuvIea3sf
i2Q68Px+am0p30w9dM2acBhw2aDzrwa8WyneFsklwQh1DnS88N40rAdLvEeuLFFC
gKwvG98/rCRPJeFiLrCepWPGoRCVNiH7HzTrOw8L4lWAMEWsUlSc9dWqOyP/VCgd
RT4VC2ZDvGV+kwIy5m3FeMBYbRkTq/xSlsSyNpEvp0iewgeXHSUgObkUypsROTMr
aCuh0DCdCpqt9djHxlVQsrbRnv88PTzYVkbytD9hbjfhCLpefDH3wQlMXmX7EH4=
=QmLw
-END PGP SIGNATURE-
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


Re: [Sugar-devel] Engadget post on XO Touch

2012-08-01 Thread Martin Langhoff
On Thu, Jul 26, 2012 at 11:21 PM, Mike Lee  wrote:
> Here's a cool demo of the Neonode multitouch frame:
> http://www.slashgear.com/neonode-3d-touch-headed-to-tablets-and-phones-hands-on-28215933/
> Not only multi-touch, but also entry direction and tilt. For a dollar!

Not all devices using Neonode zForce do tilt, distance, etc. The
Kindle Touch, which I really like, has Neonode IR touch.

cheers,



martin
-- 
 martin.langh...@gmail.com
 mar...@laptop.org -- Software Architect - OLPC
 - ask interesting questions
 - don't get distracted with shiny stuff  - working code first
 - http://wiki.laptop.org/go/User:Martinlanghoff
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


Re: [Sugar-devel] Help activity future

2012-08-01 Thread Bastien
Sascha Silbe  writes:

> Exactly. The best format is of no use when there's no content. Let those
> who are willing to contribute documentation choose the format (as long
> as it's an open format at least, i.e. no .docx or similar). When we
> actually have the documentation, we can discuss how to get it into
> something useful for distribution (including translation) and further
> editing. As long as the input is structured well enough, we can come up
> with some way to convert it.

Yes, the format should not be a problem as long as it is reusable.

IMHO the collaboration framework is a more important problem.

As I suggested back in september, using a git repo with some plain text
content (using markdown, rst, mallard, or... just text) would help.

For the non-git guys around, let's have a maintainer for the Help
content that can convert stuff (even from .docx!) into this raw text
content.

Then think on how to reformat/reuse it later on.

2 cents,

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


Re: [Sugar-devel] How to have "CellRenderer.props" take effect, without a UI refresh?

2012-08-01 Thread Ajay Garg
Thanks Sascha and Flavio.


a)
I modified the code to ::


def __favorite_set_data_cb(self, column, cell, tree_model, tree_iter):
favorite = tree_model[tree_iter][ListModel.COLUMN_FAVORITE]

if favorite:
client = gconf.client_get_default()
color = XoColor(client.get_string('/desktop/sugar/user/color'))
cell.props.xo_color = color
else:
cell.props.xo_color = None


.get_property('window').invalidate_rect(.get_allocation(), False)
.get_property('window').process_updates(True)


where I tried with values of  to ::

  *  self
  *  self.tree_view

However, it made no difference.




b)
I modified the code to ::


def __favorite_set_data_cb(self, column, cell, tree_model, tree_iter):
favorite = tree_model[tree_iter][ListModel.COLUMN_FAVORITE]

if favorite:
client = gconf.client_get_default()
color = XoColor(client.get_string('/desktop/sugar/user/color'))
cell.props.xo_color = color
else:
cell.props.xo_color = None


.get_property('window').invalidate_rect(.get_allocation(), True)
.get_property('window').process_updates(True)


where I tried with values of  to ::

  *  self
  *  self.tree_view

However, it caused an infinite recursive loop, and the journal never loaded.




c)
I modified the code to ::


def __favorite_set_data_cb(self, column, cell, tree_model, tree_iter):
favorite = tree_model[tree_iter][ListModel.COLUMN_FAVORITE]

if favorite:
client = gconf.client_get_default()
color = XoColor(client.get_string('/desktop/sugar/user/color'))
cell.props.xo_color = color
else:
cell.props.xo_color = None


.get_property('window').invalidate_rect(.get_allocation(), False)
.get_property('window').process_updates(True)


where I tried with values of  to ::

  *  column
  *  cell

However, it caused the following traceback ::

Traceback (most recent call last):
  File
"/home/ajay/sugar-jhbuild-dx3/install/lib/python2.7/site-packages/jarabe/journal/listview.py",
line 329, in __favorite_set_data_cb
column.get_property('window').invalidate_rect(column.get_allocation(),
False)
TypeError: object of type `GtkTreeViewColumn' does not have property
`window'




d)
I modified the code to ::


def __favorite_set_data_cb(self, column, cell, tree_model, tree_iter):
favorite = tree_model[tree_iter][ListModel.COLUMN_FAVORITE]

if favorite:
client = gconf.client_get_default()
color = XoColor(client.get_string('/desktop/sugar/user/color'))
cell.props.xo_color = color
else:
cell.props.xo_color = None


.get_property('window').invalidate_rect(.get_allocation(), True)
.get_property('window').process_updates(True)


where I tried with values of  to ::

  *  column
  *  cell

Same as before - it caused the following traceback ::

Traceback (most recent call last):
  File
"/home/ajay/sugar-jhbuild-dx3/install/lib/python2.7/site-packages/jarabe/journal/listview.py",
line 329, in __favorite_set_data_cb
column.get_property('window').invalidate_rect(column.get_allocation(),
False)
TypeError: object of type `GtkTreeViewColumn' does not have property
`window'



:-\



Regards,
Ajay




On Tue, Jul 31, 2012 at 7:07 AM, Flavio Danesse  wrote:

> self.get_property('window').invalidate_rect(self.get_allocation(), True)
> self.get_property('window').process_updates(True)
>
>
>
>
> 2012/7/30 Sascha Silbe 
>
>> Ajay Garg  writes:
>>
>> >> [adding short-circuit logic to
>> >> jarabe.journal.listview.BaseListView.refresh()]
>> [...]
>> >> What we should do is enhancing the logic to
>> >>
>> >> a) just redraw instead of querying the back-end again for changes we
>> >>triggered ourselves and / or
>> >> b) update our model based on the change notifications rather than
>> >>throwing away our state.
>> >>
>> >
>> > Well, that's exactly what I did, via the patch
>> >
>> http://git.sugarlabs.org/dextrose/mainline/commit/ad3897946e013f1ff4020aeab35375ccb122758b
>>
>>