Re: Mentor request for PyDebug Activity
George, I am curious why start on a new activity? The Develop activity is well along and needs bug fixing and updating. A debugger would be a nice addition to it. http://wiki.laptop.org/go/Develop http://git.sugarlabs.org/projects/develop rihowa...@gmail.com linux - the best things in life are free On Oct 14, 2009, at 2:56 PM, George Hunt wrote: I am excited about developing a tool to help me develop other XO Activities. When I shared my ideas with Adam Holt, he suggested that I seek a mentor, or a few partners to help me clarify my ideas, and increase the usefulness of the end product. I am writing this to request such help. As a programmer, I'm fairly new to python. I started writing assembly language in 1975 for the terminal division of Hewlett-- Packard, which was soon to become the Personal Computer division. I only started python after I got my G1G1 in early 2008. I'm fairly averse to re-inventing the wheel. So I have been thinking of combining Activities that already run on the XO as my main strategy. At this point I have hacked together Write, Terminal, and Browse to all exist in a notebook under the Sugar toolbar. I can read and write Activity.xo files from the journal. So I've learned a lot from what is already written. Whatever the final form factor, the work I've done up to now will not be lost. At this point I'm debating whether to substitute gedit for the functionality of abiword. Gedit includes many of the feature a programmer is looking for. It is extensively internationalized. It has a python extension system that I think will make for easy integration into my application. I'm leaning towards the structure of a remote debugger, even though the client and server will mostly reside on the same machine. I'd like for the application to be insulated from errant client programs. I'm having a lot of fun, and feeling much more productive than I did a few months ago. I'd love to hear from a few people who are willing to help me perfect my ideas or have experience that could keep me from going down unfruitful paths. I've written a wiki page trying to pull together some of my ideas: http://wiki.laptop.org/go/ Python_Debugger_activity_for_the_XO. There is also a little more bio info about me at http://wiki.laptop.org/go/User:GeorgeHuntd Thanks, George ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] incremental activity update
2009/10/15 Martin Langhoff : > For the F9 series (8.2.1) my current plan is to work to polish the > imagecreator scripts so that it is easier for deployents to > > - prepare a custom image (mostly covered) > - base on an existing image ("in place", even if the tar isn't available) > - create and inject signatures with the local keys (ofw, initramfs, kernel) I know I myself hacked the image-builder script into this direction, but in hindsight I feel that it got too hacky and that was the wrong approach. It presented various surprises along the way and at the very end left me with the "this is the wrong thing" feeling. I feel that for making such customizations, the deployments should clone the build setup (pilgrim) and make changes there. It's more complex but works well and doesn't leave such a bad taste in the mouth. Daniel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: XO-1 Build 802 doesn't turn off speaker amplifier
james wrote: > On Sat, Oct 10, 2009 at 11:00:29PM +0100, Tiago Marques wrote: > > As anyone ever measured this? > > I've just measured it now. > > Unfortunately my meter lacks accuracy on this range, but in two tests, > with or without backlight, without any battery, I saw a 20mA (+/- 10mA) > improvement as a result of disabling the amplifier with alsamixer. The > hiss from the speakers also went away. (I had to place my ears within a > few inches to be able to hear the change). The input voltage 12.06V. this sounds worthy of a trac ticket, as well as the attention of any F11-on-XO1 folks. paul > > There was no change to the current consumed during suspend. > > -- > James Cameron > http://quozl.linux.org.au/ > ___ > Devel mailing list > Devel@lists.laptop.org > http://lists.laptop.org/listinfo/devel =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: XO-1 Build 802 doesn't turn off speaker amplifier
On Sat, Oct 10, 2009 at 11:00:29PM +0100, Tiago Marques wrote: > As anyone ever measured this? I've just measured it now. Unfortunately my meter lacks accuracy on this range, but in two tests, with or without backlight, without any battery, I saw a 20mA (+/- 10mA) improvement as a result of disabling the amplifier with alsamixer. The hiss from the speakers also went away. (I had to place my ears within a few inches to be able to hear the change). The input voltage 12.06V. There was no change to the current consumed during suspend. -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] MANIFEST experiments
Confirmed. On Wed, Oct 14, 2009 at 05:29:09PM +0545, Daniel Drake wrote: > So, I reflashed 2 XOs, booted for the first time, entered a name. On > one, I modified sugar.bundle.ActivityBundle.read_manifest() to be a > no-op, then turned it off. On the other, I just turned it off. I reproduced this experiment. Used build 802, with a limited set of 22 activities [1], with a similar change [2]. > Then I powered both on at the same time and started a stopwatch. I > measured how long it takes for the XOs to reach the stage of boot > where the XO stick figure and the activity icons are visible. 1255565448 power up both XOs 1255565533 modified XO boot complete 1255565539 unmodified XO boot complete > The one with the modification reached this point *55* seconds faster > than the other one! In my case, about 6 seconds. I feel that even this small time was worth it, so I plan to patch this for the friends' kids I've got laptops deployed to. Is there a collection of 802 performance improvement patches? Notes: 1. the activities installed were from "G1G1 Activities for 8.2" and were "Browse Calculate Chat Distance Etoys Implode Maze Measure Memorize Moon Paint Pippy Read Record Ruler Scratch Speak TamTamMini TamTamSynthLab Terminal TurtleArt Write" 2. the change was to activitybundle.py in /usr/lib/python2.5/site-packages/sugar/bundle/ and removed all code in read_manifest(), leaving just "pass": def read_manifest(self): pass -- James Cameron http://quozl.linux.org.au/ --- activitybundle.py.orig 2009-10-15 00:09:04.0 + +++ activitybundle.py 2009-10-15 00:09:40.0 + @@ -79,43 +79,7 @@ return ret def read_manifest(self): -"""read_manifest: sets self.manifest to list of lines in MANIFEST, -with invalid lines replaced by empty lines. - -Since absolute order carries information on file history, it should -be preserved. For instance, when renaming a file, you should leave -the new name on the same line as the old one. -""" -lines = self._raw_manifest() - -# Remove trailing newlines, they do not help keep absolute position. -while lines and lines[-1] == "": -lines = lines[:-1] - -for num, line in enumerate(lines): -if not line: -continue - -# Remove duplicates -if line in lines[0:num]: -lines[num] = "" -logging.warning("Bundle %s: duplicate entry in MANIFEST: %s" -% (self._name,line)) -continue - -# Remove MANIFEST -if line == "MANIFEST": -lines[num] = "" -logging.warning("Bundle %s: MANIFEST includes itself: %s" -% (self._name,line)) - -# Remove invalid files -if not self.is_file(line): -lines[num] = "" -logging.warning("Bundle %s: invalid entry in MANIFEST: %s" -% (self._name,line)) - -self.manifest = lines + pass def get_files(self, manifest = None): files = [line for line in (manifest or self.manifest) if line] ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Hosting Request for PyDebug Activity debugger
1. Project name :PyDebug Python Debugger for XO activities 2. Existing website, if any : 3. One-line description :Provide native stand alone facility for writing and debugging Activities 4. Longer description :This project is to combine programs which currently exist on :the XO, or easily modifiable thereto, to create, modify, debug, :and ultimately distribute finished Activity packages : 5. URLs of similar projects : I suppose ActiveState's Komodo debugger is similar, although source code : debuugging seems too much for the first pass. Command line debugging is ok 6. Committer list Please list the maintainer (lead developer) as the first entry. Only list developers who need to be given accounts so that they can commit to your project's code repository, or push their own. There is no need to list non-committer developers. Username Full name SSH2 key URLE-mail - -- #1 ghunt George Hunt georgejh...@gmail.com #2 #3 ... If any developers don't have their SSH2 keys on the web, please attach them to the application e-mail. 7. Preferred development model [X] Central tree. Every developer can push his changes directly to the project's git tree. This is the standard model that will be familiar to CVS and Subversion users, and that tends to work well for most projects. [] Maintainer-owned tree. Every developer creates his own git tree, or multiple git trees. He periodically asks the maintainer to look at one or more of these trees, and merge changes into the maintainer-owned, "main" tree. This is the model used by the Linux kernel, and is well-suited to projects wishing to maintain a tighter control on code entering the main tree. If you choose the maintainer-owned tree model, but wish to set up some shared trees where all of your project's committers can commit directly, as might be the case with a "discussion" tree, or a tree for an individual feature, you may send us such a request by e-mail, and we will set up the tree for you. 8. Set up a project mailing list: [ ] Yes, named after our project name [ ] Yes, named __ [X] No When your project is just getting off the ground, we suggest you eschew a separate mailing list and instead keep discussion about your project on the main OLPC development list. This will give you more input and potentially attract more developers to your project; when the volume of messages related to your project reaches some critical mass, we can trivially create a separate mailing list for you. If you need multiple lists, let us know. We discourage having many mailing lists for smaller projects, as this tends to stunt the growth of your project community. You can always add more lists later. 9. Commit notifications [ ] Notification of commits to the main tree should be e-mailed to the list we chose to create above [ ] A separate mailing list, -git, should be created for commit notifications [X] No commit notifications, please 10. Shell accounts As a general rule, we don't provide shell accounts to developers unless there's a demonstrated need. If you have one, please explain here, and list the usernames of the committers above needing shell access. 11. Translation [X] Set up the laptop.org Pootle server to allow translation commits to be made [ ] Translation arrangements have already been made at ___ 12. Notes/comments: I would really appreciate the help and support of a mentor. Adam Holt suggested it. I would love to be able to talk over ideas and trade-offs. id_rsa.pub Description: Binary data ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Mentor request for PyDebug Activity
I am excited about developing a tool to help me develop other XO Activities. When I shared my ideas with Adam Holt, he suggested that I seek a mentor, or a few partners to help me clarify my ideas, and increase the usefulness of the end product. I am writing this to request such help. As a programmer, I'm fairly new to python. I started writing assembly language in 1975 for the terminal division of Hewlett--Packard, which was soon to become the Personal Computer division. I only started python after I got my G1G1 in early 2008. I'm fairly averse to re-inventing the wheel. So I have been thinking of combining Activities that already run on the XO as my main strategy. At this point I have hacked together Write, Terminal, and Browse to all exist in a notebook under the Sugar toolbar. I can read and write Activity.xo files from the journal. So I've learned a lot from what is already written. Whatever the final form factor, the work I've done up to now will not be lost. At this point I'm debating whether to substitute gedit for the functionality of abiword. Gedit includes many of the feature a programmer is looking for. It is extensively internationalized. It has a python extension system that I think will make for easy integration into my application. I'm leaning towards the structure of a remote debugger, even though the client and server will mostly reside on the same machine. I'd like for the application to be insulated from errant client programs. I'm having a lot of fun, and feeling much more productive than I did a few months ago. I'd love to hear from a few people who are willing to help me perfect my ideas or have experience that could keep me from going down unfruitful paths. I've written a wiki page trying to pull together some of my ideas: http://wiki.laptop.org/go/Python_Debugger_activity_for_the_XO. There is also a little more bio info about me at http://wiki.laptop.org/go/User:GeorgeHuntd Thanks, George ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] incremental activity update
On Wed, Oct 14, 2009 at 1:19 PM, Tomeu Vizoso wrote: > Wonder how we could make it easier for other deployments to benefit > from these changes. For the F9 series (8.2.1) my current plan is to work to polish the imagecreator scripts so that it is easier for deployents to - prepare a custom image (mostly covered) - base on an existing image ("in place", even if the tar isn't available) - create and inject signatures with the local keys (ofw, initramfs, kernel) in addition to that, I hope I can pull a "8.2.2" image collecting these patches. See my 'papercuts' post a while ago. Can't promise when or how, but it's on my list. Unless someone beats me to it... 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 ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] MANIFEST experiments
On 14.10.2009, at 13:44, Daniel Drake wrote: > Today I ran a quick experiment on OLPC OS v8.2.1, based on the > question: what are the activity MANIFEST files used for? > > I see sugar frequently complaining about MANIFEST inconsistencies in > the logs, but I don't recall seeing it act on these inconsistencies in > any way. I noticed that it even logs such inconsistencies during > startup, meaning that it must be checking every file in every activity > during a regular boot... > > So, I reflashed 2 XOs, booted for the first time, entered a name. On > one, I modified sugar.bundle.ActivityBundle.read_manifest() to be a > no-op, then turned it off. On the other, I just turned it off. > > Then I powered both on at the same time and started a stopwatch. I > measured how long it takes for the XOs to reach the stage of boot > where the XO stick figure and the activity icons are visible. > > The one with the modification reached this point *55* seconds faster > than the other one! It basically zeroes the time where you can see the > XO stick figure on screen but the activity icons on the home view have > yet to appear. > > This was using OLE Nepal's customized build which includes a big > activity with many manifest errors, so the difference might be less > elsewhere. > > Tomeu points out that this behaviour has been improved in more recent > sugar versions to the point where manifest checking probably is not > happening in the startup path, but personally I question why we are > even checking at all. Perhaps we should rip out all that code and > leave MANIFESTs purely as a tool for developers to specify which files > get included in a bundle or something like that. I did indeed think that's the entire purpose of it. - Bert - ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
MANIFEST experiments
Today I ran a quick experiment on OLPC OS v8.2.1, based on the question: what are the activity MANIFEST files used for? I see sugar frequently complaining about MANIFEST inconsistencies in the logs, but I don't recall seeing it act on these inconsistencies in any way. I noticed that it even logs such inconsistencies during startup, meaning that it must be checking every file in every activity during a regular boot... So, I reflashed 2 XOs, booted for the first time, entered a name. On one, I modified sugar.bundle.ActivityBundle.read_manifest() to be a no-op, then turned it off. On the other, I just turned it off. Then I powered both on at the same time and started a stopwatch. I measured how long it takes for the XOs to reach the stage of boot where the XO stick figure and the activity icons are visible. The one with the modification reached this point *55* seconds faster than the other one! It basically zeroes the time where you can see the XO stick figure on screen but the activity icons on the home view have yet to appear. This was using OLE Nepal's customized build which includes a big activity with many manifest errors, so the difference might be less elsewhere. Tomeu points out that this behaviour has been improved in more recent sugar versions to the point where manifest checking probably is not happening in the startup path, but personally I question why we are even checking at all. Perhaps we should rip out all that code and leave MANIFESTs purely as a tool for developers to specify which files get included in a bundle or something like that. Daniel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] incremental activity update
2009/10/14 Tomeu Vizoso : > Wonder how we could make it easier for other deployments to benefit > from these changes. > > Do you have plans to push the changes to the sugar-update-control repo > and spin new F9 rpms? No - my time is too tight and at least for Paraguay and Nepal it's easier to apply customizations as patches rather than to add RPMs. Daniel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] incremental activity update
On Wed, Oct 14, 2009 at 11:43, Daniel Drake wrote: > Hi, > > At OLE Nepal we have difficulties with updating activities because our > main educational activity is so huge. Aayush Poudel implemented an > incremental activity update which I have now merged with the standard > software updater. When updating activities and content, the updater > now only downloads the files of the new activity that have changed, > greatly reducing time and bandwidth needed for updates. > > Patches at > http://dev.sugarlabs.org/ticket/1499 > > We're also adding the patch I used in paraguay so that the updater > does not try to go online when the school server has an activity > available: > http://dev.laptop.org/ticket/9259 > > I hope this is useful for other deployments too! Wonder how we could make it easier for other deployments to benefit from these changes. Do you have plans to push the changes to the sugar-update-control repo and spin new F9 rpms? Regards, Tomeu -- «Sugar Labs is anyone who participates in improving and using Sugar. What Sugar Labs does is determined by the participants.» - David Farning ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
incremental activity update
Hi, At OLE Nepal we have difficulties with updating activities because our main educational activity is so huge. Aayush Poudel implemented an incremental activity update which I have now merged with the standard software updater. When updating activities and content, the updater now only downloads the files of the new activity that have changed, greatly reducing time and bandwidth needed for updates. Patches at http://dev.sugarlabs.org/ticket/1499 We're also adding the patch I used in paraguay so that the updater does not try to go online when the school server has an activity available: http://dev.laptop.org/ticket/9259 I hope this is useful for other deployments too! Daniel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Server-devel] XS-0.6 -
On Sat, Oct 10, 2009 at 2:07 AM, Martin Langhoff wrote: > On Sat, Oct 10, 2009 at 10:57 AM, Martin Langhoff > wrote: >> We probably need a procedure to dump-and-recreate the Moodle DB >> because now it is half-there and it probably won't init correctly any >> more. > > http://wiki.laptop.org/go/XS_Techniques_and_Configuration#Moodle_Initialization_Fails > > == Moodle Initialization Fails == > > During the first boot after an installation or upgrade Moodle will run > its installation/upgrade scripts. These scripts are triggered by the > existence of /etc/moodle/needsupgrade and when they > execute, they log to /var/log/moodle-instupg.log. > > If there is no /etc/moodle/needsupgrade and the log ends > with a line saying 'Success', Moodle should be installed and running > correctly. > > In case the initialization/upgrade has failed > > * Make sure to report the situation to the server-devel mailing list, > attaching /var/log/moodle-instupg.log, and a description > of the situation. > * Drop the database: sudo -u postgres dropdb moodle-xs > * Start the Moodle 'service': service moodle-xs start. > This may take a while (specially on XS-on-XO) and you can trace the > execution by 'tailing' the logfile with tail -f > /var/log/moodle-instupg.log from a different console. > > > > > 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 > So, I re-did the install (fdisk the SD card) and let the initial boot run. I fell asleep after waiting for 1/2 hour at the Moodle upgrade point :-) Morning did yield a cleanly installed XS-on-XO. "/etc/sysconfig/olpc-scripts/domain_config sfsu.edu" followed by a reboot and everything worked as expected. Registered the first XO cleanly. Also installed Munin and Munin-node to collect graphed data (See attached. Blip is when I registered the first XO). Looking good so far. cheers, Sameer -- Dr. Sameer Verma, Ph.D. Associate Professor, Information Systems Director, Center for Business Solutions San Francisco State University http://verma.sfsu.edu/ http://cbs.sfsu.edu/ http://is.sfsu.edu/ <>___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel