Re: F11-for-XO1.5 Release 10.1.1 Release Candidate 2
Hi, Bert and Derek. Derek just send me the combined version. I tested playback and recording on the XO 1.5 and it was perfect. Hooray! I did NOT test to verify that it survives suspect resume, as Derek's previous version did. Hopefully someone else has verified that. It sounds as though this fixed version of the ALSA plugin will get into the XO Squeak VM package. In that case, should I omit it from the next version of Scratch? (A new version of XO Scratch is coming soon to include the Lego WeDo plugin which Derek just finished.) Many thanks to Derek and Sayamindu for their hard work. -- John On Jun 14, 2010, at 7:08 AM, Bert Freudenberg wrote: > > On 14.06.2010, at 13:01, John Maloney wrote: > >> Hi, Bert. >> >> Re: >>> Tried sound playback in Scratch, it's choppy, many clicks to hear. >>> Suspended fine, resumed playing sound. Recording does not freeze >>> the activity, but has bad quality. >> >> Derek says that the recorded sound is actually okay if you export >> it and play it with a good sound player. Does that fit with your >> experience? > > Yes, it seems to be playback-related. Actually, Sayamindu fixed that > already, but it got reverted with Derek's anti-freeze patch. He just > made a combined version: > > http://dev.laptop.org/ticket/9375 > > - Bert - > > > ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: F11-for-XO1.5 Release 10.1.1 Release Candidate 2
Hi, Bert. Re: > Tried sound playback in Scratch, it's choppy, many clicks to hear. > Suspended fine, resumed playing sound. Recording does not freeze the > activity, but has bad quality. Derek says that the recorded sound is actually okay if you export it and play it with a good sound player. Does that fit with your experience? The choppy sound in Scratch is known; the fact that it works in EToys makes me think that Scratch would work, too, with the right buffer size and sampling rate. I'll try a few variations... -- John ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Some testing notes for OS10 for the XO-1
Good news! As I recall, that same issue came up in 802 as well -- with a similar fix. -- John On Dec 13, 2009, at 10:15 PM, Philipp Kocher wrote: > The Prolific driver gets loaded (see logs at the bottom). > The problem are the permissions. > After plugging in the scratch board "ll /dev/ttyUSB0" shows: > crw-rw 1 root dialout 188, 0 2009-12-14 09:52 /dev/ttyUSB0 > > User olpc is not in group dialout which means it doesn't have access > to ttyUSB0. > > After adding olpc to group dialout the scratch board works fine. > > Regards, > Philipp > > On 12/13/2009 11:17 PM, John Maloney wrote: >> Hi, Steven. >> >> The USB-serial cable that comes with the Scratch Sensor board needs a >> driver from Prolifix. That driver used to be included in the >> builds, but >> perhaps it was accidentally dropped? >> >> If you use a supported USB-serial adaptor cable, then I think the >> ScratchBoard will work. >> >> I just got a report that sound playback is rough on XO 1.5: >> >> http://dev.laptop.org/ticket/9375 >> >> I'm guessing this is caused by a switch from ALSA to PulseAudio. >> We've >> seen that on Ubuntu; we still working to resolve the problem. >> PulseAudio >> itself has some buffering issues, although it appears that folks are >> working on those. The problems tend to show up more in applications >> where sounds are triggered dynamically, such as Scratch, EToys, and >> games, vs. playing music. >> >> -- John >> >> On Dec 13, 2009, at 4:00 AM, Philipp Kocher wrote: >> >>> Hi Steven >>> >>> - The scratch sensor board doesn't work (works with build 802) >>> I hoped "allow olpc access to ttyUSB nodes" (from release notes >>> os10) >>> would make it work. I added an extract of /var/log/messages at the >>> bottom of the email. >>> >>> - timezone can not be changed in gnome since administration menu is >>> missing (changing the timezone in sugar control panel has no >>> effect in >>> gnome). And talking about time, I think the clock activity is really >>> nice and useful. >>> >>> - build information "OLPC release 11 (Leonidas)" in sugar control >>> panel is more confusing than helpful. What about "10 (based on >>> Fedora >>> 11)"? >>> >>>> Does it boot consistently into Sugar? Gnome? >>> Worked fine here. >>>> Does sound work? >>> Yes,no problem. >>>> Can you suspend? Does it wake up? >>> Suspend yes, but no proper wake up as mentioned by other testers >>> (but the shutdown with the power button is really nice and useful). >>> >>> Regards, >>> Philipp >>> >>> Plug in Scratch Sensor board with build 10 on Fedora 11: >>> Dec 12 07:56:16 xo-11-08-d6 kernel: [ 88.687028] usb 1-2: new full >>> speed USB device using ohci_hcd and address 2 >>> Dec 12 07:56:17 xo-11-08-d6 kernel: [ 88.908698] usb 1-2: configura >>> tion #1 chosen from 1 choice >>> Dec 12 07:56:17 xo-11-08-d6 kernel: [ 89.080490] usbcore: registere >>> d new interface driver usbserial >>> Dec 12 07:56:17 xo-11-08-d6 kernel: [ 89.080490] USB Serial support >>> registered for generic >>> Dec 12 07:56:17 xo-11-08-d6 kernel: [ 89.080490] usbcore: registere >>> d new interface driver usbserial_generic >>> Dec 12 07:56:17 xo-11-08-d6 kernel: [ 89.080490] usbserial: USB Ser >>> ial Driver core >>> Dec 12 07:56:17 xo-11-08-d6 kernel: [ 89.162673] USB Serial support >>> registered for pl2303 >>> Dec 12 07:56:17 xo-11-08-d6 kernel: [ 89.162861] pl2303 1-2:1.0: pl >>> 2303 converter detected >>> Dec 12 07:56:17 xo-11-08-d6 kernel: [ 89.185652] usb 1-2: pl2303 co >>> nverter now attached to ttyUSB0 >>> Dec 12 07:56:17 xo-11-08-d6 kernel: [ 89.185960] usbcore: registere >>> d new interface driver pl2303 >>> Dec 12 07:56:17 xo-11-08-d6 kernel: [ 89.185982] pl2303: Prolific P >>> L2303 USB to serial adaptor driver >>> Dec 12 07:56:17 xo-11-08-d6 NetworkManager: (ttyUSB0): ignori >>> ng due to lack of mobile broadband capabilties >>> >>> >>> Plug in Scratch Sensor board with build 802 on Fedora 9: >>> Dec 13 08:48:55 localhost kernel: [ 155.465098] hub_port_wait_reset: >>> portstatus=501 portchange=10 >>> Dec 13 08:48:55 localhost kernel: [ 155.536006] hub_port_wait_reset: >>> portstatus=100 portchange=1 >>> Dec 13
Re: Some testing notes for OS10 for the XO-1
Hi, Steven. The USB-serial cable that comes with the Scratch Sensor board needs a driver from Prolifix. That driver used to be included in the builds, but perhaps it was accidentally dropped? If you use a supported USB-serial adaptor cable, then I think the ScratchBoard will work. I just got a report that sound playback is rough on XO 1.5: http://dev.laptop.org/ticket/9375 I'm guessing this is caused by a switch from ALSA to PulseAudio. We've seen that on Ubuntu; we still working to resolve the problem. PulseAudio itself has some buffering issues, although it appears that folks are working on those. The problems tend to show up more in applications where sounds are triggered dynamically, such as Scratch, EToys, and games, vs. playing music. -- John On Dec 13, 2009, at 4:00 AM, Philipp Kocher wrote: > Hi Steven > > - The scratch sensor board doesn't work (works with build 802) > I hoped "allow olpc access to ttyUSB nodes" (from release notes > os10) would make it work. I added an extract of /var/log/messages at > the bottom of the email. > > - timezone can not be changed in gnome since administration menu is > missing (changing the timezone in sugar control panel has no effect > in gnome). And talking about time, I think the clock activity is > really nice and useful. > > - build information "OLPC release 11 (Leonidas)" in sugar control > panel is more confusing than helpful. What about "10 (based on > Fedora 11)"? > >> Does it boot consistently into Sugar? Gnome? > Worked fine here. >> Does sound work? > Yes,no problem. >> Can you suspend? Does it wake up? > Suspend yes, but no proper wake up as mentioned by other testers > (but the shutdown with the power button is really nice and useful). > > Regards, > Philipp > > Plug in Scratch Sensor board with build 10 on Fedora 11: > Dec 12 07:56:16 xo-11-08-d6 kernel: [ 88.687028] usb 1-2: new full > speed USB device using ohci_hcd and address 2 > Dec 12 07:56:17 xo-11-08-d6 kernel: [ 88.908698] usb 1-2: configura > tion #1 chosen from 1 choice > Dec 12 07:56:17 xo-11-08-d6 kernel: [ 89.080490] usbcore: registere > d new interface driver usbserial > Dec 12 07:56:17 xo-11-08-d6 kernel: [ 89.080490] USB Serial support > registered for generic > Dec 12 07:56:17 xo-11-08-d6 kernel: [ 89.080490] usbcore: registere > d new interface driver usbserial_generic > Dec 12 07:56:17 xo-11-08-d6 kernel: [ 89.080490] usbserial: USB Ser > ial Driver core > Dec 12 07:56:17 xo-11-08-d6 kernel: [ 89.162673] USB Serial support > registered for pl2303 > Dec 12 07:56:17 xo-11-08-d6 kernel: [ 89.162861] pl2303 1-2:1.0: pl > 2303 converter detected > Dec 12 07:56:17 xo-11-08-d6 kernel: [ 89.185652] usb 1-2: pl2303 co > nverter now attached to ttyUSB0 > Dec 12 07:56:17 xo-11-08-d6 kernel: [ 89.185960] usbcore: registere > d new interface driver pl2303 > Dec 12 07:56:17 xo-11-08-d6 kernel: [ 89.185982] pl2303: Prolific P > L2303 USB to serial adaptor driver > Dec 12 07:56:17 xo-11-08-d6 NetworkManager: (ttyUSB0): ignori > ng due to lack of mobile broadband capabilties > > > Plug in Scratch Sensor board with build 802 on Fedora 9: > Dec 13 08:48:55 localhost kernel: [ 155.465098] > hub_port_wait_reset: portstatus=501 portchange=10 > Dec 13 08:48:55 localhost kernel: [ 155.536006] > hub_port_wait_reset: portstatus=100 portchange=1 > Dec 13 08:48:55 localhost kernel: [ 155.539599] > hub_port_wait_reset: device went away! > Dec 13 08:48:55 localhost kernel: [ 155.549596] hub 2-0:1.0: unable > to enumerate USB device on port 2 > Dec 13 08:48:55 localhost kernel: [ 155.831725] > hub_port_wait_reset: portstatus=103 portchange=10 > Dec 13 08:48:55 localhost kernel: [ 155.904029] usb 1-2: new full > speed USB device using ohci_hcd and address 4 > Dec 13 08:48:55 localhost kernel: [ 155.997296] > hub_port_wait_reset: portstatus=103 portchange=10 > Dec 13 08:48:56 localhost kernel: [ 156.077180] usb 1-2: > configuration #1 chosen from 1 choice > Dec 13 08:48:56 localhost kernel: [ 156.413019] usbcore: registered > new interface driver usbserial > Dec 13 08:48:56 localhost kernel: [ 156.417722] drivers/usb/serial/ > usb-serial.c: USB Serial support registered for generic > Dec 13 08:48:56 localhost kernel: [ 156.431937] usbcore: registered > new interface driver usbserial_generic > Dec 13 08:48:56 localhost kernel: [ 156.439535] drivers/usb/serial/ > usb-serial.c: USB Serial Driver core > Dec 13 08:48:56 localhost kernel: [ 156.476346] drivers/usb/serial/ > usb-serial.c: USB Serial support registered for pl2303 > Dec 13 08:48:56 localhost kernel: [ 156.479963] pl2303 1-2:1.0: > pl2303 converter detected > Dec 13 08:48:56 localhost kernel: [ 156.516365] usb 1-2: pl2303 > converter now attached to ttyUSB0 > Dec 13 08:48:56 localhost kernel: [ 156.522309] usbcore: registered > new interface driver pl2303 > Dec 13 08:48:56 localhost kernel: [ 156.536892] drivers/usb/serial/ > pl2303.c
Re: Journal integration for Scratch
Ahh, that would explain it! Maybe we need a couple of lines of shell script to check for the link and create it if it isn't there. -- John On Jan 15, 2009, at 7:56 AM, Bert Freudenberg wrote: > On 15.01.2009, at 13:55, John Maloney wrote: > >> Hi, Phillip. >> >> Re: >>> There is a bug in Scratch version 12. The symbolic link of the >>> Project >>> directory doesn't get created (Open Projects shows Scratch.activity >>> folder instead). I checked the scripts (scratch-activity and >>> scratch-wrapper) but couldn't find where the link should get >>> created. >> >> In Scratch 11, a symbolic link was included in the .xo and >> unzipping re-created that link. Someone else helped me create that >> mechanism (sorry I can't quite remember who). But you are right, it >> no longer works in v12, either because I changed something about my >> process for creating the .xo file or perhaps because of a change in >> the XO software (less likely). >> >> I will look into this. > > > Unless someone fixed this in the mean time, symbolic links in > bundles are not preserved: > > http://dev.laptop.org/ticket/4584 > > - Bert - > > ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Journal integration for Scratch
Hi, Phillip. Re: > There is a bug in Scratch version 12. The symbolic link of the Project > directory doesn't get created (Open Projects shows Scratch.activity > folder instead). I checked the scripts (scratch-activity and > scratch-wrapper) but couldn't find where the link should get created. In Scratch 11, a symbolic link was included in the .xo and unzipping re-created that link. Someone else helped me create that mechanism (sorry I can't quite remember who). But you are right, it no longer works in v12, either because I changed something about my process for creating the .xo file or perhaps because of a change in the XO software (less likely). I will look into this. -- John > > > Regards, > Philipp > > Bert Freudenberg wrote: >> The script looks good, except for the name mangling magic (which is >> a bit hard to understand because of mis-indentations). This >> wouldn't even work with your XO's language set to non-English >> (which the majority of XOs use). >> I would simply name the file "$object_id.sb". >> - Bert - >> On 14.01.2009, at 07:04, Philipp Kocher wrote: >>> Hi John >>> >>> Yes, we need the mimetypes.xml file as well (thanks Tomeu I forgot >>> the USB flash drive use case). I have tested the attached >>> mimetypes.xml. It is working fine. Put it in the activity directory. >>> >>> Furthermore we have to change the scratch-activity script, so the >>> parameter with the scratch project object-id gets converted (copy- >>> from-journal) in a file and passed on to scratch. See the attached >>> scratch-activity script. I am not an expert with bash scripts, so >>> please give feedback. >>> >>> I would like to extend the script so project files in the journal >>> directory are copied back to the journal after exiting scratch, >>> but for opening project it should work fine. >>> >>> Best regards, >>> Philipp >>> >>> John Maloney wrote: >>>> Hi, Phillip. >>>> Thanks for all your hard work in tracking this down. I had looked >>>> at several other packages, including EToys, and couldn't figure >>>> out from them how to do this. >>>> I will make these changes to the next XO Scratch bundle. >>>> Is that all I need to do? What about the mime types XML file >>>> similar to the one added by Etoys? Does that turn out to be >>>> unnecessary? >>>> -- John >>>> On Jan 13, 2009, at 12:55 AM, Philipp Kocher wrote: >>>>> Tomeu Vizoso wrote: >>>>>> On Mon, Jan 12, 2009 at 18:50, Bert Freudenberg >>>>> > wrote: >>>>>>> On 12.01.2009, at 18:11, Tomeu Vizoso wrote: >>>>>>>>> So what would the Scratch activity have to do so files put >>>>>>>>> into the >>>>>>>>> Journal >>>>>>>>> (maybe by downloading) are displayed using a Scratch icon >>>>>>>>> rather than the >>>>>>>>> generic document icon? >>>>>>>> Shipping a mimetypes.xml file inside the bundle as explained >>>>>>>> here: >>>>>>>> >>>>>>>> http://wiki.laptop.org/go/Activity_bundles#Bundle_Structure >>>>>>>> >>>>>>>> Sugar will call update-mime-database and will merge that file >>>>>>>> into the >>>>>>>> xdg mime database. >>>>>>>> >>>>>>>> I think that John is already trying this. >>>>>>> >>>>>>> Guess I'm confused then - I thought that's exactly what >>>>>>> Philipp had done. >>>>>> I think he just changed the mime_types field in the .info file. >>>>>>> And I just checked and it does work with Etoys projects. When >>>>>>> downloading >>>>>>> one it indeed gets an etoys icon (although at a smaller size - >>>>>>> why is that?) >>>>>> No idea, though I think that the mime database is updated in >>>>>> the etoys >>>>>> rpm and not in the bundle, am I right? >>>>>> Regards, >>>>>> Tomeu >>>>> >>>>> Thanks Tomeu to lead me to the /home/olpc/.local directory. >>>>> However, the >>>>> mimetypes.xml is no
Re: Journal integration for Scratch
Hi, Phillip. Thanks for all your hard work in tracking this down. I had looked at several other packages, including EToys, and couldn't figure out from them how to do this. I will make these changes to the next XO Scratch bundle. Is that all I need to do? What about the mime types XML file similar to the one added by Etoys? Does that turn out to be unnecessary? -- John On Jan 13, 2009, at 12:55 AM, Philipp Kocher wrote: > Tomeu Vizoso wrote: >> On Mon, Jan 12, 2009 at 18:50, Bert Freudenberg >> wrote: >>> On 12.01.2009, at 18:11, Tomeu Vizoso wrote: > So what would the Scratch activity have to do so files put into > the > Journal > (maybe by downloading) are displayed using a Scratch icon rather > than the > generic document icon? Shipping a mimetypes.xml file inside the bundle as explained here: http://wiki.laptop.org/go/Activity_bundles#Bundle_Structure Sugar will call update-mime-database and will merge that file into the xdg mime database. I think that John is already trying this. >>> >>> Guess I'm confused then - I thought that's exactly what Philipp >>> had done. >> I think he just changed the mime_types field in the .info file. >>> And I just checked and it does work with Etoys projects. When >>> downloading >>> one it indeed gets an etoys icon (although at a smaller size - why >>> is that?) >> No idea, though I think that the mime database is updated in the >> etoys >> rpm and not in the bundle, am I right? >> Regards, >> Tomeu > > Thanks Tomeu to lead me to the /home/olpc/.local directory. However, > the > mimetypes.xml is not necessary to get the icon in the journal. I just > had to copy the scratch icon file in the activity directory to > "application-x-scratch-project.svg" (also in the scratch activity > dirctory). The Memorize Activity is a good example for using that > feature. > Sugar has to be restarted after installing Scratch to show the icon. > > John, could you please make the following changes in the next Scratch > version: > - add the line "mime_types = application/x-scratch-project" to the > activity.info file > - copy the scratch icon to "application-x-scratch-project.svg" in the > activity directory > > Etoys gets configured by different packages. e.g. the rpm > etoys-3.0.2153-1.noarch is adding the file > /usr/share/mime/packges/etoys.xml and the rpm sugar- > artwork-0.82.3-1.olpc3 is > adding the file > /usr/share/icons/sugar/scalable/mimetypes/application-x-squake- > project.svg. > > Regards, > Philipp > ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Journal integration for Scratch
Hi, Eben. Not to worry -- I did not see your email as an attack at all. You were just pointing out the fact that the Journal does support thumbnails and text info. That's a good point. Something as innovative as Sugar simply takes time to mature, and you can't get everything 100% right the first time. You need to have real applications and real users and you need to iterate many, many times. Sugar is still in the "rapid-evolution" phase of its development. (Even more so for the Journal.) I've been working with the XO for about 18 months now, and over that time the software has made enormous progress. And rapid progress is still being made. I'm sure that things will continue to get easier over the next 18 months -- both for XO users and for those of us porting applications. Keep up the good work! -- John On Dec 18, 2008, at 1:25 PM, Eben Eliason wrote: > Thanks John! > > My previous comments weren't meant as an attack against you or > Scratch, of course. We know as well as anyone about resource > constraints! I just want to keep everyone honest, and make sure that > the broader goals for Sugar and the Journal don't get lost while we > struggle to figure out how to reach them. > > I wish I could say "the Journal does all of these things > wonderfully!", but alas, I can only muster "the Journal, as > (re)designed, would do all of these things wonderfully!" Hopefully > we'll get there. > > - Eben > > On Thu, Dec 18, 2008 at 12:57 PM, John Maloney > wrote: >> Hi, Eben. >> >> Yes, using the Journal would be optimal for XO users, and perhaps >> we will >> make Scratch do that in the long run. >> >> -- John >> >> >>>> Re: >>>>> >>>>> At the moment it is not possible to delete scratch projects easily >>>>> (just in terminal) and our students have difficulty to understand >>>>> the file and folder structure in the dialog with the very small >>>>> font. >>>> >>>> Yes, I see the problem. Your solution sounds like it would work, >>>> but >>>> the downside is that browsing for existing Scratch projects would >>>> be >>>> done using the Journal, rather than Scratch's "open" dialog. That >>>> means the user would not see the project thumbnail and project >>>> notes. >>> >>> I'm not sure this is the downside. That's one of the benefits. In >>> fact, the Journal itself supports thumbnails and a description >>> field, >>> so a similar experience could be offered there, in a place that's >>> familiar to those using Sugar. >>> >>> - Eben >> >> ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Journal integration for Scratch
Hi, Eben. Yes, using the Journal would be optimal for XO users, and perhaps we will make Scratch do that in the long run. -- John >> Re: >>> At the moment it is not possible to delete scratch projects easily >>> (just in terminal) and our students have difficulty to understand >>> the file and folder structure in the dialog with the very small >>> font. >> >> Yes, I see the problem. Your solution sounds like it would work, but >> the downside is that browsing for existing Scratch projects would be >> done using the Journal, rather than Scratch's "open" dialog. That >> means the user would not see the project thumbnail and project notes. > > I'm not sure this is the downside. That's one of the benefits. In > fact, the Journal itself supports thumbnails and a description field, > so a similar experience could be offered there, in a place that's > familiar to those using Sugar. > > - Eben ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Journal integration for Scratch
Hi, Phillip. Re: Do you plan a journal integration for scratch? Probably not in the near future. There has been talk about making an API for the Journal that looks more like a file system to application programs. That might be the easiest way to integrate the Journal into Scratch in the long run. Sugar continues to evolve. Earlier versions still allowed access to the file system in a way that made it fairly easy to port applications like Scratch. More recently, with the Rainbow security system, it became much more difficult to use the file system directly. I support Scratch on many different platforms. The XO is an important one due to the educational mission of OLPC. Still, my time is limited and I can only spend so much of it on the XO version of Scratch. Thus, I try to steer a middle path -- create a Scratch port for the XO without changing too much of the Scratch source code. I am hoping that eventually Sugar will make life easier for those porting applications from file-based platforms by providing some sort of virtual file system API. The Journal and the virtual file system could just be two views on the same set of files. Re: > At the moment it is not possible to delete scratch projects easily > (just in terminal) and our students have difficulty to understand > the file and folder structure in the dialog with the very small font. Yes, I see the problem. Your solution sounds like it would work, but the downside is that browsing for existing Scratch projects would be done using the Journal, rather than Scratch's "open" dialog. That means the user would not see the project thumbnail and project notes. If project deletion is the only issue, my preference would be to add a way to delete projects to the Scratch open and save dialogs. (Although I'm not promising to do that immediately, since we're currently working on the release of Scratch 1.4.) Another solution (which could be more near-term) would be to increase the font size in the file dialog. Do you think that would help? -- John ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Downloading Scratch project to XO
Hi, Bert. Thanks for the help on this. To clarify, what I was doing was using the clipboard to move a downloaded Scratch project file. I dragged it from the Journal to the clipboard, then went to the Scratch activity and dropped it onto the Scratch window. So that's a somewhat different path from trying to open the project directly in the Journal. It would be great to get both paths working eventually. Re: But this retrieval could be done in the Scratch wrapper script. Cool! That would be an easy solution for me if the wrapper script is not too complex. Could you give me a hint about what the wrapper script would look like? Meanwhile, I will try to make the drag-n-drop-from-clipboard solution work. -- John On Dec 16, 2008, at 6:35 PM, Bert Freudenberg wrote: > Not quite, Sugar will not actually pass the file name of the Journal > entry when launching the activity. Instead, it passes the id of a > datastore object, and the activity is supposed to retrieve that from > the datastore. But this retrieval could be done in the Scratch > wrapper script. > > - Bert - > > On 17.12.2008, at 00:35, John Maloney wrote: > >> Hi, Bert. >> >> Re: does Scratch accept a .sb file on its command line? >> >> Yes, it does. >> >> The problem is that the journal is changing the file extension to >> something like .bin, and Scratch doesn't think a .bin file is a >> Scratch project file and simply ignores it. >> >> I believe the issue is just that we need one extra file in the >> Scratch activity info to tells the Journal that Scratch handles the >> file extensions .sb and .sprite. I figured out what that file >> should have in it a few weeks back but haven't yet had a chance to >> try it. >> >> I'll give it a try and, if it works, I'll release a new version of >> Scratch on the XO that includes that file. >> >> -- John >> >> On Dec 15, 2008, at 2:46 PM, Bert Freudenberg wrote: >> >>> John, >>> >>> does Scratch accept a .sb file on its command line? >>> >>> If so, the launcher script could get the file from the Journal and >>> pass it on. >>> >>> - Bert - >>> >>> On 15.12.2008, at 18:53, John Maloney wrote: >>> >>>> Hi, Phillipp. >>>> >>>> Thanks for reporting this problem. I believe there is a way to tell >>>> the XO to associate the .sb file extension with Scratch. I will >>>> look >>>> into that and let you know if I figure it out. >>>> >>>>-- John >>>> >>>> >>>> On Dec 14, 2008, at 8:03 PM, Philipp Kocher wrote: >>>> >>>>> Hi >>>>> >>>>> I would like to download Scratch projects from a local server to >>>>> the >>>>> XO. >>>>> >>>>> On the server I added the following line to the file /etc/ >>>>> mime.types: >>>>> application/scratch sb >>>>> >>>>> The apache server is now sending files with sb-extension with mime >>>>> type application/scratch. >>>>> >>>>> On the XO the mime type gets stored in the datastore metadata- >>>>> file. >>>>> After adding the following line to the Scratch activity/ >>>>> activity.info file, Scratch gets started when clicking on the >>>>> Scratch project in the Journal: >>>>> mime_types = application/scratch >>>>> >>>>> The problem is that the project doesn't get opened. The scratch >>>>> start script bin/scratch-activity gets called with the -u argument >>>>> holding a datastore object ID, but the script doesn't handle the >>>>> -u >>>>> argument. >>>>> >>>>> How can I convert a datastore object ID to a filename, so scratch >>>>> can open the project? And how do I get the necessary permissions >>>>> to >>>>> access the file? >>>>> >>>>> Thanks, >>>>> Philipp >>>>> Pepyride School >>>>> Cambodia >>>> ___ >>>> 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: Downloading Scratch project to XO
Hi, Bert. Re: does Scratch accept a .sb file on its command line? Yes, it does. The problem is that the journal is changing the file extension to something like .bin, and Scratch doesn't think a .bin file is a Scratch project file and simply ignores it. I believe the issue is just that we need one extra file in the Scratch activity info to tells the Journal that Scratch handles the file extensions .sb and .sprite. I figured out what that file should have in it a few weeks back but haven't yet had a chance to try it. I'll give it a try and, if it works, I'll release a new version of Scratch on the XO that includes that file. -- John On Dec 15, 2008, at 2:46 PM, Bert Freudenberg wrote: > John, > > does Scratch accept a .sb file on its command line? > > If so, the launcher script could get the file from the Journal and > pass it on. > > - Bert - > > On 15.12.2008, at 18:53, John Maloney wrote: > >> Hi, Phillipp. >> >> Thanks for reporting this problem. I believe there is a way to tell >> the XO to associate the .sb file extension with Scratch. I will look >> into that and let you know if I figure it out. >> >> -- John >> >> >> On Dec 14, 2008, at 8:03 PM, Philipp Kocher wrote: >> >>> Hi >>> >>> I would like to download Scratch projects from a local server to the >>> XO. >>> >>> On the server I added the following line to the file /etc/ >>> mime.types: >>> application/scratch sb >>> >>> The apache server is now sending files with sb-extension with mime >>> type application/scratch. >>> >>> On the XO the mime type gets stored in the datastore metadata-file. >>> After adding the following line to the Scratch activity/ >>> activity.info file, Scratch gets started when clicking on the >>> Scratch project in the Journal: >>> mime_types = application/scratch >>> >>> The problem is that the project doesn't get opened. The scratch >>> start script bin/scratch-activity gets called with the -u argument >>> holding a datastore object ID, but the script doesn't handle the -u >>> argument. >>> >>> How can I convert a datastore object ID to a filename, so scratch >>> can open the project? And how do I get the necessary permissions to >>> access the file? >>> >>> Thanks, >>> Philipp >>> Pepyride School >>> Cambodia >> >> ___ >> 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: Downloading Scratch project to XO
Hi, Phillipp. Thanks for reporting this problem. I believe there is a way to tell the XO to associate the .sb file extension with Scratch. I will look into that and let you know if I figure it out. -- John On Dec 14, 2008, at 8:03 PM, Philipp Kocher wrote: > Hi > > I would like to download Scratch projects from a local server to the > XO. > > On the server I added the following line to the file /etc/mime.types: > application/scratch sb > > The apache server is now sending files with sb-extension with mime > type application/scratch. > > On the XO the mime type gets stored in the datastore metadata-file. > After adding the following line to the Scratch activity/ > activity.info file, Scratch gets started when clicking on the > Scratch project in the Journal: > mime_types = application/scratch > > The problem is that the project doesn't get opened. The scratch > start script bin/scratch-activity gets called with the -u argument > holding a datastore object ID, but the script doesn't handle the -u > argument. > > How can I convert a datastore object ID to a filename, so scratch > can open the project? And how do I get the necessary permissions to > access the file? > > Thanks, > Philipp > Pepyride School > Cambodia ___ 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
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: Scratch localization.
Hi, Erik. Unfortunately, the LocalePlugin does not solve this problem. Scratch must still read the Spanish translation file and re-layout the UI. I've forward you an email I sent to Scott about updating XO Scratch to the 1.3 release. -- John On Sep 11, 2008, at 5:35 PM, Erik Garrison wrote: > John, > > In Peru the team is using the Scratch.ini file to set the language to > spanish. There is a long delay between Scratch startup and the > setting > of the language, in which Scratch is in english. Does the > LocalePlugin > rectify this? > > What work needs to be done to update XO Scratch to Scratch 1.3? > > Erik > > On Thu, Sep 11, 2008 at 05:37:48PM -0400, John Maloney wrote: >> Hi, Erik. >> >> Apologies for the delay in responding. I was on vacation, then >> finishing >> the Scratch 1.3 release. >> >> Scratch remembers the last language set by the user in the >> Scratch.ini >> file. If that file is read-only, it fails gracefully. >> >> In older versions of Scratch (such as the current XO version), if no >> language was specified in the Scratch.ini file, Scratch would start >> up >> in English. However, it now uses the Squeak LocalePlugin to set the >> default language. So if the computer's locale is set to Spanish, >> Scratch >> should start up in Spanish. This feature has not yet been tested on >> Linux, but it does work on Mac OS and Windows. >> >> Many thanks to the Squeak folks for creating the LocalePlugin! >> >> So I think things may work fine as they are, once we've updated XO >> Scratch to the 1.3 release. (I'm working on that now, with help from >> Scott if he is willing). >> >> Scratch does not need to write persistent data to any other files. >> >> (It does need to write user projects somewhere, but Scott has solved >> that problem for now.) >> >> -- John >> >> >> On Aug 27, 2008, at 1:00 PM, Erik Garrison wrote: >>> On Wed, Aug 27, 2008 at 06:54:18PM +0200, Bert Freudenberg wrote: >>>> >>>> Am 27.08.2008 um 18:38 schrieb C. Scott Ananian: >>>> >>>>> Scratch appears to require manual editing of the Scratch.ini >>>>> file in >>>>> order to come up in a language other than English. Is there any >>>>> way I >>>>> can pass a command-line option in bin/scratch-activity to set the >>>>> Language preference based on the value of $LANG? I'd prefer >>>>> that we >>>>> not have to ship a different Scratch bundle per-country. >>>> >>>> The Right Way to do it would be using the LocalePlugin, as Etoys >>>> does. >>>> >>>> If you need to patch up the bundle you could use the symlink trick >>>> again, the actual Scratch.ini would live in data/. Thus the >>>> language >>>> (and other settings possibly) that the user choses would persist. >>>> When >>>> running for the first time, the startup script could generate an >>>> initial Scratch.ini for the right language. >>> >>> What other persistent data beyond Scratch.ini does Scratch like to >>> modify? >> ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Getting a path to SUGAR_ACTVITY_ROOT
Hi, Scott.
I wonder if you could give me a bit of guidance. The Scratch file
dialogs have shortcuts for common folders on Windows and Mac, such as
the desktop and the user's documents folder. Most of these shortcuts
make no sense on the XO, but I thought that perhaps the documents
shortcut could go to $SUGAR_ACTVITY_ROOT/data. But my first attempt to
lookup that environment variable did not seem to work (although I have
not tried it in the context of your new wrapper; maybe it does work
now).
Anyhow, the code I wrote to do this is:
char *s = NULL;
path[0] = 0; // a zero-length path indicates failure
s = getenv("SUGAR_ACTVITY_ROOT");
if (s != NULL) {
strncat(path, s, maxPath);
strncat(path, "/data", maxPath);
}
where path is a C string passed in by the client that is supposed to
get filled in with the path to documents folder.
I'm not used to programming in Unix. Does this look okay to you?
-- John
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
Scratch Sensor Board needs access to TTYUSB*
Hi, Jim. Claudia Urrea would like to get the Scratch Sensor Board working on the XO. There was a minor bug in the Scratch serial port support, which I've now fixed. The fix will be in the next Scratch activity bundle. But the other problem is that the USB port is not readable and writable by default. I've posted some instructions at http://wiki.laptop.org/go/Scratch#Scratch_Sensor_Board (also attached below). It would much better if XO users did not need to do this Unix black magic. Could we get this rule (or equivalent) into the standard build? Thanks! -- John -- NOTE: There is a bug in Scratch v7 and earlier that keeps the sensor board from working. I've fixed the bug and am working on updating the Scratch activity. But once the new activity is ready, the following should get the sensor board working. To use the Scratch Sensor Board or Pico Sensor Board (http://scratch.wik.is/Support/Sensor_Boards ), you must add a file to the folder: /etc/udev/rules.d This file should contain the single line: KERNEL=="ttyUSB*", MODE="0666" Adding this file allows Scratch to read and write data to the sensor board. You will need to make yourself root using the "su" command in order to add a file to that folder. -- ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Scratch localization.
Hi, Erik. Apologies for the delay in responding. I was on vacation, then finishing the Scratch 1.3 release. Scratch remembers the last language set by the user in the Scratch.ini file. If that file is read-only, it fails gracefully. In older versions of Scratch (such as the current XO version), if no language was specified in the Scratch.ini file, Scratch would start up in English. However, it now uses the Squeak LocalePlugin to set the default language. So if the computer's locale is set to Spanish, Scratch should start up in Spanish. This feature has not yet been tested on Linux, but it does work on Mac OS and Windows. Many thanks to the Squeak folks for creating the LocalePlugin! So I think things may work fine as they are, once we've updated XO Scratch to the 1.3 release. (I'm working on that now, with help from Scott if he is willing). Scratch does not need to write persistent data to any other files. (It does need to write user projects somewhere, but Scott has solved that problem for now.) -- John On Aug 27, 2008, at 1:00 PM, Erik Garrison wrote: > On Wed, Aug 27, 2008 at 06:54:18PM +0200, Bert Freudenberg wrote: >> >> Am 27.08.2008 um 18:38 schrieb C. Scott Ananian: >> >>> Scratch appears to require manual editing of the Scratch.ini file in >>> order to come up in a language other than English. Is there any >>> way I >>> can pass a command-line option in bin/scratch-activity to set the >>> Language preference based on the value of $LANG? I'd prefer that we >>> not have to ship a different Scratch bundle per-country. >> >> The Right Way to do it would be using the LocalePlugin, as Etoys >> does. >> >> If you need to patch up the bundle you could use the symlink trick >> again, the actual Scratch.ini would live in data/. Thus the language >> (and other settings possibly) that the user choses would persist. >> When >> running for the first time, the startup script could generate an >> initial Scratch.ini for the right language. > > What other persistent data beyond Scratch.ini does Scratch like to > modify? ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: CSound server questions
Hi, Victor and Bert. I agree with Bert -- it would probably be most convenient for Scratch to use the MIDI option, if possible. Ideally, it would work the same as MIDI does on other versions of Linux, so we could just use the Squeak MIDI Plugin. That said, I have not explored how the MIDI plugin works on Linux. Supposedly you can use it to talk to the Timidity software MIDI synth. Could we arrange for the shell script that launches Scratch to also launch the CSound server when Scratch is launched and close it when Scratch quits? -- John On Aug 31, 2008, at 2:50 PM, victor wrote: > No, you have to run it with a command-line option and then use > aconnect I suppose. I need to check how to do soft connections, > as I am used to just connecting straight to hardware . > > Victor > > - Original Message - From: "Bert Freudenberg" <[EMAIL PROTECTED] > > > To: "OLPC Development" > Cc: "John Maloney" <[EMAIL PROTECTED]> > Sent: Sunday, August 31, 2008 7:01 PM > Subject: Re: CSound server questions > > >> Am 31.08.2008 um 19:04 schrieb victor: >>> Well, you can ask me. I suppose there are various ways you could >>> connect to Csound: >>> >>> 1. using the API (via a C or C++ squeak plugin >>> module, if it is possible to do these things), >>> 2. through MIDI (if >>> squeak can output MIDI and we can then connect via alsa midi) >>> 3. OSC >>> 4. IP socket (by starting a minimal server written in Python >>> and issuing Python commands as string data) >>> 5. line events at stdin (a little awkward) >> I like the MIDI option. Squeak does have a MIDI plugin (although I >> am not entirely sure how functional it is currently). >> Is CSound registered as a MIDI device by default? >> - Bert - >> ___ >> 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: CSound server questions
Thanks, Jim and Victor. Jim, your explanation makes sense. Good to know what the future direction is for OLPC and CSound. If I have questions about making Scratch use CSound, who is the best person to ask? -- John On Aug 28, 2008, at 12:31 PM, victor wrote: > I'd just like to correct, for the record, that the Csound 5 > project leader, of which I am part, is and has always been > John ffitch. I am the fedora package maintainer for the > olpcsound subset (and I'lll probably pick up the full Csound5 > package too). John has also done a substantial work in > setting up the subset build. > > We would welcome, very much, Barry's input in > Csound 5 development, if he'd like to be involved. > > Victor > > - Original Message - From: "Jim Gettys" <[EMAIL PROTECTED]> > To: "John Maloney" <[EMAIL PROTECTED]> > Cc: <[EMAIL PROTECTED]>; ; "Chris > Ball" <[EMAIL PROTECTED]>; "C. Scott Ananian" <[EMAIL PROTECTED]> > Sent: Thursday, August 28, 2008 4:08 PM > Subject: Re: CSound server questions > > >> John, >> >> We cannot use code from Barry since he tends to work by himself, his >> code is unmaintainable except by him and its licensing has also been >> somewhat questionable at times, though the licening problems may have >> been addressed.. Were he to be run over by a truck (God forbid!), >> we'd >> be in a complete pickle. >> >> The community CSound, that Victor leads, is widely used and >> supported by >> a large community of people. >> >> Previous objections of "CSound bloat" (by things like the public >> csound >> using the TK/TCL internally to the CSound library) have been >> addressed >> by Victor, who now has (at configure time) a version of CSound5 built >> out of the same source pool that drops those dependencies. >> >> You can be sure that *anything* that runs on the CSound lite we run >> on >> OLPC will run on the public full CSound used in the music >> community; it >> is an *exact* subset of the full CSound used by everyone except >> Barry. >> >> So we are also in a very much better compatibility situation than >> using >> Barry's version. >> >> Hope this explanation helps. >>- Jim >> >> >> On Wed, 2008-08-27 at 06:42 -0400, John Maloney wrote: >>> Thanks for the info. >>> >>> I had the impression that Barry Vercoe was working on a new, light- >>> weight CsoundServer. Is that not true? >>> >>> -- John >>> >>> On Aug 27, 2008, at 5:15 AM, [EMAIL PROTECTED] wrote: >>> > There is no CsoundServer anymore; we use Csound as a library >>> > through its API. If anyone wants some help on how to use it, to >>> > play MIDI or anything else, he/she can talk to me, privately or >>> > on this list. I'm away to ICMC at the moment, so replies might >>> > be slow. But I'll give as much help as I can. >>> > >>> > Regards >>> > >>> > Victor >>> > >>> > - Original Message - >>> > From: Chris Ball <[EMAIL PROTECTED]> >>> > Date: Tuesday, August 26, 2008 11:35 pm >>> > Subject: Re: CSound server questions >>> > To: "C. Scott Ananian" <[EMAIL PROTECTED]> >>> > Cc: John Maloney <[EMAIL PROTECTED]>, devel@lists.laptop.org >>> > >>> > > Hi, >>> > > >>> > >> Did you ever get a satisfactory answer to your >>> > > questions? I think >>> > >> Pippy contains the best examples of using csound >>> > > to play sounds -- >>> > >> is that right, Chris? >>> > > >>> > > Well, I'd say that TamTam does. :) But yes, Pippy >>> > > does some basic >>> > > synthesis using sinewaves and music files with csound. >>> > > >>> > > - Chris. >>> > > -- >>> > > Chris Ball <[EMAIL PROTECTED]> >>> > > ___ >>> > > 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 >> -- >> Jim Gettys <[EMAIL PROTECTED]> >> One Laptop Per Child > ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: CSound server questions
Thanks for the info. I had the impression that Barry Vercoe was working on a new, light- weight CsoundServer. Is that not true? -- John On Aug 27, 2008, at 5:15 AM, [EMAIL PROTECTED] wrote: > There is no CsoundServer anymore; we use Csound as a library > through its API. If anyone wants some help on how to use it, to > play MIDI or anything else, he/she can talk to me, privately or > on this list. I'm away to ICMC at the moment, so replies might > be slow. But I'll give as much help as I can. > > Regards > > Victor > > - Original Message - > From: Chris Ball <[EMAIL PROTECTED]> > Date: Tuesday, August 26, 2008 11:35 pm > Subject: Re: CSound server questions > To: "C. Scott Ananian" <[EMAIL PROTECTED]> > Cc: John Maloney <[EMAIL PROTECTED]>, devel@lists.laptop.org > > > Hi, > > > >> Did you ever get a satisfactory answer to your > > questions? I think > >> Pippy contains the best examples of using csound > > to play sounds -- > >> is that right, Chris? > > > > Well, I'd say that TamTam does. :) But yes, Pippy > > does some basic > > synthesis using sinewaves and music files with csound. > > > > - Chris. > > -- > > Chris Ball <[EMAIL PROTECTED]> > > ___ > > 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: Scratch fails to write to Scratch.activity/Projects
Hi, Scott. What's wrong with just making the directory Scratch.activity/Projects writable by the world? Seems to me that it could not hurt other applications. Scratch does not run any binary files from that folder, so it should be pretty safe. At worse, some malicious software could write a bogus project file that Scratch would refuse to open. The Scratch activity used to install that way but I suppose something about the installation process has changed. I'm currently in the process of getting Scratch 1.3 out the door. When the dust settles from that I will see what I can do about making Scratch work better on the XO. But I don't think I want to add journal support even if is easy because I'd like to keep the same version of Scratch across all platforms, and Scratch was designed to be file-based. Is there a Wiki page that explains how to use the bug database? Feel free to re-package the current Scratch activity installer to include your patch, if you think that makes sense. -- John On Aug 26, 2008, at 6:36 PM, C. Scott Ananian wrote: > In http://dev.laptop.org/ticket/8166 there's a problem reported: Peru > can't save their work in Scratch, because Scratch tries to write to > Scratch.activity/Projects, and this is not writable. Luckily, there > is an easy workaround: the directory $SUGAR_ACTIVITY_ROOT/data is > persistent storage which is writable by the activity, and properly > protected. On the trac page I've also provided a patch which wraps > Scratch so that it writes to the proper place. > > Tomeu also volunteered on IRC earlier today to help you implement > proper Journal support for Scratch. > > Finally: there are a number of bugs filed against scratch in our bug > tracker, but it doesn't appear to have a proper component and owner > created for it in the tracker. We'd like to fix that: do you have a > username on the dev.laptop.org trac instance that we could make the > default owner of bugs filed against 'scratch-activity' so that you are > promptly notified if/when people have problems? > > Thanks for porting scratch, the kids in Peru seem to really like > it. ;-) > --scott > > -- > ( http://cscott.net/ ) ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
CSound server questions
Greetings, all. I am porting Scratch to the XO. (Scratch is an easy-to-learn programming environment designed to help young people create interactive multimedia. See scratch.mit.edu.) Scratch includes commands to play notes and trigger drum sounds. On Windows and Mac OS, these commands use the underlying OS MIDI synthesizer. On the XO, I've been told that the best way to implement these commands is to send messages to the CSound Server (http:// rhythmicdesign.com/CsoundXO/). I tried some of the Python examples on that page, but they did not work on my XO under build 653. (It appears that the path to the CSound Server was wrong.) Here are my questions: a. Is the CSound server pre-installed? b. Is the CSound server started up automatically at boot time? If not, how do I start it? c. Is there a complete General MIDI soundbank/orchestra available for the XO? If so, how do I use it? I am new to the OLPC developer's list. If this is not the right forum for these questions, perhaps someone could tell me where I should ask them. Thank you! -- John ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
