Re: [Sugar-devel] Hello to everybody!
Ernesto, To answer your question, I don't know. Frankly, I've never tried anything like this - though I have two XO's and a neighbor with one. Art Hunkins - Original Message - From: "Coltivare Fiori" To: "Art Hunkins" Cc: Sent: Tuesday, October 09, 2012 4:36 PM Subject: Re: [Sugar-devel] Hello to everybody! On 09/10/2012 21:31, Art Hunkins wrote: FWIW, I have an Intel Classmate Go2PC, and the SoaS sticks I've made, via Live USB Creator (on Windows XP), have all worked fine. I have two Intel Classmate 2009 running Sugar 0.96.1 and I cannot have them cooperate. If they are close to each other and both of they connect to "Ad-hoc network 1", "Ad-hoc network 6" or "Ad-hoc network 11", they can't see each other. If one of them is close to a Sugar 0.96.1 running on an older laptop, it is seen by it, but cannot see it. Could your Intel Classmate ever cooperate with another Sugar? This issue is possibly the worst one affecting me. Ernesto ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Hello to everybody!
FWIW, I have an Intel Classmate Go2PC, and the SoaS sticks I've made, via Live USB Creator (on Windows XP), have all worked fine. I recommend Live USB Creator 3.9.3 for recent builds of SoaS, as it does not hang at the SysLinux screen. (V 3.11.7 also does reasonably well: a single press of Enter gets you out beyond SysLinux if there is a hang.) I've tested through Sugar 0.96 (Fedora 17); all works correctly on the Classmate. The latest nightly builds based on Fedora 18 do *not* boot correctly (though they seem to install correctly to a 4GB USB stick), so I've no ready way to test Sugar 0.98. I do think it wise (possibly required?) to use a USB stick > 1GB. Art Hunkins - Original Message - From: "Coltivare Fiori" To: Sent: Tuesday, October 09, 2012 9:13 AM Subject: Re: [Sugar-devel] Hello to everybody! Yes! I have tried it a LOT :-))) Sometimes I succeeded, sometimes not really. I'm using it on one Intel Classmate 2009 PC and I am about to test it on two of such machines. I'll let the list know! TIA Ernesto On 09/10/2012 15:04, Martin Abente wrote: Hello! Have you tried Sugar On A Stick? You can run sugar on your own laptop. http://wiki.sugarlabs.org/go/Sugar_on_a_Stick Saludos, Tincho. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Review Request for ChimePlay-2
Would a reviewer kindly rescue my ChimePlay-2 from the sandbox? It's been languishing there for about a week, and has unfortunately developed sunburn. And all because he was caught with a small bug and disciplined accordingly. Thanks. Art Hunkins ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] 0.96 Change?
I notice that for Sugar 0.96 it seems necessary, in copying a file from the Terminal to a USB stick, to do: cp myfile.py /run/media/liveuser/myUSB/myfile.py (perhaps I've got liveuser and myUSB reversed) instead of the much simpler (in 0.94 and before): cp myfile.py /media/myUSB/myfile.py (two new levels!) Is this really the case? Seems unfortunate if so. Art Hunkins ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Fedora-17-Beta-TC2-i686-Live-SoaS testing results
FWIW, this version fails to install correctly to a 2GB USB stick via Live-USB-Creator. The log report: Traceback (most recent call last): File "liveusb\gui.pyc", line 420, in status TypeError: QTextEdit.append(QString): argument 1 has unexpected type 'int' The stick also fails to boot on a computer. I suspect the problem has more to do with the compatibility between Live-USB-Creator and the TC2-Beta .iso however. Am I correct? Art Hunkins - Original Message - From: Thomas C Gilliard To: SoaS ; Sugar Devel Sent: Sunday, March 18, 2012 7:15 PM Subject: [Sugar-devel] Fedora-17-Beta-TC2-i686-Live-SoaS testing results Please look at this: These activities need to be fixed Abacus etoys read Tom Gilliard satellit_ on #sugar Test results: a.. http://wiki.sugarlabs.org/go/Community/Distributions/Fedora-SoaS#Fedora-17-Beta-TC2-i686-Live-SoaS Fedora-17-Beta-TC2-i686-Live-SoaS a.. http://koji.fedoraproject.org/koji/getfile?taskID=3907156&name=Fedora-17-Beta-TC2-i686-Live-SoaS.iso Tested CD usingPenguin Libre GNU / Linux Notebook i3. (all free drivers) a.. Boots to name___; Color___ b.. Wireless AP (WEP) Connects and stays connected c.. Sees Jabber About my Computer Build Sugar on a Stick 7 Fedora release 17 (Beefy Miracle) Sugar 0.95.4 Firmware 2.60 Activities 2-) Tested in VirtualBox 4.1.10 install to 8 GB HD Use whole Disk [x]use LVM key &=not favorite; ok=starts and saves; ==> updates to: etoys 116 no DBusError: Process /usr/bin/sugar-presence-service exited with status 1 (pulsing in top bar after quit) visual match35 ok chat73 ok ==>74 ok maze15 ok moon13 ok abacus 31 no failed to start AttributeError: 'AbacusActivity' object has no attribute 'set_toolbox' are we shipping too new a version here? turtle art 136 ok write 77 ok ==>78 ok typing turtle 29 ok speak 36 ok ==37 ok jukebox 23 ok irc 10 ok pippy 45 ok?* ==>46 ok fixed*(Physics does not start in 45) memorize39 ok & portfolio 21 ok image viewer19 ok? no matching entries log 26 ok ==>27 ok calculate 38 ok record 93==>94 ok sees VirtualBox USB Camera ruler 19 ok clock7 ok physics 9 ok terminal35 ok & read 97 no failed to start & browse 131 ok ==>132 ok tools_livecd-iso-to-disk Persistent USB-stick 4 GB EMTEC USB-sticksudo ./tools_livecd-iso-to-disk.sh --reset-mbr --overlay-size-mb 500 --home-size-mb 900 --delete-home --unencrypted-home Fedora-17-Beta-TC2-i686-Live-SoaS.iso /dev/sd(x)1 Verifying image... ./tools_livecd-iso-to-disk.sh: line 806: checkisomd5: command not found Are you SURE you want to continue? Press Enter to continue or ctrl-c to abort Copying live image to target device. squashfs.img 489975808 100%6.98MB/s0:01:06 (xfer#1, to-check=0/1) sent 490035693 bytes received 31 bytes 7259788.50 bytes/sec total size is 489975808 speedup is 1.00 osmin.img 8192 100%0.00kB/s0:00:00 (xfer#1, to-check=0/1) sent 8265 bytes received 31 bytes 16592.00 bytes/sec total size is 8192 speedup is 0.99 Updating boot config file Initializing persistent overlay file 500+0 records in 500+0 records out 524288000 bytes (524 MB) copied, 86.1616 s, 6.1 MB/s Initializing persistent /home 900+0 records in 900+0 records out 943718400 bytes (944 MB) copied, 211.095 s, 4.5 MB/s Formatting unencrypted /home mke2fs 1.41.11 (14-Mar-2010) Filesystem label= OS type: Linux Block size=4096 (log=2) Fragment size=4096 (log=2) Stride=0 blocks, Stripe width=0 blocks 57600 inodes, 230400 blocks 11520 blocks (5.00%) reserved for the super user First data block=0 Maximum filesystem blocks=239075328 8 block groups 32768 blocks per group, 32768 fragments per group 7200 inodes per group Superblock backups stored on blocks: 32768, 98304, 163840, 229376 Writing inode tables: done Creating journal (4096 blocks): done Writing superblocks and filesystem accounting information: done This filesystem will be automatically checked every 39 mounts or 180 days, whichever comes first. Use tune2fs -c or -i to override. tune2fs 1.41.11 (14-Mar-2010) Setting maximal mount count to -1 Setting interval between checks to 0 seconds Installing boot loader Target device is now set up with a Live image! -- ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Testing Activities with Sugar 0.96
Thanks to Tom and others who responded to my inquiry. I have found that the nightly Fedora17 SoaS compose at (Tom's): http://people.sugarlabs.org/Tgillard/Fedora-17-Nightly-20120221.07-i686-Live-soas.isodoes indeed install (to a USB stick) and work with Live-USB-Creator (thoughstrangely, more recent nightly composes - for example, 20120307.09 and20120313.10 - do not).The sugar version for the above nightly compose is 0.95.4. Can I assume thatmy activities, which all work with 0.95.4, are (or will be) compatible withSugar 0.96?I ask because 0.96 compatibility is one of the options for Sugar activities,and many activities are already indicated as being "0.96 compatible." I'dlike to be sure mine are as well.Art Hunkins- Original Message -From: "Thomas C Gilliard" To: "Art Hunkins" Cc: Sent: Tuesday, March 13, 2012 6:19 PMSubject: Re: [Sugar-devel] Testing Activities with Sugar 0.96>>> On 03/13/2012 02:42 PM, Art Hunkins wrote:>> I've been eager to test my activities with 0.96, but don't find a readymeans of doing it.>>>> I primarily look to Sugar-on-a-Stick, but 0.94 (Pineapple) is the lastofficial release.>> 1-) Install works>http://wiki.sugarlabs.org/go/Community/Distributions/Fedora-SoaS#Fedora-17-Beta-TC1-x86_64-Live-XFCE_with_Sugar_0.95.4>> 2-) Make bootable Sugar 0.95.4 persistent USB-sticks>http://wiki.sugarlabs.org/go/Sugar_Creation_Kit/sck/tools_livecd-iso-to-disk#Fedora-17-Beta-TC1-i686-Live-Desktop>http://wiki.sugarlabs.org/go/Sugar_Creation_Kit/sck/tools_livecd-iso-to-disk#Fedora-17-Nightly-20120221.07-i686-Live-soas [1] (no longer available fromnightly composes)>> 3-)Activity testing:>http://wiki.sugarlabs.org/go/Sugar_Creation_Kit/sck/Activity_Matrix%28A_to_I%29>http://wiki.sugarlabs.org/go/Sugar_Creation_Kit/sck/Activity_Matrix%28J_to_Z%29>> Cordially;>> Tom Gilliard> satellit_>> [1]http://people.sugarlabs.org/Tgillard/Fedora-17-Nightly-20120221.07-i686-Live-soas.iso>> Live-USB-Creator won't make me a bootable USB stick with the latestFedora17 nightly builds eit her. (It all fails - goes black - just before theusername screen should appear.)>>>> I've an XO-1 and XO-1.5 available as well, if an 0.96 is available foreither of these.>>>> Art Hunkins>> ___>> Sugar-devel mailing list>> Sugar-devel@lists.sugarlabs.org>> http://lists.sugarlabs.org/listinfo/sugar-devel>> ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Testing Activities with Sugar 0.96
I've been eager to test my activities with 0.96, but don't find a ready means of doing it. I primarily look to Sugar-on-a-Stick, but 0.94 (Pineapple) is the last official release. Live-USB-Creator won't make me a bootable USB stick with the latest Fedora17 nightly builds either. (It all fails - goes black - just before the username screen should appear.) I've an XO-1 and XO-1.5 available as well, if an 0.96 is available for either of these. Art Hunkins ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Fw: [REQUEST] ChimePlay-1
I'd appreciate a reviewer taking the time to review my new activity, ChimePlay. It has been in the queue for several weeks now (originally the queue contained 13 activities; it still does, FWIW). In case it matters, I've included here my response to Walter's request in regard to ChimePlay. (My response wasn't originally addressed to this list or to Walter personally.) Perhaps someone was waiting for me to address it? In any case, thanks for your support. Art Hunkins - Original Message - From: "Art Hunkins" To: Cc: Sent: Saturday, March 03, 2012 4:36 PM Subject: Re: [REQUEST] ChimePlay-1 Hello, Walter, Thanks so much for your on-going help and encouragement for and with my Sugar activities. Without it, and similar counsel from other seasoned Sugar activity developers, I'd still be stuck in the "Sugar starting gate." Your observations here can apply just as well to my previous 7 activities. Indeed, perhaps it is ironic that in ChimePlay there is the *least* amount of displayed verbiage of any of my activities; I've done my best to keep it down. (For my last three activities, which urge children to create their own audio samples, most of my commentary is included in a ReadMe.txt file. Only "immediately relevent" material is presented on-screen.) Some context: I am a professional art music composer, whose main "electronic" language is Csound. All my Sugar activities are spinoffs of live-performance Csound works composed for adults (please see my website, www.arthunkins.com, where these relationships are clear enough). At the urging of Richard Boulanger, I was led into OLPC, Sugar and the XO, to offer some of my work to at least the older children of the world. As an exclusively Windows person, Linux has been a strange new world - also inhabited by Sugar, Python, PyGTK, git, Inkscape - all equally new and strange. ChimePlay almost didn't get written; I thought that SamplePlay was my last activity. However, inspired by a couple of chime sets at the St. Francis Springs Prayer Center (Stoneville, NC, USA) and my life-long fascination with chimes and bells, ChimePlay manifested and here we are. In the future, I intend no more activities; I'll simply maintain and continue to test the 8 activities I have so that hopefully they remain useful. Hopefully you can humor me this one last time. I also hope my work points the way for other Csound artists to become involved with Sugar with an equally limited investment of time and technology. (Though I admit the requirements of my doing *anything* in Linux/Sugar was infinitely beyond any investment I'd anticipated. It's been an incredibly difficult and arduous learning curve. For example, I just spent three intense and frustrating days relearning Inkscape in order to create a passable icon for ChimePlay.) Early in my activity work, I found some Python/GTK code structures that I could reasonably understand and continue to use in all my activites. I've intentionally limited the depth of tech work I've exposed myself to, and only bugged other developers, like yourself, with issues I considered crucial. I've dealt with others (such as on-screen text, the limit to English, the treatment of MIDI device insertion/detection) in "non-Sugar-like" ways, which were understandable by "low/non-tech" me. I did this to protect myself and my sanity - as well as to complete anything. I'm well aware that most children will not have access to MIDI devices. For live Csound work in the adult world, however, MIDI devices are universally required. (In my recent activity ReadMe's, I've indeed recommended certain inexpensive devices to children and their teachers, especially the Korg nanoKontrol.) It seems to me that for any performance activity with Csound (such as for the XO or Sugar), classrooms might well opt to invest in a few MIDI devices, such as keyboard controllers. My activities allow for a very wide range of devices. In previous activities, I've made alternate versions which used only the ASCII keyboard. However, I've found these versions awkward and counterintuitive, as well as requiring considerable additional written explanation. I never use them for my own demonstrations. (They also are a pain to program.) Instead, in ChimePlay, I've paired one live-performance MIDI version with an auto-play incarnation, which requires no controller at all. Just (optionally) adjust the presets, press START and instant chimes (your choice of two chime sets). Once again, thanks for your most valuable help and advice - and the spirit and tone in which it has been given - over several years. Art Hunkins - Original Message - From: "Sugar Labs Activities" To: Cc: Sent: Friday, March 02, 2012 11:03 PM Subject: [REQUEST] ChimePlay-1 A Suga
Re: [Sugar-devel] git initial commit
Thanks, Alan and James, Once I created a respository I successfully made an initial commit. Strange, however, 1) I don't recall it ever being suggested I *needed* to create a repository. I'd think "mainline.git" would be automatically set up for a new project, and be part of the project creation process. 2) Clicking on "Add a repository" (which suggested there was already a repository in existence), I tried to name the repository "mainline," but it was named instead "chimeplay.git." I wonder whatever happened to "mainline"? At any rate, "next time" I'll check to see if any repository exists before trying to save to one. (Go figure.) Art Hunkins - Original Message - From: Alan Jhonn Aguiar Schwyn To: abhun...@uncg.edu ; sugar-devel@lists.sugarlabs.org Sent: Sunday, March 04, 2012 6:15 PM Subject: RE: [Sugar-devel] git initial commit > [liveuser@localhost chimeplay.git]$ git push > gitori...@git.sugarlabs.org:chimeplay/mainline.git master > > == Gitorious: == > Access denied or wrong repository path > > > fatal: The remote end hung up unexpectedly > [liveuser@localhost chimeplay.git]$ > > - > BTW, I get the same response when I omit "master" from the last command. > > What am I doing wrong please? > I see a problem: you create the project in http://git.sugarlabs.org/chimeplay but no a "repository" For each project you can have some repositories.. Go tohttp://git.sugarlabs.org/chimeplay and in the right panel select: Add a repository and select a name: for example: mainline After.. make this in your machine if is the first time that uses GIT: git config --global user.name 'your name' git config --global user.email "your mail" After, go to the master brach: git checkout master Add the remote of your activity: (mainline is only for example) git remote add origin gitori...@git.sugarlabs.org:chimeplay/mainline.git And finally: git push origin master Regards! Alan___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] git initial commit
I'm having trouble again (sorry) with an initial git commit. Here's what I've done: 1) Login to gitorious and create a new project. Slug: chimeplay 2) While there I check to see that my ssh-r key is installed correctly. 3) From my chimeplay.git (top level) directory I run the following sequence. All responses except the last are what I'd expect: [liveuser@localhost chimeplay.git]$ git init Initialized empty Git repository in /home/liveuser/Activities/chimeplay.git/.git/ [liveuser@localhost chimeplay.git]$ git add . [liveuser@localhost chimeplay.git]$ git status # On branch master # # Initial commit # # Changes to be committed: # (use "git rm --cached ..." to unstage) # # new file: ChimePlay.csd # new file: ChimePlayAuto.csd # new file: ChimePlayReadMe.txt # new file: MANIFEST # new file: activity/activity-chimeplay.svg # new file: activity/activity.info # new file: chimeplay.py # new file: csndsugui.py # new file: setup.py # new file: soundin.0 # new file: soundin.1 # new file: soundin.10 # new file: soundin.11 # new file: soundin.12 # new file: soundin.13 # new file: soundin.14 # new file: soundin.15 # new file: soundin.16 # new file: soundin.17 # new file: soundin.18 # new file: soundin.2 # new file: soundin.3 # new file: soundin.4 # new file: soundin.5 # new file: soundin.6 # new file: soundin.7 # new file: soundin.8 # [liveuser@localhost chimeplay.git]$ git commit -a -m"Version 1" [master (root-commit) b84ae12] Version 1 27 files changed, 1691 insertions(+), 0 deletions(-) create mode 100644 ChimePlay.csd create mode 100644 ChimePlayAuto.csd create mode 100644 ChimePlayReadMe.txt create mode 100644 MANIFEST create mode 100644 activity/activity-chimeplay.svg create mode 100644 activity/activity.info create mode 100644 chimeplay.py create mode 100644 csndsugui.py create mode 100644 setup.py create mode 100644 soundin.0 create mode 100644 soundin.1 create mode 100644 soundin.10 create mode 100644 soundin.11 create mode 100644 soundin.12 create mode 100644 soundin.13 create mode 100644 soundin.14 create mode 100644 soundin.15 create mode 100644 soundin.16 create mode 100644 soundin.17 create mode 100644 soundin.18 create mode 100644 soundin.2 create mode 100644 soundin.3 create mode 100644 soundin.4 create mode 100644 soundin.5 create mode 100644 soundin.6 create mode 100644 soundin.7 create mode 100644 soundin.8 [liveuser@localhost chimeplay.git]$ git push gitori...@git.sugarlabs.org:chimeplay/mainline.git master == Gitorious: == Access denied or wrong repository path fatal: The remote end hung up unexpectedly [liveuser@localhost chimeplay.git]$ - BTW, I get the same response when I omit "master" from the last command. What am I doing wrong please? Art Hunkins ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [SoaS] SoaS v7?
Yes, SoaS v6 is indeed wonderful. It seems speedier to load the OS, load Activities, and shut down than previous versions. Kudos to Peter Robinson especially. Art Hunkins - Original Message - From: Thomas C Gilliard To: s...@lists.sugarlabs.org Cc: IAEP SugarLabs ; Sugar Devel Sent: Thursday, November 10, 2011 1:17 PM Subject: Re: [Sugar-devel] [SoaS] SoaS v7? This is an example of a dd writable SoaS-v2.img file which produces a fully functional Conventional install on a USB. This is equivalent to a liveinst install to USB.[1] It was first suggested by bernie [2] in early 2010 as a better alternative to the currently used live USB SoaS filesystems with their fragile and limited sized overlay, a.. This functionality is expected to be included in fedora 17 liveinst (Anaconda) b.. It would be even nicer to be able to create and install to USB, the Soas-v7.img file directly from the first sugar boot screen as a third option line, rather from a obscure liveinst command in terminal. [1] http://wiki.sugarlabs.org/go/Sugar_Creation_Kit#A-Non-Live_.28real_file_structured.29_USB (a working 4GB dd Soas-v2.img file and description. As proof of concept) [2] http://people.sugarlabs.org/Tgillard/Direct_Soas.txt (Original Announcement) SoaS-v6 is great...thanks Tom Gilliard satellit_ On 11/09/2011 04:18 PM, Peter Robinson wrote: Hi All, So there's no rest for the wicked its time to think about what you would like to develop for SoaS v7. I know upstream is all very busy already the sugar team are full pelt into the conversion of sugar to gtk3 and PyGI and there's all sorts of fun stuff going into Fedora... so what do you want? Peter ___ SoaS mailing list s...@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/soas -- ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] SamplePlay-2.xo in Sandbox
Yes, Spanish-language versions of my activities would be very appropriate and useful. I would welcome them. I am not Spanish-speaking, and would need a collaborator who is equally versed in both Spanish and English. The collaborator would be in complete charge of translation (I could help with details of intent); my role would be to check and test screen formatting (including various monitor resolutions) and insure that the activities run as intended. Please have anyone interested contact me. My activities are: Our Music and Our Music MC Sun-Moon Music and Sun-Moon Music MC FileMix FileMixAuto SamplePlay Art Hunkins - Original Message - From: Chris Leonard To: Art Hunkins Cc: sugar-devel@lists.sugarlabs.org Sent: Tuesday, October 11, 2011 11:51 AM Subject: Re: [Sugar-devel] SamplePlay-2.xo in Sandbox On Tue, Oct 11, 2011 at 11:34 AM, Art Hunkins wrote: I'm well aware that my "single-language-only" approach is probably unique to the world of Sugar; I would have liked to envisage a practical, feasible alternative that might "reach more children." I'd also appreciate feedback from developers, users, whomever who have looked at the activities (such as SamplePlay or FileMix). To date, I've received very little - no doubt at least partly because the activities are rather complex and clearly directed at older children. While I can appreciate the care you put into the aesthetics of your design, it is reasonably safe to say that more than half of all Sugar users speak Spanish (through the large XO deployments in South and Central America). I would at least consider generating a Spanish language version to double your potential user-base. cjl ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] SamplePlay-2.xo in Sandbox
Chris, Thanks for your observation. I seriously considered the internationalization option prior to getting involved in writing Sugar activities. I found that what I wanted to do was *intensively* text-based, and that if I wanted control of the look of the text (i.e., text onscreen formatting), I'd need to carefully control it - often even down to the precise number of characters. Screen formatting especially became an issue with labels and associated text in widgets (e.g., buttons). The width of a widget would depend, for example, on the number of characters in the label - so how could I guarantee that widgets would be approximately the same size (along with corresponding text)? I've spent a lot of effort trying to get my text screens "looking right." An international approach would require a completely different and more graphics-oriented programming approach (and I'm sure, a far more technical one than I'm capable of). These are just *some* of my thoughts on the issue; I've a number of others. (Incidentally, in several of my activities, I've even included a supplementary .txt file with *further* explanations. It would certainly be feasible to translate these files *in toto* to different languages, and simply include them in the distribution. OTOH, the .txt files *supplement* rather than replace the on-screen materials.) I'm well aware that my "single-language-only" approach is probably unique to the world of Sugar; I would have liked to envisage a practical, feasible alternative that might "reach more children." I'd also appreciate feedback from developers, users, whomever who have looked at the activities (such as SamplePlay or FileMix). To date, I've received very little - no doubt at least partly because the activities are rather complex and clearly directed at older children. Art Hunkins - Original Message - From: Chris Leonard To: Art Hunkins Cc: sugar-devel@lists.sugarlabs.org Sent: Monday, October 10, 2011 10:43 PM Subject: Re: [Sugar-devel] SamplePlay-2.xo in Sandbox Art, Would you please consider setting up the internationaliization to make it possible to translate this activity? http://en.flossmanuals.net/make-your-own-sugar-activities/going-international-with-pootle/ cjl On Mon, Oct 10, 2011 at 9:33 PM, Art Hunkins wrote: I hate to bother someone again to reclaim my new version of SamplePlay from the sandbox. It's been there for 5 or more days. Anything I should be doing to ring my bell louder? Or should I just wait quietly? Thanks to whomever - Art Hunkins ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] SamplePlay-2.xo in Sandbox
I hate to bother someone again to reclaim my new version of SamplePlay from the sandbox. It's been there for 5 or more days. Anything I should be doing to ring my bell louder? Or should I just wait quietly? Thanks to whomever - Art Hunkins ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Sugar on a Stick v5 Coconut release
- Original Message - From: "Peter Robinson" To: ; "Development of live Sugar distributions" ; "Sugar Labs Marketing" Sent: Sunday, October 09, 2011 3:51 PM Subject: Re: [Sugar-devel] Sugar on a Stick v5 Coconut release Browse was also substituted for Surf due to API changes with xulrunner Did you mean the opposite? Art Hunkins Peter ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] FileMixAuto-5.xo in Sandbox
Could a reviewer please retrieve FileMixAuto-5.xo from the sandbox so it can become available? It has been languishing there for several weeks now. I'd really appreciate it. Art Hunkins ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] gtk.button initial state on?
James,
I can't seem to get you very clear suggestions working here. While I'm
having a difficult time getting the gray and green to show at the right
times, the most important problem is that switching the self.buttons.append
call from 0 to 1 doesn't effectively change the initial state.
I'd be much obliged if you could make me a proper gtk.ToggleButton method as
a substitute. Initial state: on, color: green. Toggle to off, color: gray.
Here's the "original" code below for your ready reference. (I presume the
buttcallback method might remain as is?)
def buttcallback(self, widget, data=None):
for i in self.buttons:
if i[0] == widget:
if i[2]:
i[2] = 0
i[0].modify_bg(gtk.STATE_NORMAL,
gtk.gdk.Color(0x8000,0x8000,0x8000, 1))
i[0].modify_bg(gtk.STATE_PRELIGHT,
gtk.gdk.Color(0x8000,0x8000,0x8000, 2))
else:
i[2] = 1
i[0].modify_bg(gtk.STATE_NORMAL, gtk.gdk.Color(0,0x7700,0, 1))
i[0].modify_bg(gtk.STATE_PRELIGHT, gtk.gdk.Color(0,0x7700,0, 2))
self.set_channel(i[1], i[2])
def button(self,box, title="",label=""):
"""Creates a button (on/off)
box: parent box
title: if given, the button name,
which will also be the bus channel
name. Otherwise a default name is
given, BN, where N is button number
in order of creation.
label: if given, an alternative button name,
which will be displayed instead of title
returns the widget instance"""
self.butts = self.butts + 1
if title == "":
title = "B%d" % self.butts
if label == "": name = title
else: name = label
butt = gtk.Button(" %s " % name)
self.scale_font(butt.child)
butt.modify_bg(gtk.STATE_PRELIGHT,
gtk.gdk.Color(0x8000,0x8000,0x8000, 2))
box.pack_start(butt, False, False, 1)
self.buttons.append([butt,title,0])
butt.connect("clicked", self.buttcallback)
butt.show()
return butt
Art Hunkins
- Original Message -
From: "James Cameron"
To:
Sent: Friday, August 26, 2011 8:11 PM
Subject: Re: [Sugar-devel] gtk.button initial state on?
On Tue, Aug 23, 2011 at 03:00:10PM -0400, Art Hunkins wrote:
In my latest activity (SamplePlay), I've several normal buttons for
which I'd like the initial state to be *on*.
The code is creating a gtk.Button (which has no persistent state) and
then modifying the button background to indicate some sort of internal
persistent state.
(It should instead create a gtk.ToggleButton and use the set_active() and
get_active() methods; it would be much easier to comprehend and change.
But this code is written in a hurry using only the tools known to the
programmer.)
Can someone show me how to modify the code below to achieve this? (The
off state is gray; the on state, green.)
Sure. It is the butt.modify_bg call when the button is created that is
responsible for showing the gray. It is the 0 in self.buttons.append
that is responsible for setting the initial state off.
(The programmer has taken control of how to show the button state).
So you might change the butt.modify_bg call, and the self.buttons.append
call. Change the butt.modify_bg call by adopting the colour green, in
the same way as you can see in buttcallback. Change the
self.buttons.append call by switching from 0 to 1 in the last list
value.
--
James Cameron
http://quozl.linux.org.au/
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Simplification help request
In my current activity (SamplePlay), I've got 26 buttons that allow a user
to select (from the Journal) up to 26 audio samples/loops to play. AFAIK,
the "filename" must be sent to Csound as a discrete variable, on its own
channel (see below).
As a result, I've 26 iterations(!) (0-25) of the same basic code. I'd like
to simplify it if possible (the code itself works fine). Any suggestions are
very much welcomed.
self.path0 = "0"
.
self.path25 = "0"
self.jobject0 = None
.
self.jobject25 = None
def choose0(self, widget):
chooser = ObjectChooser(parent=self, what_filter=mime.GENERIC_TYPE_AUDIO)
result = chooser.run()
if result == gtk.RESPONSE_ACCEPT:
self.jobject0 = chooser.get_selected_object()
self.path0 = str(self.jobject0.get_file_path())
else:
self.jobject0 = None
self.path0 = "0"
.
def choose25(self, widget):
chooser = ObjectChooser(parent=self, what_filter=mime.GENERIC_TYPE_AUDIO)
result = chooser.run()
if result == gtk.RESPONSE_ACCEPT:
self.jobject25 = chooser.get_selected_object()
self.path25 = str(self.jobject25.get_file_path())
else:
self.jobject25 = None
self.path25 = "0"
def send_data(self):
self.w.set_filechannel("file0", self.path0)
self.w.set_filechannel("file1", self.path1)
.
self.w.set_filechannel("file24", self.path24)
self.w.set_filechannel("file25", self.path25)
Hoping (as a Python novice) to be shown a better way -
Art Hunkins
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] gtk.button initial state on?
In my latest activity (SamplePlay), I've several normal buttons for which
I'd like the initial state to be *on*. Can someone show me how to modify the
code below to achieve this? (The off state is gray; the on state, green.)
The code works fine except for the initial state (by default, off). (The
code is from Victor Lazzarini's csndsugui.py, a gtk gui toolkit for
Sugar/Csound.)
def buttcallback(self, widget, data=None):
for i in self.buttons:
if i[0] == widget:
if i[2]:
i[2] = 0
i[0].modify_bg(gtk.STATE_NORMAL,
gtk.gdk.Color(0x8000,0x8000,0x8000, 2))
i[0].modify_bg(gtk.STATE_PRELIGHT,
gtk.gdk.Color(0x8000,0x8000,0x8000, 2))
else:
i[2] = 1
i[0].modify_bg(gtk.STATE_NORMAL, gtk.gdk.Color(0,0x7700,0, 1))
i[0].modify_bg(gtk.STATE_PRELIGHT, gtk.gdk.Color(0,0x7700,0, 2))
self.set_channel(i[1], i[2])
def button(self,box, title="",label=""):
"""Creates a button (on/off)
box: parent box
title: if given, the button name,
which will also be the bus channel
name. Otherwise a default name is
given, BN, where N is button number
in order of creation.
label: if given, an alternative button name,
which will be displayed instead of title
returns the widget instance"""
self.butts = self.butts + 1
if title == "":
title = "B%d" % self.butts
if label == "": name = title
else: name = label
butt = gtk.Button(" %s " % name)
self.scale_font(butt.child)
butt.modify_bg(gtk.STATE_PRELIGHT,
gtk.gdk.Color(0x8000,0x8000,0x8000, 2))
box.pack_start(butt, False, False, 1)
self.buttons.append([butt,title,0])
butt.connect("clicked", self.buttcallback)
butt.show()
return butt
Art Hunkins
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] ASCII keypresses
James,
Thanks so much for this response; it solved my keypress problem
magnificently - especially the autorepeat issue.
One problem remained, for my Csound program: a *bonafide repeat keypress*
could not be recognized. So I modified the python code to send along an
ASCII "0" when a key is released; this tells Csound that the following
"repeat" is a bonafide keypress. Here is my final code:
def onKeyPress(self, widget, event):
if self.p:
keyval = event.keyval
if keyval in self.kp:
return True
self.kp.append(keyval)
self.w.set_channel("ascii", keyval)
return True
def onKeyRelease(self, widget, event):
self.kp.remove(event.keyval)
self.w.set_channel("ascii", 0)
return True
def playcsd(self, widget):
.
self.connect("key-press-event", self.onKeyPress)
self.connect("key-release-event", self.onKeyRelease)
Again, many thanks for your help. I'm really happy with the way this turned
out.
Art Hunkins
- Original Message -
From: "James Cameron"
To: "Art Hunkins"
Cc:
Sent: Monday, August 15, 2011 10:41 PM
Subject: Re: [Sugar-devel] ASCII keypresses
Perhaps your question is "How do I defeat autorepeat?"
When a key is pressed down, you will get a key-press-event for it.
When a key is released, you will get a key-release-event for it.
If a key is pressed, held down, and then released, you will get an
initial key-press-event, then a key-press-event for each autorepeat,
followed by the key-release-event.
It is up to your program to process this stream.
I don't know offhand how to defeat autorepeat for a widget, the GTK+
documentation hasn't been any help on this question.
But here's one potential method; remember that is a key is down, and if
it is, ignore the new event. Here is code using a list.
def __init__(self, ...):
self.kp = [] # keys pressed
def onKeyPress(self, widget, event):
keyval = event.keyval
if keyval in self.kp:
return True # this is an autorepeat key press event
self.kp.append(keyval)
if self.p:
self.w.set_channel("ascii", keyval)
return True
def onKeyRelease(self, widget, event):
self.kp.remove(event.keyval)
return True
def playcsd(...):
...
self.connect("key-press-event", self.onKeyPress)
self.connect("key-release-event", self.onKeyRelease)
As you can see, storing the status of all keys that are down is quite
easy.
--
James Cameron
http://quozl.linux.org.au/
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] ASCII keypresses
To clarify:
an "a" keypress needs to be sent for a single cycle, then nothing further
until another key - or another "a" - is pressed.
It's not clear to me that the second "a" would be sent, without somehow
checking that the first one had been released.
And then, of course, a different key could be pressed before the first one
was released. This could require the status of a good number of keys (all of
them?) to be stored and tested.
Ugh.
Art Hunkins
- Original Message -----
From: "James Cameron"
To: "Art Hunkins"
Cc:
Sent: Monday, August 15, 2011 6:44 PM
Subject: Re: [Sugar-devel] ASCII keypresses
On Mon, Aug 15, 2011 at 06:23:07PM -0400, Art Hunkins wrote:
In a new activity I'm working on, I'm catching (and passing on)
ASCII keypresses with the following Python snippet:
def onKeyPress(self, widget, event):
if self.p:
self.w.set_channel("ascii", event.keyval)
def playcsd(self, widget):
if self.p == False:
self.p = True
self.w.play()
self.but.child.set_label("STOP !")
self.connect("key-press-event", self.onKeyPress)
Basically the code works; I need, however, for the keypress to be
passed on *for a single cycle only*, and for the routine also to
accommodate repeat keypresses.
For a single cycle only, assuming by cycle you mean a key press cycle,
you might disconnect the signal that you connected in playcsd. This
will prevent further key press events from being propagated to your
onKeyPress function.
But then you wouldn't catch repeat key press events. So I'm just
utterly confused as to what you are looking for.
http://dev.laptop.org/git/projects/olpcquotes/commit/?id=4bd778fd9f5d05355de47331dff6d3a89b90bded
suggests you should return either True or False from the onKeyPress
function. The default in PyGTK is False, which means the key press
event will be propagated further. So the widget with focus will also
get the event. This might not be what you want, but as I don't really
understand what you want I'm not sure if it matches your problem.
You might capture also key-release-event ... for interest. ;-)
--
James Cameron
http://quozl.linux.org.au/
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] ASCII keypresses
In a new activity I'm working on, I'm catching (and passing on) ASCII
keypresses with the following Python snippet:
def onKeyPress(self, widget, event):
if self.p:
self.w.set_channel("ascii", event.keyval)
def playcsd(self, widget):
if self.p == False:
self.p = True
self.w.play()
self.but.child.set_label("STOP !")
self.connect("key-press-event", self.onKeyPress)
Basically the code works; I need, however, for the keypress to be passed on
*for a single cycle only*, and for the routine also to accommodate repeat
keypresses.
Thanks for some help with this.
Art Hunkins
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Record-93 and recent Fedora nightly builds of SoaS
Where is the last F-15 available? The link to Fedora-15-i686-Live-SoaS.iso is broken, from the Sugar downloads page. Is this perchance the same as SoaSv5-20110612-i686.iso? Art Hunkins - Original Message - From: Peter Robinson To: Art Hunkins Cc: sugar-devel@lists.sugarlabs.org Sent: Thursday, July 28, 2011 3:57 AM Subject: Re: [Sugar-devel] Record-93 and recent Fedora nightly builds of SoaS I suggest you stick with the last F-15 build for the time being. F-16 which the nightlys are based on is still in a lot of churn. Peter On Wed, Jul 27, 2011 at 3:43 PM, Art Hunkins wrote: The dbus errors shown in the Record-93 logs are now clearly related to the jabber server issue, and to activities not starting the first, and sometimes second, time they are launched. The inability of recent versions of Record to playback (and/or record?) may thus be related to the following log entries (these are the only ones that seem further to indicate anything amiss): /usr/lib/python2.7/site-packages/sugar/graphics/palette.py:211: Warning: g_object_set_qdata: assertion `G_IS_OBJECT (object)' failed if menu_item.props.submenu is not None: /usr/share/sugar/activities/Record.activity/gplay.py:80: Warning: g_object_set_qdata: assertion `G_IS_OBJECT (object)' failed if not self._player.props.video_sink: (Could this record?/playback problem have anything to do with an incompatible version of Python?) Art Hunkins ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Record-93 and recent Fedora nightly builds of SoaS
The dbus errors shown in the Record-93 logs are now clearly related to the jabber server issue, and to activities not starting the first, and sometimes second, time they are launched. The inability of recent versions of Record to playback (and/or record?) may thus be related to the following log entries (these are the only ones that seem further to indicate anything amiss): /usr/lib/python2.7/site-packages/sugar/graphics/palette.py:211: Warning: g_object_set_qdata: assertion `G_IS_OBJECT (object)' failed if menu_item.props.submenu is not None: /usr/share/sugar/activities/Record.activity/gplay.py:80: Warning: g_object_set_qdata: assertion `G_IS_OBJECT (object)' failed if not self._player.props.video_sink: (Could this record?/playback problem have anything to do with an incompatible version of Python?) Art Hunkins ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] f15 Soas Remix with updates testing 07/27/2011
I can corroborate Tom's finding that entering in Terminal: sugar-control-panel -s jabber "" in recent Fedora nightly updates to SoaS eliminates: 1) dbus errors; 2) thus, all initial "fails to start" for activities; 3) and the long delay in booting Sugar. Also, the jabber "fix" persists (on future boots) and is only necessary to do once. Hopefully a real cure to the jabber issue will be available soon. Art Hunkins - Original Message - From: "Thomas C Gilliard" To: "SoaS" Cc: "Sugar Devel" Sent: Wednesday, July 27, 2011 9:15 AM Subject: [Sugar-devel] f15 Soas Remix with updates testing 07/27/2011 f15 Soas Remix with updates testing 07/27/2011 http://wiki.sugarlabs.org/go/Community/Distributions/Fedora-SoaS#f15-soas-Remix-727 Tom Gilliard satellit ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [ASLO] Release Record-93
FWIW, with regard to audio recording, this release: 1) works fine on the XO-1.0 upgraded to Sugar 0.92; 2) works with occasional stutter on the XO-1.5 upgraded to Sugar 0.92; 3) doesn't (record?)/playback on SoaS latest Fedora nightly build. Reports a debus timeout error. (Seems to record and save, but otherwise apparently "normal" playback is silent.) Art Hunkins - Original Message - From: "Sugar Labs Activities" To: Sent: Friday, July 22, 2011 6:50 PM Subject: [Sugar-devel] [ASLO] Release Record-93 Activity Homepage: http://activities.sugarlabs.org/addon/4081 Sugar Platform: 0.92 - 0.92 Download Now: http://activities.sugarlabs.org/downloads/file/27481/record-93.xo Release notes: Sugar Labs Activities http://activities.sugarlabs.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Fw: [Csnd] Default Scons build and backward compatibility (Csound/Fedora15)
I too can verify that without ethernet connection there are no
activities-not-starting issues at all. Indeed, just about everything seems a
bit snappier.
Now if the latest (audio) Records only worked with Fedora15. (For me, the
activity seems to record, but plays back a silent file. Then, too, it seems
confused as to whether the format is Ogg Speex or Ogg Vorbis.)
Art Hunkins
- Original Message -
From: Peter Robinson
To: Art Hunkins
Cc: sugar-devel@lists.sugarlabs.org
Sent: Wednesday, June 15, 2011 4:05 PM
Subject: Re: Fw: [Csnd] Default Scons build and backward compatibility
(Csound/Fedora15)
Hey Art,
AWESOME on the csound.
On the Activities I've encountered similar results.
Cheers,
Peter
On Wed, Jun 15, 2011 at 8:56 PM, Art Hunkins wrote:
Peter -
Great news - your new Csound modules work *perfectly*.
FWIW, "perfectly" includes not only the crucial "old-parser" default, but
also MIDI and multiple-controller MIDI. (I hadn't suspected problems with these
latter two items, but thought I'd mention them anyway.)
In any case, my Csound-based activities run fine now without modification,
and the new Fedora 15 SoaS release will be backwardly compatible as far as
Csound (and Csound-python) is concerned.
BTW, I've a little hint about the "activities not opening" phenomenon.
Though often (usually?) they do not open the first time they are selected, if
they are selected *again* immediately, they always do open. (Or so it seems.)
Thanks again for all your help and forbearance with Csound.
Art Hunkins
- Original Message -
From: Peter Robinson
To: Art Hunkins
Sent: Wednesday, June 15, 2011 3:09 AM
Subject: Re: Fw: [Csnd] Default Scons build and backward compatibility
easiest will be
"rpm -Uvh
http://kojipkgs.fedoraproject.org/packages/csound/5.13.0/5.fc15/i686/csound-5.13.0-5.fc15.i686.rpm
http://kojipkgs.fedoraproject.org/packages/csound/5.13.0/5.fc15/i686/csound-python-5.13.0-5.fc15.i686.rpm";
Peter
On Wed, Jun 15, 2011 at 4:51 AM, Art Hunkins wrote:
Thanks, Peter.
I'll try this out tomorrow.
Do I upgrade simply with:
yum upgrade csound
?
Art Hunkins
- Original Message -h
From: Peter Robinson
To: Art Hunkins
Sent: Tuesday, June 14, 2011 7:06 PM
Subject: Re: Fw: [Csnd] Default Scons build and backward compatibility
https://admin.fedoraproject.org/updates/csound-5.13.0-5.fc15
On Tue, Jun 14, 2011 at 10:42 PM, Peter Robinson
wrote:
Hmm. We'll see how we get on. Build csound-5.13.0-5.fc15 will have
the change in it. It will be submitted as an update shortly.
Peter
On Tue, Jun 14, 2011 at 9:52 PM, Art Hunkins
wrote:
Peter,
FYI (another response). Felipe is the Debian maintainer for
Csound. He's quite active and knowledgeable about Csound (and has followed it
over a period of time), FWIW.
bmity
Art Hunkins
- Original Message - From: "Felipe Sateler"
To:
Sent: Tuesday, June 14, 2011 4:32 PM
Subject: Re: [Csnd] Default Scons build and backward compatibility
I agree with most of your comments but...
On Tue, Jun 14, 2011 at 13:02, Art Hunkins
wrote:
Everyone knows I'm a Windows person, and normally wouldn't be
affected
by such largely "Linux issues." However, I am involved with the
Fedora-based
Sugar-on-a-Stick project. A new release is about to come out,
and Csound has
been built with default Scons options, resulting in its being
incompatible
with the Activities I've written, as well as with all previous
Sugar-on-a-Stick releases. This is "a problem that shouldn't
be".
This is really a problem that shouldn't be, but not for the
reasons
you argue. The csound maintainer in fedora should be specifying
all
the features he wants and disabling all that he doesn't. Leaving
the
build script to do whatever it feels like is wrong.
At the very least, the default Scons script should indicate
clearly the
meaning of each option, and *in giant red letters/flags* (or
the equivalent)
indicate experimental and untested features. Then by all means,
make a safe
and compatible default build.
Am I way off base? Please let me know what I'm missing.
This is my opinion only, but relying on defaults is the wrong way
to
Re: [Sugar-devel] Fw: [Csnd] Default Scons build and backward compatibility (Csound/Fedora15)
Peter -
Great news - your new Csound modules work *perfectly*.
FWIW, "perfectly" includes not only the crucial "old-parser" default, but also
MIDI and multiple-controller MIDI. (I hadn't suspected problems with these
latter two items, but thought I'd mention them anyway.)
In any case, my Csound-based activities run fine now without modification, and
the new Fedora 15 SoaS release will be backwardly compatible as far as Csound
(and Csound-python) is concerned.
BTW, I've a little hint about the "activities not opening" phenomenon. Though
often (usually?) they do not open the first time they are selected, if they are
selected *again* immediately, they always do open. (Or so it seems.)
Thanks again for all your help and forbearance with Csound.
Art Hunkins
- Original Message -----
From: Peter Robinson
To: Art Hunkins
Sent: Wednesday, June 15, 2011 3:09 AM
Subject: Re: Fw: [Csnd] Default Scons build and backward compatibility
easiest will be
"rpm -Uvh
http://kojipkgs.fedoraproject.org/packages/csound/5.13.0/5.fc15/i686/csound-5.13.0-5.fc15.i686.rpm
http://kojipkgs.fedoraproject.org/packages/csound/5.13.0/5.fc15/i686/csound-python-5.13.0-5.fc15.i686.rpm";
Peter
On Wed, Jun 15, 2011 at 4:51 AM, Art Hunkins wrote:
Thanks, Peter.
I'll try this out tomorrow.
Do I upgrade simply with:
yum upgrade csound
?
Art Hunkins
- Original Message -h
From: Peter Robinson
To: Art Hunkins
Sent: Tuesday, June 14, 2011 7:06 PM
Subject: Re: Fw: [Csnd] Default Scons build and backward compatibility
https://admin.fedoraproject.org/updates/csound-5.13.0-5.fc15
On Tue, Jun 14, 2011 at 10:42 PM, Peter Robinson
wrote:
Hmm. We'll see how we get on. Build csound-5.13.0-5.fc15 will have the
change in it. It will be submitted as an update shortly.
Peter
On Tue, Jun 14, 2011 at 9:52 PM, Art Hunkins wrote:
Peter,
FYI (another response). Felipe is the Debian maintainer for Csound.
He's quite active and knowledgeable about Csound (and has followed it over a
period of time), FWIW.
bmity
Art Hunkins
- Original Message - From: "Felipe Sateler"
To:
Sent: Tuesday, June 14, 2011 4:32 PM
Subject: Re: [Csnd] Default Scons build and backward compatibility
I agree with most of your comments but...
On Tue, Jun 14, 2011 at 13:02, Art Hunkins wrote:
Everyone knows I'm a Windows person, and normally wouldn't be
affected
by such largely "Linux issues." However, I am involved with the
Fedora-based
Sugar-on-a-Stick project. A new release is about to come out, and
Csound has
been built with default Scons options, resulting in its being
incompatible
with the Activities I've written, as well as with all previous
Sugar-on-a-Stick releases. This is "a problem that shouldn't be".
This is really a problem that shouldn't be, but not for the reasons
you argue. The csound maintainer in fedora should be specifying all
the features he wants and disabling all that he doesn't. Leaving the
build script to do whatever it feels like is wrong.
At the very least, the default Scons script should indicate clearly
the
meaning of each option, and *in giant red letters/flags* (or the
equivalent)
indicate experimental and untested features. Then by all means,
make a safe
and compatible default build.
Am I way off base? Please let me know what I'm missing.
This is my opinion only, but relying on defaults is the wrong way to
build software.
--
Saludos,
Felipe Sateler
Send bugs reports to the Sourceforge bug tracker
https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sy...@lists.bath.ac.uk with body
"unsubscribe csound"
=
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Fedora 15 SoaS release and Csound5
Peter,
My feelings exactly.
As regards Csound, most of our listservs are users; developers are relatively
few and tend to communicate largely among themselves.
Though I also am a member of csound-dev, I was unaware of the old/new parser
status. I knew the new parser was (and has been long) "under development". I'd
no idea how or if it was incorporated into Csound5.13.
Only a few folk (not including myself) actually build Csound - mostly Linux
people (again, not me). I just installed Windows Csound(5.13) this evening for
the first time - to discover that it was built with default old parser. News to
me.
There's much discussion of Csound lists about how documentation and user
materials are subpar - especially for newbees. This makes it overly difficult
for Csound to attract new users.
At any rate, thanks again for all you do. And I'm always here to test.
Art Hunkins
- Original Message -
From: Peter Robinson
To: Art Hunkins
Cc: sugar-devel@lists.sugarlabs.org ; Development of live Sugar distributions
Sent: Monday, June 13, 2011 7:13 PM
Subject: Re: Fedora 15 SoaS release and Csound5
Art,
It seems I did get the mail but some how missed it.
Sigh! How so typical of CSound to make the new parser the default even though
they themselves don't recommend it, nor do they really even document it
anywhere! GRR!
I'll have a look at the build and see what else it will affect, csound isn't
just there for Sugar.
Peter
On Mon, Jun 13, 2011 at 11:05 PM, Art Hunkins wrote:
Peter -
Did you ever receive the messages collated below? (They largely occurred on
the csound-dev list.)
Are the questions you mentioned (ones that were never answered) the ones
addressed here?
If not, please send them again. To my knowledge, the simple "Csound
solution" is running scons with the option:
buildRelease=1
But maybe I completely misunderstand.
Art Hunkins
- Original Message - From: "Art Hunkins"
To:
Sent: Wednesday, June 08, 2011 9:59 AM
Subject: Re: Fedora 15 SoaS release and Csound5
Peter:
I presume you received the messages immediately listed below, regarding a
solution to the old/new Csound parser issue ("build csound with the scons
option buildRelease=1").
If you sent questions either to this group, or the Csound-developers
list, I'm sorry; I didn't receive them. Are they perhaps answered in the
messages quoted below?
Also, as I wrote to you a week or so ago, there are no current MIDI
issues with Csound and Sugar. (I had mistakenly thought there were earlier.)
I remain eager to test a rebuilt Csound in the Fedora 15 SoaS context, to
determine if my activities are compatible - and look forward to your upcoming
test release.
Thanks again for all your work on behalf of things musical within SoaS.
Art Hunkins
---
(Message to csound development listserv)
Steve, Victor and Peter Robinson:
The run-time (CsOptions) flag --old-parser makes my CSD's run flawlessly.
(Thanks for the suggestion/solution, Steve.)
I don't imagine my CSD's are the only ones affected.
Peter, I'd strongly recommend Victor's suggestion of incorporating the
scons option buildRelease=1 into the Csound build for Fedora 15. (For one
thing, it would for the time being not require changes to my Activities.)
Comments anyone?
Art Hunkins
From: Victor Lazzarini
To: Developer discussions
Sent: Wednesday, June 01, 2011 4:42 PM
Subject: Re: [Cs-dev] Fw: Csound - CsOptions flag for old parser?
That is a run-time option. But if you build csound with the scons
option buildRelease=1, the old parser
should be the default. This is the recommended (new parser is no ready
for big time yet).
Victor
On 1 Jun 2011, at 21:30, Peter Robinson wrote:
Hi Steve,
Is that a compile or run time option? If the former what are the
implications?
Peter
On 1 Jun 2011 21:18, "Steven Yi" wrote:
Dr Victor Lazzarini
Senior Lecturer
Dept. of Music
NUI Maynooth Ireland
tel.: +353 1 708 3545
Victor dot Lazzarini AT nuim dot ie
- Original Message - From: "Peter Robinson"
To: "Art Hunkins"
Sent: Wednesday, June 08, 2011 4:48 AM
Subject: Re: Fedora 15 SoaS release and Csound5
Hi Art,
No idea. I replied to the email you CC:ed me on and had no answers to
my questions. I have a couple of outstanding items I need to test and
fix on SoaS and will put out a test image in the next couple of days
and you can test it and tell me as you well no I have no ability to
test midi on soas.
As a side note please make
Re: [Sugar-devel] Fedora 15 SoaS release and Csound5
Peter -
Did you ever receive the messages collated below? (They largely occurred on
the csound-dev list.)
Are the questions you mentioned (ones that were never answered) the ones
addressed here?
If not, please send them again. To my knowledge, the simple "Csound
solution" is running scons with the option:
buildRelease=1
But maybe I completely misunderstand.
Art Hunkins
- Original Message -
From: "Art Hunkins"
To:
Sent: Wednesday, June 08, 2011 9:59 AM
Subject: Re: Fedora 15 SoaS release and Csound5
Peter:
I presume you received the messages immediately listed below, regarding a
solution to the old/new Csound parser issue ("build csound with the scons
option buildRelease=1").
If you sent questions either to this group, or the Csound-developers list,
I'm sorry; I didn't receive them. Are they perhaps answered in the
messages quoted below?
Also, as I wrote to you a week or so ago, there are no current MIDI issues
with Csound and Sugar. (I had mistakenly thought there were earlier.)
I remain eager to test a rebuilt Csound in the Fedora 15 SoaS context, to
determine if my activities are compatible - and look forward to your
upcoming test release.
Thanks again for all your work on behalf of things musical within SoaS.
Art Hunkins
---
(Message to csound development listserv)
Steve, Victor and Peter Robinson:
The run-time (CsOptions) flag --old-parser makes my CSD's run flawlessly.
(Thanks for the suggestion/solution, Steve.)
I don't imagine my CSD's are the only ones affected.
Peter, I'd strongly recommend Victor's suggestion of incorporating the
scons option buildRelease=1 into the Csound build for Fedora 15. (For one
thing, it would for the time being not require changes to my Activities.)
Comments anyone?
Art Hunkins
From: Victor Lazzarini
To: Developer discussions
Sent: Wednesday, June 01, 2011 4:42 PM
Subject: Re: [Cs-dev] Fw: Csound - CsOptions flag for old parser?
That is a run-time option. But if you build csound with the scons option
buildRelease=1, the old parser
should be the default. This is the recommended (new parser is no ready
for big time yet).
Victor
On 1 Jun 2011, at 21:30, Peter Robinson wrote:
Hi Steve,
Is that a compile or run time option? If the former what are the
implications?
Peter
On 1 Jun 2011 21:18, "Steven Yi" wrote:
Dr Victor Lazzarini
Senior Lecturer
Dept. of Music
NUI Maynooth Ireland
tel.: +353 1 708 3545
Victor dot Lazzarini AT nuim dot ie
- Original Message -
From: "Peter Robinson"
To: "Art Hunkins"
Sent: Wednesday, June 08, 2011 4:48 AM
Subject: Re: Fedora 15 SoaS release and Csound5
Hi Art,
No idea. I replied to the email you CC:ed me on and had no answers to
my questions. I have a couple of outstanding items I need to test and
fix on SoaS and will put out a test image in the next couple of days
and you can test it and tell me as you well no I have no ability to
test midi on soas.
As a side note please make sure you:
1) Create a new email when sending things and no hijack a completely
irrelevant email.
2) Send it to the SoaS list. There is no need to send this directly to
me.
Regards,
Peter
On Tue, Jun 7, 2011 at 11:23 PM, Art Hunkins wrote:
Hello, Peter,
Is the Csound5 new/old parser issue now solved for the upcoming Fedora
15
SoaS release?
If so, is there a testing .iso I could try - to see if my activities are
compatible with it?
Thanks -
Art Hunkins
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] new SoaSv5 test image - Last change to test andfix issues
Thanks for the new SoaS5 test. Here is my experience:
1) No more keyrings (cheers) - for me anyway.
2) No GDM login (cheers) - again, for me anyway.
3) Main issue #1: Csound "still" uses the new cursor. (I gather Csound remains
to be rebuilt with (scons option) buildRelease=1. At least, that's what Victor
Lazzarini says.) Otherwise I'll need to add the --old-parser flag to all my (6)
activities - which I'd prefer not to do uniquely for this release. I'd
certainly hope this can be adjusted before SoaS5 release.
4) Main issue #2: activities only start 50% of the time. This is true for *all*
activities. It's not clear why an activity will start one time and not another
(it prints "didn't start" message). With Mango Lassi, this happens
occasionally/rarely for me; here it happens *a lot*.
I thought maybe this had something to do with the USB drives I'd made with
LiveUSB Creator. It doesn't. I created two: one 2GB, one 4GB with all memory
protected.
5) Noted difference in Journal: hovering over an entry does nothing; a
right-click on an entry does nothing. Only a left-click resumes the activity -
normally the one it originated in (see 5 below). Apparently you cannot erase
from the Journal (except by clicking on the rightmost arrow, to another page),
nor resume in a different activity any more. I appreciated those features.
6) Record (audio) continues to cause me problems. Record apparently records
correctly (or does it?) but does not play back. When a recording is "resumed"
from the Journal, it resumes (not in Record) but in either Surf or Etoys,
depending on whether it was saved automatically from Record, or as a clipping
that was kept. In any case, no activity plays the "recorded" file. Go figure.
(One possibility: Record seems to be interchanging Ogg Vorbis and Ogg Speex
formats - ugh.) FWIW, here's the complete Record log (seems to involve the Dbus
and an elapsed timeout):
** Message: pygobject_register_sinkfunc is deprecated (GstObject)
** Message: pygobject_register_sinkfunc is deprecated (HippoCanvasBox)
Traceback (most recent call last):
File "/usr/bin/sugar-activity", line 21, in
main.main()
File "/usr/lib/python2.7/site-packages/sugar/activity/main.py", line 158, in
main
create_activity_instance(activity_constructor, activity_handle)
File "/usr/lib/python2.7/site-packages/sugar/activity/main.py", line 37, in
create_activity_instance
activity = constructor(handle)
File "/usr/share/sugar/activities/Record.activity/record.py", line 66, in
__init__
super(Record, self).__init__(handle)
File "/usr/lib/python2.7/site-packages/sugar/activity/activity.py", line 328,
in __init__
warn_if_none=False)
File "/usr/lib/python2.7/site-packages/sugar/presence/presenceservice.py",
line 89, in get_activity
dbus_interface=CONN_INTERFACE_ACTIVITY_PROPERTIES)
File "/usr/lib/python2.7/site-packages/dbus/proxies.py", line 68, in __call__
return self._proxy_method(*args, **keywords)
File "/usr/lib/python2.7/site-packages/dbus/proxies.py", line 140, in __call__
**keywords)
File "/usr/lib/python2.7/site-packages/dbus/connection.py", line 630, in
call_blocking
message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Message did
not receive a reply (timeout by message bus)
Exited with status 1, pid 1841 data (None, ', mode 'w' at
0xdf70e38>, dbus.ByteArray('1e429af21558998191b528d4c9c3b5572f388430',
variant_level=1))
Art Hunkins
- Original Message -
From: Peter Robinson
To: sugar-devel@lists.sugarlabs.org ; Development of live Sugar distributions
Sent: Monday, June 13, 2011 5:30 AM
Subject: Re: [Sugar-devel] new SoaSv5 test image - Last change to test andfix
issues
On Sun, Jun 12, 2011 at 8:49 PM, Peter Robinson wrote:
Hi All,
I was hoping to have this out over a week ago but I had a slight diversion
via hospital which delayed proceedings.
So below are links to a new pair (32 and 64 bit) of images for your testing
pleasure.
http://fedora.roving-it.com/SoaSv5-20110612-x86_64.iso
http://fedora.roving-it.com/SoaSv5-20110612-i686.iso
The network issue is still there, its partially working from the work that
I did with some assistance from John Dulaney. I've included another utility to
enable initial configuration of a wireless access point and from there it will
auto connect and should mostly work. There's issues with the main network view
and in the control panel but it seems no one else cares enough to assist me in
getting it fixed. To configure an AP run the command "nm-connection-editor"
from a terminal as the standard user (not root).
I don't believe there are any other major blockers for this release. If you
bel
Re: [Sugar-devel] Strawberry - login screen
That's the same SoaS I tried. Didn't happen for me. Art Hunkins - Original Message - From: Bert Freudenberg To: Development of live Sugar distributions Cc: sugar-devel Devel Sent: Monday, June 13, 2011 1:39 PM Subject: Re: [Sugar-devel] Strawberry - login screen On 13.06.2011, at 10:35, Peter Robinson wrote: On Mon, Jun 13, 2011 at 6:23 PM, Bert Freudenberg wrote: On 13.06.2011, at 06:50, Peter Robinson wrote: On Mon, Jun 13, 2011 at 2:38 PM, Esteban Arias wrote: hi! do you know why sugar on stick - SoaS release 1 (Strawberry), shows login when I change configuration from control panel ? for example, I change nike name in "About me"; then restart with login screen... I put "liveuser" and the system starts ok! It is possible to dont show login screen? You can change settings in the gdm.conf file It would be nice if SoaS would not show the GDM login screen at all, just like on the XO. This still happens in SoaS v5. Have you tested the new images I posted yesterday? It shouldn't on those. Yes, it happens in SoaSv5-20110612-i686.iso. Getting rid of it all together has pros and cons and I've not seen patches, or even suggestions for that matter, from anyone for the best way to address this issue to also allow multiple UX and users. and it needs a blank password. When doing a liveinst it does not accept a blank password. Doesn't stop you from removing it later. Doesn't stop me, true, but stops teachers and other "normal" users. - Bert - -- ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [SoaS] Strawberry - login screen
Indeed, the new images get rid of the GDM login screen - as well as all those *#$%@ keyring popups (cheers). Art Hunkins - Original Message - From: Peter Robinson To: Development of live Sugar distributions Cc: sugar-devel Sent: Monday, June 13, 2011 1:35 PM Subject: Re: [Sugar-devel] [SoaS] Strawberry - login screen On Mon, Jun 13, 2011 at 6:23 PM, Bert Freudenberg wrote: On 13.06.2011, at 06:50, Peter Robinson wrote: On Mon, Jun 13, 2011 at 2:38 PM, Esteban Arias wrote: hi! do you know why sugar on stick - SoaS release 1 (Strawberry), shows login when I change configuration from control panel ? for example, I change nike name in "About me"; then restart with login screen... I put "liveuser" and the system starts ok! It is possible to dont show login screen? You can change settings in the gdm.conf file It would be nice if SoaS would not show the GDM login screen at all, just like on the XO. This still happens in SoaS v5. Have you tested the new images I posted yesterday? It shouldn't on those. Getting rid of it all together has pros and cons and I've not seen patches, or even suggestions for that matter, from anyone for the best way to address this issue to also allow multiple UX and users. and it needs a blank password. When doing a liveinst it does not accept a blank password. Doesn't stop you from removing it later. Peter -- ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] new SoaSv5 test image - Last change to test and fixissues
Peter, I'm trying to test but have problems. I test with LiveUSB Creator, to create a SoaS USB drive. I note the iso is only 100+MB, so Linux must not be included? At any rate, at the SYSLINUX 4.04 screen, I get: No default or UI configuration directive found Boot: What do I type here? Linux0 doesn't work. Is there any way I can test with LiveUSB Creator? (All the Fedora 15 nightly composes were testable this way.) Art Hunkins - Original Message - From: Peter Robinson To: sugar-devel@lists.sugarlabs.org ; Development of live Sugar distributions Sent: Sunday, June 12, 2011 3:49 PM Subject: [Sugar-devel] new SoaSv5 test image - Last change to test and fixissues Hi All, I was hoping to have this out over a week ago but I had a slight diversion via hospital which delayed proceedings. So below are links to a new pair (32 and 64 bit) of images for your testing pleasure. http://fedora.roving-it.com/SoaSv5-20110612-x86_64.iso http://fedora.roving-it.com/SoaSv5-20110612-i686.iso The network issue is still there, its partially working from the work that I did with some assistance from John Dulaney. I've included another utility to enable initial configuration of a wireless access point and from there it will auto connect and should mostly work. There's issues with the main network view and in the control panel but it seems no one else cares enough to assist me in getting it fixed. To configure an AP run the command "nm-connection-editor" from a terminal as the standard user (not root). I don't believe there are any other major blockers for this release. If you believe there to be any issues speak up now and provide fixes for it. NOTE: This is the last chance to test and get things fixed. Please provide concise details to any issues in reply to this mail. Cheers, Peter -- ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Fedora 15 SoaS release and Csound5
Peter:
I presume you received the messages immediately listed below, regarding a
solution to the old/new Csound parser issue ("build csound with the scons
option buildRelease=1").
If you sent questions either to this group, or the Csound-developers list,
I'm sorry; I didn't receive them. Are they perhaps answered in the messages
quoted below?
Also, as I wrote to you a week or so ago, there are no current MIDI issues
with Csound and Sugar. (I had mistakenly thought there were earlier.)
I remain eager to test a rebuilt Csound in the Fedora 15 SoaS context, to
determine if my activities are compatible - and look forward to your
upcoming test release.
Thanks again for all your work on behalf of things musical within SoaS.
Art Hunkins
---
(Message to csound development listserv)
Steve, Victor and Peter Robinson:
The run-time (CsOptions) flag --old-parser makes my CSD's run flawlessly.
(Thanks for the suggestion/solution, Steve.)
I don't imagine my CSD's are the only ones affected.
Peter, I'd strongly recommend Victor's suggestion of incorporating the scons
option buildRelease=1 into the Csound build for Fedora 15. (For one thing,
it would for the time being not require changes to my Activities.)
Comments anyone?
Art Hunkins
From: Victor Lazzarini
To: Developer discussions
Sent: Wednesday, June 01, 2011 4:42 PM
Subject: Re: [Cs-dev] Fw: Csound - CsOptions flag for old parser?
That is a run-time option. But if you build csound with the scons option
buildRelease=1, the old parser
should be the default. This is the recommended (new parser is no ready for
big time yet).
Victor
On 1 Jun 2011, at 21:30, Peter Robinson wrote:
Hi Steve,
Is that a compile or run time option? If the former what are the
implications?
Peter
On 1 Jun 2011 21:18, "Steven Yi" wrote:
Dr Victor Lazzarini
Senior Lecturer
Dept. of Music
NUI Maynooth Ireland
tel.: +353 1 708 3545
Victor dot Lazzarini AT nuim dot ie
- Original Message -
From: "Peter Robinson"
To: "Art Hunkins"
Sent: Wednesday, June 08, 2011 4:48 AM
Subject: Re: Fedora 15 SoaS release and Csound5
Hi Art,
No idea. I replied to the email you CC:ed me on and had no answers to
my questions. I have a couple of outstanding items I need to test and
fix on SoaS and will put out a test image in the next couple of days
and you can test it and tell me as you well no I have no ability to
test midi on soas.
As a side note please make sure you:
1) Create a new email when sending things and no hijack a completely
irrelevant email.
2) Send it to the SoaS list. There is no need to send this directly to me.
Regards,
Peter
On Tue, Jun 7, 2011 at 11:23 PM, Art Hunkins wrote:
Hello, Peter,
Is the Csound5 new/old parser issue now solved for the upcoming Fedora 15
SoaS release?
If so, is there a testing .iso I could try - to see if my activities are
compatible with it?
Thanks -
Art Hunkins
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Record (audio) and latest Fedora 15 nightly builds (SoaS)
FWIW, Record v90 and 91 do not work with the latest Fedora 15 nightly builds. They "record and playback" silent ogg speex files. OTOH, with Mango Lassi, Record v90 and 91 work well and as expected. Following is the complete log of a Record v90 run with the June 2 nightly build, in case anything can be made from it: ** Message: pygobject_register_sinkfunc is deprecated (GstObject) ** Message: pygobject_register_sinkfunc is deprecated (HippoCanvasBox) 1307156370.557735 WARNING root: No gtk.AccelGroup in the top level window. 1307156370.561032 WARNING root: No gtk.AccelGroup in the top level window. /usr/lib/python2.7/site-packages/sugar/graphics/window.py:197: Warning: g_object_set_qdata: assertion `G_IS_OBJECT (object)' failed self.__vbox.pack_start(toolbar_box, False) ** (sugar-activity:1444): DEBUG: Got client ID "10c73beedf8b26b2a113071563706547130013390001" ** (sugar-activity:1444): DEBUG: Setting initial properties ** (sugar-activity:1444): DEBUG: Received SaveYourself(SmSaveLocal, !Shutdown, SmInteractStyleNone, !Fast) in state idle ** (sugar-activity:1444): DEBUG: Sending SaveYourselfDone(True) for initial SaveYourself ** (sugar-activity:1444): DEBUG: Received SaveComplete message in state save-yourself-done ** (sugar-activity:1444): CRITICAL **: file gstvorbistag.c: line 591 (gst_tag_to_vorbis_comments): should not be reached /usr/lib/python2.7/site-packages/sugar/graphics/palette.py:211: Warning: g_object_set_qdata: assertion `G_IS_OBJECT (object)' failed if menu_item.props.submenu is not None: /usr/share/sugar/activities/Record.activity/gplay.py:80: Warning: g_object_set_qdata: assertion `G_IS_OBJECT (object)' failed if not self._player.props.video_sink: 1307156452.836129 WARNING root: No gtk.AccelGroup in the top level window. /usr/lib/python2.7/site-packages/sugar/activity/namingalert.py:194: Warning: g_object_set_qdata: assertion `G_IS_OBJECT (object)' failed vbox.pack_start(toolbar, False) 1307156456.274288 WARNING root: No gtk.AccelGroup in the top level window. 1307156456.296265 WARNING root: No gtk.AccelGroup in the top level window. 1307156456.296552 WARNING root: No gtk.AccelGroup in the top level window. Exited with status 0, pid 1444 data (None, ', mode 'w' at 0xa470650>, 'af61e1e83f929fe2418956f54918670131584e6f') Art Hunkins ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] #2399 UNSP: Record 79 (and 86) issues - Sugar 0.84-0.88
Rafael -
Your reply suggests that most children working with SoaS will have upgraded
beyond Strawberry.
What is the case (particularly where high-speed internet connections are not
available)?
This is surely an important fact for developers to know.
Art Hunkins
- Original Message -
From: Rafael Ortiz
To: Art Hunkins
Cc: sugar-devel@lists.sugarlabs.org
Sent: Friday, June 03, 2011 8:50 PM
Subject: Re: [Sugar-devel] #2399 UNSP: Record 79 (and 86) issues - Sugar
0.84-0.88
Thanks for the precise information, this is also a problem of back
portability, as SOAS is a shorthanded project, I think that is preferred to
test activities on latest versions, I'm closing some of these bugs as obsolete
for that reason, but with an open window (re-open state) if there are people
that can work on fix them.
Cheers and thanks.
Art Hunkins
- Original Message - From: "Sugar Labs Bugs"
Cc:
Sent: Friday, June 03, 2011 12:33 PM
Subject: Re: #2399 UNSP: Record 79 (and 86) issues - Sugar 0.84-0.88
#2399: Record 79 (and 86) issues - Sugar 0.84-0.88
--+-
Reporter: abhunkin | Owner: dsd
Type: defect | Status: closed
Priority: Unspecified by Maintainer | Milestone: Unspecified by
Release Team
Component: Record |Version: 0.84.x
Severity: Major | Resolution: obsolete
Keywords: | Distribution: Fedora
Status_field: Unconfirmed|
--+-
Changes (by RafaelOrtiz):
* status: new => closed
* resolution: => obsolete
Comment:
I suggest re-testing with new versions (v91) of Record.
--
Ticket URL: <http://bugs.sugarlabs.org/ticket/2399#comment:4>
Sugar Labs <http://sugarlabs.org/>
Sugar Labs bug tracking system
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] #2399 UNSP: Record 79 (and 86) issues - Sugar 0.84-0.88
@ Rafael expecially: With respect to various versions of Sugar and Record, I currently supply the following information in my readme.txt files for my FileMix and FileMixAuto activities (these activities suggest using Record to create audio files for use with FileMix): The natural vehicle for soundfile creation is the Record activity. This activity is fairly simple and straightforward; the only problem is that many versions of it do not work with various incarnations of Sugar. The following pairings of Record with Sugar seem to work reliably: v64 with Sugar-on-a-Stick Strawberry (0.84 - works rather poorly); and v86 with XO-1.5, and XO-1 upgraded to Sugar 0.84. Sugar 0.86 (Blueberry) and above (as of 5/2011) are compatible with Record v90/91, including XO's upgraded to at least Sugar 0.90 (Mango lassi - Fedora 14). -- The above pairings are the *only* ones that are compatible and produce Ogg Vorbis (not Speex) files. The problem is largely with SoaS Strawberry. Record v86, 90 or 91 are inoperative there. (FWIW, neither Record 90 nor 91 seem to work with the 2 June current nightly Fedora SoaS build either.) This SoaS/audio Record compatibility issue is certainly a complicated one. For the moment, I rest my case, and only hope that eventually SoaS Strawberry will have a new Record that works well with it. Art Hunkins - Original Message - From: "Sugar Labs Bugs" Cc: Sent: Friday, June 03, 2011 12:33 PM Subject: Re: #2399 UNSP: Record 79 (and 86) issues - Sugar 0.84-0.88 #2399: Record 79 (and 86) issues - Sugar 0.84-0.88 --+- Reporter: abhunkin | Owner: dsd Type: defect | Status: closed Priority: Unspecified by Maintainer | Milestone: Unspecified by Release Team Component: Record |Version: 0.84.x Severity: Major | Resolution: obsolete Keywords: | Distribution: Fedora Status_field: Unconfirmed| --+- Changes (by RafaelOrtiz): * status: new => closed * resolution: => obsolete Comment: I suggest re-testing with new versions (v91) of Record. -- Ticket URL: <http://bugs.sugarlabs.org/ticket/2399#comment:4> Sugar Labs <http://sugarlabs.org/> Sugar Labs bug tracking system ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Csound MIDI with Mango Lassi (and later)
@ Peter: Please disregard my report that Csound MIDI was not working correctly in SoaS Mango Lassi or the latest nightly builds of Fedora 15. MIDI is working fine - my mistake. Art Hunkins ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] SunMoonMusic Activity does not open in Mango Lassi
@ Walter: Thanks for the info. In Mango Lassi, indeed, user-installed activities *cannot* be erased. I've filed a ticket: http://bugs.sugarlabs.org/ticket/2876 Strangely, the latest nightly Fedora 15 builds work correctly in this regard. Apparently, quite a bit of my problem was related to running out of protected memory on my USB sticks. Perhaps a warning should be posted somewhere that "more protected memory (or larger capacities) on SoaS sticks is better" - since SoaS/Fedora is getting larger, and now that pre-installed activities cannot be easily deleted. (I note, for the record, that most pre-installed activities *are* eraseable in Strawberry, all except Etoys on Blueberry, and some on Mirabelle. This option freed up space and allowed for greater user-customization - a desirable situation in *some* cases certainly.) Just curious: are different versions (i.e., Strawberry, Blueberry, Mirabelle, etc.) of SoaS tailored to specific deployments? If not, why are there such variations in installed activities and whether they are regarded as permanent or not? Art Hunkins - Original Message - From: Walter Bender To: Art Hunkins Cc: James Cameron ; sugar-devel@lists.sugarlabs.org Sent: Tuesday, May 31, 2011 12:13 PM Subject: Re: [Sugar-devel] SunMoonMusic Activity does not open in Mango Lassi The only activities where deleting is disabled are pre-installed ones. The ones you install should be able to be deleted. If not, this is a bug. Regarding the decision to make pre-installed activities permanent, it is driven by Sugar deployments: teachers requested that certain activities always be available. Which ones is a deployment x deployment decision. For SoaS, we have a very limited set of pre-installed activities, but as the Fedora image grows, the user-space shrinks. FWIW, from the Terminal Activity, you can delete the pre-loaded activities in /usr/share/sugar regards. -walter -- Walter Bender Sugar Labs http://www.sugarlabs.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] SunMoonMusic Activity does not open in Mango Lassi
James,
Thanks both for your well-expressed advice, as well as your continued
interest in my musical projects. I've recently had several "go's" at git -
and thanks to your help, did not experience heart failure (it went quite
well in fact).
I've discovered what was wrong, and so file your suggestions for my next set
of troubles.
I've been using primarily 1GB USB sticks, which (with Mango especially)
doesn't leave much extra room (I use the LiveUSB Creator, reserving the
remainder of the stick's space). The hitch about Mango is that it doesn't
allow you to delete any activities, *and* once you add some, you can't
delete *them* either - even though there is an option to do so.
I always load in my six activities, two of which (with sound files) are 7MB
each. I've apparently always loaded in the big ones prior to SunMoonMusic.
It seems the stick just runs out of space. If I load SunMoonMusic before the
others, it opens and runs fine.
I would hope that all distributions would allow for deleting activities,
*especially* those added by the user. (This seems to be intended; is
probably a bug in Mango Lassi.) Many previous distros allowed you to delete
any activity you wanted.
BTW, I enjoyed your tunes, especially the last few. The "fiddle tune" in
triplets is particularly fetching.
Thanks again -
Art Hunkins
- Original Message -
From: "James Cameron"
To: "Art Hunkins"
Cc:
Sent: Monday, May 30, 2011 7:54 PM
Subject: Re: [Sugar-devel] SunMoonMusic Activity does not open in Mango
Lassi
I've no idea what might be special, the activity looks normal to me, but
if there is no error log left behind my next step in diagnosis is to
launch the activity from a Terminal prompt using sugar-launch, then if
still no output is visible launch it with strace and interpret the
output.
To launch using sugar-launch, start Terminal, "cd" to the activity
directory, check the activity bundle id or service name from the
activity/activity.info file, and then use it like so:
sugar-launch ${NAME}
where ${NAME} os the bundle id or service name, in your case
org.laptop.SunMoonMusic.
It is unfortunate that this is so complex, but an alternative is:
cd ~/Activities/SunMoonMusic.activity && \
sugar-launch \
$(grep bundle_id activity/activity.info | cut -f3 -d' ')
To capture further diagnostic data using strace, add the word strace
before the word sugar-launch. You can redirect the output to a file.
cd ~/Activities/SunMoonMusic.activity && \
strace -o strace.log -f \
sugar-launch \
$(grep bundle_id activity/activity.info | cut -f3 -d' ')
I offer to review the output if you still don't see what is causing
the problem.
--
James Cameron
http://quozl.linux.org.au/
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] SunMoonMusic Activity does not open in Mango Lassi
I've just noticed a strange phenomenon with one of my activities, SunMoonMusic; it refuses to open in SoaS Mango Lassi (only). It leaves no error log behind either. (SunMoonMusic behaves normally in all other instances of Sugar.) I've six activities; all open in all versions of Sugar except for this one case. Even its close sister program, SunMoonMusicMC opens. And SunMoonMusic opens in Fedora 15 (Coconut) fine as well. The activity downloads to the Journal fine, but never appears in either Home view. All other activities of mine show up in Home view, and can be opened from Home view or Journal. Is there anything special about Mango Lassi that would cause this, with this single activity? Art Hunkins ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Latest Audio Tests with Record Activity
I've just completed exhaustive tests for audio recording (ogg/vorbis) using the Record activity with various incarnations of Sugar. Happily, there are many more compatibilities that I've observed before. FWIW, these are the results: SoaS Strawberry (0.84): Record v64 only (and the quality is only fair; there is some breakup). This is currently the weak link in the chain; it's too bad this SoaS Strawberry isn't compatible with Record v86 (see immediately below). XO-1 and XO-1.5, the former upgraded to 0.84: Record v86 (excellent). Blueberry, Mirabelle, Mango lassi, and both XO-1 and XO-1.5 when upgraded to Fedora 15 (0.92): Record v90 and 91 (excellent). Incidentally, all my SoaS tests were carried out via USB sticks made by Live USB Creator v3.10. It's able successfully to create SoaS thumb drives *that boot* from Strawberry up through the latest nightly Fedora 15 builds (a really handy utility). Art Hunkins ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [OLPC-AU] another Favorites View proposal
Your first suggestion is a particularly good one. +1 Art Hunkins - Original Message - From: Walter Bender To: Bastien ; Gonzalo Odiard ; sugar-devel ; OLPC Australia list ; James Cameron ; Gary C Martin Sent: Wednesday, May 18, 2011 11:22 AM Subject: Re: [Sugar-devel] [OLPC-AU] another Favorites View proposal I don't want to coop the current thread about search, but I have one concrete proposal (for which I volunteer to write a patch if we have consensus) and one long-standing feature request that we should dust off. (1) I propose that whenever you go to the Home View, you end up in the standard view. The only way to get to the list view would be by selecting it from the standard view. I'd even go so far as to suggest that if you navigate away, you would return to the standard view. This simple change would take some pressure off the need to distinguish the list view from the Journal and make it really just for organizing favorites and nothing else, which keeps it simple. (Even an experience Sugar user such as myself gets confused sometimes when I end up in the list view... I repeatedly hit the home view button and type F3 to no effect and think there must be something broken.) (2) Multiple groups beyond just the binary favorites/not favorites selection. Lots of teacher (and kid) feedback about wanting multiple home view collections. This is more invasive, but if we really think about list view more narrowly, then adding this would be seemingly doable from the UI perspective. (One home view could be *all*, meaning we could even eliminate the need to launch activities from the list view). -walter -- Walter Bender Sugar Labs http://www.sugarlabs.org -- ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Browse activity
Yes, this is particularly crucial as there is no Browse in 0.92 Sugar. (I gather it is currently inoperable.) Thus there is no easy way of downloading Activities from the web. (I download them on another computer, copy to a USB drive, then drag to the Journal on the first computer.) Art Hunkins - Original Message - From: Gonzalo Odiard To: Nicholas Doiron Cc: Sugar-dev Devel Sent: Wednesday, May 18, 2011 10:12 AM Subject: Re: [Sugar-devel] Browse activity I am more interested in trying to know who is interested in work in the 155 tickets open against Browse.([1] and [2]) You know, the dirty work ;) Or a least, receive patches and do releases. If nobody is doing it, we must found a new maintainer, Browse is the most used activity, and have more open tickets than any other activity. Gonzalo [1] http://dev.laptop.org/query?status=assigned&status=new&status=reopened&component=browse-activity&order=priority&col=id&col=summary&col=status&col=owner&col=type&col=milestone [2] http://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=Browse&order=priority&col=id&col=summary&col=priority&col=status&col=owner&col=type&col=milestone On Wed, May 18, 2011 at 10:56 AM, Nicholas Doiron wrote: I would be interested in continuing development of the Browse activity. We could connect with Mozilla's program to teach the web to kids, called Hackasaurus ( http://hackasaurus.org ). I have a quick hack to add their X-Ray Goggles, a kid-friendly HTML inspector, to the Edit toolbar: http://mapadelsur.blogspot.com/2011/03/hackasaurus-xo.html Or maybe that's a separate activity idea. I suppose most people won't need that in their browser. Regards, Nick Doiron On Wed, May 18, 2011 9:46 am, Gonzalo Odiard wrote: > According to git, nobody is working in Browse master. > Who is the actual maintainer? > Any plans? > > > Gonzalo > ___ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel > > -- ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Record v90 (was: v89)
I made an error is reporting on Record v90 (and the 0.92 nightly version cited below). With an appropriate mike, at least one of my systems (the one with camera - a Go2PC) records - and without stutter or silent interruptions. The remaining problem is that the output is ogg SPEEX. Hopefully this can be corrected. Art Hunkins - Original Message - From: "Art Hunkins" To: Sent: Monday, May 16, 2011 2:56 PM Subject: Re: [Sugar-devel] Record v90 (was: v89) Testing audio-only Record-90: Strange results. I tested with the latest 0.92 nightly version (Fedora-15-Nightly-20110515.07-i686-Live-soas.iso) that Tom Gilliard found to boot. (I was able to successfully create it with Live USB Creator.) I recorded on two systems, one with camera, one without. Record worked as might be expected except for two crucial facts: 1) playback was a silent file, with only an opening and closing click/short noise-burst; 2) the files are generated in ogg SPEEX format, not ogg vorbis (hence they are of no use to me). With the camera system, during audio recording color video was animated (unlike below). One other test: Record-90 on an XO-1.5 upgraded to 0.84. Things generally proceded as expected, but with a frozen video picture during recording. Unexpectedly, the resultant audio was ogg VORBIS, but with intermittent stuttering or pauses. I verified all audio results by playing them with Audacity on my desktop PC; same results as described above. Strange indeed . . . Art Hunkins - Original Message - From: "Daniel Drake" To: "Art Hunkins" Cc: Sent: Friday, May 06, 2011 3:06 PM Subject: Re: [Sugar-devel] Record v89 On 11 March 2011 18:14, Art Hunkins wrote: FWIW, I get the same results when attempting an audio recording as with other recent versions of Record: after hitting STOP (following recording) the circulating arrow within the circle (presumably indicating SAVE), never exits - continuing indefinitely. Close activity. This is with 0.90 SoaS. Should be fixed with v90. The problem is that audio recording was broken without a camera, and I guess you don't have a camera on your setup. In v90 this works, its usable but there are some UI oddities to be resolved at a later date. Daniel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Record v90 (was: v89)
Testing audio-only Record-90: Strange results. I tested with the latest 0.92 nightly version (Fedora-15-Nightly-20110515.07-i686-Live-soas.iso) that Tom Gilliard found to boot. (I was able to successfully create it with Live USB Creator.) I recorded on two systems, one with camera, one without. Record worked as might be expected except for two crucial facts: 1) playback was a silent file, with only an opening and closing click/short noise-burst; 2) the files are generated in ogg SPEEX format, not ogg vorbis (hence they are of no use to me). With the camera system, during audio recording color video was animated (unlike below). One other test: Record-90 on an XO-1.5 upgraded to 0.84. Things generally proceded as expected, but with a frozen video picture during recording. Unexpectedly, the resultant audio was ogg VORBIS, but with intermittent stuttering or pauses. I verified all audio results by playing them with Audacity on my desktop PC; same results as described above. Strange indeed . . . Art Hunkins - Original Message - From: "Daniel Drake" To: "Art Hunkins" Cc: Sent: Friday, May 06, 2011 3:06 PM Subject: Re: [Sugar-devel] Record v89 On 11 March 2011 18:14, Art Hunkins wrote: FWIW, I get the same results when attempting an audio recording as with other recent versions of Record: after hitting STOP (following recording) the circulating arrow within the circle (presumably indicating SAVE), never exits - continuing indefinitely. Close activity. This is with 0.90 SoaS. Should be fixed with v90. The problem is that audio recording was broken without a camera, and I guess you don't have a camera on your setup. In v90 this works, its usable but there are some UI oddities to be resolved at a later date. Daniel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [IAEP] Olidata computers in Uruguay
FWIW, this is a method I include in all my (strictly text-based) activities.
It both sizes fonts to fit on various-width screens, and allows a user (or
deployment) to decrease/increase font size. (It also works with all versions
of Sugar for the XO and SoaS, to my knowledge.)
def scale_font(self, widget):
font = widget.get_pango_context().get_font_description()
# The FONT DISPLAY in this activity can be resized (smaller or larger)
# by changing the value of "resize" below. "Resize" can be positive
# or negative, and is not limited to integers. A value of 1 equals a
# point in font size.
resize = 0
font_size = font.get_size() + (resize * 1024)
width = gtk.gdk.screen_width()
mult = width * .00076
if os.path.exists("/etc/olpc-release") or
os.path.exists("/etc/power/olpc-pm"):
mult = width * .00082
elif os.path.exists("/etc/fedora-release"):
release = open("/etc/fedora-release").read()
if release.find("SoaS release 1 ") != -1:
mult = width * .00132
elif release.find("SoaS release 2 ") != -1:
mult = width * .00085
elif release.find("Fedora release ") != -1:
mult = width * .00119
font.set_size(int(font_size * mult))
widget.modify_font(font)
Art Hunkins
- Original Message -
From: "Gary Martin"
To: "Yamandu Ploskonka"
Cc: "IAEP SugarLabs" ; "Sugar-dev Devel"
Sent: Monday, May 02, 2011 1:13 PM
Subject: Re: [Sugar-devel] [IAEP] Olidata computers in Uruguay
On 2 May 2011, at 16:47, Yamandu Ploskonka wrote:
the Sur list is following this thread in detail, I just wanted to share a
FYI for developers.
30,000 Olidata laptops have been purchased by Ceibal at $130 apiece and
teachers are being "upgraded" to those, trading in their XOs.
Thanks for raising this issue! I've cc:ed the sugar-devel list as it's the
first I've read of this.
One of the most noticeable source for incompatibilities seems to be screen
definition, 800x600 in the Olidata, and thus several Activities are
cropped,
Ouch, quite a few Activity toolbars will likely overflow at 800x600
(overflow widgets land in a drop down menu in the far right of the toolbar
that shows the text from the tool button hint only). The XO is a 1200x900
screen, about a year or two back there was general consensus that we should
try and make sure Activities worked well down too 1024x768 as that was
common in emulated environments and regular laptops/desktops.
These 800x600 display machines will want to make sure they are running Sugar
using an environmental variable of SUGAR_SCALING=72, this will shrink the
UI scale down to fit the lower screen resolution. SUGAR_SCALING currently
only has an effect at either 72 (works well for 800x600 and 1024x768) or 100
(for 1200x900 or larger).
There will likely still be activities drawing their canvas with hard coded
expectations of screen size, but hopefully these will be reasonably few in
number by now. Please file a ticket if you find any (bugs.sugarlabs.org), or
feel free to email me and I'll try and chase them up.
One last additional issue you may find is with the dpi of text. Some
activities may seem to display overly large or small text fonts. This issue
is quite a black art to solve well, but still worth keeping an eye out for
and reporting back to the Activity developer.
Regards,
--Gary
maybe something to be aware of. Etoys appears to have been fixed already.
On 05/02/2011 02:15 AM, nanon...@mediagala.com wrote:
El pLan Ceibal en Uruguay está entregando a las Aaestras de Primaria las
Olidata "Jump PC", con disco flash de 8 GB
http://www.olidata.cl/index.php/netbook_web/show/id/10
Las "olidata" se las dan a las MAestras a cambio de sus XO. Me parece una
decisión errada, ya que la intención del PLan ceibal es darles a las
Maestras una maquina más potente y al dÃa (con respecto a las XO 1 de los
niños, de hace dos o tres años), pero eso me parece un gran disparate, no
puede ser que la MAestra no pueda hacer pruebas sobre las XO de los
Niños.
La MAestra tiene que entregar su XO 1.0 al Plan Ceibal (que le fue
entregada hace un par de años) y el Plan ceibal se la cambia por una
Olidata. El Año pasado fueron compradas 30.000 olidata , según la pagina
web institucional del Plan Ceibal.
---
Una cosa que no me parece correcta es que la laptop de maestra sea
diferente ala XO: tiene más capacidad ara el Diario, eso es bueno(8 Gb
contra 1 Gb), pero la pantalla es diferente, el hardware es distinto, y
el sugar no funciona en forma identica, por lo tanto cualquier cosa que
la Maestra use en su Laptop no podrá ser repetido por los alumnos de la
misma forma.
NO tiene sentido querer darle una maquina más potente a las MAestras, ya
que si por ejemplo la Maestra hace una actividad Etoys en su casa ,
usando sonidos, animación , etc e
Re: [Sugar-devel] [Csnd] ALSA MIDI output causes segmentation fault
Don't know if this is related or not, but under the latest nightly development versions of Sugar (0.92) and Fedora 15 (Linux), I get an error message with MIDI and this specification: -+rtmidi=alsa -M hw:1,0 The specification works fine with earlier versions of Sugar and Fedora. Strangely, Sugar 0.92 on the XO-1 (upgraded with Fedora 14 or earlier?) doesn't give the error. The error specifically says it can't find the MIDI device (whose number is correct). I've asked Peter Robinson (of SoaS development) to try to track down this issue. So far, no luck. Art Hunkins - Original Message - From: "Chuckk Hubbard" To: "Csound List" Sent: Friday, April 22, 2011 3:40 PM Subject: [Csnd] ALSA MIDI output causes segmentation fault Hi everyone. For some reason, on Debian Linux testing, with Csound 5.12 (both my own compiled version and the Debian repository version), I get a segmentation fault with this .csd. If I comment out the ALSA MIDI line and uncomment the portmidi line, it works as expected. Does anyone else get this behavior? If not, any ideas why I would? Thanks. -Chuckk -- http://www.badmuthahubbard.com Send bugs reports to the Sourceforge bug tracker https://sourceforge.net/tracker/?group_id=81968&atid=564599 Discussions of bugs and features can be posted here To unsubscribe, send email sy...@lists.bath.ac.uk with body "unsubscribe csound" ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Sugar 0.92 MIDI Controller Issue
Thanks, Peter; I will continue this thread with the dev group as you
suggest.
To respond to your question:
The command line you asked about returns nothing - when run either before an
activity (involving MIDI) is opened, or after the activity is closed.
The file "midiC1D0" does exist however, though with my rudimentary knowledge
of Linux, I've no idea what kind of animal it is. I just know it's not a
directory, and prints nothing with "cat midiC1D0" (from the appropriate snd
directory).
Art Hunkins
- Original Message -
From: "Peter Robinson"
To: "Art Hunkins"
Cc: "SoaS"
Sent: Friday, April 15, 2011 11:48 AM
Subject: Re: Sugar 0.92 MIDI Controller Issue
Hey Art,
Firstly. Can you make sure you send these to SoaS mailing list and not
direct to me. It allows others to see the problems and possibly help.
I'm on the list so I'll see the mails.
It looks like its seeing the device:
ALSA lib rawmidi_hw.c:233:(snd_rawmidi_hw_open) open /dev/snd/midiC1D0
failed: Device or resource busy
It looks like the device is already in use.
if you do "lsof /dev/snd/midiC1D0" what do you get?
Peter
On Fri, Apr 15, 2011 at 4:24 PM, Art Hunkins wrote:
Hi Peter,
With recent nightly builds of SoaS, I've noticed that MIDI devices are no
longer being recognized.
On builds through 0.90, devices were recognized correctly as long as the
device was inserted after Sugar was booted. Now this is not the case.
Below are the two log files, both for 0.92. Log 1 is when a MIDI device
(hw:1,0) is inserted before Sugar boot. This does not work now, nor did
it
recognize the device previously.
Log 2 is when the device is inserted after boot, and is what worked in
prior
versions of SoaS. The device is inserted before the activity is run The
log
indicates that the (ALSA) device is not being found.
I hope you can suggest what might be done about this, as my activities
are
majorly dependent on MIDI devices, as you know.
Thanks much -
Art Hunkins
Log 1 (MIDI device inserted prior to system boot):
** Message: pygobject_register_sinkfunc is deprecated (HippoCanvasBox)
time resolution is 1.111 ns
1302861517.648102 WARNING root: No gtk.AccelGroup in the top level
window.
1302861517.668884 WARNING root: No gtk.AccelGroup in the top level
window.
/usr/lib/python2.7/site-packages/sugar/graphics/window.py:195: Warning:
g_object_set_qdata: assertion `G_IS_OBJECT (object)' failed
self.__vbox.pack_start(toolbar_box, False)
** (sugar-activity:1339): DEBUG: Got client ID
"107a95140eb1d17fec1302861518268610001252"
** (sugar-activity:1339): DEBUG: Setting initial properties
** (sugar-activity:1339): DEBUG: Received SaveYourself(SmSaveLocal,
!Shutdown, SmInteractStyleNone, !Fast) in state idle
** (sugar-activity:1339): DEBUG: Sending SaveYourselfDone(True) for
initial
SaveYourself
** (sugar-activity:1339): DEBUG: Received SaveComplete message in state
save-yourself-done
0dBFS level = 32768.0
Csound version 5.12 beta (float samples) Dec 27 2010
libsndfile-1.0.23
UnifiedCSD: /home/liveuser/Activities/SunMoonMusic.activity/SunMusic.csd
STARTING FILE
Creating options
Creating orchestra
Creating score
orchname: /tmp/csound-hGkCXW.orc
scorename: /tmp/csound-BDHtQc.sco
rtaudio: ALSA module enabled
rtmidi: ALSA module enabled
orch compiler:
51 (52) lines read
instr 1
sorting score ...
... done
Csound version 5.12 beta (float samples) Dec 27 2010
midi channel 1 using instr 1
midi channel 2 using instr 1
midi channel 3 using instr 1
midi channel 4 using instr 1
midi channel 5 using instr 1
midi channel 6 using instr 1
midi channel 7 using instr 1
midi channel 8 using instr 1
midi channel 9 using instr 1
midi channel 10 using instr 1
midi channel 11 using instr 1
midi channel 12 using instr 1
midi channel 13 using instr 1
midi channel 14 using instr 1
midi channel 15 using instr 1
midi channel 16 using instr 1
displays suppressed
0dBFS level = 32768.0
ALSA lib rawmidi_hw.c:233:(snd_rawmidi_hw_open) open /dev/snd/midiC1D0
failed: No such file or directory
ALSA: error opening MIDI input device: 'hw:1,0'
*** error opening MIDI in device: -1 (Unknown MIDI error)
inactive allocs returned to freespace
end of score. overall amps: 0.0 0.0
overall samples out of range: 0 0
1 errors in performance
1302861553.480113 WARNING root: No gtk.AccelGroup in the top level
window.
1302861553.489591 WARNING root: No gtk.AccelGroup in the top level
window.
Removing temporary file /tmp/csound-DyTPJs.srt ...
Removing temporary file /tmp/csound-BDHtQc.sco ...
Removing temporary file /tmp/csound-hGkCXW.orc ...
Exited with status 0, pid 1339 data (None, ', mode
'w'
at 0xa314a18>, dbus.ByteArray('469e8e60c487c8337deb7e89986ba2cd54b5de59',
variant_level=1))
Log 2 (MIDI device inserted after system
Re: [Sugar-devel] SoaS v5 status
FWIW, I can attest that recent nightly builds of SoaS, including those with Fedora 15, are nicely installed to USB sticks by Live USB Creator (on Windows XP). My activities (Our Music, SunMoonMusic, and the two FileMix's) all run correctly on these builds. The two most obvious remaining problems for the public release of SoaS 5 are: 1) the "keyring" login, which requires 9 clicks to cancel/get past; 2) the Browse activity, which doesn't open. The latter means that no activities can be downloaded, of course. (I'm fully aware that these two issues are well-known; I'm only trying to vote them toward the front of the pack.) I was not able to initially login the way Peter suggested, but rather had to use this variant: at the login window: CTRL-ALT-F2 rpm -e sugar (no ENTER) CTRL-ALT-F8 click on Live System User window click on Login in the following window The next time you boot, there are no logins at all. Art Hunkins - Original Message - From: "Peter Robinson" To: "Sugar on a Stick List" ; "Sugar devel" Sent: Tuesday, April 05, 2011 4:13 AM Subject: [Sugar-devel] SoaS v5 status Hi All, Sorry for a lot of the recent radio silence. In short I've been travelling a lot and work and my personal life took over pretty close to completely since FUDCon at the end of January :-( That said I've spent some time over the last couple of days to fix up and update some SoaS bits and as of the next compose the Fedora 15 live image should be working [1]. Those impatient people can boot up the current release and when it boots to the login screen do a "Ctrl + Alt + F2" login as root, run "rpm -e openbox", do a "Ctrl + Alt + F8" and then login and you should get a lovely sweet Sugar :-D So next on the SoaS release ToDo list is the following: - List of shipped (and working) Activities - Release name (Suggestions?) - Testing. Cheers, Peter [1] http://alt.fedoraproject.org/pub/alt/nightly-composes/soas/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Fedora_15_gnome3_with_sugar_0.92.0
Is there yet a public SoaS release that incorporates Sugar 0.92? (Hopefully as an .iso installable via Live USB Creator?) Art Hunkins - Original Message - From: "Thomas C Gilliard" To: "SoaS" Cc: "Sugar Devel" Sent: Friday, April 01, 2011 11:00 AM Subject: [Sugar-devel] Fedora_15_gnome3_with_sugar_0.92.0 FYI New today: The f15 desktop live .iso [1] Boots from CD to gnome3 and installs to HD. sugar 0.92.0 can also be installed see method: http://wiki.sugarlabs.org/go/Community/Distributions/Fedora#Fedora_15_gnome3_with_sugar_0.92.0 Tom Gilliard satellit on freenode #sugar IRC Download: [1] http://serverbeach1.fedoraproject.org/pub/alt/stage/15-Beta.TC1/Live/i686/Fedora-15-Beta-i686-Live-Desktop.iso ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] tamtammini-57.xo, csound and ubuntu
As a Csound user (but except for Sugar, lacking Linux experience), I can
perhaps be of some help.
The problem is shown by these lines:
insert_score_event(): invalid instrument number or name
insert_score_event(): invalid instrument number or name
insert_score_event(): invalid instrument number or name
insert_score_event(): invalid instrument number or name
insert_score_event(): invalid instrument number or name
insert_score_event(): invalid instrument number or name
insert_score_event(): invalid instrument number or name
insert_score_event(): invalid instrument number or name
insert_score_event(): invalid instrument number or name
insert_score_event(): invalid instrument number or name
insert_score_event(): invalid instrument number or name
insert_score_event(): invalid instrument number or name
Clearly, the "orchestra" has been compiled correctly. The "score" is the
problem. Score events are obviously being inserted in real time as you press
keys. As each score event is initiated, it looks for its designated
instrument name or number and doesn't find it in the orchestra; so it gives
a click and cancels the event. Offhand, it looks like the activity has a
"name communication" problem; either that, or the necessary instruments
aren't being generated in the orchestra (although there is no indication of
that).
Other than that, there are a very large number of (gtk) deprecation warnings
indicated. Could this indicate python-related version incompatibilites?
Others with more expertise than I should address this possibility.
Art Hunkins
- Original Message -
From: "Andrea Mayr"
To:
Sent: Friday, April 01, 2011 5:13 AM
Subject: [Sugar-devel] tamtammini-57.xo, csound and ubuntu
Hi!
I am putting together an Ubuntu based Live-System for Kids from 6
to 12 years. I am exited that sugar is available as a package for
installation within Ubuntu now. Two years ago i tried so hard to
get it running (on debian), but failed. Most of the activities
are now running without problems after installing them with
sugar-install-bundle. But still i have a problem with TamTammini,
which is one of the essential programs for the paedagogical
approach of our setup. Maybe somebody could have a look at my
logfile. A friend tried it on a debian system and had similar
problems. Should i direct my questions to another place? I am
very thankful for advice and help.
Andrea
System is: Ubuntu 10.10.. Sugar 0.88.1, Csound version 5.12,
tamtammini-57.xo
Problem: TamTammini starts within sugar on ubuntu. When clicking
on an instrument you hear the sound you get when clicking a
button (sound is working, i.e Speak.activity is working fine),
but you don't hear the instrument. Also the keyboard gives no
sounds.
Log file:
** Message: pygobject_register_sinkfunc is deprecated
(HippoCanvasBox)
1301392836.158145 DEBUG root: Debug Level 0
1301392836.158415 DEBUG root: INFO: loaded
TAMTAM_ROOT=/home/jux/Activities/TamTamMini.activity
1301392836.214454 DEBUG root: skip
/home/jux/Activities/TamTamMini.activity/common/Util/Clooper/linux64_511_deb
blobs: /home/jux/Activities/Tam
TamMini.activity/common/Util/Clooper/linux64_511_deb/aclient.so:
falsche ELF-Klasse: ELFCLASS64
1301392836.216862 DEBUG root: skip
/home/jux/Activities/TamTamMini.activity/common/Util/Clooper/linux64_510
blobs: /home/jux/Activities/TamTamM
ini.activity/common/Util/Clooper/linux64_510/aclient.so: falsche
ELF-Klasse: ELFCLASS64
1301392836.218069 DEBUG root: skip
/home/jux/Activities/TamTamMini.activity/common/Util/Clooper/linux32_508
blobs: libcsound.so.5.1: Kann die S
hared-Object-Datei nicht öffnen: Datei oder Verzeichnis nicht
gefunden
1301392836.226332 DEBUG root: use
/home/jux/Activities/TamTamMini.activity/common/Util/Clooper/linux32_511_deb
blobs
1301392836.293436 DEBUG root: datastore.get
1301392836.298367 WARNING root: .has_key() is deprecated, use
'in'
1301392836.303999 DEBUG root: *** Act
fe6faa0ce02bb0dce54e1510cf9c965b80cde2b4, mesh instance None,
scope private
1301392836.326327 DEBUG root: PaletteWindow.popdown immediate
True
1301392836.335281 DEBUG root: PaletteWindow.popdown immediate
True
1301392836.340254 WARNING root: No gtk.AccelGroup in the top
level window.
1301392836.344155 WARNING root: No gtk.AccelGroup in the top
level window.
/usr/lib/python2.6/dist-packages/sugar/graphics/window.py:290:
DeprecationWarning: use toolbar_box instead of toolbox
warnings.warn('use toolbar_box instead of toolbox',
DeprecationWarning)
Logging disabled on purpose
PortMIDI real time MIDI plugin for Csound
virtual_keyboard real time MIDI plugin for Csound
PortAudio real-time audio module for Csound
0dBFS level = 32768.0
Csound version 5.12 (double samples) Sep 15 2010
libsndfile-1.0.21
UnifiedCSD:
/home/jux/Activities/TamTamMini.activity/common/Resources/tamtamorc.csd
STARTING FILE
Creating options
Herstellen des Orchesters
Creating score
orchname: /tmp/csound-uN7ijG.orc
sc
Re: [Sugar-devel] [DESIGN] Record UI
Thanks, Gonzalo; that's a very good idea. I'll look forward to testing. Art Hunkins - Original Message - From: Gonzalo Odiard To: Art Hunkins Cc: C. Scott Ananian ; Sugar-dev Devel Sent: Thursday, March 31, 2011 11:39 PM Subject: Re: [Sugar-devel] [DESIGN] Record UI Art, I don't know if i will see the glitches when we do the visual representation. I agree, in a tool to record audio, is important the audio is well recorded. And when I have anything to show, I will inform and we can test it and see what can we do. Regards Gonzalo On Thu, Mar 31, 2011 at 10:15 PM, Art Hunkins wrote: - Original Message - From: "C. Scott Ananian" To: "Art Hunkins" Cc: "Gonzalo Odiard" ; "Sugar-dev Devel" Sent: Thursday, March 31, 2011 6:54 PM Subject: Re: [Sugar-devel] [DESIGN] Record UI On Fri, Mar 18, 2011 at 12:18 PM, Art Hunkins wrote: Please ensure that, in *audio* recording mode, any video display (including an oscilloscope-style display) does not cause glitches in the audio. (This was an apparent problem in earlier versions.) Of course, the surest guarantee of this is no simultaneous (changing) video display. I think video feedback is vital. How do you know it's actually doing something if nothing seems to happen when you start recording audio? It doesn't necessarily have to be a waveform display, but *something* needs to be changing. A waveform display has pedagogical value. It's worth making that work right. --scott If it "works right", fine. Otherwise, there is the elapsed time indicator that is the "something" that "needs to be changing. Also there are visual changes when you start and stop recording - all sorts of visual cues. I too rather like the waveform display - it does have some pedagogical value; it just *must not* interrupt smooth audio flow. Art Hunkins ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [DESIGN] Record UI
- Original Message - From: "C. Scott Ananian" To: "Art Hunkins" Cc: "Gonzalo Odiard" ; "Sugar-dev Devel" Sent: Thursday, March 31, 2011 6:54 PM Subject: Re: [Sugar-devel] [DESIGN] Record UI On Fri, Mar 18, 2011 at 12:18 PM, Art Hunkins wrote: Please ensure that, in *audio* recording mode, any video display (including an oscilloscope-style display) does not cause glitches in the audio. (This was an apparent problem in earlier versions.) Of course, the surest guarantee of this is no simultaneous (changing) video display. I think video feedback is vital. How do you know it's actually doing something if nothing seems to happen when you start recording audio? It doesn't necessarily have to be a waveform display, but *something* needs to be changing. A waveform display has pedagogical value. It's worth making that work right. --scott If it "works right", fine. Otherwise, there is the elapsed time indicator that is the "something" that "needs to be changing. Also there are visual changes when you start and stop recording - all sorts of visual cues. I too rather like the waveform display - it does have some pedagogical value; it just *must not* interrupt smooth audio flow. Art Hunkins ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [DESIGN] Record UI
- Original Message - From: Gonzalo Odiard To: Gary Martin Cc: Sugar-dev Devel Sent: Thursday, March 31, 2011 9:29 AM Subject: Re: [Sugar-devel] [DESIGN] Record UI - I suggested the sugar-artwork microphone icon (lips) would be good for the audio recording icon (I believe it was originally designed for use as the device icon for a proposed microphone input gain control palette). We didn't formally +1 in the meeting, but worth considering if you don't find it controversial I think the lips icons is better to text to speech (I am using it in Read now). We need a coherent set of metaphor here. What will be represent the icon? The action done by computer or the action done by the child? Also, we can record music too, no only talking. I totally agree with Gonzalo about the lips icon (see my previous mail) - for these and other reasons. Frankly, I really like the microphone icon. Any reason not to use (reuse) it? (Otherwise, perhaps the ear.) Art Hunkins___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [DESIGN] Record UI
Comments/suggestions regarding the Record UI:
1) I think Tom's ideas (http://www.flatlandfarm.de/blog/?p=283) are right on
target in re: audio recording. +1.
2) I'm unclear as to whether the oscilloscope ("measure-type") display is a
preview only, or is active during the entire record process. If the latter,
I fear for audio glitches (and if Record ends up audio-glitching, you are
likely to hear from me about it indefinitely!) Probably safer would be to
display oscilloscope only in preview mode, for setting appropriate record
level, and demoing (or otherwise exploring) other aspects of sound. (By
"preview" here, I refer to testing the record level.)
3) Let's keep in mind that Audacity is available as a Suger activity - at
least from the command line. It's full-featured, can edit soundfiles and be
used for all kinds of sound demos and displays. In my view, we should not
worry that Record doesn't include these features.
4) I dislike the lips icon intensely. Besides otherwise being misleading, it
suggests *voice* recording only (and probably only speech). The "ear" seems
much more appropriate, or (for that matter) a stylized waveform or
oscilloscope display. I see the primary application as the recording of
environmental (often nature) sounds, i.e., exploring the *world* of sound.
Art Hunkins
- Original Message -
From: "Gary Martin"
To: "Gonzalo Odiard"
Cc: "Sugar-dev Devel"
Sent: Thursday, March 31, 2011 8:56 AM
Subject: Re: [Sugar-devel] [DESIGN] Record UI
Hi Gonzalo,
On 18 Mar 2011, at 15:15, Gonzalo Odiard wrote:
I have prepared mockups about the changes I want to do in the Record UI.
[1]
The changes were discussed with Simon Schampijer and we take ideas from
Tom Staubitz.
Just following up from Sunday's design meeting:
http://meeting.sugarlabs.org/sugar-meeting/meetings/2011-03-27T15:04:42
See the above log for details, but here's a quick summary:
- place the chronometer combo in the secondary toolbars, as opposed to the
main toolbar
- write each object to Journal upon its creation rather than trying to write
all of them at once on an Activity switch or Stop (which can feel like a
crash/hang if you have recorded more than a few new objects)
- remove the (i) info icon from the toolbar and instead badge each media
thumbnail on the bottom right corner with an info widget (icon still to be
decided)
- use the Journal detail view API explicitly for editing individual object
metadata information, rather than the custom info/take notes side bar, see
Browse and its download complete alert for example code. We standardise on
an edit details UI for all Activities that want to edit their metadata at
any time, an existing proposal already being worked on [1].
- camera icon should be the one as seen in sugar-artwork for
camera-external, need a similar styled icon for video (Walter has also
recently started using camera-external in Turtle Art/Blocks)
- I suggested the sugar-artwork microphone icon (lips) would be good for the
audio recording icon (I believe it was originally designed for use as the
device icon for a proposed microphone input gain control palette). We didn't
formally +1 in the meeting, but worth considering if you don't find it
controversial
There is still some concern over the user interaction for a primary tool,
with sub-toolbar, triggering a full screen canvas change (e.g. as mocked up
in your Record camera vs video vs audio, and my Memorize play vs create UI
modes), as it might be confusing to get back out of a mode (especially when
triggered unexpectedly by hover delay). I'll make a test activity with this
interaction for next Sunday's design meeting and see how it feels.
Regards,
--Gary
[1] Option 1. from Christian's 'detail view anywhere' mockups
http://wiki.sugarlabs.org/go/File:Detailview_20110313.pdf
Regards
Gonzalo
[1] http://wiki.laptop.org/go/User:Godiard/Record/NewToolbar
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Fw: 0.92 Activity Testing
My results upgrading my XO-1 to Sugar 0.92 were somewhat different from
upgrading my XO-1.5. Whereas Record v89 worked flawlessly on XO-1 (audio mode),
it produced some audio glitches and stuttering on XO-1.5. (The quality
otherwise was good.)
On the XO-1.5, another phenomenon, perhaps unrelated, showed up as well.
Regardless of how many Journal entries were present (including a single entry),
a "Journal full; eliminate some activities" window consistently pops up. This
happens when starting an activity; it's possible to continue by simply resuming
the activity in the menu bar.
Again, probably unrelated, I note that *many* activities are included in this
"release", and it is impossible to delete them - even activities I have
downloaded.
Can anyone comment on these observations, or explain them?
Art Hunkins
- Original Message -
From: Art Hunkins
To: Gonzalo Odiard
Cc: Sugar Devel
Sent: Sunday, March 13, 2011 8:11 PM
Subject: Re: [Sugar-devel] 0.92 Activity Testing
Thanks, Gonzalo. With this info I was able to install an OS13 image (or
whatever you call it) to my XO-1 and test all my Activities (which were
compatible with 0.92 as I had expected).
Thanks, too, to Tom Gilliard for your suggestions. I'm afraid, given my lack of
Linux/Sugar knowledge, they mostly passed over my head.
I'm happy to report that (here in 0.92 on the XO-1) audio recording with
Record-89 works fine. This, despite failing with SoaS and 0.90. Hopefully it
will continue to work when a non-beta version of 0.92 (SoaS) emerges.
Art Hunkins
- Original Message -----
From: Gonzalo Odiard
To: Art Hunkins
Sent: Sunday, March 13, 2011 12:16 AM
Subject: Re: [Sugar-devel] 0.92 Activity Testing
You can test it in XO 1 or XO 1.75 with the last OLPC images
http://wiki.laptop.org/go/11.2.0
I think you can test it too with Fedora 15 alpha.
Gonzalo
On Sat, Mar 12, 2011 at 11:32 PM, Art Hunkins wrote:
I'd like to rephrase my question:
Is there anywhere a Sugar 0.92-class .iso that I can install with Live USB
Creator on a USB drive?
I am looking to test my activities in 0.92.
(If this is at all relevent, I cannot make a working stick from any of the
recent nightly releases using the current (3.10.0) version of Live USB Creator.)
Art Hunkins
- Original Message ----- From: "Thomas C Gilliard"
To: "Art Hunkins"
Cc:
Sent: Friday, March 11, 2011 4:50 PM
Subject: Re: [Sugar-devel] 0.92 Activity Testing
Art Hunkins wrote:
I notice that all recent activity releases indicate compatibility with
0.92 Sugar.
How can that be true if 0.92 is not yet released?
I'd like to test my activities, and have assumed that maybe the latest
nightly releases represent 0.92 (??). I also note that the "rawhide" folder in
the nightly repository is unpopulated.
I create my Sugars (SoaS) via the Live USB Creator, and the latest
Windows version (3.10.0) does not work with these nightly releases (Live
Creator only seems to handle final releases). Is there some other .iso (e.g.,
rawhide) that represents 0.92 that I can install on a USB stick with Live USB
Creator?
Confused.
here is transcript of a successful install I did today booted from a dd
created USB to a 320GB external USB Drive.
#fedora-test-day IRC freenode (03/11/2011)
dd if=Fedora-15-AlphaRC2-i686-Live-Desktop.iso of=/dev/sdg
boots 2 GB USB on ACER ASPIRE ONE in gnome3 with wireless
---clip---
adamw; jlaska: doing test install to external USB 320GB HD
from gnome3 test x86_64 booted USB in ACER ASPIRE ONE (atom N450) boots;
firstboot; smolt;login gnome3...works
satellit_: you've got a streak of luck going :)
booted from 320GB USB drive. nice netbook installer
why does dd work so well?
./topic Why does dd work so well?
this was the x86-64 .iso dd to USB did not expect it to boot
N450 atom...
* satellit_ i removed ACER internal HD physically to avoid accidentally
involving it in anaconda writes
installing Xchat from Add/Remove Software worked
* satellit-gn3 (~su...@.bendbroadband.com) has joined #fedora-test-day
here is the gnome3 install
it is in the proper activites internet menu
xchat
will try updates now
* satellit-gn3 has quit (Client Quit)
147 updates shown
selenix denial..pop up continues to Downloading packages
* lewis41 has quit (Quit: Leaving)
installing:
https://admin.fedoraproject.org/updates/F15/FEDORA-2011-3099
finished. All software is up to date.. try restart for boot
test...here is hoping
log out shutdown no menu item for shutdown?
fedora ("f") on reboot
gdm login; gnome3 IT Works: )
*
Re: [Sugar-devel] [DESIGN] Record UI
A request concerning the new design of Record: Please ensure that, in *audio* recording mode, any video display (including an oscilloscope-style display) does not cause glitches in the audio. (This was an apparent problem in earlier versions.) Of course, the surest guarantee of this is no simultaneous (changing) video display. Also, please ensure that there is no such interruption for *all audio recording resolutions*, as well as for all Sugar releases that this version of Record targets. Art Hunkins - Original Message - From: Gonzalo Odiard To: Sugar-dev Devel Sent: Friday, March 18, 2011 11:15 AM Subject: [Sugar-devel] [DESIGN] Record UI I have prepared mockups about the changes I want to do in the Record UI. [1] The changes were discussed with Simon Schampijer and we take ideas from Tom Staubitz. Regards Gonzalo [1] http://wiki.laptop.org/go/User:Godiard/Record/NewToolbar -- ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] 0.92 Activity Testing
Thanks, Gonzalo. With this info I was able to install an OS13 image (or
whatever you call it) to my XO-1 and test all my Activities (which were
compatible with 0.92 as I had expected).
Thanks, too, to Tom Gilliard for your suggestions. I'm afraid, given my lack of
Linux/Sugar knowledge, they mostly passed over my head.
I'm happy to report that (here in 0.92 on the XO-1) audio recording with
Record-89 works fine. This, despite failing with SoaS and 0.90. Hopefully it
will continue to work when a non-beta version of 0.92 (SoaS) emerges.
Art Hunkins
- Original Message -
From: Gonzalo Odiard
To: Art Hunkins
Sent: Sunday, March 13, 2011 12:16 AM
Subject: Re: [Sugar-devel] 0.92 Activity Testing
You can test it in XO 1 or XO 1.75 with the last OLPC images
http://wiki.laptop.org/go/11.2.0
I think you can test it too with Fedora 15 alpha.
Gonzalo
On Sat, Mar 12, 2011 at 11:32 PM, Art Hunkins wrote:
I'd like to rephrase my question:
Is there anywhere a Sugar 0.92-class .iso that I can install with Live USB
Creator on a USB drive?
I am looking to test my activities in 0.92.
(If this is at all relevent, I cannot make a working stick from any of the
recent nightly releases using the current (3.10.0) version of Live USB Creator.)
Art Hunkins
- Original Message - From: "Thomas C Gilliard"
To: "Art Hunkins"
Cc:
Sent: Friday, March 11, 2011 4:50 PM
Subject: Re: [Sugar-devel] 0.92 Activity Testing
Art Hunkins wrote:
I notice that all recent activity releases indicate compatibility with
0.92 Sugar.
How can that be true if 0.92 is not yet released?
I'd like to test my activities, and have assumed that maybe the latest
nightly releases represent 0.92 (??). I also note that the "rawhide" folder in
the nightly repository is unpopulated.
I create my Sugars (SoaS) via the Live USB Creator, and the latest
Windows version (3.10.0) does not work with these nightly releases (Live
Creator only seems to handle final releases). Is there some other .iso (e.g.,
rawhide) that represents 0.92 that I can install on a USB stick with Live USB
Creator?
Confused.
here is transcript of a successful install I did today booted from a dd
created USB to a 320GB external USB Drive.
#fedora-test-day IRC freenode (03/11/2011)
dd if=Fedora-15-AlphaRC2-i686-Live-Desktop.iso of=/dev/sdg
boots 2 GB USB on ACER ASPIRE ONE in gnome3 with wireless
---clip---
adamw; jlaska: doing test install to external USB 320GB HD
from gnome3 test x86_64 booted USB in ACER ASPIRE ONE (atom N450) boots;
firstboot; smolt;login gnome3...works
satellit_: you've got a streak of luck going :)
booted from 320GB USB drive. nice netbook installer
why does dd work so well?
./topic Why does dd work so well?
this was the x86-64 .iso dd to USB did not expect it to boot
N450 atom...
* satellit_ i removed ACER internal HD physically to avoid accidentally
involving it in anaconda writes
installing Xchat from Add/Remove Software worked
* satellit-gn3 (~su...@.bendbroadband.com) has joined #fedora-test-day
here is the gnome3 install
it is in the proper activites internet menu
xchat
will try updates now
* satellit-gn3 has quit (Client Quit)
147 updates shown
selenix denial..pop up continues to Downloading packages
* lewis41 has quit (Quit: Leaving)
installing:
https://admin.fedoraproject.org/updates/F15/FEDORA-2011-3099
finished. All software is up to date.. try restart for boot
test...here is hoping
log out shutdown no menu item for shutdown?
fedora ("f") on reboot
gdm login; gnome3 IT Works: )
* You are now known as satellit_afk
* satellit-gn3 (~su...@.bendbroadband.com) has joined #fedora-test-day
--
(logged in from USB Hard Drive gnome3 desltop with installed Xchat)
Tom Gilliard
satellit
Art Hunkins
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] 0.92 Activity Testing
I'd like to rephrase my question:
Is there anywhere a Sugar 0.92-class .iso that I can install with Live USB
Creator on a USB drive?
I am looking to test my activities in 0.92.
(If this is at all relevent, I cannot make a working stick from any of the
recent nightly releases using the current (3.10.0) version of Live USB
Creator.)
Art Hunkins
- Original Message -
From: "Thomas C Gilliard"
To: "Art Hunkins"
Cc:
Sent: Friday, March 11, 2011 4:50 PM
Subject: Re: [Sugar-devel] 0.92 Activity Testing
Art Hunkins wrote:
I notice that all recent activity releases indicate compatibility with
0.92 Sugar.
How can that be true if 0.92 is not yet released?
I'd like to test my activities, and have assumed that maybe the latest
nightly releases represent 0.92 (??). I also note that the "rawhide"
folder in the nightly repository is unpopulated.
I create my Sugars (SoaS) via the Live USB Creator, and the latest
Windows version (3.10.0) does not work with these nightly releases (Live
Creator only seems to handle final releases). Is there some other .iso
(e.g., rawhide) that represents 0.92 that I can install on a USB stick
with Live USB Creator?
Confused.
here is transcript of a successful install I did today booted from a dd
created USB to a 320GB external USB Drive.
#fedora-test-day IRC freenode (03/11/2011)
dd if=Fedora-15-AlphaRC2-i686-Live-Desktop.iso of=/dev/sdg
boots 2 GB USB on ACER ASPIRE ONE in gnome3 with wireless
---clip---
adamw; jlaska: doing test install to external USB 320GB HD
from gnome3 test x86_64 booted USB in ACER ASPIRE ONE (atom N450) boots;
firstboot; smolt;login gnome3...works
satellit_: you've got a streak of luck going :)
booted from 320GB USB drive. nice netbook installer
why does dd work so well?
./topic Why does dd work so well?
this was the x86-64 .iso dd to USB did not expect it to boot
N450 atom...
* satellit_ i removed ACER internal HD physically to avoid accidentally
involving it in anaconda writes
installing Xchat from Add/Remove Software worked
* satellit-gn3 (~su...@.bendbroadband.com) has joined #fedora-test-day
here is the gnome3 install
it is in the proper activites internet menu
xchat
will try updates now
* satellit-gn3 has quit (Client Quit)
147 updates shown
selenix denial..pop up continues to Downloading packages
* lewis41 has quit (Quit: Leaving)
installing:
https://admin.fedoraproject.org/updates/F15/FEDORA-2011-3099
finished. All software is up to date.. try restart for boot
test...here is hoping
log out shutdown no menu item for shutdown?
fedora ("f") on reboot
gdm login; gnome3 IT Works: )
* You are now known as satellit_afk
* satellit-gn3 (~su...@.bendbroadband.com) has joined #fedora-test-day
--
(logged in from USB Hard Drive gnome3 desltop with installed Xchat)
Tom Gilliard
satellit
Art Hunkins
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] 0.92 Activity Testing
I notice that all recent activity releases indicate compatibility with 0.92 Sugar. How can that be true if 0.92 is not yet released? I'd like to test my activities, and have assumed that maybe the latest nightly releases represent 0.92 (??). I also note that the "rawhide" folder in the nightly repository is unpopulated. I create my Sugars (SoaS) via the Live USB Creator, and the latest Windows version (3.10.0) does not work with these nightly releases (Live Creator only seems to handle final releases). Is there some other .iso (e.g., rawhide) that represents 0.92 that I can install on a USB stick with Live USB Creator? Confused..... Art Hunkins ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Record v89
FWIW, I get the same results when attempting an audio recording as with other recent versions of Record: after hitting STOP (following recording) the circulating arrow within the circle (presumably indicating SAVE), never exits - continuing indefinitely. Close activity. This is with 0.90 SoaS. Here is the complete log: ** Message: pygobject_register_sinkfunc is deprecated (GstObject) ** Message: pygobject_register_sinkfunc is deprecated (HippoCanvasBox) 1299865885.754301 WARNING root: No gtk.AccelGroup in the top level window. 1299865885.757993 WARNING root: No gtk.AccelGroup in the top level window. ** (sugar-activity:1505): DEBUG: Got client ID "10c6692be3a5190acd12998658858572110013730001" ** (sugar-activity:1505): DEBUG: Setting initial properties ** (sugar-activity:1505): DEBUG: Received SaveYourself(SmSaveLocal, !Shutdown, SmInteractStyleNone, !Fast) in state idle ** (sugar-activity:1505): DEBUG: Sending SaveYourselfDone(True) for initial SaveYourself ** (sugar-activity:1505): DEBUG: Received SaveComplete message in state save-yourself-done 1299866172.585172 WARNING root: No gtk.AccelGroup in the top level window. 1299866172.590108 WARNING root: .has_key() is deprecated, use 'in' 1299866176.361087 WARNING root: No gtk.AccelGroup in the top level window. 1299866176.378032 WARNING root: No gtk.AccelGroup in the top level window. 1299866176.378315 WARNING root: No gtk.AccelGroup in the top level window. Exited with status 0, pid 1505 data (None, ', mode 'w' at 0x9cf99c0>, '6c4467ac822902ed16cecfd64e97e3dc16cd0f09') Art Hunkins ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Etoys Query
Are soundfiles created in etoys available for use by other activities? Or are they only accessible within etoys projects? It would be wonderful if etoys soundfiles could be individually saved to the Journal (and the same for the output of etoy's sound editor - with its looping capacity). (It is also very nice that etoys can create both Ogg Vorbis format and wav.) If exportable to the Journal, both the FileMix and FileMixAuto activities could make good use of these files. Currently, the Record activity only produces Ogg Vorbis on Sugar 0.84, and the two other (orphaned?) activities that generate audio, TimeLapse and ShowNTell, are limited to 0.82 (and Ogg Speex). Art Hunkins ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [ASLO] Release Record-87
FWIW, I've tested both Record-87 and Record-88 on two SoaS 0.90 USB drives
created by the latest version of Fedora Live USB Creator. I've tested only
the audio record capability, and have been unable to make it work. All audio
tests were short, about 15-20 seconds in duration. (I did include a full 2
minute recording to see if this duration made any difference; it didn't.)
Everything goes well until the stop record button is clicked; at this point
the large right-angle cursor reappears, complete with rotating, circular
arrow. Record loops forever (as does the circular arrow) at this point.
In the middle of this series of tests, I updated gstreamer. This made no
difference either.
Two representative complete logs are quoted below. They include no error
messages; all conclude with an open write file. The second log followed the
gstreamer update.
Log 1:
** Message: pygobject_register_sinkfunc is deprecated (GstObject)
** Message: pygobject_register_sinkfunc is deprecated (HippoCanvasBox)
1298230640.495337 WARNING root: No gtk.AccelGroup in the top level window.
1298230640.499099 WARNING root: No gtk.AccelGroup in the top level window.
** (sugar-activity:1581): DEBUG: Got client ID
"108a40cedb27387dc512982306405933810014250001"
** (sugar-activity:1581): DEBUG: Setting initial properties
** (sugar-activity:1581): DEBUG: Received SaveYourself(SmSaveLocal,
!Shutdown, SmInteractStyleNone, !Fast) in state idle
** (sugar-activity:1581): DEBUG: Sending SaveYourselfDone(True) for initial
SaveYourself
** (sugar-activity:1581): DEBUG: Received SaveComplete message in state
save-yourself-done
1298230851.408873 WARNING root: No gtk.AccelGroup in the top level window.
1298230851.413801 WARNING root: .has_key() is deprecated, use 'in'
1298230855.088719 WARNING root: No gtk.AccelGroup in the top level window.
1298230855.106809 WARNING root: No gtk.AccelGroup in the top level window.
1298230855.107083 WARNING root: No gtk.AccelGroup in the top level window.
Exited with status 0, pid 1581 data (None, ', mode 'w'
at 0x9178e90>, '69b5229805ab25a2be14549c682c118e8b28af6e')
Log2:
** Message: pygobject_register_sinkfunc is deprecated (GstObject)
** Message: pygobject_register_sinkfunc is deprecated (HippoCanvasBox)
1298232914.204209 WARNING root: .has_key() is deprecated, use 'in'
1298232914.437015 WARNING root: No gtk.AccelGroup in the top level window.
1298232914.440554 WARNING root: No gtk.AccelGroup in the top level window.
** (sugar-activity:1520): DEBUG: Got client ID
"101d582495709faaed12982329145604940013740001"
** (sugar-activity:1520): DEBUG: Setting initial properties
** (sugar-activity:1520): DEBUG: Received SaveYourself(SmSaveLocal,
!Shutdown, SmInteractStyleNone, !Fast) in state idle
** (sugar-activity:1520): DEBUG: Sending SaveYourselfDone(True) for initial
SaveYourself
** (sugar-activity:1520): DEBUG: Received SaveComplete message in state
save-yourself-done
1298233085.909043 WARNING root: No gtk.AccelGroup in the top level window.
1298233085.909324 WARNING root: No gtk.AccelGroup in the top level window.
Exited with status 0, pid 1520 data (None, ', mode 'w'
at 0x9464700>, dbus.ByteArray('69b5229805ab25a2be14549c682c118e8b28af6e',
variant_level=1))
Summary: I've still to identify a version of Record that produces audio (Ogg
Vorbis) recordings with any SoaS higher than Strawberry (0.84). (This test
confirms my previously registered bug reports.)
Art Hunkins
- Original Message -
From: "Daniel Drake"
To: "Peter Robinson"
Cc:
Sent: Wednesday, February 02, 2011 5:15 PM
Subject: Re: [Sugar-devel] [ASLO] Release Record-87
On 2 February 2011 18:30, Peter Robinson wrote:
What is the current recommended version of Record at the moment? And
what gst does this one need? Would it be useful to have it in the
rawhide nightly tests to allow for broader testing?
Yes, it would be useful to have further testing. This is definitely
the version going forward. It requires gstreamer-0.10.25 or newer.
Daniel
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [ASLO] Release FileMixAuto-1
Many thanks to James Cameron for help with a particularly thorny problem relative to the Csound API, about which I understand nothing. I really appreciate how many of you developers have stepped up to help me with my various Activities, when I've run into problems beyond my expertise. Your suggestions have been invaluable - and productive. Art Hunkins - Original Message - From: "Sugar Labs Activities" To: Sent: Wednesday, February 16, 2011 11:18 AM Subject: [Sugar-devel] [ASLO] Release FileMixAuto-1 Activity Homepage: http://activities.sugarlabs.org/addon/4402 Sugar Platform: 0.82 - 0.90 Download Now: http://activities.sugarlabs.org/downloads/file/27219/filemixauto-1.xo Release notes: Sugar Labs Activities http://activities.sugarlabs.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] mime types when moving files from journal to usb
FWIW, I've experienced no problems simply copying my activities into the Activities directory (from a USB drive). cp -r does just fine. Art Hunkins - Original Message - From: Erik Blankinship To: Sugar Devel Sent: Monday, February 14, 2011 1:36 PM Subject: Re: [Sugar-devel] mime types when moving files from journal to usb On Sat, Feb 12, 2011 at 8:18 PM, Erik Blankinship wrote: On Fri, Feb 11, 2011 at 4:17 PM, Sascha Silbe wrote: Excerpts from Erik Blankinship's message of Fri Feb 11 21:08:20 +0100 2011: > I noticed there were two svg icons in the physics activity directory: > application-x-physics-project.svg and activity-physics.svg. > > Is there now a way to assign an icon to the files generated/used by my > activity based on their extension type? You already discovered that way. If you ship your icons as activity/-.svg Sugar will automatically install them [1]. Thank you for your help as I try to get this to work. I must be doing something wrong with mimetypes.xml. Here is a very small activity that let's you click a button to save your game state. https://github.com/jedierikb/supes.activity Things broken with this activity: (1) The icon application-x-supes-saved.svg is not used in the journal for saved game files. (2) Activity instance files dragged to usb are not given the extension *.superduper (3) Saved game files dragged to usb are not given the extension *.superduper_saved [note: trying this on olpc 10.1.3, sugar 84, but would like it to work with sugar 84+] Got this working with the help of alsroot on #sugar (thx!). Here are some notes for future developers and documenters: You cannot just copy your activity into the ~/Activities directory. You have to install it as a .xo bundle or using 'setup.py install' (note that the latter is tricky as the command might get your paths messed up). This installation step will create a file --> ~/.local/share/mime/packages/.xml -- ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [ASLO] Release Record-87
I, for one, do care. I'm very much looking forward to when Record, in Sugar post-0.84, will output ogg/vorbis audio - in some kind of standard release. (I'm not aware of any version of Record that does so.) I gather that this release doesn't meet the above criteria. (I tried Anish's v87, and IIRC, it didn't work off the shelf for me.) Is the gstreamer you mention perhaps available via yum upgrade? Art Hunkins - Original Message - From: "Daniel Drake" To: Sent: Wednesday, February 02, 2011 1:26 PM Subject: Re: [Sugar-devel] [ASLO] Release Record-87 On 2 February 2011 18:21, Sugar Labs Activities wrote: Activity Homepage: http://activities.sugarlabs.org/addon/4081 Sugar Platform: 0.90 - 0.90 Download Now: http://activities.sugarlabs.org/downloads/file/27200/record-87.xo This should probably not be marked public because it requires a newer gstreamer version than what is specified by the sugar platform, and because it's an experimental release. Not sure if anyone cares... Daniel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Fw: Help Request - Python Timer
Still having trouble with a timer in Python.
Can anyone come up with a couple of lines of Python code that will let me
know when an already-playing csd has finished, so I can call something else?
(I assume it will call the Csound Python API; and, FWIW, csndsugui is
available.)
Art Hunkins
- Original Message -
From: "Art Hunkins"
To:
Sent: Tuesday, January 25, 2011 8:58 PM
Subject: Help Request - Python Timer
I'd like help to create a timer in my activity.
The following code works fine. A callback button alternately selects START
and STOP options in playcsd() (only crucial lines of code are included):
import csndsugui
from timeit import Timer
self.p = False
def playcsd(self, widget):
if self.p == False:
self.p = True
self.but.child.set_label("STOP !")
else:
self.p = False
self.but.child.set_label("START !")
self.but = self.w.cbbutton(self.b7, self.playcsd, "START !")
I need to add timer code that will call playcsd() after a specified time
period (here, 30 seconds), as an option to pressing the callback button. I
thought the following added code should work, but it doesn't. No errors
are reported, but the desired switch to START (call to playcsd() with
self.p == True) doesn't happen either. (The code follows immediately the
last line above):
if self.p == True:
self.t = Timer(30.0, self.playcsd(self.but))
self.t = start()
Art Hunkins
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Help Request - Python Timer
I'd like help to create a timer in my activity.
The following code works fine. A callback button alternately selects START
and STOP options in playcsd() (only crucial lines of code are included):
import csndsugui
from timeit import Timer
self.p = False
def playcsd(self, widget):
if self.p == False:
self.p = True
self.but.child.set_label("STOP !")
else:
self.p = False
self.but.child.set_label("START !")
self.but = self.w.cbbutton(self.b7, self.playcsd, "START !")
I need to add timer code that will call playcsd() after a specified time
period (here, 30 seconds), as an option to pressing the callback button. I
thought the following added code should work, but it doesn't. No errors are
reported, but the desired switch to START (call to playcsd() with self.p ==
True) doesn't happen either. (The code follows immediately the last line
above):
if self.p == True:
self.t = Timer(30.0, self.playcsd(self.but))
self.t = start()
Art Hunkins
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] New Dextrose 2 build: os438dx
Bernie, I wish I had the technical wherewithall to offer a (partial) fix for Record. Unfortunately, it's beyond me; sorry. Art Hunkins - Original Message - From: "Bernie Innocenti" To: "Art Hunkins" Cc: "Sugar Devel" Sent: Monday, January 17, 2011 7:53 PM Subject: Re: [Sugar-devel] New Dextrose 2 build: os438dx On Mon, 2011-01-10 at 13:04 -0500, Art Hunkins wrote: Bernie, Thanks for this info. I can report that Record-87 acts like v86 in that it does not allow for audio recording. In both cases, when you hit Stop following recording, the activity seems to get lost during the save process and never reemerges. You can close the activity, but that's all. FWIW, I've copied the logs for both v86 and v87. One difference I noted is that the v87 activity icon gets stuck in "Starting..", whereas I don't think this is the case with v86. It looks like both versions saved correctly and then got sidetracked. (I gave both runs several minutes or more time to "recover" from saving.) I continue to be very concerned about Record because, to my knowledge, *with versions of SoaS higher than Strawberry*, no Record produces Ogg Vorbis sound recordings (one or two produce Ogg Speex, which of course are both of lower sound quality, and are not handled by Csound). For certain, starting with Record-76, *all* should produce Ogg Vorbis. If you come up with a patch, we'll include it in Dextrose. We already have a forked version to fix the UI layout, it can't hurt to have this bug fixed as well. -- // Bernie Innocenti - http://codewiz.org/ \X/ Sugar Labs - http://sugarlabs.org/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Read Only ? (Fedora-14-i686-Live-SoaS)
Live USB Creator 3.9.3 works fine with SoaS 4 (Fedora-14) and recent nightly builds, but not for SoaS 1 through 3. With SoaS 1-3, booting halts at the SYXLINUX screen with multiple iterations of: ()esamenu.c32: not a COM32R image Boot:_ I can't determine the first character above, as it is off my screen. You can type: linux0 at the Boot prompt and continue normally (as with 3.9.2), and you don't need to press SHIFT during boot to do this. Live USB Creator 3.9 works with SoaS 1 through 3 correctly. Art Hunkins - Original Message - From: "Peter Robinson" To: "Walter Bender" Cc: "HARUN KARADOGAN" ; Sent: Friday, January 07, 2011 11:24 AM Subject: Re: [Sugar-devel] Read Only ? (Fedora-14-i686-Live-SoaS) On Fri, Jan 7, 2011 at 4:17 PM, Walter Bender wrote: On Thu, Jan 6, 2011 at 11:54 AM, Peter Robinson wrote: On Tue, Dec 28, 2010 at 4:20 PM, HARUN KARADOGAN wrote: Hi, I tried SoaS on usb-stick Fedora Spin-(Fedora-14-i686-Live-SoaS), This sugar environment is read-only ? Is it possible that changes stay permanently on usb ? Just to let you know that a new liveusb-creator has now been released to support Fedora 4 and SoaS 4. You can get it from here http://lewk.org/blog/liveusb-creator-3.9.3.html :) Does anyone know: * Is this the same as the one at https://fedorahosted.org/liveusb-creator/#Download ? Yes. * Does it work for older versions of Fedora/SoaS ? Not sure. thanks. -walter Cheers, Peter ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- Walter Bender Sugar Labs http://www.sugarlabs.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] New Dextrose 2 build: os438dx
Bernie, Thanks for this info. I can report that Record-87 acts like v86 in that it does not allow for audio recording. In both cases, when you hit Stop following recording, the activity seems to get lost during the save process and never reemerges. You can close the activity, but that's all. FWIW, I've copied the logs for both v86 and v87. One difference I noted is that the v87 activity icon gets stuck in "Starting..", whereas I don't think this is the case with v86. It looks like both versions saved correctly and then got sidetracked. (I gave both runs several minutes or more time to "recover" from saving.) I continue to be very concerned about Record because, to my knowledge, *with versions of SoaS higher than Strawberry*, no Record produces Ogg Vorbis sound recordings (one or two produce Ogg Speex, which of course are both of lower sound quality, and are not handled by Csound). For certain, starting with Record-76, *all* should produce Ogg Vorbis. v86 log: ** Message: pygobject_register_sinkfunc is deprecated (GstObject) ** Message: pygobject_register_sinkfunc is deprecated (HippoCanvasBox) ** (sugar-activity:1453): DEBUG: Got client ID "1027b4439824e6e7941294680259835615001360" ** (sugar-activity:1453): DEBUG: Setting initial properties 1294680260.165316 WARNING root: No gtk.AccelGroup in the top level window. 1294680260.168594 WARNING root: No gtk.AccelGroup in the top level window. ** (sugar-activity:1453): DEBUG: Received SaveYourself(SmSaveLocal, !Shutdown, SmInteractStyleNone, !Fast) in state idle ** (sugar-activity:1453): DEBUG: Sending SaveYourselfDone(True) for initial SaveYourself ** (sugar-activity:1453): DEBUG: Received SaveComplete message in state save-yourself-done 1294680415.212556 WARNING root: No gtk.AccelGroup in the top level window. 1294680415.217616 WARNING root: .has_key() is deprecated, use 'in' 1294680419.427188 WARNING root: No gtk.AccelGroup in the top level window. 1294680419.427484 WARNING root: No gtk.AccelGroup in the top level window. 1294680419.439692 WARNING root: No gtk.AccelGroup in the top level window. Exited with status 0, pid 1453 data (None, ', mode 'w' at 0xa8f26a8>, '0bdd41a01716456782442307097c00bc93912004') v87 log: ** Message: pygobject_register_sinkfunc is deprecated (GstObject) ** Message: pygobject_register_sinkfunc is deprecated (HippoCanvasBox) ** (sugar-activity:1526): DEBUG: Got client ID "1027b4439824e6e7941294680786959955001363" ** (sugar-activity:1526): DEBUG: Setting initial properties 1294680787.189781 WARNING root: No gtk.AccelGroup in the top level window. 1294680787.193502 WARNING root: No gtk.AccelGroup in the top level window. ** (sugar-activity:1526): DEBUG: Received SaveYourself(SmSaveLocal, !Shutdown, SmInteractStyleNone, !Fast) in state idle ** (sugar-activity:1526): DEBUG: Sending SaveYourselfDone(True) for initial SaveYourself ** (sugar-activity:1526): DEBUG: Received SaveComplete message in state save-yourself-done 1294680787.301455 ERROR record:record.py: read_file: [Errno 2] No such file or directory: '/home/liveuser/.sugar/default/org.laptop.RecordActivity/instance/1294680787' Art Hunkins - Original Message - From: "Bernie Innocenti" To: "Art Hunkins" Cc: "Sugar Devel" ; "Daniel Drake" Sent: Monday, January 10, 2011 12:09 PM Subject: Re: [Sugar-devel] New Dextrose 2 build: os438dx On Mon, 2011-01-10 at 11:48 -0500, Art Hunkins wrote: Is an .xo bundle of Record-87 available anywhere? It's not yet posted at activities.sugarlabs.org. It's here: http://people.sugarlabs.org/anish/Record-87.xo This version contains a kludge to fix for the UI layout on Sugar 0.88 and on any non-1200x900 display. The current maintainer of Record, Daniel Drake, requested a complete rewrite of the UI, but nobody so far has had the time to work on it. At this point, I think we should just admit that the proper fix isn't going to happen anytime soon and go with the current kludge. Daniel, how do you feel about it? -- // Bernie Innocenti - http://codewiz.org/ \X/ Sugar Labs - http://sugarlabs.org/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] New Dextrose 2 build: os438dx
Is an .xo bundle of Record-87 available anywhere? It's not yet posted at activities.sugarlabs.org. Art Hunkins - Original Message - From: "Bernie Innocenti" To: "Dextrose" Cc: "OLPC Devel" ; "Sugar Devel" Sent: Saturday, January 08, 2011 11:19 PM Subject: [Sugar-devel] New Dextrose 2 build: os438dx This release of Dextrose 2 is intended for beta testing. Images for the XO-1 and XO-1.5 can be downloaded here: http://wiki.sugarlabs.org/go/Dextrose I've not bothered uploading GNOME-enabled images, since Paraguay does not use it. I could be convinced to generate them if it's needed by a deployment for evaluation purposes only. The major highlight in this release is a simple automated updater based on yum which will hopefully enable us to deploy small updates effortlessly. The final release should be ready by Feb 22, when schools reopen in Paraguay, and if the updater works well we'll be able to fix any remaining bugs post-release. This build also includes a refresh of the new activity updater which supports the "OLPC microformat" protocol. Please test both these features vigorously. This release is missing several Sugar fixes that went into OLPC 10.1.3 over the last weeks. The queue of patches waiting to be merged in Dextrose is quite long and new features have to take precedence so they can get tested early on. We also have some small features that we hope to merge in time for this release. Consult the todo list for more information. === Changes === * Yum updater (alsroot, m_anish) * Notification system (tch) * Refresh activity updater (m_anish) * Revert to old build naming scheme, to avoid confusing users (bernie) === Updated activities === * Abacus-19 * Arithmetic-2 * Calculate-35 * Chat-69 * Distance-21 * Edit-8 * FotoToon-5 * Implode-10 * IRC-8 * Jukebox-20 * Labyrinth-11 * Maze-6 * Measure-32 * Memorize-36 * Paint-30 * Physics-8 * Pippy-38 * Record-87 * Speak-19 * TurtleArt-105 * VisualMatch-27 * Write-72 === Updated OS packages === * bitfrost-1.0.10-3.fc11.i586 * bootfw-q3a62-1.unsigned.i386 * etoys-4.0.2340-2.noarch * kernel-2.6.31_xo1.5-20101222.1243.1.olpc.7b21b8f27f2887b.i586 * kernel-firmware-2.6.31_xo1.5-20101222.1243.1.olpc.7b21b8f27f2887b.i586 * olpc-bootanim-2.12-5.dxo4.fc11.i586 * olpc-contents-2.6-1.fc11.i586 * olpc-kbdshim-16-1.fc11.i586 * olpc-powerd-32-1.fc11.i586 * olpc-powerd-dbus-32-1.fc11.i586 * olpc-runin-tests-0.9.43-1.noarch * olpc-update-2.23-1.fc11.noarch * olpc-utils-1.0.37-1.fc11.i586 * squeak-vm-3.10.5-4.fc11.i586 * xorg-x11-drv-openchrome-0.2.990-2.fc11.i586 * xorg-x11-drv-sisusb-0.9.1-2.fc11.i586 * xulrunner-1.9.1.9-2.fc11.i586 -- // Bernie Innocenti - http://codewiz.org/ \X/ Sugar Labs - http://sugarlabs.org/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Read Only ? (Fedora-14-i686-Live-SoaS)
I've tested. The new Fedora Live USB Creator (3.9.3) only correctly produces SoaS Mango (Fedora14). With Fedora13, as well as SoaS Strawberry, Blueberry and Mirabelle, it produces a boot error at the SYSLINUX screen similar to what the previous Live USB Creator did with Fedora14. Strangely, too, you can still type "linux0" at the Boot: prompt to move forward - and this time, without having to hold a SHIFT key down. Art Hunkins - Original Message - From: "Walter Bender" To: "Peter Robinson" Cc: "HARUN KARADOGAN" ; Sent: Friday, January 07, 2011 11:44 AM Subject: Re: [Sugar-devel] Read Only ? (Fedora-14-i686-Live-SoaS) On Fri, Jan 7, 2011 at 11:24 AM, Peter Robinson wrote: On Fri, Jan 7, 2011 at 4:17 PM, Walter Bender wrote: On Thu, Jan 6, 2011 at 11:54 AM, Peter Robinson wrote: On Tue, Dec 28, 2010 at 4:20 PM, HARUN KARADOGAN wrote: Hi, I tried SoaS on usb-stick Fedora Spin-(Fedora-14-i686-Live-SoaS), This sugar environment is read-only ? Is it possible that changes stay permanently on usb ? Just to let you know that a new liveusb-creator has now been released to support Fedora 4 and SoaS 4. You can get it from here http://lewk.org/blog/liveusb-creator-3.9.3.html :) Does anyone know: * Is this the same as the one at https://fedorahosted.org/liveusb-creator/#Download ? Yes. Great. I see someone has already updated the 'Download" page in the wiki to reflect the renewed availability of liveusb-creator, which was why I was asking. * Does it work for older versions of Fedora/SoaS ? Not sure. I'll do some testing. regards. -walter thanks. -walter Cheers, Peter ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- Walter Bender Sugar Labs http://www.sugarlabs.org -- Walter Bender Sugar Labs http://www.sugarlabs.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Read Only ? (Fedora-14-i686-Live-SoaS)
Actually, for me, installing Fedora-14-i686-Live-SoaS.iso to a USB drive via Fedora liveusb-creator does work. But it is tricky, and requires some extra work. And yes, it is important to specify persistent storage (I select all additional available storage) when creating the stick. As discussed some months ago on this list, the trick is to immediately press and hold down the SHIFT key upon selecting boot from USB. If you are lucky, the SYSLINUX display will come up with a second line: Boot: After releasing SHIFT, type: linux0 The dot cursor will move to the following line and several seconds later your USB stick will boot as you expect. (Unfortunately, you need to repeat all this each time you boot.) I wonder if anyone is looking into this issue? (And whose issue is it?) The current condition renders 0.90 SoaS highly problemmatic - especially for Windows users. Art Hunkins - Original Message - From: HARUN KARADOGAN To: Sugar-devel@lists.sugarlabs.org Sent: Wednesday, December 29, 2010 4:28 AM Subject: Re: [Sugar-devel] Read Only ? (Fedora-14-i686-Live-SoaS) I used "Fedora liveusb-creator" for Fedora-14-i686-Live-SoaS.iso, but It did not work. So I am using "unetbootin-windows-494" for creating usb-stick, but this time changes do not stay. Could you explain "set a non-zero value to the persistent storage option when you create the stick" ? From: Walter Bender [mailto:walter.ben...@gmail.com] Sent: Tuesday, December 28, 2010 6:23 PM To: HARUN KARADOGAN Cc: Sugar-devel@lists.sugarlabs.org Subject: Re: [Sugar-devel] Read Only ? (Fedora-14-i686-Live-SoaS) On Tue, Dec 28, 2010 at 11:20 AM, HARUN KARADOGAN wrote: Hi, I tried SoaS on usb-stick Fedora Spin-(Fedora-14-i686-Live-SoaS), This sugar environment is read-only ? Is it possible that changes stay permanently on usb ? You need to set a non-zero value to the persistent storage option when you create the stick. (Alas, zero is the default value.) -walter Regards, Harun ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- Walter Bender Sugar Labs http://www.sugarlabs.org -- ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] git problems (reprise)
Sasha, I appreciate this helpful clarification re: git. Indeed I was unaware that one normally ran an activity from the local repository. This does simplify things. I'm also glad that this material is now among the revised git information available at Sugarlabs. Art Hunkins - Original Message - From: "Sascha Silbe" To: "Art Hunkins" ; "Sugar-devel" Sent: Wednesday, December 29, 2010 6:49 AM Subject: Re: [Sugar-devel] git problems (reprise) ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] git problems (reprise)
James,
Thanks for your attention to my added comments.
I'm sure your observation is correct.
No, I was not referring to a passphrase of the SSH key. I've never used a
passphrase; it's one of those items that, as a beginner, I've always thought
of as an unnecessary complication. (And I've the impression that the current
discussion tends to validate this thought.)
My comment about the necessity of logging in was prompted by my frustration
at being "hung up (on) unexpectedly" most times when I tried to do something
with git - I presume, now, mostly when *pushing* to gitorious. And this
turned out to be because I had neglected to log in. Maybe I'm touchy, but
one of the more frustrating things in life is to be "hung up on" -
particularly with no explanation (or an impenetrable one).
Perhaps the message needs to be changed to the necessity of logging in when
*pushing* to gitorious (and the message relocated). Please feel free to
change this yourself, or to tell me precisely what needs to change and I'll
happily do it.
Art Hunkins
- Original Message -
From: "James Cameron"
To: "Art Hunkins"
Cc: "Walter Bender" ;
Sent: Thursday, December 30, 2010 9:56 PM
Subject: Re: [Sugar-devel] git problems (reprise)
Art, you added a comment that logging in to gitorious was required for
*every* step in the tutorial. That's not how it worked for me.
Is it possible that you are referring to a passphrase of the SSH key?
If so, you can delete the passphrase of the SSH key and you won't be
prompted. You can delete the passphrase by changing it to an empty
passphrase.
The command to change the passphrase of an SSH key is
ssh-keygen -p -f ${FILE}
For example:
$ ssh-keygen -p -f .ssh/id_dsa
Enter old passphrase:
Enter new passphrase (empty for no passphrase):
Enter same passphrase again:
Your identification has been saved with the new passphrase.
--
James Cameron
http://quozl.linux.org.au/
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] git problems (reprise)
Walter et al.- I did take the opportunity to add some comments/clarifications to the Git FAQ. If I've misled anywhere, I hope to be corrected. As it stands now, I feel it is a good beginner tutorial - one that just about anyone could follow fairly easily. Thanks for both your help and encouragement, Walter - and all others who jumped in. Art Hunkins - Original Message - From: Walter Bender To: James Cameron Cc: Art Hunkins ; Sugar-devel@lists.sugarlabs.org Sent: Wednesday, December 29, 2010 9:33 AM Subject: Re: [Sugar-devel] git problems (reprise) On Wed, Dec 29, 2010 at 1:03 AM, James Cameron wrote: On Tue, Dec 28, 2010 at 10:16:55PM -0500, Art Hunkins wrote: > My sources of gitorious info were: the Activity Team/Git FAQ, the > Activity Team /Git Tutorial, and Importing your project from OLPC. > > I found the material disorganized, unnecessarily abstruse and > technical, and not at all user-friendly (at least for the beginner). I agree. As I used it, I learned to use other sources of guidance instead. The material on sugarlabs.org and laptop.org presumes too much foreknowledge. > Take, for example, the Git Tutorial - which I expected to be the most > helpful of the above: three-quarters of the material is nonessential, > and the info on creating an account and SSH key are grossly > inadequate. Furthermore, there is no treatment of anything but the git > *init* procedure - nothing about creating a local depository through > pulling from gitorious (my particular issue). Taking your feedback into account, I've reworked the page. http://wiki.sugarlabs.org/go/Activity_Team/Git_Tutorial Please review, comment, or edit accordingly. I made a few changes... the download file system is a bit different than you described. I also did a first pass at reworking the description of git on the Activity_Team ;page itself (incorporating Sascha's text and pointing people towards your tutorial.) Art, if you could add more clarity there, it may help the next person who comes along. -walter -- James Cameron http://quozl.linux.org.au/ -- Walter Bender Sugar Labs http://www.sugarlabs.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] git problems (reprise)
Walter, My sources of gitorious info were: the Activity Team/Git FAQ, the Activity Team/Git Tutorial, and Importing your project from OLPC. I found the material disorganized, unnecessarily abstruse and technical, and not at all user-friendly (at least for the beginner). For the newbee, only the essentials are needed, and clarity of expression and direction are crucial. This, particularly. for those of us whose knowledge of Linux and Sugar is elementary. Take, for example, the Git Tutorial - which I expected to be the most helpful of the above: three-quarters of the material is nonessential, and the info on creating an account and SSH key are grossly inadequate. Furthermore, there is no treatment of anything but the git *init* procedure - nothing about creating a local depository through pulling from gitorious (my particular issue). Specifically, the nuts and bolts of a practical, understandable series of steps to accomplish simple objectives are lacking. Solving these problems by furnishing down-to-earth practical instructions would be of great help. (I also know that this is somewhat of a challenge in an open-source environment, so I don't expect miracles. Often, as in my case, listservs such as this one - and generous souls such as you - are the principal resource for newbees. And thank goodness for yawl (I'm from North Carolina - aka the South). Art Hunkins - Original Message - From: Walter Bender To: Art Hunkins Cc: James Cameron ; Sugar-devel@lists.sugarlabs.org Sent: Tuesday, December 28, 2010 4:49 PM Subject: Re: [Sugar-devel] git problems (reprise) On Tue, Dec 28, 2010 at 3:47 PM, Art Hunkins wrote: James, Thanks for your wonderful, clear and understandable instructions. They work wonderfully and all my problems are gone. BTW, your procedure is *much* more user-friendly (and simpler) than any of the git material on the wiki. It would really be helpful to have your easy step-by-step available online: perhaps one procedure for initial commit, and one for followups (like for my case). Of all the challenges I've faced with Linux/Sugar, perhaps gitorious has been the greatest and most frustrating. Can you tell me where in the wiki you were finding confusing instructions so we can update them? -walter Please advise me on one point: once the local repo is established (filemix.git), what's the simplest way to copy all my (revised) activity files (including subdirectory) to filemix.git? When preparing a new push, I've often forgotten just which files I've modified, and don't wish to omit any (and so would use git add . for the following step). Let's say that the source files were in FileMix.activity and that both FileMix.activity and filemix.git were in the Activities folder. Once again, many thanks. Art Hunkins - Original Message ----- From: "James Cameron" To: "Art Hunkins" Cc: Sent: Monday, December 27, 2010 11:09 PM Subject: Re: [Sugar-devel] git problems (reprise) On Mon, Dec 27, 2010 at 10:27:26PM -0500, Art Hunkins wrote: then: git init This is where you went wrong. You've created an entirely new repository instead of cloning the existing one. git add git status the console output then picks up and tells the rest of the story: [liveu...@localhost FileMix.activity]$ git commit -a -m"Version 4 changes: ObjectChooser and Sugar-version ID reworked" [master (root-commit) 3b7e345] Version 4 changes: ObjectChooser and Sugar-version ID reworked 3 files changed, 494 insertions(+), 0 deletions(-) create mode 100755 FileMixReadMe.txt create mode 100755 activity/activity.info create mode 100755 filemix.py [liveu...@localhost FileMix.activity]$ git push gitori...@git.sugarlabs.org:filemix/mainline.git To gitori...@git.sugarlabs.org:filemix/mainline.git ! [rejected]master -> master (non-fast-forward) error: failed to push some refs to 'gitori...@git.sugarlabs.org:filemix/mainline.git' To prevent you from losing history, non-fast-forward updates were rejected Merge the remote changes before pushing again. See the 'non-fast-forward' section of 'git push --help' for details. As you guess, the push is where the problem happened. The cause of this error is that you are trying to push from a repository that doesn't have the same history of change. This is because your new local repository is totally unrelated to the remote repository. It is unrelated because it was created with "git init" instead of "git clone". You might do one of these things: 1. clone into a new directory, c
Re: [Sugar-devel] git problems (reprise)
James,
Thanks for your wonderful, clear and understandable instructions. They work
wonderfully and all my problems are gone.
BTW, your procedure is *much* more user-friendly (and simpler) than any of
the git material on the wiki. It would really be helpful to have your easy
step-by-step available online: perhaps one procedure for initial commit, and
one for followups (like for my case). Of all the challenges I've faced with
Linux/Sugar, perhaps gitorious has been the greatest and most frustrating.
Please advise me on one point: once the local repo is established
(filemix.git), what's the simplest way to copy all my (revised) activity
files (including subdirectory) to filemix.git? When preparing a new push,
I've often forgotten just which files I've modified, and don't wish to omit
any (and so would use git add . for the following step). Let's say that the
source files were in FileMix.activity and that both FileMix.activity and
filemix.git were in the Activities folder.
Once again, many thanks.
Art Hunkins
- Original Message -
From: "James Cameron"
To: "Art Hunkins"
Cc:
Sent: Monday, December 27, 2010 11:09 PM
Subject: Re: [Sugar-devel] git problems (reprise)
On Mon, Dec 27, 2010 at 10:27:26PM -0500, Art Hunkins wrote:
then:
git init
This is where you went wrong. You've created an entirely new repository
instead of cloning the existing one.
git add
git status
the console output then picks up and tells the rest of the story:
[liveu...@localhost FileMix.activity]$ git commit -a -m"Version 4
changes: ObjectChooser and Sugar-version ID reworked"
[master (root-commit) 3b7e345] Version 4 changes: ObjectChooser and
Sugar-version ID reworked
3 files changed, 494 insertions(+), 0 deletions(-)
create mode 100755 FileMixReadMe.txt
create mode 100755 activity/activity.info
create mode 100755 filemix.py
[liveu...@localhost FileMix.activity]$ git push
gitori...@git.sugarlabs.org:filemix/mainline.git
To gitori...@git.sugarlabs.org:filemix/mainline.git
! [rejected]master -> master (non-fast-forward)
error: failed to push some refs to
'gitori...@git.sugarlabs.org:filemix/mainline.git'
To prevent you from losing history, non-fast-forward updates were
rejected
Merge the remote changes before pushing again. See the
'non-fast-forward'
section of 'git push --help' for details.
As you guess, the push is where the problem happened. The cause
of this error is that you are trying to push from a repository that
doesn't have the same history of change. This is because your new local
repository is totally unrelated to the remote repository. It is
unrelated because it was created with "git init" instead of "git clone".
You might do one of these things:
1. clone into a new directory, copy those changed files into it,
commit, and push again,
2. understand the difference between the history of your local
repository and the remote repository, and adjust it somehow, such as
with a merge before a push.
I recommend (1) above. I don't recommend (2), although it is possible,
it is not necessary.
I'm happy to try to help you through this, and I've cloned the
repository git://git.sugarlabs.org/filemix/mainline.git so that I can be
prepared to answer questions.
Expanding on (1) above:
git clone gitori...@git.sugarlabs.org:filemix/mainline.git filemix.git
cd filemix.git
cp ${THOSE_FILES} .
git add FileMixReadMe.txt activity/activity.info filemix.py
git commit -m 'Version 4 changes: ObjectChooser and Sugar-version ID
reworked'
git push
--
James Cameron
http://quozl.linux.org.au/
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] git problems (reprise)
I can't quite believe I find myself fighting gitorious again (tooth and nail). Please help. I'm logged in; my ssh keys are OK. Earlier versions of FileMix exist in gitorious. I'm trying to add v4. (I had trouble adding v3 as well, and don't know whether I succeeded then either. I've the feeling gitorious only has v2). I made a fresh directory for FileMix and copied all of version 4 to it. then: git init git add git status the console output then picks up and tells the rest of the story: [liveu...@localhost FileMix.activity]$ git commit -a -m"Version 4 changes: ObjectChooser and Sugar-version ID reworked" [master (root-commit) 3b7e345] Version 4 changes: ObjectChooser and Sugar-version ID reworked 3 files changed, 494 insertions(+), 0 deletions(-) create mode 100755 FileMixReadMe.txt create mode 100755 activity/activity.info create mode 100755 filemix.py [liveu...@localhost FileMix.activity]$ git push gitori...@git.sugarlabs.org:filemix/mainline.git To gitori...@git.sugarlabs.org:filemix/mainline.git ! [rejected]master -> master (non-fast-forward) error: failed to push some refs to 'gitori...@git.sugarlabs.org:filemix/mainline.git' To prevent you from losing history, non-fast-forward updates were rejected Merge the remote changes before pushing again. See the 'non-fast-forward' section of 'git push --help' for details. What in the world is going on? Art Hunkins ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Object Chooser (selecting user-created audio objects from the Journal)
Walter, Once again, thanks for creating this page. As is clear from my last message to this list (and Aleksey's helpful reply), a couple of small changes need to be made to the page. (I tried to do this myself, but now realize these pages can only be edited by administrators.) The two needed changes, as previously discussed are: 1) replace the final code segment with: def choose(self, widget): chooser = ObjectChooser(parent=self, what_filter=mime.GENERIC_TYPE_AUDIO) result = chooser.run() if result == gtk.RESPONSE_ACCEPT: self.jobject = chooser.get_selected_object() self.path = str(self.jobject.get_file_path()) else: self.jobject = None self.path1 = "0" 2) change the reference to "self.name1" in the last paragraph to "self.path". Thanks so much - Art Hunkins P.S. My latest FileMix (FileMix-4.xo) incorporates these changes - in the file filemix.py. Actually, there are *4* object chooser methods included, triggered by a set of 4 callback buttons. (For those interested, I've made the source code visible online for this version.) - Original Message - From: "Walter Bender" To: "Art Hunkins" Cc: Sent: Wednesday, December 22, 2010 8:58 AM Subject: Re: [Sugar-devel] Object Chooser (selecting user-created audio objects from the Journal) I created http://wiki.sugarlabs.org/go/Activity_Team/Object_Chooser with both your and Aleksey's code and comments. -walter -- Walter Bender Sugar Labs http://www.sugarlabs.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Object Chooser (selecting user-created audio objects from the Journal)
Aleksey: Thanks so much for your suggestions/corrections. And Walter: thanks
equally for posting these ideas to the wiki.
Aleksey: Please take a look at this further refinement of the Chooser
method:
def choose(self, widget):
chooser = ObjectChooser(parent=self, what_filter=mime.GENERIC_TYPE_AUDIO)
result = chooser.run()
if result == gtk.RESPONSE_ACCEPT:
self.jobject = chooser.get_selected_object()
self.path = str(self.jobject.get_file_path())
else:
self.jobject = None
self.path = "0"
It is essential that if the Journal is closed without a selection, that the
default values (for self.jobject and self.path) be reset.
Also, the user needs to be able to change his mind - to make a second
selection, as well as to revert to the default.
Is the above code a fairly good way of achieving this?
Also, I'd like to find a way to limit the selected Journal object to an
*audio* file, one included in mime.GENERIC_TYPE_AUDIO - and (likewise) to
revert to default values if such a selection is not made.
Do you see a fairly simple way of making such a "filter"? I'd rather not get
into specifying all specific file types (except, if feasible, to rule out
ogg speex).
Once again, thanks for your insights.
Art Hunkins
- Original Message -
From: "Aleksey Lim"
To: "Art Hunkins"
Cc:
Sent: Wednesday, December 22, 2010 1:22 AM
Subject: Re: [Sugar-devel] Object Chooser (selecting user-created audio
objects from the Journal)
On Tue, Dec 21, 2010 at 09:54:24PM -0500, Art Hunkins wrote:
I'd like to thank all those who helped me get Object Chooser in the
Journal
up and running in my FileMix activity. I'd also like to share my results,
in
case the code could be helpful to others.
Excerpts follow:
from sugar.graphics.objectchooser import ObjectChooser
from sugar import mime
self.jname1 = "0"
self.jobject1 = 0
if os.path.exists("/etc/fedora-release"):
release = open("/etc/fedora-release").read()
if release.find("OLPC release 9 ") == -1:
# Insert here code relevent to Sugar 0.84 and higher
# I use this to only display Object Chooser callback buttons only for >=
0.84
# Clicking one of the displayed buttons calls the choose1 method
def choose1(self, widget):
chooser = ObjectChooser(parent=self,
what_filter=mime.GENERIC_TYPE_AUDIO)
result = chooser.run()
if result == gtk.RESPONSE_ACCEPT:
jobject = chooser.get_selected_object()
if jobject and jobject.file_path:
self.jobject1 = jobject
self.jname1 = str(jobject.get_file_path())
else:
self.jname1 = "0"
Random observations:
1) I exclude Sugar 0.82 for two reasons (which means, unfortunately, "no
user soundfiles for 0.82"):
Another useful way to check sugar version is:
try:
from jarabe import config
version = [int(i) for i in config.version.split('.')][:2]
except ImportError:
version = [0, 82]
if version >= [0, 84]:
...
a) its version of Object Chooser does not allow filtering for the audio
mime type;
b) Sugar 0.82's Csound (5.08) - or more specifically its version of
libsndfile - does not handle ogg vorbis soundfiles, the type that the
Record
activity creates. Record is the most likely/accessible means that
children
would use to create their own soundfiles. (The whole idea behind using
Object Chooser here is to select user files that have been placed in the
Journal [as Record does by default] for performance in FileMix.)
c) In addition, earlier versions of Record (soundfiles; even the recent versions of Csound (actually, libsndfile) do
not
handle this (lo-fi) format.
I found that a search for "OLPC release 9 " in /etc/fedora-release
identifies all current 0.82 incarnations of Sugar of which I'm aware.
2) jname1 stores the soundfile name (complete path); jobject1 stores the
object itself. This is key to being able (in Csound) to locate and load
the
selected soundfile. jname1 is then a channel opened to send the named
soundfile to Csound.
You can make code more elegant by using only jobject1
(and None initializer):
self.jobject1 = None
...
if result == gtk.RESPONSE_ACCEPT:
...
self.jobject1 = jobject
...
if self.jobject1 is not None:
path = str(self.jobject1.get_file_path())
...
3) If the user closes the Object Chooser box instead of clicking on a
sound
object, the result is not accepted, and jname1 reverts to "0" - which is
a
flag (in Csound) to revert to the default soundfile included in FileMix.
4) The str() cast for self.jname1 converts the filename to the usual path
format readable by Csound (this too is required).
Yeah, I guess it is dbus string object... maybe we need to this type
cast in sugar-toolkit code (though in most cases this casting should
happen implicitly).
Art Hunkins
[Sugar-devel] Object Chooser (selecting user-created audio objects from the Journal)
I'd like to thank all those who helped me get Object Chooser in the Journal
up and running in my FileMix activity. I'd also like to share my results, in
case the code could be helpful to others.
Excerpts follow:
from sugar.graphics.objectchooser import ObjectChooser
from sugar import mime
self.jname1 = "0"
self.jobject1 = 0
if os.path.exists("/etc/fedora-release"):
release = open("/etc/fedora-release").read()
if release.find("OLPC release 9 ") == -1:
# Insert here code relevent to Sugar 0.84 and higher
# I use this to only display Object Chooser callback buttons only for >=
0.84
# Clicking one of the displayed buttons calls the choose1 method
def choose1(self, widget):
chooser = ObjectChooser(parent=self, what_filter=mime.GENERIC_TYPE_AUDIO)
result = chooser.run()
if result == gtk.RESPONSE_ACCEPT:
jobject = chooser.get_selected_object()
if jobject and jobject.file_path:
self.jobject1 = jobject
self.jname1 = str(jobject.get_file_path())
else:
self.jname1 = "0"
Random observations:
1) I exclude Sugar 0.82 for two reasons (which means, unfortunately, "no
user soundfiles for 0.82"):
a) its version of Object Chooser does not allow filtering for the audio
mime type;
b) Sugar 0.82's Csound (5.08) - or more specifically its version of
libsndfile - does not handle ogg vorbis soundfiles, the type that the Record
activity creates. Record is the most likely/accessible means that children
would use to create their own soundfiles. (The whole idea behind using
Object Chooser here is to select user files that have been placed in the
Journal [as Record does by default] for performance in FileMix.)
c) In addition, earlier versions of Record (soundfiles; even the recent versions of Csound (actually, libsndfile) do not
handle this (lo-fi) format.
I found that a search for "OLPC release 9 " in /etc/fedora-release
identifies all current 0.82 incarnations of Sugar of which I'm aware.
2) jname1 stores the soundfile name (complete path); jobject1 stores the
object itself. This is key to being able (in Csound) to locate and load the
selected soundfile. jname1 is then a channel opened to send the named
soundfile to Csound.
3) If the user closes the Object Chooser box instead of clicking on a sound
object, the result is not accepted, and jname1 reverts to "0" - which is a
flag (in Csound) to revert to the default soundfile included in FileMix.
4) The str() cast for self.jname1 converts the filename to the usual path
format readable by Csound (this too is required).
Art Hunkins
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] UI: Advice about UI changes in Write
FWIW, this is the "font-sizing code" I ended up using in my three activities
(OurMusic, SunMoonMusic and FileMix). It is contained near the beginning of the
csndsugui.py module.
It contains an option for the user to resize text in the given activity for the
particular monitor, and sizes for OLPC (XO-1/XO-1.5), SoaS 0.84 and up. Thank
goodness, from Mirabelle upward, SoaS seems not to be changing font size.
All multiplication factors were determined empirically - by filling a screen
width with text (the starting point was the OLPC display), then seeing what
modifications were necessary for the various incarnations of SoaS.
The code works well for all versions of Sugar I've tried, as well as monitors.
def scale_font(self, widget):
font = widget.get_pango_context().get_font_description()
# The FONT DISPLAY in this activity can be resized (smaller or larger)
# by changing the value of "resize" below. "Resize" can be positive
# or negative, and is not limited to integers. A value of 1 equals a
# point in font size.
resize = 0
font_size = font.get_size() + (resize * 1024)
width = gtk.gdk.screen_width()
mult = width * .00076
if os.path.exists("/etc/olpc-release") or
os.path.exists("/etc/power/olpc-pm"):
mult = width * .00082
elif os.path.exists("/etc/fedora-release"):
release = open("/etc/fedora-release").read()
if release.find("SoaS release 1 ") != -1:
mult = width * .00132
elif release.find("SoaS release 2 ") != -1:
mult = width * .00085
elif release.find("Fedora release ") != -1:
mult = width * .00119
font.set_size(int(font_size * mult))
widget.modify_font(font)
Art Hunkins
- Original Message -
From: Gonzalo Odiard
To: sugar-devel
Sent: Saturday, December 04, 2010 11:48 AM
Subject: Re: [Sugar-devel] UI: Advice about UI changes in Write
Sascha
I understand your comments, but I think we need to prioritize the simple use
of the more useful features.
A spinbutton is not IMHO a good interface to change the zoom level, but I am
not sure, that's the reason
why I asked to the UI team. Another option is add a button to set the zoom at
Page width, or Page height,
but probably another hacker will complain about too much controls...
Gonzalo
On Sat, Dec 4, 2010 at 7:18 AM, Sascha Silbe
wrote:
Excerpts from Gonzalo Odiard's message of Fri Dec 03 14:00:58 +0100 2010:
> You can increment/decrement the zoom with Ctrl + / - to any level.
Is that discoverable? What are the increments (step size)? How fast is
it?
It usually takes me only very few tries to choose the correct zoom level
by entering a number (good first guess + something similar to binary
search). If I can only single-step (in addition to the few fixed zoom
levels), it'll either be a bad match (too large increment) or take a lot
of key presses / time (fine increment => many steps).
Sascha
--
http://sascha.silbe.org/
http://www.infra-silbe.de/
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
--
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Record Activity and ogg vorbis audio?
Can someone indicate to me a version of Record that outputs ogg vorbis audio (versions >= 64 or so should) on SoaS Blueberry and higher (Sugar >= 0.86)? I can't find one. (There are various issues: some versions get hung at startup, a few output ogg speex, most of the later ones seem to record, but don't save or play back.) With Sugar 0.84, all is well: SoaS Strawberry works with v64; and both the XO-1.5 and the upgraded XO-1 work with v86. Art Hunkins ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Record and Ogg Vorbis
Daniel, Anish, et al., Could someone please tell me the first version of Record (audio) that produces Ogg Vorbis rather than Ogg Speex? Art Hunkins ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] ObjectChooser() Issue?
One more question:
This code tests for the presence of an XO-1 (thanks originally to Walter):
if os.path.exists("/sys/power/olpc-pm"):
Normally this is also a test for Sugar 0.82. I want, however, also to test
for Sugar *upgrades* on the XO-1; I don't want the same result as for 0.82
(as, for example, if 0.84 is installed).
So, do I use the same test, or do I need some other (if so, what)?
(Another way of phrasing the question: is the above essentially a hardware
or a software test?)
Art Hunkins
- Original Message -
From: "Sascha Silbe"
To: "sugar-devel"
Sent: Saturday, November 20, 2010 3:38 AM
Subject: Re: [Sugar-devel] ObjectChooser() Issue?
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] ObjectChooser() Issue?
Walter, Thanks for the note; you are quite right that ObjectChooser() indeed works in Sugar 0.82 and the XO-1. Indeed, surprisingly, it is also fast enough for my purposes. I will not use it in 0.82 for two reasons, however: 1) it lists objects on USB sticks as well as the Journal (confusing, and different from later Sugars); 2) it does not allow specification of what_filter=mime.GENERIC_TYPE_AUDIO (this feature appeared with 0.83; and is highly useful in targeting the audio objects). There's another reason as well: the version of Csound that comes with 0.82 is linked to a libsndfile that cannot be updated to handle ogg vorbis soundfiles; Csound (5.10) from 0.84 on is linked to (or can be updated) to a version of libsndfile that does. The Record activity - the activity most likely to be used by children to create their soundtracks - records ogg vorbis files only, depositing them directly in the Journal. (Unfortunately, versions of Record prior to about 66-67, use the ogg speex format, which even the more recent libsndfile doesn't handle.) So, quite a few reasons not to try to handle Journal audio objects in 0.82. FileMix is way too complex already; further complication will likely drive everyone away completely. I think I may have answered my previous question: "Feature unavailable in Sugar 0.82." Art Hunkins - Original Message - From: "Walter Bender" To: "Art Hunkins" Cc: "Sascha Silbe" ; "sugar-devel" Sent: Friday, November 19, 2010 1:13 PM Subject: Re: [Sugar-devel] ObjectChooser() Issue? On Fri, Nov 19, 2010 at 1:12 PM, Art Hunkins wrote: Sascha, Thanks to you and other members of this listserv I've now got multiple instances of ObjectChooser() running in my FileMix activity. Of course it does not work with the XO-1/Sugar 0.82, and I need to express this limitation clearly in my activity. I my experience, it does work, but so slowly as to not be of any practical use :) -walter So, is it better to say: "Feature unavailable on XO-1" or "Feature unavailable in Sugar 0.82" or what (please suggest something appropriate)? Thanks again for your help. Art Hunkins - Original Message - From: "Sascha Silbe" To: "sugar-devel" Sent: Sunday, November 14, 2010 6:00 PM Subject: Re: [Sugar-devel] ObjectChooser() Issue? ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- Walter Bender Sugar Labs http://www.sugarlabs.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] ObjectChooser() Issue?
Sascha, Thanks to you and other members of this listserv I've now got multiple instances of ObjectChooser() running in my FileMix activity. Of course it does not work with the XO-1/Sugar 0.82, and I need to express this limitation clearly in my activity. So, is it better to say: "Feature unavailable on XO-1" or "Feature unavailable in Sugar 0.82" or what (please suggest something appropriate)? Thanks again for your help. Art Hunkins - Original Message - From: "Sascha Silbe" To: "sugar-devel" Sent: Sunday, November 14, 2010 6:00 PM Subject: Re: [Sugar-devel] ObjectChooser() Issue? ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [SoaS] SoaS 4 - Mango Lassi is out.
This is the same issue I've raised twice before - with no response. I've copied Luke Macken, creator of LiveUSB Creator, as well. The problem is what has been keeping me from testing my activities with 0.90 SoaS. Can anything be done about this? Art Hunkins - Original Message - From: "David Leeming" To: "'Thomas C Gilliard'" ; "'Development of live Sugar distributions'" Cc: "'Sugar Labs Marketing'" ; "'Sugar devel'" Sent: Monday, November 15, 2010 7:08 PM Subject: Re: [Sugar-devel] [SoaS] SoaS 4 - Mango Lassi is out. Testing SOAS 4 Mango Lassi on a 32-bit PC. Image used is Fedora-14-i686-Live-SoaS.iso and installed using Fedora LiveUSB Creator 3.9.2 on a 2GB flashdrive that has been tested OK with Marabelle. I used 498 MB of persistent storage. Tried in two different computers, reformatted (FAT) and tried again. All I get is this on boot (below), it does not proceed any further.. I guess maybe I have the wrong iso or something?? SYSLINUX 3.81 2009-05-29 EBIOS Copyright (C) 1994-2009 H. Peter Alvin et al. (then nothing happens) David Leeming Solomon Islands Rural Link -Original Message- From: sugar-devel-boun...@lists.sugarlabs.org [mailto:sugar-devel-boun...@lists.sugarlabs.org] On Behalf Of Thomas C Gilliard Sent: Wednesday, 3 November 2010 5:14 p.m. To: Development of live Sugar distributions Cc: Sugar Labs Marketing; Sugar devel Subject: Re: [Sugar-devel] [SoaS] SoaS 4 - Mango Lassi is out. Great News; Fedora-14-x86_64-Live-SoaS CD Boots fine on an Apple MacBook Air with an external hp-DVD/CD usb drive. Hold "C" and tap power button keep holding the "C" key down until the blue fedora boot screen appears Select Boot (Basic Video)-second line boots to bar display Fedora 14; (Name_); Choose password for new keyring; hit cancel 6 times. F3 Ring appears Use the usb to cat 5 Air dongle ( applesmc.78) as Network Manager does not recognize the Mac Air's wireless hardware. f1 neighborhood will be full of xxx...@jabber.sugarlabs.org names To fix this go to drop down / My settings /About me. change colors and restart. On restart the names will be correct. ONLY IF you enter the key chain password you entered 1 time when you started sugar. These are known bugs http://wiki.sugarlabs.org/go/Sugar_on_a_Stick_Bugs#Current_Bugs ALSO There is a new Boot CD for Macs and computers that cannot boot from USB Boot helper CD for Fedora-14-i686-Live-SoaS: <http://www.wronkiewicz.net/soas-4-boot-test.iso> Matt On Fri, Oct 29, 2010 at 9:45 PM, Matt Wronkiewicz wrote: > If anyone else is interested, I put together a boot helper for > Mirabelle. Burned to a CD, it enabled booting a USB stick on my > MacBook Pro. The stick was partitioned with the plain old MBR format > and labeled "FEDORA". I also got both VMware Fusion and VirtualBox to > boot the USB stick using this boot helper ISO. The soas-2-boot ISO > sort of works with Mirabelle sticks, but they have different kernel > versions so modules don't load, thus no networking. That is fixed in > this build. > > <http://www.wronkiewicz.net/soas-3-boot-test.iso> > > Matt > Please Test these result on other MAC's and report here in wiki: http://wiki.sugarlabs.org/go/Talk:Sugar_on_a_Stick_release_process#Macintosh _Testing Congratulations to all Enjoy; Tom Gilliard satellit Peter Robinson wrote: Hi All, This is the non announcement announcement of the release of Sugar on a Stick 4 Mango Lassi is out. You can download both the 32 and 64 bit version from http://spins.fedoraproject.org/soas/ There's an outline of some common bugs in Fedora 14 and hence Fedora 14 outlined here https://fedoraproject.org/wiki/Common_F14_bugs Some of the notable enhancements include: - Sugar 0.90 - Support for more wireless adapters including the rtl2xxx series of adapters that are common in eee PCs - Improved Apple Mac support (still needs SoaS verification as apparently its a major problem but I could only find Fedora people to test it for me) - Quite a lot of things that I can't remember I would like to thank Sebastian, Mel, Simon, Thomas and everyone else who has contributed to this release. Cheers, Peter ___ SoaS mailing list s...@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/soas ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] ObjectChooser() Issue?
Aleksey / Sasha / James,
Despite all your valued feedback, I remain stymied.
My current jobject code:
#Declarations
self.file = [0, 0, 0, 0]
self.fileflag = ["0", "0", "0", "0"]
def choose1(self, widget):
chooser = ObjectChooser(parent=self, what_filter=mime.GENERIC_TYPE_AUDIO)
result = chooser.run()
if result == gtk.RESPONSE_ACCEPT:
jobject = chooser.get_selected_object()
if jobject and jobject.file_path:
self.file[0] = jobject.get_file_path()
open(self.file[0], "r")
self.fileflag[0] = "1"
else:
self.fileflag[0] = "0"
close(self.file[0])
# Later, variables sent to my Csound code via:
self.w.set_channel("fileflag1", self.fileflag[0])
self.w.set_filechannel("file1", str(self.file[0]))
Comments:
The jobject is being selected just fine; the problem is, it is still being
deleted, even though I'm trying to store its path. So Csound never finds the
passed filename (self.file[0]). (The str() conversion is apparently required
by Csound, as the path is otherwise some sort of DS string, which it does
not recognize.)
Please note that there are up to *4* of these choosers (the reason why
self.file is a list); obviously the various jobjects may well
replace/interfere with each other.
So, what needs to be saved ( - from deletion), and what form of data
(filename) needs to be sent to Csound to correctly locate the still-existent
"jobjects"?
The above code sends a reasonable filename, I get "DSobject was deleted", or
some such error message.
Hopefully, with your help, I can get this thorny issue behind me soon.
Art Hunkins
- Original Message -
From: "Aleksey Lim"
To: "Gonzalo Odiard"
Cc: "Art Hunkins" ;
Sent: Tuesday, November 09, 2010 1:55 PM
Subject: Re: [Sugar-devel] ObjectChooser() Issue?
On Tue, Nov 09, 2010 at 03:10:56PM -0300, Gonzalo Odiard wrote:
On Tue, Nov 9, 2010 at 3:04 PM, Aleksey Lim
wrote:
> On Mon, Nov 08, 2010 at 01:01:02PM -0500, Art Hunkins wrote:
> > At Sasha's suggestion, I've arrived at the following code to send the
> > filepath of a soundfile to Csound via its reference in the Journal.
> > The
> > filename (self.filename[0]) is being correctly passed:
> >
> > def choose1(self, widget):
> > chooser = ObjectChooser(parent=self,
> what_filter=mime.GENERIC_TYPE_AUDIO)
> > result = chooser.run()
> > if result == gtk.RESPONSE_ACCEPT:
> > jobject = chooser.get_selected_object()
>
> After destroying "jobject" object, you will lose
> /home/olpc/.sugar/default/data/f70f03b1-fe40-44e6-9d75-5ef274cf0ad2.wav
> file, so either keep this object or move/hard-link file somethere
> for later usage (but remove it after using).
>
>
Why is destroyed jobject ?
Only curiosity, I have read the mail and don't understand what is the
problem with the code.
The thing is that after creating sugar.datastore.datastore.DSObject
(here "jobject" variable) and calling "file_path", temporary file will be
created (in fact, hard link to the file stored in ds), after deleting
"jobject" this file will be removed.
Code tries to use "file_path" after deleting "jobject", thus file is
already deleted.
Gonzalo
> > if jobject and jobject.file_path:
> > self.filename[0] = str(jobject.file_path)
> > # open(jobject.file_path).read()
> > # open(self.filename[0]).read()
> > else:
> > self.filename[0] = "0"
> >
> > The problem is that the file cannot be opened by Csound - either via
> > the
> > above function as it stands, or by the addition of either line that
> > is
> > commented out.
> >
> > I receive this error message (from Csound):
> > diskinfo can't open
> > /home/olpc/.sugar/default/data/f70f03b1-fe40-44e6-9d75-5ef274cf0ad2.wav
> > The filepath and name are correct, and the file can be played fine
> > with
> > either Browse or Jukebox.
> >
> > What must I do to make the referenced soundfile readable?
> >
> > Art Hunkins
> >
> > ___
> > Sugar-devel mailing list
> > Sugar-devel@lists.sugarlabs.org
> > http://lists.sugarlabs.org/listinfo/sugar-devel
> >
>
> --
> Aleksey
> ___
> Sugar-devel mailing list
> Sugar-devel@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
>
--
Aleksey
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] ObjectChooser() Issue?
At Sasha's suggestion, I've arrived at the following code to send the filepath of a soundfile to Csound via its reference in the Journal. The filename (self.filename[0]) is being correctly passed: def choose1(self, widget): chooser = ObjectChooser(parent=self, what_filter=mime.GENERIC_TYPE_AUDIO) result = chooser.run() if result == gtk.RESPONSE_ACCEPT: jobject = chooser.get_selected_object() if jobject and jobject.file_path: self.filename[0] = str(jobject.file_path) # open(jobject.file_path).read() # open(self.filename[0]).read() else: self.filename[0] = "0" The problem is that the file cannot be opened by Csound - either via the above function as it stands, or by the addition of either line that is commented out. I receive this error message (from Csound): diskinfo can't open /home/olpc/.sugar/default/data/f70f03b1-fe40-44e6-9d75-5ef274cf0ad2.wav The filepath and name are correct, and the file can be played fine with either Browse or Jukebox. What must I do to make the referenced soundfile readable? Art Hunkins ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Testing Problem (v0.90) using Fedora LiveUSB Creator (was: Schedule after Sugar 0.90.0 is released)
I'd like to report ongoing problems trying to test my activities with Sugar 0.90 (SoaS). Now, doing this is fairly crucial. The issues cited below are still with me: 1) the most recent Fedora LiveUSB Creator (3.9.2) will not run on my WinXP desktop, giving an unexplained configuration error upon execution (reinstall doesn't help); 2) LiveUSB Creator (3.9) does not create bootable USB sticks from any nightly releases. v3.9 does install the main SoaS iso offered at the Fedora downloads page, but this turns out to be (still?) v. 0.88, or so the installation indicates (it's Fedora-13-i686-Live-SoaS.iso). Is this correct? Is 0.90 available publically as an .iso that LiveUSB Creator will handle? Thanks to whoever can help with this. I'm stymied. Art Hunkins - Original Message - From: "Art Hunkins" To: "Sugar Devel" ; Sent: Thursday, October 07, 2010 11:25 AM Subject: Testing Problem using Fedora LiveUSB Creator (was: Schedule after Sugar 0.90.0 is released) FWIW, I've been trying to give recent daily builds a test run - both to spot problems in the projected 0.90 release and see how my own activities fare. I download the x386 .iso and install it with Fedora LiveUSB Creator (v3.9 - see further below) on my WinXP system. All goes along fine until I attempt to boot my computer using the resultant USB stick. It won't boot. It gets to a test screen with a SYSLINUX line at the top and a blinking dot on line 2, and stays there. Final SoaS builds boot fine via LiveUSB Creator, but to my knowledge, all nightly SoaS builds I've tried have suffered the above fate. Is this expected? Is there a (simple) alternative? (Is this a bug?) Also (Luke), I've had to use v3.9 to make my SoaS sticks rather than v3.9.2. The latter won't install on my XP machine; it complains about a configuration error and suggests reinstalling (which I've done to no avail). I've also uninstalled before reinstalling; nothing seems to help. Reverting to v3.9, everything works fine. Art Hunkins - Original Message - From: "Simon Schampijer" To: "Sugar Devel" Sent: Wednesday, October 06, 2010 10:54 AM Subject: [Sugar-devel] [ANNOUNCE] Schedule after Sugar 0.90.0 is released --- or "After the game is before the game" Dear Sugar community, after successfully releasing 0.90 there should be a to celebrate what has been achieved and then we can start thinking what to do next. Some items are rather near term goals but there is as well the long road that leads to a new release --- 0.92 (1.0). === Branching === After the final release of a module, a branch should be created to host further stable development. If you do not have an 'unstable' commit yet you can leave your branch as is, as this ease the work for translators by not having to translate for two branches. The details about branching are described at [1]. === Bug fix release === To make sure we have the latest packages in F14 before the Final Change deadline happens the 18th of October [2], I added another bug fix release [3]. As Fedora is the bleeding edge at the moment we just backpack on this date. * 0.90.1 will be the 15th of October * 0.90.2 will be the 27th of October === Testing 0.90 === So far we have not seen much testing of 0.90 yet, that is why the bug fix releases noted above are so important to us. We need as well your help to actually discover the bugs! There are basically three ways how you can test as of today (besides using sugar-jhbuild): * Install Fedora 14 on a machine and install the Sugar desktop * Test using Sugar on a stick: Get one of the nightly snapshots [4] and put it on a usb key. You can find instructions about it at [5]. It is good to subscribe to the Soas mailing list (low traffic) [6] for announcement and discussions in that case. * If you have an XO (XO-1 or XO-1.5) you can use an image from [7]. If you are aware of any other distribution where Sugar 0.90 can be tested easily please comment. === 0.92 === Based on the GNOME schedule I made a first draft of the 0.92 roadmap. I reintroduced the "Feature Acceptance" milestone. The idea is that the discussion about a feature does not start one day before the feature freeze. As stated in the Feature policy [9] the acceptance is a sanity check, presumed in most cases to be a formality, to ensure that new features compliment Sugar guidelines and is manageable, prior to publicizing as officially targeted for the next release. The actual code must be ready by the Feature Freeze and is reviewed by the module maintainer. On behalf of the Sugar community, Your Release Team [1] http://wiki.sugarlabs.org/go/Development_Team/Release#Branching [2] https://fedoraproject.org/wiki/Releases/14/Schedule [3] http://wiki.sugarlabs.org/go/0.90/Roadmap#Schedule [4] http://alt.fedoraproject.org/pub/alt/nightly-composes/soas [5] http
Re: [Sugar-devel] Fwd: Testing Summary - Wellington, 9 Oct 2010
Tim and Alastair, Thanks for your helpful feedback re: FileMix. My comments, in no particular order: 1) A set of default soundfiles is included, and I believe the on-screen text indicates that. 2) The name "FileMix" *is* a verb - or at least can be thought of that way (I do). Mix is here a live, real-time activity; indeed no output file "mix" is created. I realize the title is somewhat open; it is meant to suggest that you can record your own files and then "live mix" them. I'd considered "mix," but thought that term *too* wide open. 3) Yes, there is an issue with "MIDI controllers." I'm assuming that if you don't know what that means, you don't have one, and should try the two options that don't require them. MIDI can get complicated, and certainly requires teacher input. I've made a recommendation re: an appropriate, inexpensive MIDI controller, but currently it's hidden at the beginning of the filemix.py file. It should be made visible in a .txt file included in the XO bundle; I'll eventually add one - though I don't know how much that will help. (Even *more* text.) This will happen after I get #4 solved (next item). 4) I'm currently working on incorporating student-generated soundfiles into the activity, as you may have noted from mail on this listserv. I'm trying to get ObjectChooser to import sound objects from the Journal into FileMix. I'm still struggling with this, but the end result will eliminate the renaming issue. The Record activity is the obvious vehicle for soundfile-making. In the last analysis, the XO-1.5 (Sugar 0.84.x) is the *only* version of Record currently creating useable recordings. (I've filed tickets about this - even SoaS 0.84 has problems, and the XO-1 Record doesn't produce a file type [Ogg Speex] that FileMix can use.) So - development here is in process. My basic problem is that I can't seem to get the (Journal's) sound object filename communicated to Csound. (I'm working with Csounders on this issue.) 5) Thanks for your other suggestions as well. I wish I had the technical expertise to implement some of them. As far as illegal soundfile types and missing/maladjusted MIDI controllers are concerned, all I can say is that things don't work (i.e., no sound) in such cases (*some* helpful clues as to errors appear in the Log file). At least (to my knowledge) there are no system failures. Art Hunkins - Original Message - From: Tim McNamara To: Sugar Developers Sent: Sunday, October 10, 2010 12:16 AM Subject: [Sugar-devel] Fwd: Testing Summary - Wellington, 9 Oct 2010 Forwarding to Sugar-devel.. ## filemix-2 Tim => - perhaps rename activity to "mix", in keeping with Sugar HIG (Activities as verbs) - neat icon - no pulsing icon on load :( - immediate thoughts: super cool concept - perhaps use the user's colours, rather than olive green for the buttons? - had no files to test with - *lots* of text - I would like to tuck lots of this away in future versions - "You are urged to make your own" - perhaps reference a sound recording activity? - "midi device required" - how do I know if I have one? - shouldn't the activity be able to let me know? - suggestions for future versions: - make files selectable, renaming to soundin.1, ... ,soundin.4 is a lot of work - run through a diagnostics dialogue with sample files: - can you hear this? MIDI, MP3, OGG, WAV, ... Alastair => - no audio to test with ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Testing Summary: Auckland NZ - 9 October 2010
Tabitha, i very much appreciate your feedback on the FileMix activity. Actually, two of the four options in FileMix require only the ASCII keyboard, not a MIDI controller. (This is the same in my other two activities, Our Music and SunMoonMusic.) The MIDI versions give better results and are much more intuitive to use, however. Regarding your other observations, I am certainly guilty as charged. I'm well aware that most activities (understandably) use a minimum of on-screen text. (Though my other activities are not as extreme as FileMix, they too are text-intensive.) In these cases, I think the explanations are required; without them, there is no sound - only frustration. Clearly, FileMix, in particular, is appropriate only for older children. All three activities are specified as being English-language only. This is surely a crucial limitation. I accepted this limitation as text (individual words) is closely related to visual display and screen layout, both vertically and horizontally. I have two redeeming thoughts about this personal decision: 1) English is widely used as a second language; 2) Text instructions can hopefully be explained by the teacher, and once grasped, can readily be absorbed and internalized by students. From that point, the students can be creative and explore the limits on their own. A final observation: Though young learners (including my granddaughter, aged 9) take well to graphics and unbridled creative activity, as an *adult* (read: senior citizen) learner, I much appreciate instructions and some guidance to keep me from despair and frustration. As an example: it is clearly indicated (via text) in FileMix which of the four options require MIDI controller and which don't. If this info *weren't* immediately available to the user, one would *certainly* abandon the activity. Art Hunkins - Original Message - From: Tabitha Roder To: olpc...@lists.laptop.org ; OLPC testing ; sugar-devel@lists.sugarlabs.org Cc: Simon Schampijer ; Walter Bender Sent: Saturday, October 09, 2010 2:19 AM Subject: [Sugar-devel] Testing Summary: Auckland NZ - 9 October 2010 Testing Summary: Auckland NZ - 9 October 2010 Who: Abhishek, Charlotte, Fabiana, John, Leslie, Robin, Tabitha, Tom Tested activities on XO-1.0s Filemix-2 Could not test as seems we have to have a midi controller to plug in. We were a bit surprised to open a Sugar activity and see loads of text on the screen. Can this be presented better? What if you can't read all that or there is no local translation? Thanks testers Tabitha -- ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] chooser/datastore documentation
This information would help me as well. Art Hunkins - Original Message - From: "Walter Bender" To: "Sugar-dev Devel" Sent: Thursday, October 07, 2010 7:45 PM Subject: [Sugar-devel] chooser/datastore documentation I am struggling with getting my activities to behave in consistent ways when using the chooser and datastore.find() between Sugar 0.84 and more recent Sugar versions. (For example, I cannot get find() to process mime-type query in 0.84 but it will handle a title query. The exact opposite seems to be true in 0.90. Of course, I could be doing it all wrong.) Similarly, I cannot get what_filter to work with non-GENERIC mime types, but that again could be user error. (I am trying to choose only Python objects, for example.) I've searched unsuccessfully for documentation on what works in which versions. Does such documentation exist somewhere? thanks. -walter -- Walter Bender Sugar Labs http://www.sugarlabs.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Testing Problem using Fedora LiveUSB Creator (was: Schedule after Sugar 0.90.0 is released)
FWIW, I've been trying to give recent daily builds a test run - both to spot problems in the projected 0.90 release and see how my own activities fare. I download the x386 .iso and install it with Fedora LiveUSB Creator (v3.9 - see further below) on my WinXP system. All goes along fine until I attempt to boot my computer using the resultant USB stick. It won't boot. It gets to a test screen with a SYSLINUX line at the top and a blinking dot on line 2, and stays there. Final SoaS builds boot fine via LiveUSB Creator, but to my knowledge, all nightly SoaS builds I've tried have suffered the above fate. Is this expected? Is there a (simple) alternative? (Is this a bug?) Also (Luke), I've had to use v3.9 to make my SoaS sticks rather than v3.9.2. The latter won't install on my XP machine; it complains about a configuration error and suggests reinstalling (which I've done to no avail). I've also uninstalled before reinstalling; nothing seems to help. Reverting to v3.9, everything works fine. Art Hunkins - Original Message - From: "Simon Schampijer" To: "Sugar Devel" Sent: Wednesday, October 06, 2010 10:54 AM Subject: [Sugar-devel] [ANNOUNCE] Schedule after Sugar 0.90.0 is released --- or "After the game is before the game" Dear Sugar community, after successfully releasing 0.90 there should be a to celebrate what has been achieved and then we can start thinking what to do next. Some items are rather near term goals but there is as well the long road that leads to a new release --- 0.92 (1.0). === Branching === After the final release of a module, a branch should be created to host further stable development. If you do not have an 'unstable' commit yet you can leave your branch as is, as this ease the work for translators by not having to translate for two branches. The details about branching are described at [1]. === Bug fix release === To make sure we have the latest packages in F14 before the Final Change deadline happens the 18th of October [2], I added another bug fix release [3]. As Fedora is the bleeding edge at the moment we just backpack on this date. * 0.90.1 will be the 15th of October * 0.90.2 will be the 27th of October === Testing 0.90 === So far we have not seen much testing of 0.90 yet, that is why the bug fix releases noted above are so important to us. We need as well your help to actually discover the bugs! There are basically three ways how you can test as of today (besides using sugar-jhbuild): * Install Fedora 14 on a machine and install the Sugar desktop * Test using Sugar on a stick: Get one of the nightly snapshots [4] and put it on a usb key. You can find instructions about it at [5]. It is good to subscribe to the Soas mailing list (low traffic) [6] for announcement and discussions in that case. * If you have an XO (XO-1 or XO-1.5) you can use an image from [7]. If you are aware of any other distribution where Sugar 0.90 can be tested easily please comment. === 0.92 === Based on the GNOME schedule I made a first draft of the 0.92 roadmap. I reintroduced the "Feature Acceptance" milestone. The idea is that the discussion about a feature does not start one day before the feature freeze. As stated in the Feature policy [9] the acceptance is a sanity check, presumed in most cases to be a formality, to ensure that new features compliment Sugar guidelines and is manageable, prior to publicizing as officially targeted for the next release. The actual code must be ready by the Feature Freeze and is reviewed by the module maintainer. On behalf of the Sugar community, Your Release Team [1] http://wiki.sugarlabs.org/go/Development_Team/Release#Branching [2] https://fedoraproject.org/wiki/Releases/14/Schedule [3] http://wiki.sugarlabs.org/go/0.90/Roadmap#Schedule [4] http://alt.fedoraproject.org/pub/alt/nightly-composes/soas [5] http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Installation [6] http://lists.sugarlabs.org/listinfo/soas [7] http://dev.laptop.org/~erikos/F14_builds/ [8] http://wiki.sugarlabs.org/go/0.92/Roadmap#Schedule [9] http://wiki.sugarlabs.org/go/Features/Policy#Acceptance_of_a_feature ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Advice request: XO sound recording
What made me think that Object Chooser was not feasible in 0.82? This comment from a recent email of James Simmons (which I'm sure you read): "I have tried the Object Chooser. In Sugar .82 it had some serious bugs, could not list out only those entries you wanted to look at, and was slow and ugly. A big part of my book is explaining how to write Activities that will run on .82 as well as later versions of Sugar, and there was no way to make the Object Chooser a part of that strategy." I gather you don't agree? Art Hunkins - Original Message - From: "Sascha Silbe" To: "sugar-devel" Sent: Monday, October 04, 2010 2:53 PM Subject: Re: [Sugar-devel] Advice request: XO sound recording > ___ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel > ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
