Re: [Sugar-devel] Vizualisation of the Write activity develpment (gource)
Bernie Innocenti ber...@codewiz.org writes: Gnash doesn't seem to work with Vimeo's flash player, so I can't watch the videos. Sorry about that. Maybe switch to HTML5? I have no time for this right now, this is planned for the next version of our blog. I just added links to the source video files - please check at the bottom of the blog post. -- Bastien ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Development Meetings
Excerpts from James Cameron's message of Tue Oct 26 05:40:27 +0200 2010: On Tue, Oct 26, 2010 at 08:39:48AM +1300, Tim McNamara wrote: 14:00 UTC is 2am for me.. It is 1am for me. I won't be attending because /dev/brain will have shut down for the day. Same question as for Tim: What times would be preferred by resp. acceptable for you? Sascha -- http://sascha.silbe.org/ http://www.infra-silbe.de/ signature.asc Description: PGP signature ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [Dextrose] [PATCH v5 sugar] Pulsing icon delayed by 5 seconds or so SL#2080
Excerpts from Anurag Chowdhury's message of Mon Oct 25 19:22:09 +0200 2010: In my logs I noted an average processing time of 0.85 sec for running the first run of the update () function (i.e. while rendering of the first frame ) and since a XO-1.5 is nearly 2.5 times faster than a XO-1 so this processing time would approximate to nearly 2.3 second of delay , [...] How did you arrive at this number (2.5 times faster)? For what kind of operation? OLPC#9325 [1] suggests that - at least for large fills - the XO-1.5 is _slower_, not faster. Sascha [1] http://dev.laptop.org/ticket/9325 -- http://sascha.silbe.org/ http://www.infra-silbe.de/ signature.asc Description: PGP signature ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Moving forward (Sugar-devel Digest, Vol 24, Issue 161)
I did read with great interest both D. Farning's the stepping down and Moving forward as well as the public freeze that followed the first one. I'm not really in the field of ITC but I do know a bit about projects, particularly collaborative ones. Every development project to have a hope of success it needs Clearly defined aims Clearly defined road map Clearly defined tools/methods of implementation Clearly defined, tangible, milestones and annual _external_ evaluation. Internally the project needs many tangible, evaluated stages/tasks so people that work on these have specific goals and, more important, tangible appreciation for their delivered goods. I would think that SugarLabs has to work really hard in all of the above. (I will not go into specifics because criticizing is not the point now). It is true the 99% of the development projects diverge one way or another from the original definitions. This may even include the Aims, though this is usually the last to change. But that's OK! As long as the process reflects accurately the realities on the ground, adapting to realities is a good thing. This where DF's stakeholders and evaluation come into play. Otherwise everything looks like an exercise on map, where purity of code, innovative ideas, peer appreciation, adherence to principles, harmonization with upstream/downstream etc, make take precedence over the goals of the project that is to actually help _real life_ kids and teachers using Sugar to achieve a better education. Without their progress and needs in clear view and the evaluation from them on our deliverables, everything becomes irrelevant. We operate in a vacuum, and pretty soon diverge and disintegrate. To that extend I would think that any individual taking a leading role without the above thoroughly discussed and defined, will just burn-out and be wasted. The actual definition of the aforementioned issues is what will define the best person for the job. The additional benefit of an open discussion, is that the better person may still be in the sidelines because (s)he can not see any room to move, and surface through it. I do not really know if mailing lists are the best place to have these discussions. Again my experience from collaborative projects is that every successful one was preceded by an open meeting where participants openly discussed and defined (in writing) to a large extent goals, methods, milestones, tasks, evaluation and feedback. Then distal media where then used to further define the first draft into a project. Maybe is time for a Reinventing-Sugar face to face meeting. Message: 3 Date: Mon, 25 Oct 2010 19:30:39 -0500 From: David Farning dfarn...@gmail.com To: iaep i...@lists.sugarlabs.org, sugar-devel sugar-devel@lists.sugarlabs.org Subject: [Sugar-devel] Moving forward. Message-ID: aanlktik=uecbzv6ahcm1alzvt1nbh7zojejymw+xw...@mail.gmail.com Content-Type: text/plain; charset=UTF-8 Yesterday I sent a rather blunt email on my concerns about the project. It seems the observations resonated with many people while striking several nerves. The volume of private mail or CCed mail (to a subset of the Sugar Labs participants) responses was unexpectedly high. The five main themes of the responses are: 1. Could you possibility be any more abstract? 2. Several of the points are valid. Here are my responses/suggestions. This should be on a public thread, but someone else will have to start it. 3. The core problem is trust. 4. This conversation is like an iceberg, the 'community' only sees 10% and not the other 90%. 5. Dave you are just a jerk, now shut up. For better of worse, all five points are valid. I am a bumbling jerk who is struggling to rebuild community trust without airing anyone's dirty laundry, including my own. To put all of my cards on the table: 1. The ideas driving OLPC and Sugar are sound. 2. Sugar Labs will continue to fragment until the issue of trust is resolved. 3. Because of this, I left Sugar Labs to start a business which provides service and support for Sugar. 4. I need Sugar to succeed. I need OLPC to succeed. 5. I have been trying to operate 'under the radar' because some in Sugar Labs and OLPC have contacted individuals I am working with and 'suggested' that they not work with me. Talk about the pot calling the kettle black. I get pissed off about the lack of trust and community building in Sugar Labs, so I go off and form a fork which operates largely in secret. Two years ago, I suggested that the over sight board appoint Walter Bender as Executive Director of Sugar Labs so he would be able to speak on behalf of Sugar Labs. He had three skills which Sugar Labs needed. 1) He was able to clearly and effectively communicate the goals of Sugar and the mission of Sugar Labs. 2) He was able to create an identity for Sugar Labs outside of OLPC. 3) He was a tireless
Re: [Sugar-devel] Mailman's admin and archive interfaces are horrible - suggest GroupServer.org
On Mon, Oct 25, 2010 at 09:56:05PM -0400, Luke Faraone wrote: On 10/17/2010 07:15 PM, Tim McNamara wrote: I'm assuming the infrastructure team are part of this list. We are, sorry for the long reply time. The archives are easily searchable, attached files are converted to links to the server so that people's inboxes are not flooded. Removing inline attachments may break PGP/MIME, (although I haven't checked) and some people consider being able to read a message offline in its entirety a feature. I hope that behavior is configurable. I welcome any feedback. I think that a migration like this will make the mailing lists far more accessible as a knowledge archive. I've been assured that there is a migration path from mailman[4]. From what I know of Dan, its lead developer, it should be fairly easy reliable. I'll take a look at it. For it to be seriously considered, a mailman path would be needed. The linked tweet notwithstanding, I've not seen any documentation on such a migration. You might want to consider sympa too: https://www.sympa.org/ It has strong support for PGP/MIME, and a nice default web interface. - Jonas -- * Jonas Smedegaard - idealist Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: Digital signature ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Moving forward (Sugar-devel Digest, Vol 24, Issue 161)
On Tue, Oct 26, 2010 at 10:10 AM, Yioryos Asprobounitis mavrot...@yahoo.com wrote: I'm not really in the field of ITC but I do know a bit about projects, particularly collaborative ones. Every development project to have a hope of success it needs Clearly defined aims Clearly defined road map Clearly defined tools/methods of implementation Clearly defined, tangible, milestones Yes! To that extend I would think that any individual taking a leading role without the above thoroughly discussed and defined, will just burn-out and be wasted. The actual definition of the aforementioned issues is what will define the best person for the job. Yes. Maybe is time for a Reinventing-Sugar face to face meeting. Yes. I generally resist sending +1 emails but well, you just wrote a big part of what was on my mind. Marco ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Development Meetings
On Mon, Oct 25, 2010 at 01:45:21PM +, Aleksey Lim wrote: For me, default time is ok Wednesday 2010-10-27, 14:00 UTC irc://irc.freenode.net#sugar-meeting How about other possible attenders? +1 pgp18CYjHMMue.pgp Description: PGP signature ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [IAEP] stepping down as maintainer
On 24 October 2010 17:42, David Farning dfarn...@ubuntu.com wrote: Sugar Labs lost its lead developer. [...] At the risk of angering pretty much everybody Sugar Labs has three fundamental problems. Sugar Labs is optimistic to the point of untruthfulness. Sugar Labs is lead by veto rather than vision. There is a lack of accountability to stakeholders. David, Thank you for your bravery and frankness with which you have raised these concerns. My main desire from these discussion is that contributors will feel like they are contributing to a project with momentum by the end of them. I would like to address your three points. However, I would also like to add some more context to the discussion as I see it: Sugar faces several up-coming technical challenges that will test the resolve of Sugar Labs. - a move to a touch-based interface - change in hardware infrastructure for the XOs (e.g. ARM processors) - Move to GNOME 3.0 - Move to Python 2.7 eventually to 3.x From the pedagogical side, I'm sure that an increased emphasis on standardised testing (at least in the developed world) means that there will be an increased expectation for standardised teaching tools. *Issue 1*: over-promising This is a tricky problem. Sugar is enticing. I think that we will not be able to contain people's enthusiasm, nor do I think that Sugar Labs should stop aspiring to provide the world's best educational platform. Instead, we should focus on improving the technology. *Issue 2*: veto We have a small cadre of experienced and highly able contributors. *Issue 3*: lack of accountability to stakeholders I don't agree that Sugar Labs is unresponsive. Nor do I agree that a change in the leadership structure will be beneficial. WB has provided excellent service to the team. We have engaged with OLPC, Fedora and provide support several deployments. For a volunteer driven organisation, it's highly responsive. Here are some of my reflections over the last few days: The list of challenges does look overwhelming. There is probably a lack of developer capacity in our community to deal with them. At least, I'm fairly intimidated. Sugar is a very large project, with hundreds of interdependent parts. However, we should remember that each of these challenges is surmountable. They will also present developers with the possibility to innovate and interesting solutions. It would be good to quantify the risks that the project faces. Are the list of challenges I've written up valid things to worry about? I think Sugar Labs could create an informal mentor system to enable more contributions from current 'lurkers'. This proposal is I think the development teams needs to draw on IAEP others for support. I think that once everyone feels like that a degree of momentum has been reached, the community will grow and our educators will be able to go back to just educating. Sugar Labs does lots of its own infrastructure. Is that the best use of contributors' time? (Why don't we use Canonical's Launchpad?) Regards, Tim McNamara @timClicks ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [IAEP] stepping down as maintainer
Please excuse my rash pushing of the 'send' button: On 26 October 2010 23:42, Tim McNamara paperl...@timmcnamara.co.nz wrote: *Issue 2*: veto We have a small cadre of experienced and highly able contributors. This means that an expectation of very high-quality will become established as the norm. This is a hard wall to scale while contributing. However, there have been many emails on the development list surrounding changes to the patch acceptance process. I don't feel that anyone is against change if it will make things more productive. Tim ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [Dextrose] [PATCH v5 sugar] Pulsing icon delayed by 5 seconds or so SL#2080
On Tue, Oct 26, 2010 at 10:57:03AM +0200, Sascha Silbe wrote: Excerpts from Anurag Chowdhury's message of Mon Oct 25 19:22:09 +0200 2010: In my logs I noted an average processing time of 0.85 sec for running the first run of the update () function (i.e. while rendering of the first frame ) and since a XO-1.5 is nearly 2.5 times faster than a XO-1 so this processing time would approximate to nearly 2.3 second of delay , [...] How did you arrive at this number (2.5 times faster)? For what kind of operation? I agree with Sascha, I don't think nearly 2.5 times faster is a reliable method to predict an outcome. The hardware is very different; different CPU, memory, and video card. -- James Cameron http://quozl.linux.org.au/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Development Meetings
On Tue, Oct 26, 2010 at 10:47:41AM +0200, Sascha Silbe wrote: Same question as for Tim: What times would be preferred by resp. acceptable for you? UTC 21 to UTC 06. During the summer, which is now, here. -- James Cameron http://quozl.linux.org.au/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [Dextrose] [PATCH v5 sugar] Pulsing icon delayed by 5 seconds or so SL#2080
On Tue, Oct 26, 2010 at 05:41:58PM +0530, Anurag Chowdhury wrote: The conclusion of XO-1.5 being nearly 2.5 times faster than the XO-1 could be verified by comparing their hardware specifications. at http://en.wikipedia.org/wiki/OLPC_XO-1 (For XO-1) and http://wiki.laptop.org/go/Hardware_specification_1.5 (For XO-1.5) .Also we can see the test results of James'(quozl) at http://bugs.sugarlabs.org/ticket/245 which suggests that XO-1.5 is atleast twice as fast as XO-1. Those conclusions are oversimplified - in general they might be useful but you are talking about a very specific, very large and subtle set of operations with a very specific set of interacting hardware and software components, the software ones of which change a lot from release to release. Much more compelling for a problem that has been with us for a while, has been a moving target in software terms, and many people have looked at, would be just to test your change on an XO-1 and report back. If you don't have one - and even if you do - others will be interested in testing your changes on an XO-1, too. Please can you provide an easy way for people with an XO-1 and a well-supported release to objectively gather the speedup of your patch? Or at least some numbers of your own? Martin pgp31cLTrdkMg.pgp Description: PGP signature ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] [ASLO] Release Turtle Blocks-102
Activity Homepage: http://activities.sugarlabs.org/addon/4027 Sugar Platform: 0.82 - 0.90 Download Now: http://activities.sugarlabs.org/downloads/file/27087/turtle_art-102.xo Release notes: 102 * fixed bug with refactoring of depreciated setxy block Sugar Labs Activities http://activities.sugarlabs.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] [RELEASE] Turtle Blocks 102
Sorry about the quick succession of releases. I discovered a bug with a depreciated block that would prevent some old projects from running. == Source == http://download.sugarlabs.org/sources/sucrose/fructose/TurtleArt/TurtleArt-102.tar.bz2 == News == BUG FIXES: * fixed bug with refactoring of depreciated setxy block -walter -- 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] Mailman's admin and archive interfaces are horrible - suggest GroupServer.org
On Tue, Oct 26, 2010 at 04:13:42PM +0200, Bert Freudenberg wrote: On 26.10.2010, at 11:14, Jonas Smedegaard wrote: On Mon, Oct 25, 2010 at 09:56:05PM -0400, Luke Faraone wrote: On 10/17/2010 07:15 PM, Tim McNamara wrote: I'm assuming the infrastructure team are part of this list. We are, sorry for the long reply time. The archives are easily searchable, attached files are converted to links to the server so that people's inboxes are not flooded. Removing inline attachments may break PGP/MIME, (although I haven't checked) and some people consider being able to read a message offline in its entirety a feature. I hope that behavior is configurable. I welcome any feedback. I think that a migration like this will make the mailing lists far more accessible as a knowledge archive. I've been assured that there is a migration path from mailman[4]. From what I know of Dan, its lead developer, it should be fairly easy reliable. I'll take a look at it. For it to be seriously considered, a mailman path would be needed. The linked tweet notwithstanding, I've not seen any documentation on such a migration. You might want to consider sympa too: https://www.sympa.org/ It has strong support for PGP/MIME, and a nice default web interface. For easier participation, a system that had a seamless forums interface would be great. Unfortunately I have not found one that works well, yet. Yeah, I think I share your interest here. Years back I was in love with http://pessoal.org/papercut/ but sadly that haven't been maintained. Also, my experimentation with it revealed that webforum users tend to use a different writing style, especially regarding quoting, which makes the marriage a mess for both email and webforum lovers. Sympa provides a seemingly nice web interface, usable also for users (i.e. not only an admin interface), including posting from web (i.e. not only archival). I have not yet played much with sympa myself - have fought with packaging it for Debian for a couple of years, though. The recent 6.x releases seem pretty mature (no longer needs heavy patching which is what consumed much of my packaging time earlier on). - Jonas -- * Jonas Smedegaard - idealist Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: Digital signature ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [Dextrose] [PATCH v5 sugar] Pulsing icon delayed by 5 seconds or so SL#2080
Sure, I would certainly do a similar benchmark test on an XO-1 also . I am presently waiting for the developers' key of my XO-1 to flash it into the latest build of dextrose, then I will run the benchmark test and will post the results asap. On Tue, Oct 26, 2010 at 6:59 PM, Martin Dengler mar...@martindengler.comwrote: On Tue, Oct 26, 2010 at 05:41:58PM +0530, Anurag Chowdhury wrote: The conclusion of XO-1.5 being nearly 2.5 times faster than the XO-1 could be verified by comparing their hardware specifications. at http://en.wikipedia.org/wiki/OLPC_XO-1 (For XO-1) and http://wiki.laptop.org/go/Hardware_specification_1.5 (For XO-1.5) .Also we can see the test results of James'(quozl) at http://bugs.sugarlabs.org/ticket/245 which suggests that XO-1.5 is atleast twice as fast as XO-1. Those conclusions are oversimplified - in general they might be useful but you are talking about a very specific, very large and subtle set of operations with a very specific set of interacting hardware and software components, the software ones of which change a lot from release to release. Much more compelling for a problem that has been with us for a while, has been a moving target in software terms, and many people have looked at, would be just to test your change on an XO-1 and report back. If you don't have one - and even if you do - others will be interested in testing your changes on an XO-1, too. Please can you provide an easy way for people with an XO-1 and a well-supported release to objectively gather the speedup of your patch? Or at least some numbers of your own? Martin ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Development Meetings
People UTC - Aleksey Lim alsr...@member.fsf.org any James Cameron qu...@laptop.org-11 Martin Dengler mar...@martindengler.com00 Martin Jose Abente Lahaye martin.abente.lah...@gmail.com -04 Sascha Silbe sascha-ml-reply-to-201...@silbe.org +1 Simon Schampijer si...@schampijer.de +1 Steven Parrish smparr...@gmail.com ? Tim McNamara paperl...@timmcnamara.co.nz -12 Walter Bender walter.ben...@gmail.com -5 -4 What about having [only] upcoming meeting on nearest weekends, something like Saturday, 22:00 UTC? Saturday your time is Sunday for NZ and Australia - if there is anything coming out of these meetings that tells us what to test for you then you might want to consider that we test every Saturday at 11am our time. Also Saturday night your time means no one in your time zone gets to go out for dinner on Saturday night ever again. The Monday to Wednesday idea previously suggested was good. Tabitha ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Development Meetings
On Tue, Oct 26, 2010 at 07:56:17AM -0700, Tabitha Roder wrote: People UTC - Aleksey Lim alsr...@member.fsf.org any James Cameron qu...@laptop.org-11 Martin Dengler mar...@martindengler.com00 Martin Jose Abente Lahaye martin.abente.lah...@gmail.com -04 Sascha Silbe sascha-ml-reply-to-201...@silbe.org +1 Simon Schampijer si...@schampijer.de +1 Steven Parrish smparr...@gmail.com ? Tim McNamara paperl...@timmcnamara.co.nz -12 Walter Bender walter.ben...@gmail.com -5 -4 What about having [only] upcoming meeting on nearest weekends, something like Saturday, 22:00 UTC? Saturday your time is Sunday for NZ and Australia - if there is anything coming out of these meetings that tells us what to test for you then you might want to consider that we test every Saturday at 11am our time. Also Saturday night your time means no one in your time zone gets to go out for dinner on Saturday night ever again. The Monday to Wednesday idea previously suggested was good. Sorry if it was not clear from my previous posts (it was not clear for me as well:). My idea is about gathering as many as possible developers who are interested in how Development Team should move forward and make a clear statements about organizational procedures within Development Team and core development process (to leverage current, not so funny, situation). During this meeting we can decide what time will be convenient for regular meetings. I hope interested in people will manage to bear one meeting on Saturday, 2010-10-30, 22:00 UTC :). -- Aleksey ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Development Meetings
Excerpts from Aleksey Lim's message of Tue Oct 26 17:22:28 +0200 2010: I hope interested in people will manage to bear one meeting on Saturday, 2010-10-30, 22:00 UTC :). I don't think I'll be able to participate this Saturday, I'm afraid. :( The next one (06.11.) should be fine. Sascha -- http://sascha.silbe.org/ http://www.infra-silbe.de/ signature.asc Description: PGP signature ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] [PATCH] Clipboard menu off screen fixed for long text strings(SL #2201)
Changing maximum text length to a suitable value in clipboardmenu which is dependent on the screen width and pixel size of characters --- src/jarabe/frame/clipboardmenu.py |5 - 1 files changed, 4 insertions(+), 1 deletions(-) diff --git a/src/jarabe/frame/clipboardmenu.py b/src/jarabe/frame/clipboardmenu.py index b998110..b0d141d 100644 --- a/src/jarabe/frame/clipboardmenu.py +++ b/src/jarabe/frame/clipboardmenu.py @@ -38,7 +38,10 @@ from jarabe.model import bundleregistry class ClipboardMenu(Palette): def __init__(self, cb_object): -Palette.__init__(self, text_maxlen=100) +char_lable = gtk.Label() +create_layout = char_lable.create_pango_layout(W) +Palette.__init__(self, text_maxlen=int(0.75 * gtk.gdk.screen_width +() / create_layout.get_pixel_size()[0])) self._cb_object = cb_object -- 1.7.0.4 ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [PATCH] Clipboard menu off screen fixed for long text strings(SL #2201)
Team, Unfortunately, I had not mentioned the version number in the previous patch. I apologize for the mistake. I am correcting the indentation with adding the versions correctly. Regards, Mukul Gupta Research Engineer, SEETA On Wed, Oct 27, 2010 at 1:22 AM, Mukul Gupta mu...@seeta.in wrote: Changing maximum text length to a suitable value in clipboardmenu which is dependent on the screen width and pixel size of characters --- src/jarabe/frame/clipboardmenu.py |5 - 1 files changed, 4 insertions(+), 1 deletions(-) diff --git a/src/jarabe/frame/clipboardmenu.py b/src/jarabe/frame/clipboardmenu.py index b998110..b0d141d 100644 --- a/src/jarabe/frame/clipboardmenu.py +++ b/src/jarabe/frame/clipboardmenu.py @@ -38,7 +38,10 @@ from jarabe.model import bundleregistry class ClipboardMenu(Palette): def __init__(self, cb_object): -Palette.__init__(self, text_maxlen=100) +char_lable = gtk.Label() +create_layout = char_lable.create_pango_layout(W) +Palette.__init__(self, text_maxlen=int(0.75 * gtk.gdk.screen_width +() / create_layout.get_pixel_size()[0])) self._cb_object = cb_object -- 1.7.0.4 ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] [PATCH v2] Clipboard menu off screen fixed for long text strings(SL #2201)
Changing maximum text length to a suitable value in clipboardmenu which is dependent on the screen width and pixel size of characters --- src/jarabe/frame/clipboardmenu.py |5 - 1 files changed, 4 insertions(+), 1 deletions(-) v1-v2: text_maxlen dependent on screen size and character pixel size diff --git a/src/jarabe/frame/clipboardmenu.py b/src/jarabe/frame/clipboardmenu.py index b998110..b0d141d 100644 --- a/src/jarabe/frame/clipboardmenu.py +++ b/src/jarabe/frame/clipboardmenu.py @@ -38,7 +38,10 @@ from jarabe.model import bundleregistry class ClipboardMenu(Palette): def __init__(self, cb_object): -Palette.__init__(self, text_maxlen=100) +char_lable = gtk.Label() +create_layout = char_lable.create_pango_layout(W) +Palette.__init__(self, text_maxlen=int(0.75 * gtk.gdk.screen_width +() / create_layout.get_pixel_size()[0])) self._cb_object = cb_object -- 1.7.0.4 ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Transbot: An Interchannel IRC Translator
Hello, Transbot is an IRC translation bot designed to be a tool to connect IRC channels that are in different languages. Transbot is now in a state of development where it will benefit from community feedback and testing. There is a dedicated version of the bot that communicates between the following channels: #transbot-test-en, #transbot-test-es Please drop by and check it out. For more information about the type of feedback we are looking for and transbot in general visit out wiki: https://fedorahosted.org/transbot/wiki/testing If you would like to leave feedback regarding transbot please send an email to: mrt...@rit.edu or tjr1...@rit.edu Thanks, Transbot Team ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Testing Problem (v0.90) using Fedora LiveUSB Creator (was: Schedule after Sugar 0.90.0 is released)
I'd like to report ongoing problems trying to test my activities with Sugar 0.90 (SoaS). Now, doing this is fairly crucial. The issues cited below are still with me: 1) the most recent Fedora LiveUSB Creator (3.9.2) will not run on my WinXP desktop, giving an unexplained configuration error upon execution (reinstall doesn't help); 2) LiveUSB Creator (3.9) does not create bootable USB sticks from any nightly releases. v3.9 does install the main SoaS iso offered at the Fedora downloads page, but this turns out to be (still?) v. 0.88, or so the installation indicates (it's Fedora-13-i686-Live-SoaS.iso). Is this correct? Is 0.90 available publically as an .iso that LiveUSB Creator will handle? Thanks to whoever can help with this. I'm stymied. Art Hunkins - Original Message - From: Art Hunkins abhun...@uncg.edu To: Sugar Devel Sugar-devel@lists.sugarlabs.org; lmac...@redhat.com Sent: Thursday, October 07, 2010 11:25 AM Subject: Testing Problem using Fedora LiveUSB Creator (was: Schedule after Sugar 0.90.0 is released) FWIW, I've been trying to give recent daily builds a test run - both to spot problems in the projected 0.90 release and see how my own activities fare. I download the x386 .iso and install it with Fedora LiveUSB Creator (v3.9 - see further below) on my WinXP system. All goes along fine until I attempt to boot my computer using the resultant USB stick. It won't boot. It gets to a test screen with a SYSLINUX line at the top and a blinking dot on line 2, and stays there. Final SoaS builds boot fine via LiveUSB Creator, but to my knowledge, all nightly SoaS builds I've tried have suffered the above fate. Is this expected? Is there a (simple) alternative? (Is this a bug?) Also (Luke), I've had to use v3.9 to make my SoaS sticks rather than v3.9.2. The latter won't install on my XP machine; it complains about a configuration error and suggests reinstalling (which I've done to no avail). I've also uninstalled before reinstalling; nothing seems to help. Reverting to v3.9, everything works fine. Art Hunkins - Original Message - From: Simon Schampijer si...@schampijer.de To: Sugar Devel Sugar-devel@lists.sugarlabs.org Sent: Wednesday, October 06, 2010 10:54 AM Subject: [Sugar-devel] [ANNOUNCE] Schedule after Sugar 0.90.0 is released --- or After the game is before the game Dear Sugar community, after successfully releasing 0.90 there should be a to celebrate what has been achieved and then we can start thinking what to do next. Some items are rather near term goals but there is as well the long road that leads to a new release --- 0.92 (1.0). === Branching === After the final release of a module, a branch should be created to host further stable development. If you do not have an 'unstable' commit yet you can leave your branch as is, as this ease the work for translators by not having to translate for two branches. The details about branching are described at [1]. === Bug fix release === To make sure we have the latest packages in F14 before the Final Change deadline happens the 18th of October [2], I added another bug fix release [3]. As Fedora is the bleeding edge at the moment we just backpack on this date. * 0.90.1 will be the 15th of October * 0.90.2 will be the 27th of October === Testing 0.90 === So far we have not seen much testing of 0.90 yet, that is why the bug fix releases noted above are so important to us. We need as well your help to actually discover the bugs! There are basically three ways how you can test as of today (besides using sugar-jhbuild): * Install Fedora 14 on a machine and install the Sugar desktop * Test using Sugar on a stick: Get one of the nightly snapshots [4] and put it on a usb key. You can find instructions about it at [5]. It is good to subscribe to the Soas mailing list (low traffic) [6] for announcement and discussions in that case. * If you have an XO (XO-1 or XO-1.5) you can use an image from [7]. If you are aware of any other distribution where Sugar 0.90 can be tested easily please comment. === 0.92 === Based on the GNOME schedule I made a first draft of the 0.92 roadmap. I reintroduced the Feature Acceptance milestone. The idea is that the discussion about a feature does not start one day before the feature freeze. As stated in the Feature policy [9] the acceptance is a sanity check, presumed in most cases to be a formality, to ensure that new features compliment Sugar guidelines and is manageable, prior to publicizing as officially targeted for the next release. The actual code must be ready by the Feature Freeze and is reviewed by the module maintainer. On behalf of the Sugar community, Your Release Team [1] http://wiki.sugarlabs.org/go/Development_Team/Release#Branching [2] https://fedoraproject.org/wiki/Releases/14/Schedule [3] http://wiki.sugarlabs.org/go/0.90/Roadmap#Schedule [4] http://alt.fedoraproject.org/pub/alt/nightly-composes/soas [5]
Re: [Sugar-devel] Edit/audit wikipedia activity
On Thu, Oct 21, 2010 at 12:06 PM, Martin Langhoff martin.langh...@gmail.com wrote: Unfortunately, there is a clear need to organise a facility to audit/edit the wikipedia snapshots we have and repack the archive. Some simple rough mods to server.py to allow local edits -- start server.py with an additional argument (a path to an existing directory) and it'll save its results there. Start it like ./server.py 8080 /home/martin/wikiedits The server shows the changed files, which will go into a 'wiki' subdirectory there. You can check the edits thus: diff -ur /home/martin/wikiedits/wiki.orig /home/martin/wikiedits/wiki And mergeupdates.py to... um, merge those updates bzcat es_PE.xml.bz2.processed | tools/mergeupdates.py //wiki | bzip2 es_PE.xml.bz2.processed.changed You'll have to re-create the indexes (look at what woip/sh/process does right after processing the file). git clone git://dev.laptop.org/users/martin/wikiserver cheers, m -- martin.langh...@gmail.com mar...@laptop.org -- School Server Architect - 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
[Sugar-devel] Sugar Digest 2010-10-26
==Sugar Digest== 1. Tomeu's departure from the project has set off a lot of introspection, speculation, 'blunt' emails, and thoughtful responses. There is no doubt that we will miss Tomeu. He has been not just a prolific contributor to the project, but also a steady hand, with the professional's eye. Under his leadership, we have been able to raise the quality of Sugar and we are much better integrated into the work flows both upstream and downstream from Sugar. We must ensure that this level of professionalism is not diminished. The occasion of Tomeu's departure has triggered the voicing of many unrelated frustrations with Sugar and Sugar Labs. Yioryos Asprobounitis posted a thoughtful email [http://lists.sugarlabs.org/archive/sugar-devel/2010-October/028319.html] to the Sugar Developer list. In it, he reminded us of those things that every successful project needs: * Clearly defined aims * Clearly defined road map * Clearly defined tools/methods of implementation * Clearly defined, tangible, milestones and annual _external_ evaluation While I think that the Sugar Community has worked hard towards providing clarity, there remain deficiencies and disagreements. Personally, my aims for are unwavering: Sugar is a software platform that is designed for children for learning. Sugar is developed and maintained by Sugar Labs, a global volunteer community of software developers and educators. Our goal is to raise a generation of critical thinkers and problem-solvers by establishing a culture of independent thinking and learning. Through Sugar, we strive to provide every child with the opportunity to learn learning within a context that will allow them both to engage in an on-going critical dialog with others and to develop independent means towards their personal goals. The technical underpinnings of Sugar are deliberately designed maximize the probability that children will learn. Through the Sugar-platform affordances, we encourage learners to explore by dig deeply into topics for which they are passionate, to express by building upon what they discover, and to reflect by engaging in peer-to-peer and personal criticism. Free Software is fundamental to the project not just as a means to an end, but also because of its culture: it is no coincidence that Free Software developers don't just write code; they talk about Free Software, they criticize it, and they discuss other people's criticisms. Regarding road maps, in my opinion we are quite disciplined in terms of our day-to-day release process. However we are lacking a long-term road map, which I would equate to an architectural specification. Such a document could serve as a metric that would help us with some of our short-term decisions and also help shape the project going forward. Regarding tools and methods of implementation, while there has been lots of heated discussion, I don't think we are so far apart in our opinions. The seemingly endless debate about git vs email vs trac for patch review is winding down. And we are getting better as a community in showing patience with our handling of the influx of patches and questions from newbies. Perhaps the best evidence that we are not so far off track is the great job that has been done packaging Sugar downstream by various organizations and deployments. We are producing a product that they can work with and want to work with. Of course there is always room for improvement and no doubt the debate about tools and process will continue. That said, one legacy of Tomeu is to be uncompromising on quality. I have submitted many patches and have had very few accepted. But I have gotten thoughtful feedback and learned a great deal in the process. My subsequent patches are better for the effort of the Sugar maintainers. Regarding tangible milestones and evaluation, I give us a mixed review. We have a reasonable mechanisms in place for our release process and we are cultivating ever-increasing feedback from the Sugar deployments. However, we are lacking clarity around our long-range technical goals. In terms of evaluation, Sugar in the context of deployments is undergoing some level of scrutiny. There are on-going evaluations underway in all of the major deployments. But with few exceptions it is not clear how Sugar itself is being evaluating in the field. We have some active testing teams, but we have not provided them with very good tool chains; we have almost no automated data collection to inform us as to how children are using Sugar. These deficiencies are mitigated in part by an increasingly vocal community of teachers and mentors and facilitators. Ultimately I think we will learn more from our user community than is typical of other software projects. Indeed, the fact that two teachers are running for positions on our Oversight Board is really encouraging. Dave Neary wrote a blog post about Ubuntu's plans to move to Unity as the default desktop in which he mentions Sugar. OLPC had many teething
Re: [Sugar-devel] Transbot: An Interchannel IRC Translator
Hey Mark, So a few people have already tested Transbot and brought up that we should provide all available languages for testing. We can list them on the wiki and people can choose which languages they want to join. I figured I'd post this up just to keep the conversation in the public. -Taylor On Tue, Oct 26, 2010 at 4:21 PM, MARK THILL (RIT Student) mrt8...@rit.eduwrote: Hello, Transbot is an IRC translation bot designed to be a tool to connect IRC channels that are in different languages. Transbot is now in a state of development where it will benefit from community feedback and testing. There is a dedicated version of the bot that communicates between the following channels: #transbot-test-en, #transbot-test-es Please drop by and check it out. For more information about the type of feedback we are looking for and transbot in general visit out wiki: https://fedorahosted.org/transbot/wiki/testing If you would like to leave feedback regarding transbot please send an email to: mrt...@rit.edu or tjr1...@rit.edu Thanks, Transbot Team ___ 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] Development Meetings
On Tue, Oct 26, 2010 at 12:16:47PM +, Aleksey Lim wrote: What about having [only] upcoming meeting on nearest weekends, something like Saturday, 22:00 UTC? Nak. Already booked, weekly event, high priority. http://whenisgood.net/ may interest you, it is a way to schedule an event ... I've found it very useful. -- James Cameron http://quozl.linux.org.au/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [Dextrose] [PATCH v5 sugar] Pulsing icon delayed by 5 seconds or so SL#2080
On Tue, Oct 26, 2010 at 05:41:58PM +0530, Anurag Chowdhury wrote: The conclusion of XO-1.5 being nearly 2.5 times faster than the XO-1 could be verified by comparing their hardware specifications. at http://en.wikipedia.org/wiki/OLPC_XO-1 (For XO-1) and http://wiki.laptop.org/go/Hardware_specification_1.5 (For XO-1.5) These specifications do not describe CPU or graphics performance, and so your conclusion 2.5 times faster is not supported by these specifications. Also we can see the test results of James'(quozl) at http://bugs.sugarlabs.org/ticket/245 which suggests that XO-1.5 is atleast twice as fast as XO-1. That test compared two entirely different methods of rendering the languages control panel section; one method used by Sugar 0.82.1 and the other method used Sugar 0.84.11. So your conclusion 2.5 times faster is not supported by this test either. http://dev.laptop.org/ticket/9325 is the best test result that I can remember that compares CPU and graphics performance, and the latest results there show XO-1 and XO-1.5 at about equal, because the bit plane depth has changed from 16 on XO-1 to 24 on XO-1.5 at the same time as the graphics subsystem became faster. The test is less relevant to Sugar though, since it is (a) full screen fill, and (b) using SDL and pygame rather than GTK+. I'd like to test your change on Sugar 0.84 (not HEAD) on XO-1 and XO-1.5 once I can understand how to measure the performance. It is more important for me that power is conserved. -- James Cameron http://quozl.linux.org.au/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [Dextrose] [PATCH v3] Reduction in the time taken for loading of the menu (SL#1169)
Bernie and Sascha, Are we ready to commit this patch? Manu On Fri, Oct 22, 2010 at 12:56 AM, shan...@seeta.in wrote: From: Shanjit Singh Jajmann shan...@seeta.in Reduction in the lead time for loading the drop down menus. Changes made in the time delay for rendering of the secondary palette to improve human computer interaction and experience. Co-authored-by: Frederick Grose fgr...@sugarlabs.org Reviewed-by: Bernie Innocenti ber...@codewiz.org --- v1 - v2 : Since the time 0.0, was too short for comfortable viewing, arguments have been modified suitably to bring in a smooth pop-up and pop-down feature. Suggestions taken from SL#2367. v2 - v3 : Position of changelog changed and text wrapping done. src/sugar/graphics/palette.py |2 +- src/sugar/graphics/palettewindow.py |2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/src/sugar/graphics/palette.py b/src/sugar/graphics/palette.py index d4f844c..5be8304 100644 --- a/src/sugar/graphics/palette.py +++ b/src/sugar/graphics/palette.py @@ -103,7 +103,7 @@ class Palette(PaletteWindow): self._menu_content_separator = gtk.HSeparator() -self._secondary_anim = animator.Animator(2.0, 10) +self._secondary_anim = animator.Animator(1.0, 10) self._secondary_anim.add(_SecondaryAnimation(self)) # we init after initializing all of our containers diff --git a/src/sugar/graphics/palettewindow.py b/src/sugar/graphics/palettewindow.py index f51c938..4f19e0d 100644 --- a/src/sugar/graphics/palettewindow.py +++ b/src/sugar/graphics/palettewindow.py @@ -148,7 +148,7 @@ class PaletteWindow(gtk.Window): self._up = False self._old_alloc = None -self._popup_anim = animator.Animator(.5, 10) +self._popup_anim = animator.Animator(0.0, 10) self._popup_anim.add(_PopupAnimation(self)) self._popdown_anim = animator.Animator(0.6, 10) -- 1.7.2.2 ___ Dextrose mailing list dextr...@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/dextrose ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [Dextrose] New maintainer for Words
Bernie, Shachi and Sarvagya are interested to co-maintain Words. They did submit a patch this month (needs to be reviewed). Would you and Chris like to have a word with them on this matter? Manu On Thu, Oct 21, 2010 at 1:37 PM, Bernie Innocenti ber...@codewiz.orgwrote: On Thu, 2010-10-21 at 00:53 +0530, Ishan Bansal wrote: hi I had submitted the patch for ticket #2210. Wish if you can review it and provide me any changes required. First we'd have to determine who the maintainer of Words is. Chris is the original author, but now he has no time to work on it. Do we have any volunteers with the necessary experience? -- // Bernie Innocenti - http://codewiz.org/ \X/ Sugar Labs - http://sugarlabs.org/ ___ Dextrose mailing list dextr...@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/dextrose ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [Dextrose] [PATCH v3] Reduction in the time taken for loading of the menu (SL#1169)
On Wed, Oct 27, 2010 at 06:05:58AM +0530, Manusheel Gupta wrote: Are we ready to commit this patch? Well, it's only a year after there were some quite significant discussions about it: http://lists.sugarlabs.org/archive/sugar-devel/2009-October/020141.html There were many concerns. Have they all been addressed? Perhaps just nobody can be bothered to object again? Manu Martin pgpy21YF9tekI.pgp Description: PGP signature ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
