[Sugar-devel] Sugar-devel Digest, Vol 20, Issue 57
Tomeu Vizoso
tomeu at sugarlabs.org
Mon Jun 14 06:50:43 EDT 2010
On Mon, Jun 14, 2010 at 12:37, javed khan <javedkhan2k2 at 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-request at lists.sugarlabs.org>
> wrote:
>>
>> Send Sugar-devel mailing list submissions to
>> sugar-devel at 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-request at lists.sugarlabs.org
>>
>> You can reach the person managing the list at
>> sugar-devel-owner at 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 <andresambrois at gmail.com>
>> Subject: [Sugar-devel] [PATCH 3/3] Add config.py.in and update
>> AC_CONFIG_FILES.
>> To: sugar-devel at lists.sugarlabs.org
>> Cc: dcastelo at plan.ceibal.edu.uy, mabente at paraguayeduca.org
>> Message-ID:
>>
>> <729f759614a6b93e151c86b658b612e2e4cc36d7.1276488220.git.andresambrois at 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 <andresambrois at 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 0000000..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 <anishmangal2002 at gmail.com>
>> Subject: [Sugar-devel] test email, please ignore
>> To: Sugar Devel <sugar-devel at lists.sugarlabs.org>
>> Message-ID:
>> <AANLkTimWM9Svfg_fabtsscH2fBY-7Wh2k_ciQF3njBq9 at 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 <anishmangal2002 at gmail.com>
>> Subject: Re: [Sugar-devel] [PATCH] Add NotifyRedAlert inherited from
>> NotifyAlert
>> To: Sugar Devel <sugar-devel at lists.sugarlabs.org>
>> Message-ID:
>> <AANLkTikJGxjqLsLhNwp1kLRC51-iuLaYIZwmbqPY01Rp at mail.gmail.com>
>> Content-Type: text/plain; charset=UTF-8
>>
>> Hi Michael,
>>
>> > Is this alert really about being red or about notifying the user about
>> > errors
>> > in a more eyecatching fashion?
>>
>> I guess the latter.
>>
>> > The value of the color variable can be more concisely calculated like
>> > so:
>> >
>> > color = "#%02x0000" % self.saturation
>>
>> Thanks, made the change.
>>
>> Cheers,
>> Anish
>>
>>
>>
>> On Mon, Jun 14, 2010 at 6:11 AM, Michael Stone <michael at laptop.org> wrote:
>> > On Mon, Jun 14, 2010 at 02:51:23AM +0530, anishmangal2002 at gmail.com
>> > wrote:
>> >
>> > Hi Anish,
>> >
>> > Thanks for the patches. Here are one small question and one comment for
>> > you...
>> >
>> >> From: anishmangal2002 <anishmangal2002 at gmail.com>
>> >>
>> >> Adds the NotifyRedAlert class which is an alert inherited from
>> >> NotifyAlert. When the alert message is displayed, it glows the
>> >> alert bar Red before slowly fading out to black, thus resulting
>> >> in a more visible notification.
>> >>
>> >> Signed-off-by: anishmangal2002 <anishmangal2002 at gmail.com>
>> >> ---
>> >> src/sugar/graphics/alert.py | 46
>> >> +++++++++++++++++++++++++++++++++++++++++++
>> >> 1 files changed, 46 insertions(+), 0 deletions(-)
>> >>
>> >> diff --git a/src/sugar/graphics/alert.py b/src/sugar/graphics/alert.py
>> >> index 4441909..b4dfee1 100644
>> >> --- a/src/sugar/graphics/alert.py
>> >> +++ b/src/sugar/graphics/alert.py
>> >> @@ -432,3 +432,49 @@ class NotifyAlert(Alert):
>> >> self._response(gtk.RESPONSE_OK)
>> >> return False
>> >> return True
>> >> +
>> >> +class NotifyRedAlert(NotifyAlert):
>> >
>> > Is this alert really about being red or about notifying the user about
>> > errors
>> > in a more eyecatching fashion?
>> >
>> >
>> >> + """
>> >> + Timeout alert with only an "OK" button and a glowing Red border-
>> >> just
>> >> for notifications
>> >> +
>> >> + Examples
>> >> + --------
>> >> +
>> >> + .. code-block:: python
>> >> + from sugar.graphics.alert import NotifyRedAlert
>> >> + ...
>> >> + #### Method: _alert_notify, create a NotifyRed alert (with
>> >> only
>> >> an 'OK'
>> >> + button)
>> >> + # and add it to the UI.
>> >> + def _alert_notify(self):
>> >> + #Notice that for a NotifyRedAlert, you pass the number of
>> >> seconds in
>> >> + #which to notify. By default, this is 5.
>> >> + alert = NotifyRedAlert(10)
>> >> + alert.props.title=_('Title of Alert Goes Here')
>> >> + alert.props.msg = _('Text message of notify alert goes
>> >> here')
>> >> + alert.connect('response', self._alert_response_cb)
>> >> + self.add_alert(alert)
>> >> +
>> >> + """
>> >> +
>> >> + def __init__(self, timeout=5, **kwargs):
>> >> + NotifyAlert.__init__(self, timeout, **kwargs)
>> >> + self.saturation = 255
>> >> +
>> >> + gobject.timeout_add(20, self.__modify_color_timeout)
>> >> +
>> >> + def __modify_color_timeout(self):
>> >> + if self.saturation:
>> >> + self.saturation -= 1
>> >> +
>> >> + # Form the hex color representation
>> >> + if self.saturation <= 15:
>> >> + color = '#0%s0000' % hex(self.saturation)[2:]
>> >> + else:
>> >> + color = '#%s0000' % hex(self.saturation)[2:]
>> >
>> > The value of the color variable can be more concisely calculated like
>> > so:
>> >
>> > color = "#%02x0000" % self.saturation
>> >
>> > Regards,
>> >
>> > Michael
>> >
>>
>>
>> ------------------------------
>>
>> Message: 4
>> Date: Mon, 14 Jun 2010 01:09:17 -0400
>> From: "C. Scott Ananian" <cscott at laptop.org>
>> Subject: Re: [Sugar-devel] Datastore rewrite
>> To: Frederick Grose <fgrose at gmail.com>
>> Cc: sugar-devel at lists.sugarlabs.org
>> Message-ID:
>> <AANLkTinX4W_X3_Y_7w9aqVpCx3oa4BiafNXy0T7xW2nl at mail.gmail.com>
>> Content-Type: text/plain; charset=ISO-8859-1
>>
>> As far as I know, you could use fuse-mounted olpcfs to store the
>> journal files, and obtain this space savings (which is technically
>> known as "deduplication") with no extra effort. You could also store
>> the files in git for the same effect.
>> --scott
>>
>> On Sat, Jun 12, 2010 at 3:07 PM, Frederick Grose <fgrose at gmail.com> wrote:
>> > On Sat, Jun 12, 2010 at 12:57 PM, Bernie Innocenti <bernie at codewiz.org>
>> > wrote:
>> >>
>> >> El Sat, 12-06-2010 a las 11:40 -0400, Benjamin M. Schwartz escribi?:
>> >> > It is one thing to say that we need a new datastore, and another to
>> >> > say
>> >> > what the new datastore should look like. ?I believe we have consensus
>> >> > on
>> >> > the first part, and I'm fairly sure we don't have consensus on the
>> >> > second.
>> >>
>> >> I tend to agree with you.
>> >>
>> >> > For the record, I am pushing a proposal in which no deltas are
>> >> > computed.
>> >> > Files are stored as whole files. ?Instead, I want each datastore
>> >> > object
>> >> > version to consist of an entire directory. ?To save space, files that
>> >> > are
>> >> > identical inside multiple objects would only be stored once on disk.
>> >> > ?This
>> >> > allows us to store and launch Activity Bundles directly from the
>> >> > journal.
>> >> > ?It also allows slight modifications to objects (including
>> >> > activities)
>> >> > to
>> >> > be stored efficiently if the object consists of multiple files and
>> >> > not
>> >> > all
>> >> > of them are changed.
>> >>
>> >> Sounds like a good approach, please ping me to review the spec when
>> >> it's
>> >> available.
>> >
>> > Some references here:
>> > http://wiki.sugarlabs.org/go/Design_Team/Proposals/Journal
>> > Sascha Silbe's Datastore redesign draft with embedded comments from
>> > Eben,
>> > Tomeu, & Sascha:
>> >
>> > https://docs.google.com/a/sugarlabs.org/Doc?docid=0AUl2E5uTm959ZGd3N3FucXdfMWhzbjVjeGht&hl=en
>> > (Sugar Labs account holders may edit this document.)
>> >
>> >>
>> >> As an optimization to reduce the number of inodes and vfs syscalls,
>> >> perhaps it might be worthwhile to let the activity specify whether it
>> >> needs to store one file or a directory with multiple files.
>> >
>> > _______________________________________________
>> > Sugar-devel mailing list
>> > Sugar-devel at lists.sugarlabs.org
>> > http://lists.sugarlabs.org/listinfo/sugar-devel
>> >
>> >
>>
>>
>>
>> --
>> ( http://cscott.net/ )
>>
>>
>> ------------------------------
>>
>> Message: 5
>> Date: Mon, 14 Jun 2010 16:22:14 +1000
>> From: James Cameron <quozl at laptop.org>
>> Subject: Re: [Sugar-devel] [DESIGN] Alerting users in case of write
>> errors (sl#1842)
>> To: Anish Mangal <anishmangal2002 at gmail.com>
>> Cc: Sugar Devel <sugar-devel at lists.sugarlabs.org>, Gary Martin
>> <garycmartin at googlemail.com>
>> Message-ID: <20100614062214.GC6602 at us.netrek.org>
>> Content-Type: text/plain; charset=us-ascii
>>
>> 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/
>>
>>
>> ------------------------------
>>
>> Message: 6
>> Date: Sun, 13 Jun 2010 23:35:30 -0700
>> From: Grant Bowman <grantbow at gmail.com>
>> Subject: [Sugar-devel] excludedocs
>> To: Sugar Devel <sugar-devel at lists.sugarlabs.org>
>> Message-ID:
>> <AANLkTim_qtR0cB1Y-nfFWWQPhzwAvt_ixQ1OSV4LC8ZF at mail.gmail.com>
>> Content-Type: text/plain; charset=ISO-8859-1
>>
>> 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
>>
>>
>> ------------------------------
>>
>> Message: 7
>> Date: Mon, 14 Jun 2010 17:22:04 +1000
>> From: James Cameron <quozl at laptop.org>
>> Subject: Re: [Sugar-devel] excludedocs
>> To: Grant Bowman <grantbow at gmail.com>
>> Cc: Sugar Devel <sugar-devel at lists.sugarlabs.org>
>> Message-ID: <20100614072204.GD6602 at us.netrek.org>
>> Content-Type: text/plain; charset=us-ascii
>>
>> 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 devel at lists.laptop.org
>> mailing list archives. http://lists.laptop.org/
>>
>> --
>> James Cameron
>> http://quozl.linux.org.au/
>>
>>
>> ------------------------------
>>
>> Message: 8
>> Date: Mon, 14 Jun 2010 17:37:15 +1000
>> From: James Cameron <quozl at laptop.org>
>> Subject: Re: [Sugar-devel] ANNOUNCE: Sugar 0.88 for the XO-1
>> To: Bernie Innocenti <bernie at codewiz.org>
>> Cc: forster at ozonline.com.au, sugar-devel at lists.sugarlabs.org
>> Message-ID: <20100614073715.GE6602 at us.netrek.org>
>> Content-Type: text/plain; charset=us-ascii
>>
>> 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/
>>
>>
>> ------------------------------
>>
>> Message: 9
>> Date: Mon, 14 Jun 2010 11:02:40 +0200
>> From: Tomeu Vizoso <tomeu at sugarlabs.org>
>> Subject: Re: [Sugar-devel] activity updater
>> To: Bernie Innocenti <bernie at codewiz.org>
>> Cc: Sugar Devel <sugar-devel at lists.sugarlabs.org>, Gary C Martin
>> <garycmartin at googlemail.com>
>> Message-ID:
>> <AANLkTikybDYcrUtMj4Rcy2JW4cLmXFi60Pzvw0y1B__n at mail.gmail.com>
>> Content-Type: text/plain; charset=ISO-8859-1
>>
>> On Sun, Jun 13, 2010 at 23:51, Bernie Innocenti <bernie at 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 at lists.sugarlabs.org
>> > http://lists.sugarlabs.org/listinfo/sugar-devel
>> >
>>
>>
>> ------------------------------
>>
>> _______________________________________________
>> Sugar-devel mailing list
>> Sugar-devel at lists.sugarlabs.org
>> http://lists.sugarlabs.org/listinfo/sugar-devel
>>
>>
>> End of Sugar-devel Digest, Vol 20, Issue 57
>> *******************************************
>
>
>
> --
> Javid Alam
> Software Developer and Technical support Officer OLPC
> Ministry of Education
> Kabul Afghanistan
> contact: +93(0)798123451
> alternative email: javid.alam at moe.gov.af
>
> _______________________________________________
> Sugar-devel mailing list
> Sugar-devel at lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
>
>
More information about the Sugar-devel
mailing list