Journal2 patches + timings + notes
Scott, I spent some more time with Journal2 today and implemented two minor features; namely, * display of the estimated no. of results - (which helps deal with the display of empty result-sets) * incremental display of results - (which makes it easier to time things). Please review and consider merging my patches, which can be found in http://dev.laptop.org/git/users/mstone/journal2. (That repo contains your journal2 code but none of the big pdfs or screencasts you made since these are very time-consuming to download onto an XO.) I also did a bit of timing on my XO, (see the 'timing' branch), wherein I learned, _anecdotally_ (i.e. with sample-size n=1) that: * startup time seems okay, but the initial query takes about 10s to return results. I have about 300 MB of data indexed under /home/olpc, plus a bit of other junk. (~/.pinot is ~ 35 MB). * it takes around 4.2 seconds to fetch and display each new result * the standard deviation in my sample was large, e.g. about 3.3 seconds. * 19 results were fetched. Notes: * I did not take care to ensure that the indexer had quiesced before my test run. (However, I don't think it was working hard since it did the bulk of the indexing yesterday; today, it only had to deal files changed by my editing and by the test run itself.) * With today's code, the search system is effectively unusable while the indexer is hard at work. * While I have not yet measured it carefully, it seemed to me that "full" indexing of a basic 767 system + activities _on XO_ may have taken as long as several hours. * With some, but not all queries, I noticed that the query failed because pinot failed to reply to journal2's blocking message sends within the usual dbus timeout of (30? 60?) seconds. I have no idea what was happening inside pinot. Michael P.S. - Thanks for the stimulating vacation entertainment. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Music Keyboard for TamTam?
See also http://www.flickr.com/photos/curiouslee/189728345/ Walter and Simon demonstrate MIDI keyboard input into the A-TEST board Taken on July 14, 2006, uploaded July 14, 2006 On Sun, Nov 30, 2008 at 9:16 PM, Gary C Martin <[EMAIL PROTECTED]> wrote: > On 1 Dec 2008, at 04:01, Gary C Martin wrote: > >> On 30 Nov 2008, at 22:16, Erik Garrison wrote: >> >>> On Sun, Nov 30, 2008 at 12:20 AM, Gary C Martin >>> <[EMAIL PROTECTED]> wrote: On 30 Nov 2008, at 01:29, Erik Garrison wrote: > On Mon, Nov 17, 2008 at 8:23 AM, <[EMAIL PROTECTED]> wrote: >> >> ignacio wrote: >>> >>> On Mon, 2008-11-17 at 04:24 +, Gary C Martin wrote: On a more disappointing note I found this ticket "G1G1 tamtam suite should respond to MIDI keyboard input" from 10 months ago. Closed. Wont fix :-( https://dev.laptop.org/ticket/6031 >>> >>> All "wontfix" means is that they're waiting for someone with a >>> stronger >>> itch to scratch it ;) >> >> i really have no idea how such devices are normally presented to >> the systems, but is it possible that the keyboard is consists of >> more than one USB device (i.e., via a built-in hub) and that not >> all the drivers are present on the XO? >> > > FWIW, The M-audio systems abide by open midi specifications and are > platform-independent. I don't know about the driver situation. > > There is a program which can be used to dump midi signals to > stdout. > It might be a good test as it's very simple to configure and its > results are very clear, unlike the audio programs you'll want to > use. ... and it's called??? Gah! ;-) >> >> Just for reference, after connecting the USB Midi keyboard amidi -l >> gives me: >> >> [EMAIL PROTECTED] ~]$ amidi -l >> Dir DeviceName >> IO hw:1,0,0 Keystation 49e MIDI 1 >> >>> I'm not at an XO or my development machine now, but looked around the >>> web to try to find some information to help. >>> >>> See: http://www.4front-tech.com/pguide/midi.html >> >> Will go read. >> >>> Does the system have a /dev/midi* when you plug the device in? >> >> Yep, I get a /dev/midi1 >> >>> Do you see anything interesting in the kernel logs returned with >>> dmesg? >>> >>> Unfortunately our kernel configs aren't online anywhere i can find... >>> but I'll check to see if it's enabled. My guess would be not, but >>> perhaps I'm mistaken. >>> I'm trying to hack my way through coding csound, but I've not had much time to play so far. A magic midi data dumping tool would be a nice shortcut to test – FWIW, I can see my M-audio correctly listed on the USB as an available MIDI input device, but not got any further yet. >>> >>> Perhaps cat /dev/midi* if the file(s) exist. >> >> Fab, yes, cat/dev/midi1 gives me wild ascii characters each time I >> press a key, looks like both note and velocity (this particular >> keyboard doesn't emit pressure but I have another one somewhere that >> does), also other controls (volume, pitch blend & modulation) trigger >> comms. >> >> I'd say the drivers are good to go, and I need to get back to reading >> csound documentation and try a demo to pickup the incoming midi feed. > > OK, really boring but working example (XO 8.2-767): > > 1) Plug in your USB MIDI input device > > 2) In terminal run "amidi -l" it should list something like: > >Dir DeviceName >IO hw:1,0,0 Keystation 49e MIDI 1 > > 3) Make a file bells.csd, it MUST be called .csd, > that alone wasted hours of my life :-( here's a what should go in it, > the one thing to watch is the -M hw:1,0,0 as this is the option that > tells csound which midi device to listen to, if "amidi -l" shows your > MIDI device with a different reference, use that instead: > > > > -odac -M hw:1,0,0 > > > instr 1 > idec = 1 > iamp ampmidi 32767 > kfrq cpsmidib 2 > kenv expsegr 1, idec, 0.1, 0.1, 0.01 > asig oscili kenv*iamp, kfrq, 1 >out asig > endin > > > f0 36000 > f1 0 16384 10 1 > > > > 4) Then again in console run: > >csound bells.csd > > 5) Start pressing keys and make beautiful music, see I said it wasn't > too exciting, but nice to get this far :-) The XO speakers don't do > very well below middle C (with this instrument), but it's a start. > > So... hardware/kernel/driver all working in 8.2-767. MIDI input is now > demoted to just ;-) a client software side feature for the TamTam > activities. I'll do a little more csound reading on the python side > and try to hack on TamTamMini, will ping the list if I make useful > progress. > > Regards, > --Gary > >>> Erik >> >> Many thanks, >> --Gary >> ___ >> Devel mailing list >> Devel@lists.laptop.org >> http://lists.laptop.org/listinfo/devel > > ___ > Devel mailing list > Devel@lists.laptop.org > http://lists.laptop.org/list
Re: New joyride build 2570
is this ready for people to start testing yet? David Lang On Mon, 1 Dec 2008, Build Announcer v2 wrote: > Date: Mon, 1 Dec 2008 17:22:30 -0500 (EST) > From: Build Announcer v2 <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subject: New joyride build 2570 > > http://xs-dev.laptop.org/~cscott/olpc/streams/joyride/build2570 > > Changes in build 2570 from build: 2569 > > Size delta: 0.00M > > -kernel 2.6.27-20081124.2.olpc.a47f7144dd2fd0a > +kernel 2.6.27-20081201.1.olpc.672cde9409f412e > > -- > 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 > ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
New joyride build 2570
http://xs-dev.laptop.org/~cscott/olpc/streams/joyride/build2570 Changes in build 2570 from build: 2569 Size delta: 0.00M -kernel 2.6.27-20081124.2.olpc.a47f7144dd2fd0a +kernel 2.6.27-20081201.1.olpc.672cde9409f412e -- 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: Running out of memory is bad
Forwarding to sugar-devel because I'm curious if people think this would be useful in other platforms than Sugar. Regards, Tomeu On Mon, Dec 1, 2008 at 7:14 PM, C. Scott Ananian <[EMAIL PROTECTED]> wrote: > In my thanksgiving XO demos, people often neglected to close > applications and kept opening activities until the XO ran out of > memory and froze. > > We can debate the "right" solution for 9.1, but I'd like to suggest > that we add a "you're out of memory, please close an activity" warning > like we have for disk space in 8.2.1. > --scott > > -- > ( http://cscott.net/ ) > ___ > 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
Running out of memory is bad
In my thanksgiving XO demos, people often neglected to close applications and kept opening activities until the XO ran out of memory and froze. We can debate the "right" solution for 9.1, but I'd like to suggest that we add a "you're out of memory, please close an activity" warning like we have for disk space in 8.2.1. --scott -- ( http://cscott.net/ ) ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: will there be an 8.2 update ?
Hi Mikus, I need to take that page down! I am remiss in doing that. Its a page which is automatically generated by Trac. Since Trac items and associated tags are not up to date, its not a useful page. I keep hoping I can fix it but since it hasn't happened, its time to take it down. Michael or anyone in engineering, do you know how to remove that Trac roadmap page? Just take it offline until I can figure out how to make it show something meaningful. The real roadmap, such as it is, is here: http://wiki.laptop.org/go/Releases Not much there right now but I think 8.2.1 will come together quickly now and 9.1 shortly after that. I will post links to more details on each of those as soon as I get enough buy in. I plan to talk about Trac usage conventions for 9.1 at the next weekly Feature planning meeting on Wed. at 2PM US ET, freenode.net #olpc-meeting. After that I should be able to tell you how to update Trac to flag a bug as a candidate for inclusion in 9.1. The 8.2.1 early thinking is here: http://lists.laptop.org/pipermail/devel/2008-November/021388.html To your question: No we do not currently plan to improve the NM 0.6 implementation in 8.2.1. It may still come up as a critical item for Uruguay or another deployment, but so far it is not on the list. I think your best bet is to have issues resolved with NM 0.7, targeted for inclusion in 9.1. Let me know if that is not clear or you need more info. Thanks, Greg S > Date: Sat, 29 Nov 2008 17:48:17 -0500 > From: Mikus Grinbergs <[EMAIL PROTECTED]> > Subject: will there be an 8.2 update ? > To: devel@lists.laptop.org > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > Looking at the "official" http://dev.laptop.org/roadmap, it is not > clear to me whether an official update to 8.2 (f9) will be released. > > My reason for asking is that I have a problem with Network Manager > 0.6 (ticket #8343). If there is a chance that 8.2 will be improved, > I will leave that ticket open. If 8.2's Network Manager will not be > updated, then I can close that ticket as 'wontfix', and instead > write a different ticket against the newer Network Manager. [What > Network Manager 0.7 does/does_not_do needs to be described > differently from what Network Manager 0.6 does/does_not_do.] > > Will a 'fixpack for 8.2' be released ? > > mikus > ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Java & Scratch on XO
Hi, Bert and Tomeu. Many thanks for the pointers and examples. I've put together a mimetypes.xml file and will test it when I get home. (I don't have my XO with me.) I will let you know if I have any problems or questions. Thanks again! -- John On Dec 1, 2008, at 9:50 AM, Bert Freudenberg wrote: > On 01.12.2008, at 15:37, Tomeu Vizoso wrote: > >> On Mon, Dec 1, 2008 at 3:16 PM, John Maloney >> <[EMAIL PROTECTED]> wrote: >>> Hi, Tomeu. >>> >>> Thanks for your reply. It's great that there is a way to handle >>> this! >>> >>> I took a quick look at the EToys .xo bundle and did not see a >>> mimetypes.xml file. However, I did notice that EToys lists a lot of >>> mime types in it's activity.info. What I don't see is how the system >>> would know what file extension to associate with a type like >>> "application/x-squeak-project". Is that what the mimetypes.xml is >>> for? >>> Do you know of any other activity that uses a mimetypes.xml file >>> that >>> would be a good model for Scratch? >> >> True, have talked with Bert and he said that the etoys.xml file they >> have in the source repository is for the rpm, not for the .xo. So >> sorry for the misleading pointer. >> >> The idea is that your scratch bundle would have a file named >> mimetypes.xml in the activity dir (so next to the activity.info file, >> the icon, etc) and the contents would be analogous to those in >> etoys.xml. As you can see, that file relates extensions to mime >> types. >> >> Unfortunately, cannot find now an activity that currently uses it, >> but >> ping me again if you have trouble putting that to work and I will >> look >> harder or do a small experiment here. > > > Yes - should be pretty simple. Here's the essence of the Etoys one > (John: we actually dropped the capital T): > > > http://www.freedesktop.org/standards/shared-mime-info > "> > > > Squeak Project > > > > > - Bert - > > ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Java & Scratch on XO
On 01.12.2008, at 15:37, Tomeu Vizoso wrote: > On Mon, Dec 1, 2008 at 3:16 PM, John Maloney > <[EMAIL PROTECTED]> wrote: >> Hi, Tomeu. >> >> Thanks for your reply. It's great that there is a way to handle this! >> >> I took a quick look at the EToys .xo bundle and did not see a >> mimetypes.xml file. However, I did notice that EToys lists a lot of >> mime types in it's activity.info. What I don't see is how the system >> would know what file extension to associate with a type like >> "application/x-squeak-project". Is that what the mimetypes.xml is >> for? >> Do you know of any other activity that uses a mimetypes.xml file that >> would be a good model for Scratch? > > True, have talked with Bert and he said that the etoys.xml file they > have in the source repository is for the rpm, not for the .xo. So > sorry for the misleading pointer. > > The idea is that your scratch bundle would have a file named > mimetypes.xml in the activity dir (so next to the activity.info file, > the icon, etc) and the contents would be analogous to those in > etoys.xml. As you can see, that file relates extensions to mime types. > > Unfortunately, cannot find now an activity that currently uses it, but > ping me again if you have trouble putting that to work and I will look > harder or do a small experiment here. Yes - should be pretty simple. Here's the essence of the Etoys one (John: we actually dropped the capital T): http://www.freedesktop.org/standards/shared-mime- info"> Squeak Project - Bert - ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Java & Scratch on XO
On Mon, Dec 1, 2008 at 3:16 PM, John Maloney <[EMAIL PROTECTED]> wrote: > Hi, Tomeu. > > Thanks for your reply. It's great that there is a way to handle this! > > I took a quick look at the EToys .xo bundle and did not see a > mimetypes.xml file. However, I did notice that EToys lists a lot of > mime types in it's activity.info. What I don't see is how the system > would know what file extension to associate with a type like > "application/x-squeak-project". Is that what the mimetypes.xml is for? > Do you know of any other activity that uses a mimetypes.xml file that > would be a good model for Scratch? True, have talked with Bert and he said that the etoys.xml file they have in the source repository is for the rpm, not for the .xo. So sorry for the misleading pointer. The idea is that your scratch bundle would have a file named mimetypes.xml in the activity dir (so next to the activity.info file, the icon, etc) and the contents would be analogous to those in etoys.xml. As you can see, that file relates extensions to mime types. Unfortunately, cannot find now an activity that currently uses it, but ping me again if you have trouble putting that to work and I will look harder or do a small experiment here. Good luck, Tomeu > On Dec 1, 2008, at 7:44 AM, Tomeu Vizoso wrote: > >> On Tue, Nov 25, 2008 at 5:01 PM, <[EMAIL PROTECTED]> wrote: >>> i'm forwarding this note from john maloney (scratch maintainer) to >>> devel. >>> >>> this certainly sounds like a mime types issue, but i'm not sure >>> where or how we'd augment the canonical list. >> >> Paul is right, Sugar is not being able to recognize those as being >> scratch files. You can see how etoys is doing this by extending the >> mime types database: >> >> http://wiki.laptop.org/go/Activity_bundles#Bundle_Structure >> http://dev.laptop.org/git?p=projects/etoys;a=blob;f=etoys.xml >> >> Regards, >> >> Tomeu >> >>> john wrote: Hi, Paul, Cynthia, and Claudia. I got a question from a professor at U. of Wisconsin about how to work with Scratch projects downloaded from the Scratch website (see below). I verified that the problem is that the .sb file gets renamed to be something in /tmp ending in .bin. I think this happens when you put the .sb file in the clipboard. In any case, when you drag the file icon onto Scratch, that is the file name that is reported. So my question is: is there a way to tell the browser the files ending in .sb are Scratch project files so that it doesn't rename them? Is it something like registering a MIME type? Does anyone else have any suggestions for making it easier to get downloaded Scratch projects to open in Scratch? -- John - My understanding of the problem (now that I'm running Scratch 1.3 everywhere) is that the XO does not properly name the files it downloads from the scratch site (i.e., they don't have .sb extensions), and Scratch refuses to recognize files without that extension. If I use the Linux terminal program to change the name (or download them onto a USB from another machine) I can get the Scratch to open the files. Does this make sense? It is a total pain in the neck though, because I can't figure out a solution that does not involve a USB: the only way I can find the Scratch program file from the Linux terminal is if I use the Journal to copy the file to the USB (I can't figure out where it lives in the Journal world). - >>> >>> =- >>> paul fox, [EMAIL PROTECTED] >>> give one laptop, get one laptop --- http://www.amazon.com/xo >>> ___ >>> 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 > ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Java & Scratch on XO
Hi, Tomeu. Thanks for your reply. It's great that there is a way to handle this! I took a quick look at the EToys .xo bundle and did not see a mimetypes.xml file. However, I did notice that EToys lists a lot of mime types in it's activity.info. What I don't see is how the system would know what file extension to associate with a type like "application/x-squeak-project". Is that what the mimetypes.xml is for? Do you know of any other activity that uses a mimetypes.xml file that would be a good model for Scratch? -- John On Dec 1, 2008, at 7:44 AM, Tomeu Vizoso wrote: > On Tue, Nov 25, 2008 at 5:01 PM, <[EMAIL PROTECTED]> wrote: >> i'm forwarding this note from john maloney (scratch maintainer) to >> devel. >> >> this certainly sounds like a mime types issue, but i'm not sure >> where or how we'd augment the canonical list. > > Paul is right, Sugar is not being able to recognize those as being > scratch files. You can see how etoys is doing this by extending the > mime types database: > > http://wiki.laptop.org/go/Activity_bundles#Bundle_Structure > http://dev.laptop.org/git?p=projects/etoys;a=blob;f=etoys.xml > > Regards, > > Tomeu > >> john wrote: >>> Hi, Paul, Cynthia, and Claudia. >>> >>> I got a question from a professor at U. of Wisconsin about how to >>> work >>> with Scratch projects downloaded from the Scratch website (see >>> below). >>> >>> I verified that the problem is that the .sb file gets renamed to be >>> something in /tmp ending in .bin. I think this happens when you put >>> the .sb file in the clipboard. In any case, when you drag the file >>> icon onto Scratch, that is the file name that is reported. >>> >>> So my question is: is there a way to tell the browser the files >>> ending >>> in .sb are Scratch project files so that it doesn't rename them? >>> Is it >>> something like registering a MIME type? >>> >>> Does anyone else have any suggestions for making it easier to get >>> downloaded Scratch projects to open in Scratch? >>> >>> -- John >>> >>> >>> >>> - >>> My understanding of the problem (now that I'm running Scratch 1.3 >>> everywhere) is that the XO does not properly name the files it >>> downloads from the scratch site (i.e., they don't have .sb >>> extensions), and Scratch refuses to recognize files without that >>> extension. If I use the Linux terminal program to change the name >>> (or >>> download them onto a USB from another machine) I can get the Scratch >>> to open the files. Does this make sense? It is a total pain in the >>> neck though, because I can't figure out a solution that does not >>> involve a USB: the only way I can find the Scratch program file from >>> the Linux terminal is if I use the Journal to copy the file to the >>> USB >>> (I can't figure out where it lives in the Journal world). >>> - >> >> =- >> paul fox, [EMAIL PROTECTED] >> give one laptop, get one laptop --- http://www.amazon.com/xo >> ___ >> 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: Java & Scratch on XO
[reposting to [EMAIL PROTECTED] and adding [EMAIL PROTECTED] to cc] On Mon, Dec 1, 2008 at 1:44 PM, Tomeu Vizoso <[EMAIL PROTECTED]> wrote: > On Tue, Nov 25, 2008 at 5:01 PM, <[EMAIL PROTECTED]> wrote: >> i'm forwarding this note from john maloney (scratch maintainer) to devel. >> >> this certainly sounds like a mime types issue, but i'm not sure >> where or how we'd augment the canonical list. > > Paul is right, Sugar is not being able to recognize those as being > scratch files. You can see how etoys is doing this by extending the > mime types database: > > http://wiki.laptop.org/go/Activity_bundles#Bundle_Structure > http://dev.laptop.org/git?p=projects/etoys;a=blob;f=etoys.xml > > Regards, > > Tomeu > >> john wrote: >> > Hi, Paul, Cynthia, and Claudia. >> > >> > I got a question from a professor at U. of Wisconsin about how to work >> > with Scratch projects downloaded from the Scratch website (see below). >> > >> > I verified that the problem is that the .sb file gets renamed to be >> > something in /tmp ending in .bin. I think this happens when you put >> > the .sb file in the clipboard. In any case, when you drag the file >> > icon onto Scratch, that is the file name that is reported. >> > >> > So my question is: is there a way to tell the browser the files ending >> > in .sb are Scratch project files so that it doesn't rename them? Is it >> > something like registering a MIME type? >> > >> > Does anyone else have any suggestions for making it easier to get >> > downloaded Scratch projects to open in Scratch? >> > >> > -- John >> > >> > >> > >> > - >> > My understanding of the problem (now that I'm running Scratch 1.3 >> > everywhere) is that the XO does not properly name the files it >> > downloads from the scratch site (i.e., they don't have .sb >> > extensions), and Scratch refuses to recognize files without that >> > extension. If I use the Linux terminal program to change the name (or >> > download them onto a USB from another machine) I can get the Scratch >> > to open the files. Does this make sense? It is a total pain in the >> > neck though, because I can't figure out a solution that does not >> > involve a USB: the only way I can find the Scratch program file from >> > the Linux terminal is if I use the Journal to copy the file to the USB >> > (I can't figure out where it lives in the Journal world). >> > - >> >> =- >> paul fox, [EMAIL PROTECTED] >> give one laptop, get one laptop --- http://www.amazon.com/xo >> ___ >> 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: Devel Digest, Vol 34, Issue 1
> > I am wondering if there is currently any possbility to completely turn > off the whole video subsystem, while leaving the cpu running? [and is > it also possible to "reclaim" the video RAM for the system BTW ?] > Yes, it's possible, but I don't know if anybody has the recipe handy, especially not in the context of the existing OS setup. To reclaim the video RAM, you would need to change the values in quite a few MSRs (machine specific registers). There are about 6 of them whose values depend on the chosen size of video RAM - MSR numbers 1028, 1029, 402a, 1810, and a0002001. Open Firmware sets that up and hands it off to Linux. In principle, the Linux kernel could change the values after the fact, but it would be tricky. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Wacom Bamboo with XO?
[adding sugar-devel to cc as it's of interest to other platforms than olpc] On Sun, Nov 30, 2008 at 10:52 PM, Chris Marshall <[EMAIL PROTECTED]> wrote: > [EMAIL PROTECTED] wrote: >> wade wrote: >> > I'm partly set up to build kernels, I can give it a try at some point. >> > >> > Ultimately though, just mouse position and clicking isn't nearly >> > enough. You *at least* need pressure information for a decent tablet >> > painting experience. >> >> right -- i'm hoping someone with some tablet experience will >> point to some tool that does the right config of the tablet. > > Well, I haven't yet figured out how to get an appropriate > OLPC kernel build set-up but from my investigation to date > it looks like the gtk.gdk class interface already has the > "smarts" to talk to tablets. > > By default, Wacom USB tablets start out in a generic HID mode. > The application would need to recognize the tablet, then > enable the full tablet driver and configuration. > > http://linuxwacom.sourceforge.net/index.php/howto/theory > > From my reading of the gtk.gdk page it looks like those > should map directly to the tablet access info on the Wacom > HOWTO site. > > http://linuxwacom.sourceforge.net/index.php/appdev > > There is even a command line utility to config > the tablet that could probably be integrated into the > Sugar shell process or Sugarized into an activity of sorts: > > http://linuxwacom.sourceforge.net/index.php/howto/xsetwacom Hi, in case someone is interested, adding a control panel section to Sugar is quite easy once you know a bit of pygtk, look here for the already existing examples: http://dev.laptop.org/git?p=sugar;a=tree;f=extensions/cpsection We should have nice documentation, but in the meantime, feel free to ask. Regards, Tomeu ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
