Re: [Sugar-devel] [DESIGN] Alerting users in case of write errors (sl#1842)
On Sun, Jun 13, 2010 at 05:27:56PM +0530, Anish Mangal wrote: Thanks for the insightful responses. I have used a slightly modded version of NotifyAlert (aptly called NotifyRedAlert). A sample screen-capture can be found here... Reviewed. I don't like timed alerts, since we have no guarantee that the attention span of the user is contiguous, and given the age of the typical user perhaps it is even more fragmented than we might think. Notification in synchronous response to user action should use the alert mechanism as you have done, just without the timer. Asynchronous notification is entirely different, since it relates to actions by others, delayed response to actions by self, or system events. An invitation to join an activity uses an asynchronous notification on the top left of the toolbar. What we have *now* for asynchronous notification that are not invitations ... can be seen as an icon that appears in the top right of the toolbar. It can be activated by typing this command at a shell prompt: notify-send title some text Unfortunately, in 0.84 at least, while the icon appears there seems to be no way to obtain the notification text. -- 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] excludedocs
On a machine with only 1G SSD I understand why it is necessary to exclude documentation. In starting development and using an XO-1.5 dogfood style I find the lack of documentation troublesome. Online documentation is not a true substitute as this excludedocs setting effects more than just man pages that may or may not be useful for the version that is installed on the local machine. CHANGELOGs and READMEs are also important. Documentation of how best to use --includedocs might also help. I don't put much weight in the arguments that they won't need docs. Anyone climbing any Unix learning curve needs them quite early and especially in the beginning. Anyone using Unix regularly still looks up less frequently used command line options from time to time. For XO 1.5s and for SOAS is there a relatively easy way to change /etc/rpm/macros.imgcreate to remove the excludedocs line? I am sure this has been discussed before. Where can I catch up on previous conversations? Regards, Grant Bowman http://wiki.sugarlabs.org/go/Activities/Toaster ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] excludedocs
On Sun, Jun 13, 2010 at 11:35:30PM -0700, Grant Bowman wrote: For XO 1.5s and for SOAS is there a relatively easy way to change /etc/rpm/macros.imgcreate to remove the excludedocs line? For XO-1.5, yes, edit osbuilder.py and remove the --excludedocs flag in the on_run method of the KspkglistStage class, then construct the build again. There might be other things that need doing as well. I'd be interested in hearing how much extra space is consumed. The extra space may increase costs to a deployment, depending on whether it passes a size threshold. There may be deployment teams who would like to decide whether to keep documentation or not, depending on size of it, and the costs of the various microSD parts they are considering. I don't know about SoaS, sorry. Where can I catch up on previous conversations? For XO-1.5 OLPC build discussions, check out the de...@lists.laptop.org mailing list archives. http://lists.laptop.org/ -- 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] ANNOUNCE: Sugar 0.88 for the XO-1
On Sat, Jun 12, 2010 at 10:00:40AM -0400, Bernie Innocenti wrote: Thou all this people aren't really children. Was there some rationale behind using very large icons with children age 6-12? It's not like they have worse vision than adults. I don't recall, sorry. -- 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] activity updater
On Sun, Jun 13, 2010 at 23:51, Bernie Innocenti ber...@codewiz.org wrote: El Sun, 13-06-2010 a las 20:55 +0100, Gary C Martin escribió: OK, not strictly a patch but attached is an updated version of the currently malformed svg module-updater icon that's not drawing correctly in F13. Not sure who this needs to get to (could only find it in Bernie's old depreciated software update git rep). It should live in the filesystem at: /usr/share/sugar/data/icons/module-updater.svg There are two updaters: the old one written by C.Scott, which is the one in my obsolete repo and Fedora packages, and a new one written from scratch by DFarning for ASLO, which lives in the sugar repository. For the F11-0.88, we have a dilemma: the new updater is missing some crucial features that deployments were relying upon. Daniel Drake and I discussed possible solutions when he visited Paraguay. There are two equally acceptable possibilities: 1) is adding the missing features to the new codebase, which shouldn't be too hard but needs someone to do it by mid-July maximum. Anyone available? 2) The other possibility is adding the OLPC microformat support to ASLO and reverting to the old updater, which would mean less developer time but reintroduces the dependency on bitfrost which we'd rather keep away from the Sugar codebase. Or even a combination of the two. The new query protocol is very slow, so we might want to teach ASLO about the microformat anyway. When I checked the php code with Daniel, it seemed very easy to do. Alsroot and I discussed the possibility to add .xol support to ASLO. While we agree that ASLO isn't a very good fit for static content, we're going to support .xol for the utilitarian purpose of making the updater work in F11-0.88. Wish I had time to help with that, but I wanted to mention that I greatly admire the work you have been doing since you arrived in Paraguay. I specially value your understanding of what is required in the field to make Sugar fulfill its mission and wish people like you had more voice in SLs as opposed to visionaries. Regards, Tomeu -- // Bernie Innocenti - http://codewiz.org/ \X/ Sugar Labs - http://sugarlabs.org/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Sugar-devel Digest, Vol 20, Issue 57
i am working in Ministry of Education Kabul Afghanistan OLPC team as software developer and technical support officer. i want some questions guys. which linux os is best for developing olpc custom images? how to sign a custom image for xo's in my country ? how to put custom image into school server so the xo's can update from ? On Mon, Jun 14, 2010 at 1:32 PM, sugar-devel-requ...@lists.sugarlabs.orgwrote: Send Sugar-devel mailing list submissions to sugar-devel@lists.sugarlabs.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.sugarlabs.org/listinfo/sugar-devel or, via email, send a message with subject or body 'help' to sugar-devel-requ...@lists.sugarlabs.org You can reach the person managing the list at sugar-devel-ow...@lists.sugarlabs.org When replying, please edit your Subject line so it is more specific than Re: Contents of Sugar-devel digest... Today's Topics: 1. [PATCH 3/3] Add config.py.in and update AC_CONFIG_FILES. (Andr?s Ambrois) 2. test email, please ignore (Anish Mangal) 3. Re: [PATCH] Add NotifyRedAlert inherited from NotifyAlert (Anish Mangal) 4. Re: Datastore rewrite (C. Scott Ananian) 5. Re: [DESIGN] Alerting users in case of write errors (sl#1842) (James Cameron) 6. excludedocs (Grant Bowman) 7. Re: excludedocs (James Cameron) 8. Re: ANNOUNCE: Sugar 0.88 for the XO-1 (James Cameron) 9. Re: activity updater (Tomeu Vizoso) -- Message: 1 Date: Mon, 14 Jun 2010 01:14:08 -0300 From: Andr?s Ambrois andresambr...@gmail.com Subject: [Sugar-devel] [PATCH 3/3] Add config.py.in and update AC_CONFIG_FILES. To: sugar-devel@lists.sugarlabs.org Cc: dcast...@plan.ceibal.edu.uy, mabe...@paraguayeduca.org Message-ID: 729f759614a6b93e151c86b658b612e2e4cc36d7.1276488220.git.andresambr...@gmail.com Content-Type: text/plain; charset=utf-8 config.py is generated from config.py.in at configure time by autoconf, so it needs to be added to AC_CONFIG_FILES in configure.ac. Signed-off-by: Andr?s Ambrois andresambr...@gmail.com create mode 100644 extensions/cpsection/modemconfiguration/config.py.in diff --git a/configure.ac b/configure.ac index 13a2f09..68a8bf3 100644 --- a/configure.ac +++ b/configure.ac @@ -56,6 +56,7 @@ extensions/cpsection/frame/Makefile extensions/cpsection/keyboard/Makefile extensions/cpsection/language/Makefile extensions/cpsection/modemconfiguration/Makefile +extensions/cpsection/modemconfiguration/config.py extensions/cpsection/Makefile extensions/cpsection/network/Makefile extensions/cpsection/power/Makefile diff --git a/extensions/cpsection/modemconfiguration/Makefile.am b/extensions/cpsection/modemconfiguration/Makefile.am index 3e2613e..525e02e 100644 --- a/extensions/cpsection/modemconfiguration/Makefile.am +++ b/extensions/cpsection/modemconfiguration/Makefile.am @@ -4,3 +4,5 @@ sugar_PYTHON = \ __init__.py \ model.py\ view.py + +nodist_sugar_PYTHON = config.py diff --git a/extensions/cpsection/modemconfiguration/config.py.inb/extensions/cpsection/modemconfiguration/ config.py.in new file mode 100644 index 000..6fa688e --- /dev/null +++ b/extensions/cpsection/modemconfiguration/config.py.in @@ -0,0 +1,20 @@ +# -*- encoding: utf-8 -*- +# Copyright (C) 2010 Andr?s Ambrois +# +# This program is free software; you can redistribute it and/or modify +# it under the terms of the GNU General Public License as published by +# the Free Software Foundation; either version 2 of the License, or +# (at your option) any later version. +# +# This program is distributed in the hope that it will be useful, +# but WITHOUT ANY WARRANTY; without even the implied warranty of +# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +# GNU General Public License for more details. +# +# You should have received a copy of the GNU General Public License +# along with this program; if not, write to the Free Software +# Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 US + +PROVIDERS_PATH = @prefix@ /share/mobile-broadband-provider-info/serviceproviders.xml +PROVIDERS_FORMAT_SUPPORTED = 2.0 +COUNTRY_CODES_PATH = @prefix@/share/zoneinfo/iso3166.tab -- 1.6.3.3 -- Message: 2 Date: Mon, 14 Jun 2010 10:04:41 +0530 From: Anish Mangal anishmangal2...@gmail.com Subject: [Sugar-devel] test email, please ignore To: Sugar Devel sugar-devel@lists.sugarlabs.org Message-ID: aanlktimwm9svfg_fabtssch2fby-7wh2k_ciqf3nj...@mail.gmail.com Content-Type: text/plain; charset=UTF-8 Something has gone bonkers somewhere and I can't seem to send emails to sugar-devel. Please ignore this email. -- Message: 3 Date: Mon, 14 Jun 2010 10:37:09 +0530 From: Anish Mangal anishmangal2...@gmail.com
Re: [Sugar-devel] Sugar-devel Digest, Vol 20, Issue 57
On Mon, Jun 14, 2010 at 12:37, javed khan javedkhan...@gmail.com wrote: i am working in Ministry of Education Kabul Afghanistan OLPC team as software developer and technical support officer. i want some questions guys. Hi Javed, welcome to our community. which linux os is best for developing olpc custom images? how to sign a custom image for xo's in my country ? how to put custom image into school server so the xo's can update from ? The authoritative mailing list for OLPC-specific questions is this one: http://lists.laptop.org/listinfo/devel There's a big overlap between this and that mailing lists, but there you may find more people focused on the OLPC. For any Sugar-specific questions this mailing list is appropriate. Regards, Tomeu On Mon, Jun 14, 2010 at 1:32 PM, sugar-devel-requ...@lists.sugarlabs.org wrote: Send Sugar-devel mailing list submissions to sugar-de...@lists.sugarlabs.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.sugarlabs.org/listinfo/sugar-devel or, via email, send a message with subject or body 'help' to sugar-devel-requ...@lists.sugarlabs.org You can reach the person managing the list at sugar-devel-ow...@lists.sugarlabs.org When replying, please edit your Subject line so it is more specific than Re: Contents of Sugar-devel digest... Today's Topics: 1. [PATCH 3/3] Add config.py.in and update AC_CONFIG_FILES. (Andr?s Ambrois) 2. test email, please ignore (Anish Mangal) 3. Re: [PATCH] Add NotifyRedAlert inherited from NotifyAlert (Anish Mangal) 4. Re: Datastore rewrite (C. Scott Ananian) 5. Re: [DESIGN] Alerting users in case of write errors (sl#1842) (James Cameron) 6. excludedocs (Grant Bowman) 7. Re: excludedocs (James Cameron) 8. Re: ANNOUNCE: Sugar 0.88 for the XO-1 (James Cameron) 9. Re: activity updater (Tomeu Vizoso) -- Message: 1 Date: Mon, 14 Jun 2010 01:14:08 -0300 From: Andr?s Ambrois andresambr...@gmail.com Subject: [Sugar-devel] [PATCH 3/3] Add config.py.in and update AC_CONFIG_FILES. To: sugar-devel@lists.sugarlabs.org Cc: dcast...@plan.ceibal.edu.uy, mabe...@paraguayeduca.org Message-ID: 729f759614a6b93e151c86b658b612e2e4cc36d7.1276488220.git.andresambr...@gmail.com Content-Type: text/plain; charset=utf-8 config.py is generated from config.py.in at configure time by autoconf, so it needs to be added to AC_CONFIG_FILES in configure.ac. Signed-off-by: Andr?s Ambrois andresambr...@gmail.com create mode 100644 extensions/cpsection/modemconfiguration/config.py.in diff --git a/configure.ac b/configure.ac index 13a2f09..68a8bf3 100644 --- a/configure.ac +++ b/configure.ac @@ -56,6 +56,7 @@ extensions/cpsection/frame/Makefile extensions/cpsection/keyboard/Makefile extensions/cpsection/language/Makefile extensions/cpsection/modemconfiguration/Makefile +extensions/cpsection/modemconfiguration/config.py extensions/cpsection/Makefile extensions/cpsection/network/Makefile extensions/cpsection/power/Makefile diff --git a/extensions/cpsection/modemconfiguration/Makefile.am b/extensions/cpsection/modemconfiguration/Makefile.am index 3e2613e..525e02e 100644 --- a/extensions/cpsection/modemconfiguration/Makefile.am +++ b/extensions/cpsection/modemconfiguration/Makefile.am @@ -4,3 +4,5 @@ sugar_PYTHON = \ __init__.py \ model.py \ view.py + +nodist_sugar_PYTHON = config.py diff --git a/extensions/cpsection/modemconfiguration/config.py.in b/extensions/cpsection/modemconfiguration/config.py.in new file mode 100644 index 000..6fa688e --- /dev/null +++ b/extensions/cpsection/modemconfiguration/config.py.in @@ -0,0 +1,20 @@ +# -*- encoding: utf-8 -*- +# Copyright (C) 2010 Andr?s Ambrois +# +# This program is free software; you can redistribute it and/or modify +# it under the terms of the GNU General Public License as published by +# the Free Software Foundation; either version 2 of the License, or +# (at your option) any later version. +# +# This program is distributed in the hope that it will be useful, +# but WITHOUT ANY WARRANTY; without even the implied warranty of +# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +# GNU General Public License for more details. +# +# You should have received a copy of the GNU General Public License +# along with this program; if not, write to the Free Software +# Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 US + +PROVIDERS_PATH = @prefix@/share/mobile-broadband-provider-info/serviceproviders.xml +PROVIDERS_FORMAT_SUPPORTED = 2.0 +COUNTRY_CODES_PATH = @prefix@/share/zoneinfo/iso3166.tab -- 1.6.3.3 -- Message: 2 Date: Mon, 14 Jun 2010 10:04:41 +0530 From: Anish Mangal anishmangal2...@gmail.com Subject: [Sugar-devel] test email, please
Re: [Sugar-devel] Fructose Dependencies?
On Sun, Jun 13, 2010 at 05:15, Gary C Martin garycmar...@googlemail.com wrote: Hi Guys, Should pygame be listed as an official Fructose Dependency (or even Glucose)? I can't find it referenced on the wiki road map pages. Only ask as have just installed Sugar as the desktop in a regular F13 install and it didn't pull in pygame as a dependency, so will cause failures for things like Pippy, Physics, Maze when added from ASLO. I think so, we should probably add to the platform page the most common dependencies of activities on 802, provided they are generally available in distros. Regards, Tomeu Regards, --Gary ___ 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] Alerting users in case of write errors
El Sun, 13-06-2010 a las 21:04 -0400, Michael Stone escribió: I like the color fade too but the red hue is, for me, a bit overpowering. Have you considered any alternatives like, for example, only applying the red to the border of the alert or using the user's colors instead of red? Yeah, like this one: http://codewiz.org/wiki/$ http://en.wikipedia.org/wiki/Guru_Meditation -- // Bernie Innocenti - http://codewiz.org/ \X/ Sugar Labs - http://sugarlabs.org/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [PATCH] fix malformed svg module-updater icon revealed in F13
On Sun, Jun 13, 2010 at 21:55, Gary C Martin garycmar...@googlemail.com wrote: OK, not strictly a patch but attached is an updated version of the currently malformed svg module-updater icon that's not drawing correctly in F13. Not sure who this needs to get to (could only find it in Bernie's old depreciated software update git rep). It should live in the filesystem at: /usr/share/sugar/data/icons/module-updater.svg TA was the only other broken svg in Sugar on F13 I've seen, Walter has already patched that in git. FWIW the general svg issue seems to be not setting the stroke/fill/stroke-width for a given element and relying on what looks like a side effect default behaviour in the older svg lib. Thanks, have pushed it. Regards, Tomeu Regards, --Gary ___ 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] GCompris packaging
On Fri, Jun 11, 2010 at 10:58:54PM +0200, Bruno Coudoin wrote: Le vendredi 11 juin 2010 à 16:30 -0400, Walter Bender a écrit : Maybe a checkbox system to let a teach customize a collection for a class/grade-level across curricula areas and leave the individual activities available for download for children who want more? This is another option but it will require some computing power to prepare the bundles server side. But we already have Administration activity that customize list of activities. I'm finishing sugarizing it and will release version for testing. The idea is: * There is fully bundled GC all time * teacher creates GC journal object with list of users(to login) and list of activities to run * teacher shares (in sugar terms) this object * students join(or download somehow this object) and run it, they will see only activities that are in list * after finishing some activity by student, results will be saved to this journal object and teacher could see them in runtime (if it is * shared object) or in offline (just by running the same object in Administration activity) -- Aleksey ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] GCompris packaging
On Mon, Jun 14, 2010 at 11:00 AM, Aleksey Lim alsr...@member.fsf.org wrote: On Fri, Jun 11, 2010 at 10:58:54PM +0200, Bruno Coudoin wrote: Le vendredi 11 juin 2010 à 16:30 -0400, Walter Bender a écrit : Maybe a checkbox system to let a teach customize a collection for a class/grade-level across curricula areas and leave the individual activities available for download for children who want more? This is another option but it will require some computing power to prepare the bundles server side. But we already have Administration activity that customize list of activities. I'm finishing sugarizing it and will release version for testing. The idea is: I didn't realize. This seems to be what is needed. -walter * There is fully bundled GC all time * teacher creates GC journal object with list of users(to login) and list of activities to run * teacher shares (in sugar terms) this object * students join(or download somehow this object) and run it, they will see only activities that are in list * after finishing some activity by student, results will be saved to this journal object and teacher could see them in runtime (if it is * shared object) or in offline (just by running the same object in Administration activity) -- Aleksey -- 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] review process changes
On Sat, Jun 12, 2010 at 14:17, Bernie Innocenti ber...@codewiz.org wrote: El Thu, 03-06-2010 a las 12:19 +0200, Tomeu Vizoso escribió: Thanks, this is really useful. A few observations: - how to link tickets and patches? One way is to always end the commit message with a link to the bug: http://bugs.sugarlabs.org/ticket/1622 This is what git-bz does automatically. With proper email search, you can get all tracmail and patch reviews with a single search. +1 - queue control: I still feel it will be harder to find the right patch to review but at the same time, in all the other projects I submit patches to, I need to ping people in irc to get them reviewed. Should we move from a system with a strict queue to a ping-based system? If so, we may need a patch manager as mentioned in http://producingoss.com/en/producingoss.html#patch-manager I'm not a fan of patch managers, but Patchwork seems to be a very good one with a lightweight interface. Ping-based systems work well in practice because it puts the initiative on the side which submitted the patch and presumably cares the most about it. It works more like TCP than ping: if the maintainer forgot about your patch, you keep resending your patch until you obtain an ACK (or a NAK). Like in TCP, resending should be an exceptional case. If all patches routinely need to be resent multiple times, it means that we have insufficient reviewer bandwidth. I'm ok with moving to a ping-based system. In my upstream work, I find myself having to ping people all the time so my patches get reviewed, even if bugzilla has quite good patch management and there are tools for automating it such as git-bz and splinter. Regards, Tomeu -- // Bernie Innocenti - http://codewiz.org/ \X/ Sugar Labs - http://sugarlabs.org/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Fwd: Problems adapting activity
Again, I forgot to send it to all. -- Forwarded message -- From: Alberto Arruda de Oliveira alberto.a.o...@gmail.com Date: 2010/6/14 Subject: Re: [Sugar-devel] Problems adapting activity To: Daniel Drake d...@laptop.org Sorry for taking so long to answer. Anyway, the null.png problem is quite weird, since I could find it there. It seems like the problem now isn't with the adaptation, but with the code itself. Thank you all for the help. I'll update here if I make any progress / find any other problem. 2010/6/11 Daniel Drake d...@laptop.org On 11 June 2010 08:43, Alberto Arruda de Oliveira alberto.a.o...@gmail.com wrote: Here's the log my activity generated. 1276255872.662322 WARNING root: Bundle Blocos: invalid entry in MANIFEST: COPYING 1276255872.664506 WARNING root: Bundle Blocos: MANIFEST includes itself: MANIFEST aviso! imagem 'null.png' nao encontrada Traceback (most recent call last): File /usr/bin/sugar-activity, line 136, in module create_activity_instance(activity_constructor, activity_handle) File /usr/bin/sugar-activity, line 36, in create_activity_instance activity = constructor(handle) File /home/amarcorin/Activities/Blocos.activity/Blocos.py, line 99, in __init__ self.generate_blocklist() File /home/amarcorin/Activities/Blocos.activity/Blocos.py, line 420, in generate_blocklist self.add_block_tree( self.treeList[0], None, on_block() ) File /home/amarcorin/Activities/Blocos.activity/Blocos.py, line 395, in add_block_tree if block.get_width() self.maxblockwidth: File /home/amarcorin/Activities/Blocos.activity/blockcanvas/block.py, line 599, in get_width return self.get_image()[0].get_width() AttributeError: 'NoneType' object has no attribute 'get_width' Seems like the main problem is the MANIFEST thing. Also, a lot of stuff that seems related to the code itself, although, most of them are pretty strange, since I didn't really change anything within the code besides importing the sugar class and doing the changes related to it. The MANIFEST thing is unrelated and harmless. I guess your error is that the activity cannot locate null.png Daniel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [DESIGN] Alerting users in case of write errors
El Mon, 14-06-2010 a las 10:06 -0400, Bernie Innocenti escribió: Yeah, like this one: http://codewiz.org/wiki/$ http://en.wikipedia.org/wiki/Guru_Meditation If it wasn't sufficiently clear: ;-P -- // Bernie Innocenti - http://codewiz.org/ \X/ Sugar Labs - http://sugarlabs.org/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] activity updater
On Sun, Jun 13, 2010 at 4:51 PM, Bernie Innocenti ber...@codewiz.org wrote: El Sun, 13-06-2010 a las 20:55 +0100, Gary C Martin escribió: OK, not strictly a patch but attached is an updated version of the currently malformed svg module-updater icon that's not drawing correctly in F13. Not sure who this needs to get to (could only find it in Bernie's old depreciated software update git rep). It should live in the filesystem at: /usr/share/sugar/data/icons/module-updater.svg There are two updaters: the old one written by C.Scott, which is the one in my obsolete repo and Fedora packages, and a new one written from scratch by DFarning for ASLO, which lives in the sugar repository. To give credit where credit is due, the ASLO updater is just a update of Scott's code to parse the xml ASLO dynamically creates rather than micoroformat. david For the F11-0.88, we have a dilemma: the new updater is missing some crucial features that deployments were relying upon. What missing features are important? david Daniel Drake and I discussed possible solutions when he visited Paraguay. There are two equally acceptable possibilities: 1) is adding the missing features to the new codebase, which shouldn't be too hard but needs someone to do it by mid-July maximum. Anyone available? 2) The other possibility is adding the OLPC microformat support to ASLO and reverting to the old updater, which would mean less developer time but reintroduces the dependency on bitfrost which we'd rather keep away from the Sugar codebase. Or even a combination of the two. The new query protocol is very slow, so we might want to teach ASLO about the microformat anyway. When I checked the php code with Daniel, it seemed very easy to do. Alsroot and I discussed the possibility to add .xol support to ASLO. While we agree that ASLO isn't a very good fit for static content, we're going to support .xol for the utilitarian purpose of making the updater work in F11-0.88. -- // Bernie Innocenti - http://codewiz.org/ \X/ Sugar Labs - http://sugarlabs.org/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] core maintainers
On Fri, Jun 11, 2010 at 18:39, David Farning dfarn...@gmail.com wrote: Over the past couple of months it has appeared that the ramp up of deployment submitted patches has stretched the core maintainers rather short. I would like to consider having Deployment Support Network developers start accepting additional maintainership responsibility and authority. Specifically, I am interested in which core activities are in need of a maintainer and which core modules are up for adoption. With this information, I can start identifying and recruiting potential maintainers. From my POV, in order of need/suitability: - Read - Write - Browse - hulahop - Imageviewer - Terminal I would also love help maintaining the sugar module and other maintainers may feel the same. I'm also thinking how we can hook up new maintainers best, as most skills required for this job are learned on the go. Will update soon. Regards, Tomeu david ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Hypothetical sugar-0.90 material, draft 1.
On Sat, Jun 12, 2010 at 16:15, Bernie Innocenti ber...@codewiz.org wrote: El Sat, 12-06-2010 a las 10:26 +0200, Simon Schampijer escribió: PS I'm sure Walter will back me up here! Can someone explain me what a development manager is? Didn't we talk about about Release Management? I hope people don't want to throw away what we have been establishing over the last releaeses. Our release and Feature process have been in place for several releases and to change that there should be good reasons to do so. I don't see any yet. +1. I would also very much like our next RM to preserve our 6-months release cycle and keep it synchronized with the major Linux distros, like GNOME and other high-profile projects do. FWIW, I think that keeping Sugar aligned with GNOME and other downstreams of the GNOME platform will be key for putting a limit to the growing maintenance costs. This does not imply that we cannot ever do very large restructuring of our codebase, if needed. This kind of work just needs to happen in a development trees and be merged when it's sufficiently stable. Right, other projects keep the 6 month cycle and do radical revampings from time to time. We can also do it if it's really worth it. Regards, Tomeu -- // Bernie Innocenti - http://codewiz.org/ \X/ Sugar Labs - http://sugarlabs.org/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [DESIGN] Alerting users in case of write errors
To sum up, these are the possible suggestions we have on the plate (please add if I missed anything)... 1. No fancy gimmicks, just the plain old NotifyAlert 2. A NotifyAlert that is initially Red and then slowly fades to black over its lifetime 3. Only turn the border red instead of the full background 4. Don't use red, use the user's color 5. Don't make the alert timeout and disappear. 6. Use icons next to the alert text (see below) -- In addition, I was thinking that perhaps the Alert dialogs should display some icons beside the text depending on the alert type. Maybe we could make do with these with or without the colors. Cheers, Anish P.S. To a relative newbie (like me) [1] makes for very interesting reading (as does the rest of the HIG) [1] http://wiki.laptop.org/go/OLPC_Human_Interface_Guidelines/The_Sugar_Interface/Colors On Mon, Jun 14, 2010 at 6:34 AM, Michael Stone mich...@laptop.org wrote: Gary wrote: On 13 Jun 2010, at 12:57, Anish Mangal anishmangal2...@gmail.com wrote: An alert like a chat or Activity sharing invitation would be nice, but one with a more visible signal is needed. We really really really ... need a general notification system. :D Please no popup error dialogue windows if you can avoid it ;) The alert strip that displays under the toolbar is a much more friendly notification for the Sugar UI design. Thanks for the insightful responses. I have used a slightly modded version of NotifyAlert (aptly called NotifyRedAlert). A sample screen-capture can be found here... http://people.sugarlabs.org/~anish/sl1842-journal.gif Note: The link above is a big animated gif (~1.8M) and some browsers may struggle to display it. Yea, my iPad chocked half way through :) If this seems fine, I'll mail the patch for reviewing. Looks nice. The colour fade (red to black over the time-out countdown) is something new and not in the Sugar HIG, but I don't have an objection — makes fair warning UI sense and could be something we adopt elsewhere when needed (if there aren't too many objections). Anish, Gary, I like the color fade too but the red hue is, for me, a bit overpowering. Have you considered any alternatives like, for example, only applying the red to the border of the alert or using the user's colors instead of red? Kind regards, Michael ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] core maintainers
On Mon, Jun 14, 2010 at 12:36 PM, Tomeu Vizoso to...@sugarlabs.org wrote: On Fri, Jun 11, 2010 at 18:39, David Farning dfarn...@gmail.com wrote: Over the past couple of months it has appeared that the ramp up of deployment submitted patches has stretched the core maintainers rather short. I would like to consider having Deployment Support Network developers start accepting additional maintainership responsibility and authority. Specifically, I am interested in which core activities are in need of a maintainer and which core modules are up for adoption. With this information, I can start identifying and recruiting potential maintainers. From my POV, in order of need/suitability: - Read - Write AC will accept responsibility for Read and Write. - Browse - hulahop AC will not be providing support for browse and hulahop. - Imageviewer - Terminal These are lower priority but we will pick them up as we build resources. I would also love help maintaining the sugar module and other maintainers may feel the same. I'm also thinking how we can hook up new maintainers best, as most skills required for this job are learned on the go. Will update soon. With regard the maintainer mentoring, I think we are in agreement on this. As such I will be reaching out to developers at deployments and providing incentives for them to invest the effort necessary to become core maintainers. david ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] GCompris packaging
Le lundi 14 juin 2010 à 11:02 -0400, Walter Bender a écrit : On Mon, Jun 14, 2010 at 11:00 AM, Aleksey Lim alsr...@member.fsf.org wrote: On Fri, Jun 11, 2010 at 10:58:54PM +0200, Bruno Coudoin wrote: Le vendredi 11 juin 2010 à 16:30 -0400, Walter Bender a écrit : Maybe a checkbox system to let a teach customize a collection for a class/grade-level across curricula areas and leave the individual activities available for download for children who want more? This is another option but it will require some computing power to prepare the bundles server side. But we already have Administration activity that customize list of activities. I'm finishing sugarizing it and will release version for testing. The idea is: I didn't realize. This seems to be what is needed. -walter * There is fully bundled GC all time * teacher creates GC journal object with list of users(to login) and list of activities to run * teacher shares (in sugar terms) this object * students join(or download somehow this object) and run it, they will see only activities that are in list * after finishing some activity by student, results will be saved to this journal object and teacher could see them in runtime (if it is * shared object) or in offline (just by running the same object in Administration activity) I am glad to see Aleksey filling the gap between GCompris and the Sugar community. The proposed approach relies on the most advanced features of both project. I hope it will work. -- Bruno Coudoin http://gcompris.net Free educational software for kids http://toulibre.org Logiciel Libre à Toulouse http://april.org Promouvoir et défendre le Logiciel Libre ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [IAEP] ANNOUNCE: F11-0.88 Alpha2 (os258py)
Bernie * Disabled the hot corners for the frame, as requested by participants of the OLPC Realness Summit. I'm not convinced this is really a gain, but let's first see how many people ask to revert this change (tch, bernie) good news is that this can be easily reverted with the control panel Journal list view icon does not display after selection http://wiki.sugarlabs.org/go/File:Listviewos258.jpg Default font, menus etc seems large, larger than it used to be. I dont have a strong opinion on what size it should be but it is inconveniently large in the url and page title of browse with not many chars visible Tony ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
