Re: GSoC 2009?
Sounds like a fine idea to me, Martin. Assuming we are accepted again as a mentoring org, we should be eligible for more projects than last year. But do bear in mind that we may not get anyone interested in those projects; and that a successful GSoC internship is primarily about a good experience developing a meaningful product, and the interns are free to define how to tackle the problem they undertake. SJ On Sun, Jan 25, 2009 at 9:47 PM, Martin Langhoff martin.langh...@gmail.com wrote: Ed, devel, server-devel, sj GSoC GSoC is looming. I am thinking of putting some of the things that I was planning to do in the next X months as GSoC projects (and that I know I'm unlikely to hit). Ideally, I would take take 2 or 3 mentees, with a preference towards those who live in deployment regions... retry/ignore/fail? 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] Pippy not ready for Sucrose
On Fri, Jan 23, 2009 at 2:21 PM, Simon Schampijer si...@schampijer.de wrote: Simon Schampijer wrote: Hi, the Sucrose package of Pippy is version 25 - when I last released it back in August. Since then there has been some development going into Pippy (now version 30) http://dev.laptop.org/git?p=projects/pippy-activity;a=shortlog But none of the maintainers did follow the Sucrose release cycle, even though I sent a reminder http://lists.laptop.org/pipermail/sugar/2008-November/010021.html Any, specific reason for that? Pippy has not been moved to git.sugarlabs.org, as well. please indicate clearly: * if you still want to be part of Sucrose (including following the release cycle) * any new maintainer that is willing to do this task if you does not want to * any issues/reasons you have to do so Best, Simon To follow up on this, I mainly want to find a maintainer for Pippy for Sucrose. If there is no one willing to do that we drop it, which is ok - one can still download the xo etc, I just want a clearer situation. Hi, I will maintain Pippy for Sucrose, though I may need a bit of hand holding. Please let me know if what I did seems correct (esp. step 2): 1. l got the most recent version of Pippy from git git-clone git://dev.laptop.org/projects/pippy-activity cd pippy-activity 2. ./setup.py gave a bunch of invalid entry in MANIFEST errors about different locales, so I ran: ./setup.py fix_manifest 3. ./setup.py dist_source 4. I asked a crank sysadmin to add me to the Sugar group, And I moved Pippy-30.tar.bz2 to: http://dev.laptop.org/pub/sugar/sources/Pippy/Pippy-30.tar.bz2 (805K) I will move pippy over to git.sugarlabs.org as well. Thanks, Brian Wade, do you have maybe someone in mind? Cheers, Simon ___ Sugar-devel mailing list sugar-de...@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Notes from an impromptu 8.2.1 Release Mtg.
Hal Murray wrote: please-help-test-this messages but I could easily have missed one. The latest version is Q2E28. I'm reasonably sure that it didn't get much testing since I just fixed a typo on the wiki page in the URL to download the bits. Anyway, most of the testing below was done with Q2E24. I've updated to Q2E28 and a quick test didn't show any changes. Right now e28 is what you should be testing. When the next f series release comes out (RSN) then that will be the new series going forward. Even when it isn't a total disaster, the cursor is still very hard to use. The problem seems to happen when I lift my finger off the pad so I can move it over and set it down to continue a long move. Yes, I could be being sloppy and moving before I lift, but I've been working/playing with it enough that I don't think it's me, or if it is, other normal users will be totally frustrated. Sometimes it jumps to the lower left corner. Again, this is a B2 chasis with a B3 board. If the cursor pad stuff has changed I apologize for the noise. In a B2 chassis you are going to see worse performance than later chassis as we added metal in the B3. And why do not have a MP (C2)? Mail me your shipping address and I'll see that you get a new machine. -- Richard Smith rich...@laptop.org One Laptop Per Child ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
New staging build 10
http://xs-dev.laptop.org/~cscott/xo-1/streams/staging/build10 Changes in build 10 from build: 8 Size delta: 0.00M -glibc 2.8-8 +glibc 2.8-11 -glibc-common 2.8-8 +glibc-common 2.8-11 -- This mail was automatically generated See http://dev.laptop.org/~rwh/announcer/staging-pkgs.html for aggregate logs See http://dev.laptop.org/~rwh/announcer/joyride_vs_update1.html for a comparison ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] Pippy not ready for Sucrose
Awesome, thank you Brian for stepping up! Is something additional required in order to make sure the activity runs properly in SoaS or jhbuild? -Wade On Mon, Jan 26, 2009 at 2:14 PM, Brian Jordan br...@laptop.org wrote: On Fri, Jan 23, 2009 at 2:21 PM, Simon Schampijer si...@schampijer.de wrote: Simon Schampijer wrote: Hi, the Sucrose package of Pippy is version 25 - when I last released it back in August. Since then there has been some development going into Pippy (now version 30) http://dev.laptop.org/git?p=projects/pippy-activity;a=shortlog But none of the maintainers did follow the Sucrose release cycle, even though I sent a reminder http://lists.laptop.org/pipermail/sugar/2008-November/010021.html Any, specific reason for that? Pippy has not been moved to git.sugarlabs.org, as well. please indicate clearly: * if you still want to be part of Sucrose (including following the release cycle) * any new maintainer that is willing to do this task if you does not want to * any issues/reasons you have to do so Best, Simon To follow up on this, I mainly want to find a maintainer for Pippy for Sucrose. If there is no one willing to do that we drop it, which is ok - one can still download the xo etc, I just want a clearer situation. Hi, I will maintain Pippy for Sucrose, though I may need a bit of hand holding. Please let me know if what I did seems correct (esp. step 2): 1. l got the most recent version of Pippy from git git-clone git://dev.laptop.org/projects/pippy-activity cd pippy-activity 2. ./setup.py gave a bunch of invalid entry in MANIFEST errors about different locales, so I ran: ./setup.py fix_manifest 3. ./setup.py dist_source 4. I asked a crank sysadmin to add me to the Sugar group, And I moved Pippy-30.tar.bz2 to: http://dev.laptop.org/pub/sugar/sources/Pippy/Pippy-30.tar.bz2 (805K) I will move pippy over to git.sugarlabs.org as well. Thanks, Brian Wade, do you have maybe someone in mind? Cheers, Simon ___ Sugar-devel mailing list sugar-de...@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ 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: GSoC 2009?
On Mon, Jan 26, 2009 at 11:43 AM, Samuel Klein s...@laptop.org wrote: Sounds like a fine idea to me, Martin. Assuming we are accepted again as a mentoring org, we should be eligible for more projects than last year. Who handles that stuff (application as an org, etc)? Have we applied, do we need to apply? IOWs, who do I hound? But do bear in mind that we may not get anyone interested in those projects; and that a successful GSoC internship is primarily about a good experience developing a meaningful product, and the interns are free to define how to tackle the problem they undertake. For good or bad, I'm a veteran mentor of 2 GSoCs, I hope that some of the subprojects I'm thinking of are compelling :-) Most of this year I've been doing the unsexy, burdensome plumbing, deferring the fun stuff. If GSoC'ers grab the fun stuff, more power to them. cheers, martin -- 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: Notes from an impromptu 8.2.1 Release Mtg.
Right now e28 is what you should be testing. When the next f series release comes out (RSN) then that will be the new series going forward. I just ran a half-dozen Restart cycles with e28. None of them connected automatically. All of them connected when I poked Connect. (One may have taken a second try.) I can see my icon blinking when the automatic stuff tries to connect. -- These are my opinions, not necessarily my employer's. I hate spam. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Notes from an impromptu 8.2.1 Release Mtg.
Hal Murray wrote: Right now e28 is what you should be testing. When the next f series release comes out (RSN) then that will be the new series going forward. I just ran a half-dozen Restart cycles with e28. None of them connected automatically. All of them connected when I poked Connect. (One may have taken a second try.) I can see my icon blinking when the automatic stuff tries to connect. Thats expected. You should not see any behavior change in the wlan by changing the system firmware. The copy of the wlan firmware in the laptop system firmware is completely different than the copy of the wlan firmware that is in the OS build. The system firmware has zero influence on how the wlan device operates wrt to association. The only area where they interact at all is during suspend/resume and if you put the wlan into reset. Its confusing since there are 3 different firmwares on the XO and the wlan is duplicated in both the system firmware and the build. Often the wlan firmware in the system firmware is a different version than whats in the build. The build will normally be the latest with the copy in the system firmware getting upgraded as necessary. -- Richard Smith rich...@laptop.org One Laptop Per Child ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
multitouch + audio feedback linux dev - XO-2?
Hi guys. As a lot of you probably know, Intel just announced the Tablet Classmate PC which has totally ripped off the XO's form factor functionality, upped the hardware specs added touchscreen capability (something I sorely miss when I switch from my nintendo DS touchscreen stylus to the XO when testing stuff) http://www.olpcnews.com/laptops/xo2/intel_beat_olpc_with_classmate_pc.html Well, the XO still has it beat on price, low power consumption sunlight readability. At $200 vs $499, I'd still take the XO any day. For $499, might as well get a laptop with real horsepower. That's really just too expensive for mass deployment, *ESPECIALLY* for public schools in 3rd world countries (at least from a Filipino perspective). Anyway, with dev on XO-2 in the works and with Pixel Qi working on touchscreens from what I read, here are my questions: 1) Are there any existing hooks/systems for Linux for multi-touch? That's the only proper way you can get a virtual keyboard to work for a double-touchscreen clamshell device (the feasibility of which is not sold to me because of the power consumption of running a 2nd screen vs a keyboard, and mostly mostly mostly the lack of haptic feedback from a virtual keyboard). OT, but Honestly, as an electronic musician, the 1st thing that went into my head when I saw the XO-2 concept shots was I could write totally awesome DJ/live electronic software for this! because for it to make any sense, multitouch would have to be in place. I don't have programming experience w/ multitouch systems, but IMHO it should be pretty easy- it would just be basically the same as simple 8-bit (or 1-bit) single color channel image recognition systems w/ pixel array bytes substituting for pressure levels on each physical X-Y position onscreen. In fact, you could pretty much do multitouch systems with just a camera (the XO's would be good enough, the machine would just need a CPU with stronger horsepower to do the image processing :P) and any surface where discrete image sections can be formed for img recog aid, like using shadows from hands or maybe a color-reactive transparent surface where if pressure or contact is applied, a particular color shade (like a chroma key) will appear to aid img rec. Btw, on-topic w/ multitouch, these engineering students from India just came up with their own version of Jeff Han (NYU Perceptive Pixel)'s FTIR multi-touch tech, Sparsh http://www.sparsh-i.com/ - totally awesome and they showed a DJ app too! So back to the question: any existing Linux multi-touch hooks/drivers/APIs? (btw, refresher on Jef Han's multitouch tech: http://www.perceptivepixel.com/) 2) Audio feedback A big problem with touch-screen/virtual keyboards is lack of haptic feedback (and haptic feedback would probably eat batteries a lot). A standardized/universal audio mapping to keyboard keys similar to QWERTY, Dvorak or Braille would help solve this. This has actually been an interest of mine for the longest time because blind/visually impaired computer users could have a hard time with non-haptic keyboards or non-standard keyboard key locations. Also, this would be a great aid for blind coders, one would be able to code read case, punctuation special characters via tone-mapped keymappings and playback. Yes, text to speech and screen readers exist, but I think they're pretty useless for blind coders with a need for speed. Can you imagine running PERL through a text-to-speech system? A cool side effect of this would be that any kind of text would be translated to music via tonemapping or whatever audio cues are used :) (sorry guys, am a synaesthetic, all sensory data can be translated into numbers and be remapped to any other sense :P) Well, these 2 topics are very big undertakings but does anyone know any good starting points? If not, are any of these being researched at 1CC/Media Lab? I'm very much interested in researching/studying these, especially the long-term study for the HCI development/creation of a cross-platform internationally standardized keyboard/character/unicode tone/sound map (reconfigurable by users). Many thanks! -Naz -- Carlos Nazareno http://twitter.com/naz404 http://www.object404.com -- interactive media specialist zen graffiti studios http://www.zengraffiti.com -- User Group Manager Phlashers: Philippine Flash ActionScripters Adobe Flash/Flex User Group http://www.phlashers.com -- if you don't like the way the world is running, then change it instead of just complaining. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: multitouch + audio feedback linux dev - XO-2?
1) Are there any existing hooks/systems for Linux for multi-touch? That's the only proper way you can get a virtual keyboard to work for a double-touchscreen clamshell device (the feasibility of which is not sold to me because of the power consumption of running a 2nd screen vs a keyboard, and mostly mostly mostly the lack of haptic feedback from a virtual keyboard). Peter Hutterer has been working on Multi-Pointer X for several years. It is getting pretty usable, judging by the Youtube videos. http://wearables.unisa.edu.au/mpx/ http://www.youtube.com/watch?v=olWjnfBoY8E In fact, you could pretty much do multitouch systems with just a camera (the XO's would be good enough, the machine would just need a CPU with stronger horsepower to do the image processing :P) and any surface where discrete image sections can be formed for img recog aid, like using shadows from hands or maybe a color-reactive transparent surface where if pressure or contact is applied, a particular color shade (like a chroma key) will appear to aid img rec. You can use the pygame camera module to do multitouch on an XO, though it is far from usable for anything but drawing. http://www.youtube.com/watch?v=HIDdxY3L5V8 Nirav ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
New joyride build 2635
http://xs-dev.laptop.org/~cscott/olpc/streams/joyride/build2635 Changes in build 2635 from build: 2634 Size delta: 0.00M -vnc 4.1.2-35.fc10 +vnc 4.1.3-1.fc10 -vnc-libs 4.1.2-35.fc10 +vnc-libs 4.1.3-1.fc10 -- This mail was automatically generated See http://dev.laptop.org/~rwh/announcer/joyride-pkgs.html for aggregate logs See http://dev.laptop.org/~rwh/announcer/joyride_vs_update1.html for a comparison ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
New joyride build 2635
http://xs-dev.laptop.org/~cscott/olpc/streams/joyride/build2635 Changes in build 2635 from build: 2634 Size delta: 0.00M -vnc 4.1.2-35.fc10 +vnc 4.1.3-1.fc10 -vnc-libs 4.1.2-35.fc10 +vnc-libs 4.1.3-1.fc10 -- This mail was automatically generated See http://dev.laptop.org/~rwh/announcer/joyride-pkgs.html for aggregate logs See http://dev.laptop.org/~rwh/announcer/joyride_vs_update1.html for a comparison ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: multitouch + audio feedback linux dev - XO-2?
On Mon, Jan 26, 2009 at 7:22 PM, Nirav Patel o...@spongezone.net wrote: 1) Are there any existing hooks/systems for Linux for multi-touch? That's the only proper way you can get a virtual keyboard to work for a double-touchscreen clamshell device (the feasibility of which is not sold to me because of the power consumption of running a 2nd screen vs a keyboard, and mostly mostly mostly the lack of haptic feedback from a virtual keyboard). Peter Hutterer has been working on Multi-Pointer X for several years. It is getting pretty usable, judging by the Youtube videos. http://wearables.unisa.edu.au/mpx/ http://www.youtube.com/watch?v=olWjnfBoY8E Jim Gettys put together a synopsis of multi-touch input for XO-2 in September - http://wiki.laptop.org/images/9/99/Gen-2_touch.pdf 2) Audio feedback A big problem with touch-screen/virtual keyboards is lack of haptic feedback (and haptic feedback would probably eat batteries a lot). A standardized/universal audio mapping to keyboard keys similar to QWERTY, Dvorak or Braille would help solve this. I have some insight into this topic from experience in the cell phone industry. There are several ways to do haptic responses: linear vibrators, piezo-electric elements, speakers. Localized haptics are best (the vibration comes from the area on the screen that has been touched), but that's still an emerging technology. The challenge with your idea is latency. For applications like typing, the haptic response must happen very quickly to trick the brain into thinking it is related to the press. I think I've heard the number 25 ms before, but don't quote me on that. A quick google search couldn't confirm or deny this. I did find an interesting paper ( http://aig.cs.man.ac.uk/people/jayc/jay_quantifying_latency.pdf) that stated 100-200 ms was the limit, but I don't think the results apply to typing. The game in their experiment took a second to complete, which is way longer than a keystroke takes. If you don't care about typing repeatedly, the latency is less important. But for typing quickly with a limit of 25 ms, it will be hard to interrupt the processor, load a sound file, and play it in time. A dedicated microprocessor might be up to the task though. Also, I'm not sure if a speaker would draw significantly less power than a piezo or linear vibrator. I don't remember hard numbers for either use case. Thanks, Nate ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
New staging build 11
http://xs-dev.laptop.org/~cscott/xo-1/streams/staging/build11 Changes in build 11 from build: 10 Size delta: 0.00M -bootfw q2e24-1.olpc2.unsigned +bootfw q2e28-1.olpc2.unsigned --- Changes for bootfw q2e28-1.olpc2.unsigned from q2e24-1.olpc2.unsigned --- + OLPC trac 9211 - fixed crashes when doing StandBy from Windows. + Fixed display selftest size problem (test patterns didn't fill the screen) + Added some I/O registers to the list reported by ACPI so the Windows unreported memory test will work. + Turned off the keyboard, mouse, and DCON when going into Windows StandBy, saving power and preventing spurious partial-wakeups on the screen hardware. + OLPC trac 9211 - fixed crashes when doing StandBy from Windows. + Fixed display selftest size problem (test patterns didn't fill the screen) + Added some I/O registers to the list reported by ACPI so the Windows unreported memory test will work. + Turned off the keyboard, mouse, and DCON when going into Windows StandBy, saving power and preventing spurious partial-wakeups on the screen hardware. + Fixed problems with lid switch handling and kbd/mouse during Windows resume + OLPC trac 9179 - fixed Divide Error in scan-nand examination phase. + OLPC trac 9178 - fixed test-all crash when invoking pen-tablet function in touchpad test. + Fixed a problem in the suspend/resume code that affected restoration of SD registers + Fixed a problem in the suspend/resume code that affected restoration of SD registers + Fixed a Stack Overflow message in scan-nand, that happened under unusual circumstances + Changed the SMBIOS model name string for qualification testing + Callouts to C code can now have up to 20 arguments + BIOS emulation now supports installation from USB and CD-ROM + Turned off HTTP connection persistence for faster HTTP loading + Fixed a longstanding TCP problem with passive connection termination + Trac 9135 - allow re-executing EMACS without resetting + NANDblaster auto-channel-choice improvements - choose fastest channel instead of counting APs -- This mail was automatically generated See http://dev.laptop.org/~rwh/announcer/staging-pkgs.html for aggregate logs See http://dev.laptop.org/~rwh/announcer/joyride_vs_update1.html for a comparison ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: status of OLPC project
[cc += sugar-de...@] Victor Lazzarini wrote: Thanks. Walter has kindly replied to me already, so it looks like sugar labs is my destination. Hope to be able to clear up all my marking by the end of next week and by then I think will also know where I actually fit into this new scheme of things. I'm happy to be back. Thanks a lot for helping! -- // Bernie Innocenti - http://www.codewiz.org/ \X/ Sugar Labs - http://www.sugarlabs.org/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: status of OLPC project
Bernie Innocenti wrote: [cc += sugar-de...@] Victor Lazzarini wrote: Thanks. Walter has kindly replied to me already, so it looks like sugar labs is my destination. Hope to be able to clear up all my marking by the end of next week and by then I think will also know where I actually fit into this new scheme of things. I'm happy to be back. Thanks a lot for helping! Oops, I didn't notice this was an 3 weeks old thread that had jumped back to the top due to Bastien's recent post. -- // Bernie Innocenti - http://www.codewiz.org/ \X/ Sugar Labs - http://www.sugarlabs.org/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: multitouch + audio feedback linux dev - XO-2?
On Tue, 27 Jan 2009, Carlos Nazareno wrote: 1) Are there any existing hooks/systems for Linux for multi-touch? That's the only proper way you can get a virtual keyboard to work for a double-touchscreen clamshell device (the feasibility of which is not sold to me because of the power consumption of running a 2nd screen vs a keyboard, and mostly mostly mostly the lack of haptic feedback from a virtual keyboard). SNIP So back to the question: any existing Linux multi-touch hooks/drivers/APIs? there has been some discussion on the kernel mailing list recently. they are still hammering out what reasonable APIs will be (different multi-touch systems provide different capabilities) David Lang ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: multitouch + audio feedback linux dev - XO-2?
My (unasked for) opinion is that multitouch should not be a focus of OLPC's development efforts. The real benefit will just come from being able to touch the screen in the first place. Writing a decent multitouch interface requires massive UI design and coding efforts that we frankly cannot muster right now, and the concept is so immature in the Linux world that we cannot rely on someone else to do it for us. A real multitouch device would require a development effort similar to what Apple put into the iPhone, that is hundreds of engineers over several years with absolute control over the software stack. Given financial realities that's just not going to happen with XO-2. That said, here's hoping the final solution is pressure sensitive! The Nintendo DS gets all kinds of wonderful features out of that, and it's already part of XInput. Imagine the possibilities of a screen that can become any kind of keyboard you can imagine (computer, piano, drum, painting canvas, etc). Here's to staying focused, -Wade On Mon, Jan 26, 2009 at 11:25 PM, da...@lang.hm wrote: On Tue, 27 Jan 2009, Carlos Nazareno wrote: 1) Are there any existing hooks/systems for Linux for multi-touch? That's the only proper way you can get a virtual keyboard to work for a double-touchscreen clamshell device (the feasibility of which is not sold to me because of the power consumption of running a 2nd screen vs a keyboard, and mostly mostly mostly the lack of haptic feedback from a virtual keyboard). SNIP So back to the question: any existing Linux multi-touch hooks/drivers/APIs? there has been some discussion on the kernel mailing list recently. they are still hammering out what reasonable APIs will be (different multi-touch systems provide different capabilities) David Lang ___ 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: multitouch + audio feedback linux dev - XO-2?
On Mon, 26 Jan 2009, Wade Brainerd wrote: My (unasked for) opinion is that multitouch should not be a focus of OLPC's development efforts. The real benefit will just come from being able to touch the screen in the first place. Writing a decent multitouch interface requires massive UI design and coding efforts that we frankly cannot muster right now, and the concept is so immature in the Linux world that we cannot rely on someone else to do it for us. A real multitouch device would require a development effort similar to what Apple put into the iPhone, that is hundreds of engineers over several years with absolute control over the software stack. Given financial realities that's just not going to happen with XO-2. That said, here's hoping the final solution is pressure sensitive! The Nintendo DS gets all kinds of wonderful features out of that, and it's already part of XInput. Imagine the possibilities of a screen that can become any kind of keyboard you can imagine (computer, piano, drum, painting canvas, etc). Here's to staying focused, agreed, but I don't see how you can do a keyboard and not have some multi-touch stuff (shift keys to start with) I am in the group that has serious doubts about the current XO-2 design. I suspect that when push comes to shove the idea of the second screen being the keyboard will go the way of the crank in the XO-1 ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Notes from an impromptu 8.2.1 Release Mtg.
Michael Stone wrote: ... how to push 8.2.1 a few inches closer to release. The main conclusion that we reached after we updated http://dev.laptop.org/report/38 was that staging-9 [1] needs some testing! http://wiki.laptop.org/go/Friends_in_testing still points to staging-7 and says The 8.2.1 build is currently identical to 8.2.0. ??! The instructions in Friends in testing say Clean-install the #Build under test, but I tried olpc-update from 8.2.0 anyway. `sudo olpc-update staging-9` gives I don't think the requested build number exists. `sudo olpc-update -v -v -v -v -v --latest=staging` gives Querying http://antitheft.laptop.org/antitheft/1/; (that's all) Is olpc-update possible, or are the instructions correct? :) -- =S Page ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Backlight control
On Jan 24, 2009, at 5:18 AM, Marco Pesenti Gritti wrote: On Sat, Jan 24, 2009 at 5:23 AM, John Watlington w...@laptop.org wrote: What can I call from an activity (in python) to indicate that the backlight should be turned off ? I'm playing with a photoframe app, and want to have the ability to deliberately control the backlight level from the UI. See http://git.sugarlabs.org/projects/sugar/repos/mainline/blobs/master/ src/jarabe/model/screen.py Marco Thanks for the pointer. When using those functions I receive the following error message: RuntimeError: To make asynchronous calls, receive signals or export objects, D-Bus connections must be attached to a main loop by passing mainloop=... to the constructor or calling dbus.set_default_main_loop(...) It seems like a code fragment was missing from the file, and in my particular application, I wouldn't mind if those calls were synchronous --- how do I do so ? Cheers, wad ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Server-devel] XS field stories
On Mon, 2009-01-26 at 03:31 +0100, Martin Langhoff wrote: On Mon, Jan 26, 2009 at 2:11 AM, Raul Gutierrez Segales r...@rieder.net.py wrote: Is there anyway we could choose the sampling? Like create user groups or something so you could get for example only your classmates.. Working _exactly_ on that - search this list's archive for moodle ejabberd. I found a post way back in November. Is there a ticket or repository where we can follow (and help with) your progress in this area? Have you decided how to tackle this (reading a pg table or exporting data to mnesia) ? Here at our deployment in Paraguay we are _very_ interested in this nice feature! :) ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] GSoC 2009?
Sounds like a fine idea to me, Martin. Assuming we are accepted again as a mentoring org, we should be eligible for more projects than last year. But do bear in mind that we may not get anyone interested in those projects; and that a successful GSoC internship is primarily about a good experience developing a meaningful product, and the interns are free to define how to tackle the problem they undertake. SJ On Sun, Jan 25, 2009 at 9:47 PM, Martin Langhoff martin.langh...@gmail.com wrote: Ed, devel, server-devel, sj GSoC GSoC is looming. I am thinking of putting some of the things that I was planning to do in the next X months as GSoC projects (and that I know I'm unlikely to hit). Ideally, I would take take 2 or 3 mentees, with a preference towards those who live in deployment regions... retry/ignore/fail? 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 ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] GSoC 2009?
On Mon, Jan 26, 2009 at 11:43 AM, Samuel Klein s...@laptop.org wrote: Sounds like a fine idea to me, Martin. Assuming we are accepted again as a mentoring org, we should be eligible for more projects than last year. Who handles that stuff (application as an org, etc)? Have we applied, do we need to apply? IOWs, who do I hound? But do bear in mind that we may not get anyone interested in those projects; and that a successful GSoC internship is primarily about a good experience developing a meaningful product, and the interns are free to define how to tackle the problem they undertake. For good or bad, I'm a veteran mentor of 2 GSoCs, I hope that some of the subprojects I'm thinking of are compelling :-) Most of this year I've been doing the unsexy, burdensome plumbing, deferring the fun stuff. If GSoC'ers grab the fun stuff, more power to them. cheers, martin -- 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 ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] updates
On Sun, Jan 25, 2009 at 12:19 PM, Jerry Vonau jvo...@shaw.ca wrote: latest re-roll of anaconda, srpms, rpms and patch used, updated mkusbinstall for the XO at: http://members.shaw.ca/jvonau/pub/anaconda/ That's such good news. - finds kickstart file without asking where it is... Good - does that depend on labelling the partition too? Do we have to change mkusbinstall to label it appropriately? - loader doesn't copy stage2 to RAM Cool - - fix compile error re: MD_NEW_SIZE_BLOCKS(size) - added support for method=hd:LABEL=XSRepo at the boot prompt This allows us not to ask where the install media if the usbdrive is labeled as XSRepo and passed the above string. - added support for mmc cards (for the XO) in loader. This is incomplete, loader now finds the CF card on the XO but is unavailable to partition and thus install to it. F10 has the same behavior, I filed BZ# 481441. Hope they fix the issue before I have to dig it up I've CC'd myself on the bug. The actual number is - BZ 481431 - - updated mkusbinstall added the labeling of the usbdrive for the above method and creation of /boot/olpc.fth for the XO. Ah, that's what I was alluding to earlier. Is it possible to workaround the SD card issue by building an installer image with an older kernel? From what you said it's a regression with 2.6.27.x right? I'm wondering if we can craft a just-installed image that can be dd'd to SD cards. I guess I'll explore this tomorrow -- I'm on the road today, so limited in my hacking ;-) martin -- 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 ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
