[Sugar-devel] Shell port to GTK+ 3 and gobject-introspection: open issues
Hi, looking for something cool to hack on? There is a hard focus on finishing the shell port to GTK+ 3 and gobject-introspection at the moment. Basically, we have to finish it now :) We keep track of the open items at [1]. If you want *your* name to appear in nifty Auvergne de Bourgogne-green in the Done section you are only three steps away: - grab an item - fix it - send a patch/link to an upstream solution For further coordination we hang out in the usual place #sugar. Cheers, Simon [1] http://wiki.sugarlabs.org/go/Features/GTK3/Shell ___ 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
On 07/31/2012 10:33 AM, Peter Robinson wrote: On Tue, Jul 31, 2012 at 5:01 AM, Gonzalo Odiard gonz...@laptop.org wrote: Any chance of have it packaged in F17? Should do developing, but more important testing, easier. I'm not sure, it's something that could be investigated as in theory it's suppose to be parallel installable, whether it's parallel runnable is another thing altogether though. I was planning on starting some F18 XO images shortly (I was hoping to have done so by now but I'm closing out my current job and starting a new one next week) . When I looked a week or so ago gstreamer 1.0 didn't appear to be in rawhide as yet but I'm running rawhide on the netbook and it seems quite stable, and the mass rebuild on ARM is almost done so I think it's about right to start looking at some weekly images. The SoaS v8 nightlys should be kicking of shortly too if it hasn't already. Peter There is some progress on packaging Gstreamer1 for Fedora 18 [1][2]. As well there are a lot of discussions about the the dynamic bindings [3], so it is a good moment to port Activities that are using Gstreamer and see if there are issues left and contribute to [3] in order to fix them. Now the people are working on it and things are fresh in their mind... Regards, Simon [1] http://koji.fedoraproject.org/koji/buildinfo?buildID=346341 [2] http://comments.gmane.org/gmane.linux.redhat.fedora.desktop/7551 [3] https://bugzilla.gnome.org/show_bug.cgi?id=680913 ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] [sugar-toolkit-gtk3] Replace signal used in UnfullscreenButton to enable use with touch - SL #3798
From: Gonzalo Odiard godi...@gmail.com
Use clicked instead of button-pressed, because this is not triggered
by touch device.
Signed-off-by: Gonzalo Odiard gonz...@laptop.org
---
src/sugar3/graphics/window.py | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/src/sugar3/graphics/window.py b/src/sugar3/graphics/window.py
index 2d9764d..23a8d4f 100644
--- a/src/sugar3/graphics/window.py
+++ b/src/sugar3/graphics/window.py
@@ -65,8 +65,8 @@ class UnfullscreenButton(Gtk.Window):
self._button.show()
self.add(self._button)
-def connect_button_press(self, cb):
-self._button.connect('button-press-event', cb)
+def connect_button_clicked(self, cb):
+self._button.connect('clicked', cb)
def _reposition(self):
x = Gdk.Screen.width() - self._width
@@ -114,8 +114,8 @@ class Window(Gtk.Window):
self._is_fullscreen = False
self._unfullscreen_button = UnfullscreenButton()
self._unfullscreen_button.set_transient_for(self)
-self._unfullscreen_button.connect_button_press(
-self.__unfullscreen_button_pressed)
+self._unfullscreen_button.connect_button_clicked(
+self.__unfullscreen_button_clicked)
self._unfullscreen_button_timeout_id = None
def reveal(self):
@@ -253,7 +253,7 @@ class Window(Gtk.Window):
return True
return False
-def __unfullscreen_button_pressed(self, widget, event):
+def __unfullscreen_button_clicked(self, button):
self.unfullscreen()
def __motion_notify_cb(self, widget, event):
--
1.7.11.2
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] [ASLO] Release SimpleGNUChess-4
Activity Homepage: http://activities.sugarlabs.org/addon/4593 Sugar Platform: 0.82 - 0.98 Download Now: http://activities.sugarlabs.org/downloads/file/28188/simplegnuchess-4.xo Release notes: 4 ENHANCEMENT: * New translations (es, da) * Highlight robot moves * Label rank and file BUG FIX: * Fixed problem with Copy Sugar Labs Activities http://activities.sugarlabs.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [sugar-toolkit-gtk3] Replace signal used in UnfullscreenButton to enable use with touch - SL #3798
Thanks Gonzalo,
2012/8/9 godi...@sugarlabs.org:
From: Gonzalo Odiard godi...@gmail.com
Use clicked instead of button-pressed, because this is not triggered
by touch device.
Makes sense, clicked is more general than button-pressed. From the
docs, is emitted when the button has been activated (pressed and
released).
http://developer.gnome.org/gtk3/stable/GtkButton.html#GtkButton-clicked
Signed-off-by: Gonzalo Odiard gonz...@laptop.org
Acked-by: Manuel Quiñones ma...@laptop.org
---
src/sugar3/graphics/window.py | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/src/sugar3/graphics/window.py b/src/sugar3/graphics/window.py
index 2d9764d..23a8d4f 100644
--- a/src/sugar3/graphics/window.py
+++ b/src/sugar3/graphics/window.py
@@ -65,8 +65,8 @@ class UnfullscreenButton(Gtk.Window):
self._button.show()
self.add(self._button)
-def connect_button_press(self, cb):
-self._button.connect('button-press-event', cb)
+def connect_button_clicked(self, cb):
+self._button.connect('clicked', cb)
def _reposition(self):
x = Gdk.Screen.width() - self._width
@@ -114,8 +114,8 @@ class Window(Gtk.Window):
self._is_fullscreen = False
self._unfullscreen_button = UnfullscreenButton()
self._unfullscreen_button.set_transient_for(self)
-self._unfullscreen_button.connect_button_press(
-self.__unfullscreen_button_pressed)
+self._unfullscreen_button.connect_button_clicked(
+self.__unfullscreen_button_clicked)
self._unfullscreen_button_timeout_id = None
def reveal(self):
@@ -253,7 +253,7 @@ class Window(Gtk.Window):
return True
return False
-def __unfullscreen_button_pressed(self, widget, event):
+def __unfullscreen_button_clicked(self, button):
self.unfullscreen()
def __motion_notify_cb(self, widget, event):
--
1.7.11.2
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
--
.. manuq ..
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] questions
About it, I would like to have a module in the sugar-toolkit, that would gives accelerometer data, such as inclination angle. What do you think? 2012/8/8 Gonzalo Odiard gonz...@laptop.org On Wed, Aug 8, 2012 at 4:18 PM, Flavio Danesse fdane...@gmail.com wrote: questions: 1 - You have to migrate to TelepathyGlib telepathy? I suppose so, but it was migrated to Sugar? I suppose no, but erikos can confirm. 2 - How I can I query the system to check for touch monitor? This is a good question. Should be good have in sugar-toolkit-gtk3 a way to know: * If we are in a XO or not. * XO version. * Acceleromenter available * Touch screen available. We already have code to ask this questions in a lot of activities, and this (or the moment when are ported to gtk3) is a good moment to replace it Gonzalo Preguntas: 1- Hay que migrar telepathy a TelepathyGlib ? Supongo que si, pero ya se migró esto en Sugar ? 2- Como puedo debo consultar al sistema para saber si tiene monitor touch ? ___ 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] Fwd: sugar ui
-- Forwarded message -- From: David Brown djhbr...@gmail.com Date: 10 August 2012 12:13 Subject: sugar ui To: Frederick Grose fgr...@gmail.com, xordu...@gmail.com, volunt...@laptop.org dear olpcers, i am a recently retired computer scientist who would like to contribute design ideas to the project. my cv is herehttps://sites.google.com/site/djhbrown2/CV.doc . having looked at the sugar interface, my first impression is that it needs a complete rework. i do not know what its users (kids) make of it though, nor can i find any data on user experiences. i'm disappointed not to find any openly-published separately-produced k12 stuff on xo; perhaps it is all platform-dependent? sugar is based on fedora i believe, so would it run any app written for fedora? aside from that, i would be interested to contribute to an english language learning project. there is a ton of stuff already out there which could be collected together, rather than reinvent the wheel. is there a software development management structure? who makes the release decisions? is there an olpc executive operations management structure? why isnt olpc in bed with national school curriculum/materials organisations? or maybe it is - but if so, why aren't xos available to schools who can afford to buy them? what is the target age range of xo users? i like the notion of sugar network, but when i look at the screenshots on http://wiki.sugarlabs.org/go/Sugar_Network/Tutorial i find it hard to imagine what a child would do with it. a screen full of coloured x's does not convey any useful information other than the number of them... it reads as if it was made by unix enthusiasts for unix enthusiasts scott's blog mentions an effort last year to develop narrative interfaces - this sounds like a good idea, did anything come of it? i looked at the video by Angela Chang but couldn't find any contact info for her. i noticed the text she was displaying is not read out aloud at the time it is displayed, which i would have thought is vital for a language learning tool. she also seems to be of a mind that children would use it with their parents in attendance, but children need to be able to learn a foreign language without their parents' help. this raises a general point, surely xo needs to be an obvious interface?? (ie users should not need any outside help to use it. it should be ready to hand). david website http://sites.google.com/site/djhbrown2/home +61(0)266537638 +61(0)488471949 On 10 August 2012 01:58, Frederick Grose fgr...@gmail.com wrote: On Wed, Aug 8, 2012 at 12:51 AM, David Brown djhbr...@gmail.com wrote: thanks for your comprehensive reply, Fred. i have looked at the links you cited. i am surprised olpc is still using irc chat and mail lists - is there an operational reason for this? The hardware software developers at OLPC and Sugar Labs are most comfortable with IRC and mailing lists as they are part of their current cultural tradition (they feel part ofhttp://wiki.laptop.org/go/OLPC:What_we_mean_by_free_and_openthe free/libre/open-source software http://en.wikipedia.org/wiki/Free_and_open-source_softwaretradition). Many are loath to using alternative, especially commercial software. The support staff and others at OLPC might be excepted from this characterization (in my estimation) as their work tools must align with standard business software. things like design require a lot of thought, and chat is not the best way to provoke thought, as exemplified by the inanity of academic department meetings!. chat is good for one-on-one socialising though. here is one basic principle i would advocate:the xo interface (which is intendedly predicated upon activity and communication) needs to be good enough (suitable) for xo developers to use it for their own group communication it's clearly not as it stands. you mention developers and i read somewhere about core developers. i imagine there is a team somewhere, probably in Miami, that drives the development. those are the people i would like to communicate with to start with, to jointly come up with a better basic design than the current one. then it could be implemented, bench tested and then beta tested on the user community. The basic Sugar design came from Pentagramhttp://new.pentagram.com/2006/12/new-work-one-laptop-per-child/ 's Lisa Strausfeld, Christian Marc Schmidt and Takaaki Okada collaborating with Walter Bender and Eben Eliason at OLPC. Only Walter Bender is active with Sugar Labs or OLPC. C. Scott Ananian, Director of New Technologies at OLPC, has a bloghttp://cananian.livejournal.com/that tracks his thinking and work. Other current design work centers on touch input http://wiki.sugarlabs.org/go/Design_Team/Sugar_Shell_Touch_Input and community collaboration http://wiki.sugarlabs.org/go/Sugar_Network. i thought about subscribing to http://lists.sugarlabs.org/listinfo/Sugar-devel
Re: [Sugar-devel] [DESIGN] Proposal: Contol-Panel packaging
On 2 August 2012 21:06, Jerry Vonau jvo...@shaw.ca wrote: On Thu, 2012-08-02 at 09:53 +0100, Peter Robinson wrote: Do you have any form of proxy? A local transparent proxy would mean 400 XOs still only download 800Kb over the link. There's lots of ways to skin a cat. We have no control over the network environment what so ever and need to work within the confines of what is available. This is our primary constraint: we cannot install servers or proxies. Schools in remote areas have latent/slow/expensive Internet links. You'd think that a caching proxy is common sense. Unfortunately not :( Furthermore, the newer wireless networks treat every client as potentially hostile and hence prevent them from communicating with each other. This also means that no collaboration can take place. Sridhar Sridhar Dhanapalan Engineering Manager One Laptop per Child Australia M: +61 425 239 701 E: srid...@laptop.org.au A: G.P.O. Box 731 Sydney, NSW 2001 W: www.laptop.org.au ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
