Re: [Sugar-devel] [Cs-dev] Sugar on a Stick - and OLPCsound/Csound
Art, You need to enable the testing repo. yum --help is your friend here. To enable it on a temporary basis you can do yum --enablerepo=updates-testing update csound or to enable it permanently you edit the /etc/yum.repos.d/fedora-updates-testing.repo changing the first enable= line from 0 to 1. I emailed you the details of how to do that back on Jul 1st. Peter On Sat, Jul 18, 2009 at 2:49 AM, Art Hunkinsabhun...@uncg.edu wrote: Peter, Thanks for this. Can you, or anyone, point me to specific instructions as to how to download and install either of these options? I've tried the obvious methods, such as: yum updates-testing csound and yum update csound but have hit a blank wall. I've never tried anything in testing mode before. Art Hunkins - Original Message - From: Peter Robinson pbrobin...@gmail.com To: Art Hunkins abhun...@uncg.edu Cc: sugar-devel@lists.sugarlabs.org; csound-de...@lists.sourceforge.net Sent: Thursday, July 16, 2009 7:43 AM Subject: Re: [Sugar-devel] [Cs-dev] Sugar on a Stick - and OLPCsound/Csound Hi All, I've tested and applied the patch to F11 and pushed it out as a updates-testing. Please test. https://admin.fedoraproject.org/updates/csound-5.10.1-9.fc11 Or if your too impatient to wait for the updates-testing push you can grab the rpms from koji directly http://koji.fedoraproject.org/koji/buildinfo?buildID=114648 Peter On Mon, Jul 13, 2009 at 4:03 PM, Art Hunkinsabhun...@uncg.edu wrote: Aleksey, Thanks for undertaking this task. Please let me know when the revised build of Csound5.10 is available for update on SoaS. I'm eager to be assured that it solves the compatibility issue with python 2.6. Art Hunkins - Original Message - From: Aleksey Lim alsr...@member.fsf.org To: Art Hunkins abhun...@uncg.edu Cc: Michael Gogins michael.gog...@gmail.com; sugar-devel@lists.sugarlabs.org Sent: Monday, July 13, 2009 12:02 AM Subject: Re: [Sugar-devel] [Cs-dev] Sugar on a Stick - and OLPCsound/Csound On Sun, Jul 12, 2009 at 03:19:31PM -0400, Art Hunkins wrote: Mike Gogins, a Csound developer, has taken care of the Scons issue with Csound5.10, as discussed below. I'd be overjoyed if one of you Sugar developers could take it from there so that we can have SoaS with a Csound that works with python2.6. I can build rpm for soas env. but I'm waiting for fixing my problems with ISP so, I can't do it in nearest few days. Just an option, using Mandriva of Suse ;) -- Aleksey ___ 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] testing sugar on debian
On Fri, Jul 17, 2009 at 21:48, Jonas Smedegaardd...@jones.dk wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On Thu, Jul 16, 2009 at 03:34:28PM +0200, Santiago Ruano Rincón wrote: Hi, Jonas. On Thu, Jul 16, 2009 at 02:24:30PM +0200, Jonas Smedegaard wrote: ... Yeah - that bug was causing the segfault I wrote about in another thread! Martin Stone figured out a workaround (and I have now mentioned the bugnumber next to it!) of not stripping binaries in hippo-canvas: http://wiki.sugarlabs.org/go/Development_Team/Chroot I have now (for amd64 only so far) an unofficial hippo-canvas packaged for Sid with that fix. Add the following to your /etc/apt/sources.list to get it: deb http://debian.jones.dk/ sid sugar Packaged a working hippo-canvas for both amd64 and i386, both Sid and Squeeze now. Add one of these lines as appropriate for your Debian system: deb http://debian.jones.dk/ sid sugar deb http://debian.jones.dk/ squeeze sugar I'm looking at your packages, but the only change I found is in changelog, or I am wrong? Anyway, I've added DEB_BUILD_OPTIONS += nostrip and yeah, it seems to work. I'll upload it to debian. Using nostrip violates Debian Policy! What's even stranger is that I - in the train here to Spain - experienced that a simple recompile also works! Yup, same experience here on testing. Regards, Tomeu What was your build environment for that last release? Do you use pbuilder or similar virgin-like environment? Package dependencies (for the binary package, not build-dependencies) also look odd - they are _newer_ for that old build than when recompiling against up-to-date Sid. Please test with simple recompile (standard stripping!) and consider rereleasing! Kind regards, - Jonas - -- * Jonas Smedegaard - idealist og Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iQIcBAEBCgAGBQJKYNWcAAoJECx8MUbBoAEh8VcP/1tsUs8w56unlLTk5Tqq8Qyf wDc3l4Q0EXUH+LeJxJV+3Nd4vAKXsZTaYl8lKxO9C0SmvNDsQ5IjCRNexN6DLVJF /xF9yOy4PkVZM56USRQZc6YQG7OxghU5kXqYEkPupbPYVI1k2A2Ox00kcWpfuigT 8YB/cjifJPjzBJkg35XNuttjkkCPTaUcchvyQmyHjBdUVCH2l3RpHH80xL/NJJne GhuXLeYCINJhbJzypR4uOMlDTjIOun6kTuM24NlvBXPE9MBOiw+CI2zegloETnjB yLt354yzPlzsFWlmIUDSBLype6aTBmUkNXPfw0YnwQ/YOnPahM5n6igYFUNfFooO 7Fps6jYWtKJhDBkv2uLWkeSkOoH4dUjwZcmpkvbNSGtGrbVoBM1qkh+mwyl84xCU 0xBV5iI+Rz+3ZKWTvtYJlRZiakqOOHjQvHSpucZl+BNYTo8CTk8G3rsWZRNkrMBx 3iqxC/hjSwbEqBvXWuP698QgphjTO2PRLgOolkRy/cHbhk4tXJ2hD3jmD+o46ayd tnHnuencmDNEIR4/fduXkffnA7HvGIS+P/1wD194uaG+pRK4zbOAL6jWqrYyYn47 0LjAQhBI7uy5e8OPU9mnmxyDUW8WdSv42id3SNt7mBD/QYOoVoPqWQtunNwGUHyw Lgfk2La+tBNB7fOx48EE =3amt -END PGP SIGNATURE- ___ 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] GPA School Notes Wed. July 15 - GS
On Fri, Jul 17, 2009 at 15:25, Eduardo H. Silvahoboprim...@gmail.com wrote: My humble opinions on what Sugar could learn from this report are bellow. I agree, that's quite good feedback, could someone check we have tickets for all these issues? Thanks, Tomeu 2009/7/15 Greg Smith gregsmit...@gmail.com: Hi All, Here are my notes from today's class. Anurag will send out notes on what we did in class so I will focus on UI and usability comments. I also recorded the post class warm/cold comments. Sorry I didn't get a chance to get on IRC after the class as planned. We got local collaboration working well so we will go with that and stop debugging Jabber issues for now. About 10 x 3rd graders were in the class today. This was their second time with Sugar. Caroline led the class as Walter is travelling and several kids asked where is the other guy?. The main activity was to get pictures of states of wikipedia, then put those in Memorize and create games (e.g. picture of Texas, word Texas makes a match) and share the memorize so two kids can play together. Warm/cold post class comments: Anurag Warm: Collaboration worked well. Kids were able to join each others games and reload games as needed. They could change partners easily too. The importing map from Wikipedia worked well. They quickly understood how to switch from browse to memorize and how to save and access things from the journal. They retained a lot fo what they learned before. Cold: 3 person collaboration didn't always work. Caroline Warm: Collaboration added to the kids engagement. They learned a lot about state names and the drilling aspects seemed to help them remember. There were multiple steps but they seemed to handle it well. It would have been harder with fewer adults to help each kid but every kid got it. Went great overall. Cold: 3 or person collaboration worked sometimes but not always. May have been a work flow thing (e.g. if two already playing third has to wait until end of game to join). The loading and customization of USB sticks was labor intensive. Greg Warm: Fun time and impressive production by the kids in terms of creating games. Cold: Some tasks were hard and kids needed help (see below). Jennifer Warm: kids were enthusiastic. They learned how to spell state names. Kids helped each other out. Cold: Sometimes when switching partners, some kids were left out. Usability comments from me. Educational Context The kids really wanted to know what to do next. If they didn't know where to click to download an image they would just sit and wait or get distracted or ask a teacher or me. With several kids asking you something at the same time and poking you for your attention, its a little overwhelming: what do I do now?, how do you spell Louisiana?, how do I go back to memorize?, etc. I asked the teacher how he handles that and he said he spends extra time preparing them. Gives exact steps, goes over them several times, and ask the kids to repeat back what they will do. He can handle a few kids asking follow up questions but if more than 2 - 3 need help then it probably wasn't explained well enough in advance. That was not what I expected. My inclination is to say go ahead and do whatever you want. You can do this, but anything you create will be original and interesting. Of course, to a kid, do what every you want turns in to run around in the sun and tickle my class mates. If you constrain it to: in the class using the computer, they want to know what to do next. They want to do the right thing, finish the assignment and accomplish their task. So structure and direction is important. Probably obvious to any teacher but kind of a surprise to me. Steps to accomplish the assigned task. We setup the collaboration and had connected computers in pairs with Memorize open when we started. Their task with steps as we intended was as follows: - Open browse - Go to WIkipedia.org - Type in a state name in the search field - Right click on the picture of the state and choose download - Click continue count down timer ot just wait for download to complete. - Click OK or Show in Journal - Open frame - Choose Memorize - Choose create tab as needed - Choose eye icon to upload state image - Find and select state image on journal - Type state name in matching tile - Click Add pair - Repeat as needed - Save Game - Click Play tab - Open game Play with friend or variant of choose SHare with my Neighborhood and have friend find you. Everybody got it eventually but most needed help somewhere. Examples of things they needed help with, from kids I worked with: - Couldn't remember how to start world AKA browse. - Needed help spelling Wikipedia. - Couldn't find search field on wikipedia because frame was covering half of it - Needed help spelling state names - Didn't remember Right click on image to download in browse. This is one place
Re: [Sugar-devel] sugar-update-control.aslo ready for testing
On Fri, Jul 17, 2009 at 13:10, David Farningdfarn...@sugarlabs.org wrote: On Fri, Jul 17, 2009 at 3:04 AM, Tomeu Vizosoto...@sugarlabs.org wrote: On Thu, Jul 16, 2009 at 16:10, David Farningdfarn...@sugarlabs.org wrote: Another pre-release of sugar-update-control.aslo is ready for testing. It is now available at http://git.sugarlabs.org/projects/sugar-update-control/repos/aslo-clone . Just tried it, congratulations on the fine work! Fixes include : GUI works correctly via control panel. Finds activities via SUGAR_PATH. (if SUGAR_PATH is set correctly it _should_ on SOAS but, I have not tested it yet) I wouldn't access directly the fs to check for available activities. There's already code in the shell that deals with this: http://git.sugarlabs.org/projects/sugar/repos/mainline/blobs/master/src/jarabe/model/bundleregistry.py There's also code for updating, installing, etc. Ok thanks, I was not sure of the consequences of _not_ using the bitfrost python modules for pulling activity related information. I'm afraid we will have to read the code in order to know. I'll look at bundleregistry.py today. Using client side updates provided by alsroot[1], will grab the correct versions of activities for the installed version of Sugar. TODO: By default, GUI is populated with information on all corresponding activities on ASLO not just the valid update. (You can manually select the updates you want) Please test so we can see about adding it as a feature to .86:) Will be awesome to have the updater working on 0.86, but note that sugar-update-control isn't part of Sugar as of yet. See about new module proposals here: http://wiki.sugarlabs.org/go/Development_Team/Release http://wiki.sugarlabs.org/go/Development_Team/Release/Roadmap One of the consequences of this is that distro packagers will need to be prompted specifically about packaging sugar-update-control until it is part of Glucose. Added incomplete feature tracker at http://wiki.sugarlabs.org/go/Features/SugarUpdateControl.ASLO . Well, the feature process is currently for Sugar, and sugar-update-control is not part of it. First we should make sugar-update-control a module in Glucose, then we can see about feature proposals. Until it's not in Glucose, there's no need for feature pages, it's an independent module that follows its own schedule. If you want it to be part of Glucose, we should ask Simon about the consequences of adding new modules in this part of the release cycle. Regards, Tomeu david Regards, Tomeu david 1. checkout http://activities.sugarlabs.org/services/update.php?id=org.laptop.WebActivityappVersion=0.82 http://activities.sugarlabs.org/services/update.php?id=org.laptop.WebActivityappVersion=0.84 http://activities.sugarlabs.org/services/update.php?id=org.laptop.WebActivityappVersion=0.86 aloroot rocks! -- David Farning Sugar Labs www.sugarlabs.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- David Farning Sugar Labs www.sugarlabs.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] updating from aslo
On Fri, Jul 17, 2009 at 19:39, Daniel Draked...@laptop.org wrote: 2009/7/16 David Farning dfarn...@sugarlabs.org: A possible answer would be to abstract ALSOParse.py and microformat.py as back ends for Sugar-Update-Control (SUC). It's not so much the issue of losing support for the existing widely-deployed setup (although that would be unfortunate), it's that this seems to lack design. The microformat-style update (along with certain characteristics of the updater and server implementation) is not perfect, but it is good for field use and G1G1 style internet users. The motivation for moving to aslo seems to be only that of because it's running on sugarlabs.org, without consideration for any technical pros or cons of the different format, how it might be deployed in the field, etc. I think you should take a more detailed approach to this, without limiting yourself to the quirks and current behaviour of the aslo code. I guess I'm confused, are you saying that activity authors and users don't gain anything by using ASLO instead of the previous wiki system? Then why did we spent so much time fitting ASLO to our needs? It's not like ASLO has been always running in sugarlabs.org, lots of effort from several people from several teams in SLs has gone to make it possible, it's not the wet dream of a single coder. If I misunderstood you and you weren't questioning the usefulness of ASLO itself, then I don't see why it doesn't make sense to get the update data from where it already is. Regards, Tomeu 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] creating your own templates in write activity
On Fri, Jul 17, 2009 at 21:25, Manusheel Guptam...@laptop.org wrote: Tomeu, Nice to hear from you. On Fri, Jul 17, 2009 at 12:49 PM, Tomeu Vizoso to...@sugarlabs.org wrote: I think Martin's answer has been very complete, are you already set on this one? I recommend you to send these questions to the abiword-devel mailing list where you will find Martin and the other Abiword developers: Yes, Martin's answer was very complete. We were able to add the text box feature. Will subscribe to abiword-devel mailing list. Thank you for the pointer. http://www.abisource.com/developers/ We also wish to ask you about the details of the code, which is used to enable menu selections in the advanced abiword activity. What do you mean by enable menu selections and advanced abiword activity? The advanced abiword activity is a reference implementation provided in the examples folder of pyabiword (please have a look at the examples folder in the attached pyabiword file). I see, despite of having Sugar in the class name, it has technically nothing to do with Sugar. Enable menu selections was a typo from my side. My apologies. Selecting an option from the menu bar is very well implemented in this example. Also, could you explain what are you trying to accomplish? We are trying to extend the write activity, and develop features on top of it, so that it could be used for authoring school newspapers and magazines. Template builder tool is an integral part of the activity. That sounds great, how do you plan to deploy it? Are you going to integrate your changes into the existing Write activity or will do a new one based on that? Regards, Tomeu Regards, Manu ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Language control panel broken: Chinese + Russian displayed
On Sat, Jul 18, 2009 at 01:54, Edward Cherlinecher...@gmail.com wrote: There are serious bugs in language switching in My Settings (the Sugar Control Panel). Would be better to track each of these issues in individual tickets at dev.sugarlabs.org. One is that switching to a language can result in bits of some other language appearing, and switching back does not necessarily restore the original language entirely. I have attached a portion of a screen shot showing mixed Russian and Chinese, even though English is set. Maybe these languages have poor 0.84 coverage and you have set them one on top of another so when a string is not found in a language, it tries to find it in the other one? Also, if you add another language menu with the button provided, and select two different languages on them, it is not obvious how to switch. It turns out that clicking on the menu showing the desired language, and reselecting the displayed selection, is not interpreted as a request to change languages. It appears to be necessary to select something else, and then go back and select the language desired. Third, the + button sometimes disappears. Not sure about these two, perhaps Sayamindu can comment. Regards, Tomeu -- Silent Thunder (默雷/धर्ममेघशब्दगर्ज/دھرممیگھشبدگر ج) is my name And Children are my nation. The Cosmos is my dwelling place, The Truth my destination. http://earthtreasury.org/worknet (Edward Mokurai Cherlin) ___ 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] Initial implementation of toolbars design
On Sat, Jul 18, 2009 at 04:17, Gary C Marting...@garycmartin.com wrote: Hi Caroline, On 17 Jul 2009, at 22:14, Caroline Meeks wrote: We can put it in front of actual kids once you get a sample working. We could even try playing the video for our existing classes. I don't know if they'll be able to give you feedback from just seeing the video. Might be interesting to find out. Yes that's an interesting one... I have more understanding of usability studies with literate adults, where you can have a controlled environment. With the idea that you set goals/tasks to be completed with the interface and ask the user to vocalise what they think they are doing (I'm clicking this because I think it's the search button...). You only interact with them once they are clearly stuck, to help them get back on track. Asking for any-ones opinion is usually frowned upon in usability studies, as opinion is almost always different from actual behaviour – but some opinions are better than nothing, which is why I keep asking :-) Perhaps I should work with Walter and Aleksey's initial toolbar code and make an identical test clone of TA but with the new toolbar design (I can use Aleksey's Write mock-up code as an example)? Then you could let the class (or a random selection of the class) use it for some tasks and watch how well (or not) they manage with the new interface? If that's not too much work, I think it would be great. If you are going to get stuck on that, perhaps we can get an informed guess from the people I mentioned before? Regards, Tomeu Simon: have you used TA yet in your lessons? Regards, --Gary ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Initial implementation of toolbars design
On Fri, Jul 17, 2009 at 16:57, Gary C Marting...@garycmartin.com wrote: Hi Tomeu, On 17 Jul 2009, at 09:52, Tomeu Vizoso wrote: Here are my image mock-ups for Write. All tabs are swapped out as is, for toolbar buttons. With no need to move existing tab content features about: http://wiki.sugarlabs.org/go/Design_Team/Proposals/Toolbars#Top_level_Activity_toolbar_for_Write These look really great! I would like to hear opinions from people who have worked with kids and Sugar. +1 If they agree to move forward on this, I think we can go full speed ahead. Yes, we need that feedback! Having worked closely on these, I can't fairly comment, I'm in the box so to speak. We need feedback from other folks out side the box. Though I am happy to wave a flag and shout having the Stop button always visible at the top right of every Activity toolbar is a huge win ;-) My big criticism of the design is actually there's no text for the literate. I can see adults struggling more with this interface vs. lowering the bar a for the very young and/or illiterate. Secondary palettes still get their text labels, just like they do now, thank goodness. But, the primary tool buttons are all without text labels (good for ease of translation, but good icons are much harder to create than a text name). Thanks for the great work, Thanks, glad you like them :-) Regards, --Gary P.S. I've been trying to work through your [IAEP] future of the Sugar user experience email from 6 weeks or so back from a design point of view, think I've managed to touch on most items (but not all). I have realized and I'm really enthusiastic about this. And Eduardo is also starting again to send really good feedback ;) Regards, Tomeu ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [IAEP] Share sugar objects on a standalone server
On Fri, Jul 17, 2009 at 16:49, Aleksey Limalsr...@member.fsf.org wrote: On Fri, Jul 17, 2009 at 03:42:57PM +0100, Gary C Martin wrote: On 17 Jul 2009, at 10:11, Aleksey Lim wrote: On Fri, Jul 17, 2009 at 10:48:10AM +0200, Tomeu Vizoso wrote: On Fri, Jul 17, 2009 at 04:43, Aleksey Limalsr...@member.fsf.org wrote: On Fri, Jul 17, 2009 at 03:11:15AM +0100, Gary C Martin wrote: On 17 Jul 2009, at 02:21, Aleksey Lim wrote: On Thu, Jul 16, 2009 at 08:03:15PM -0500, David Farning wrote: On Thu, Jul 16, 2009 at 7:41 PM, Aleksey Limalsr...@member.fsf.org wrote: On Fri, Jul 17, 2009 at 12:17:13AM +, Aleksey Lim wrote: Hi all, One of lacks that sugar environment has is simple way to share sugar objects for broad audience i.e. like scratch community has[1] (thanks to davidmorris form #sugar). So, I've created [2]. Original idea was having highly integrated sharing features into sugar shell but looks like we can do simple things first and even utilize only Browse for browsing/download/upload sugar objects. The problem is - what web engine we should use. * Utilize AMO[3] engine which is used in activities.sugarlabs.org in that case we can create something like library.sugarlabs.org to not Pro: * we do not split users behaviour, they need the same experience that ASLO requires * one common branding for activities and objects sites * AMO has sufficient(imo) functionality - reviews, ranking, collections and thumbs mode https://addons.mozilla.org/en-US/firefox/browse/type:2/cat:all?sort=popular * we hack AMO code anyway - its not a problem in adding new AMO environment Contra: * Locality - In may instances the stuff created by students will only be of interest to their friends, teachers, and parent. Serving via ASLO publishes the content globally. publishes the content globally is the original purpose for this feature in contrast with http://wiki.sugarlabs.org/go/Features/Peer_to_Peer_Objects_Sharing Or you mean possibility to share objects on local servers? Would be really good if we could just get the uploading of Journal entries via Browse working reliably, right now it's only certain simple object types (png, pdf, etc) that work reasonably. What do you mean exactly? Object chooser can pick any type of objects including anything option. The root of the problem is that we are uploading files, not entries. Some activities store files in their entries in formats commonly used and known. But others will store a json file and after upload nobody knows what to do with it. The good news is that we have already a format for packaging full journal entries in zip files and after downloading such an entry bundle it will be expanded and restored in the journal will all the metadata, etc. +1, had this same thought last night :-) What we would need is for a simple way to upload these bundled entries instead of just the file. Any ideas about how would look the UI like? I'm thinking about implicit behaviour, like while choosing objects for input fields in Browse we can package chosen object to bundle As per my other email we currently have Activities and Objects in the Journal. Objects could be implicitly uploaded by Browse as regular files, Objects need to be bundled as well e.g. package tags that were added by user after downloading this object to Journal. Agreed, would be a pity to lose the metadata. Also, when we have the separation between actions and objects, why would we be interested in sharing actions? Regards, Tomeu ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] sugar-update-control.aslo ready for testing
On Sat, Jul 18, 2009 at 4:27 AM, Tomeu Vizosoto...@sugarlabs.org wrote: On Fri, Jul 17, 2009 at 13:10, David Farningdfarn...@sugarlabs.org wrote: On Fri, Jul 17, 2009 at 3:04 AM, Tomeu Vizosoto...@sugarlabs.org wrote: On Thu, Jul 16, 2009 at 16:10, David Farningdfarn...@sugarlabs.org wrote: Another pre-release of sugar-update-control.aslo is ready for testing. It is now available at http://git.sugarlabs.org/projects/sugar-update-control/repos/aslo-clone . Just tried it, congratulations on the fine work! Fixes include : GUI works correctly via control panel. Finds activities via SUGAR_PATH. (if SUGAR_PATH is set correctly it _should_ on SOAS but, I have not tested it yet) I wouldn't access directly the fs to check for available activities. There's already code in the shell that deals with this: http://git.sugarlabs.org/projects/sugar/repos/mainline/blobs/master/src/jarabe/model/bundleregistry.py There's also code for updating, installing, etc. Ok thanks, I was not sure of the consequences of _not_ using the bitfrost python modules for pulling activity related information. I'm afraid we will have to read the code in order to know. I'll look at bundleregistry.py today. Using client side updates provided by alsroot[1], will grab the correct versions of activities for the installed version of Sugar. TODO: By default, GUI is populated with information on all corresponding activities on ASLO not just the valid update. (You can manually select the updates you want) Please test so we can see about adding it as a feature to .86:) Will be awesome to have the updater working on 0.86, but note that sugar-update-control isn't part of Sugar as of yet. See about new module proposals here: http://wiki.sugarlabs.org/go/Development_Team/Release http://wiki.sugarlabs.org/go/Development_Team/Release/Roadmap One of the consequences of this is that distro packagers will need to be prompted specifically about packaging sugar-update-control until it is part of Glucose. Added incomplete feature tracker at http://wiki.sugarlabs.org/go/Features/SugarUpdateControl.ASLO . Well, the feature process is currently for Sugar, and sugar-update-control is not part of it. First we should make sugar-update-control a module in Glucose, then we can see about feature proposals. Until it's not in Glucose, there's no need for feature pages, it's an independent module that follows its own schedule. If you want it to be part of Glucose, we should ask Simon about the consequences of adding new modules in this part of the release cycle. OK I'll just continue to clean it up and try to adapt the code to the current Sugar coding standards. The biggest clean ups are due to the improvements in the Sugar API. When Scott originally wrote s-u-c he had to include several error handling mechanism and helper functions which are now part of jarabre. david Regards, Tomeu david Regards, Tomeu david 1. checkout http://activities.sugarlabs.org/services/update.php?id=org.laptop.WebActivityappVersion=0.82 http://activities.sugarlabs.org/services/update.php?id=org.laptop.WebActivityappVersion=0.84 http://activities.sugarlabs.org/services/update.php?id=org.laptop.WebActivityappVersion=0.86 aloroot rocks! -- David Farning Sugar Labs www.sugarlabs.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- David Farning Sugar Labs www.sugarlabs.org -- David Farning Sugar Labs www.sugarlabs.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] [RELEASE] sugar-base-0.85.1
== Source == http://download.sugarlabs.org/sources/sucrose/glucose/sugar-base/sugar-base-0.85.1.tar.bz2 No changes since last 0.84 release, just a version bump. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] [RELEASE] sugar-base-0.85.2
== Source == http://download.sugarlabs.org/sources/sucrose/glucose/sugar-base/sugar-base-0.85.2.tar.bz2 Re-add .pot file that was removed by mistake ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] [RELEASE] sugar-0.85.2
== Source == http://download.sugarlabs.org/sources/sucrose/glucose/sugar/sugar-0.85.2.tar.bz2 Misc. bug fixes related to window management ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] [RELEASE] sugar-artwork-0.85.1
== Source == http://download.sugarlabs.org/sources/sucrose/glucose/sugar-artwork/sugar-artwork-0.85.1.tar.bz2 Remove matchbox theme ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Physics activity (Was: Release v3 tonight?)
On 17 Jul 2009, at 03:32, Gary C Martin wrote: Hi Asaf, Brian, On 15 Jul 2009, at 00:27, Gary C Martin wrote: On 13 Jul 2009, at 05:46, Asaf Paris Mandoki wrote: Friday is only good for me if we do it around 3pm GMT. Brian: is 3pm GMT good for you? #sugar-meeting is free by my calculations UK==16:00, US/Eastern==11:00. I'll be in #sugar-meeting for 1hr or so on Friday, if either of you are able to make it. Not a formal meeting, just a chat about Physics direction, ideas, next steps. For those interested in the Physics Activity, we (asaf, bjordan__, daveb, and myself) had a really productive IRC chat on Friday. The meeting bot seemed to have been taking the day off, so I've posted the meeting chat log on the Physics discussion page. Worth a read through, lots of cool stuff: http://wiki.sugarlabs.org/go/Talk:Activities/Physics Regards, --Gary ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] GSoC Groupthink Update: SharedTextDemo-4
Gary C Martin wrote: I just want to raise a note of interest. I've been pondering future possibilities for collaboration in Physics: http://wiki.sugarlabs.org/go/Activities/Physics Still early days for making a call, but Asaf has made great strides in getting Physics storing its world state to Journal. That's very interesting. It would nicely avoid the solving the really hard problem of maintaining real-time coherence between two nondeterministic physics engines over a slow link (which is really a problem of chaos prevention!). The first step is to ask: what form does the world state take? If it can be represented, for example, as a dict of object names and properties, then you can simply use the shared-dict from groupthink. Of course, getting changes in and out of the model is not so easy. --Ben signature.asc Description: OpenPGP digital signature ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] GSoC Groupthink Update: SharedTextDemo-4
On 18 Jul 2009, at 16:36, Benjamin M. Schwartz wrote: Gary C Martin wrote: I just want to raise a note of interest. I've been pondering future possibilities for collaboration in Physics: http://wiki.sugarlabs.org/go/Activities/Physics Still early days for making a call, but Asaf has made great strides in getting Physics storing its world state to Journal. That's very interesting. It would nicely avoid the solving the really hard problem of maintaining real-time coherence between two nondeterministic physics engines over a slow link (which is really a problem of chaos prevention!). The first step is to ask: what form does the world state take? If it can be represented, for example, as a dict of object names and properties, then you can simply use the shared-dict from groupthink. Asaf was already able to integrate with a new Box2D which supports python pickling of the world state, this works real well already for saving state to Journal. But, before an official Physics-3 release, we wanted to be sure Physics has some control over the file format incase Box2Ds pickeled structures change and potentially break backwards compatibility for Physics Journal entries. Asaf is now almost done with a re-work using json, just including the specific scene properties Physics need, from yesterdays IRC chat: asaf FWIW for each body i'm storing its position, userData, angle, angularVelocity, linearVelocity and shapes it's attached to asaf if the shape is a circle I store radius, density, restitution, friction and position relative to body asaf if the shape is a polygon I store the same stuff but insted of radius I store vertices asaf That for now takes care of everythin drawn, I still have to take care of joints and controllers Of course, getting changes in and out of the model is not so easy.\ Yea... My worry is that at each otherwise simple user edit, many of the world object properties will have changed (well, certainly most of the positions/angles/angularVelocities/linearVelocities), so they will all require transmission and relatively a large merge. Still trying to get my head around it :-) Regards, --Gary ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Physics activity (Was: Release v3 tonight?)
Hi, In order to make the UI more friendly y suggest removing hidden features of the joint tool that allow you to add pins because I think it is unexpected behavior. Another minor modification can be to change the name of the joint tool to rope tool. What do you think? Greetings, Asaf On Mon, Jul 13, 2009 at 1:56 AM, Simon Schampijer si...@schampijer.dewrote: On 07/13/2009 04:11 AM, Gary C Martin wrote: Just cc:ing the list to keep others in the loop. On 12 Jul 2009, at 22:55, Asaf Paris Mandoki wrote: A release will be great. Think we need to make a call on the stability of the new Physics Journal state format first, or at least make sure everyone knows the storage format may (or may not) be stable long term (hate to see a bunch of folks generating/posting examples for lesson plans only to have them all fail to resume in a few versions from now). I also suggest scheduling an IRC meeting to discuss some long term plans about what we're going to do and how we're going to do it. Yes, an IRC meeting sounds like a good idea. I'm usually only on IRC for specific meetings so we'd need to pick a time. Perhaps we could make it a Physics specific ActivityTeam meeting on Friday, some other interested parties may join the discussions? I'm thinking about adding some sort of goals and objectives but I'm not sure if there is where we want to go. Well need to chat :-) but the X2o Activity seems like the place for driving goals and objectives. I see Physics as more the open ended sand box for experiments, like a simple Paint tool for physics simulations. We need to keep an eye on the usability for younger kids, the number of tools is probably about right, but I have been looking at the idea of adding more options as secondary palettes, i.e. you hover over the circle tool and the palette includes extra options for helium balloon, rubber ball, wooden ball, stone ball for some pre-set material types, this would vary depending on the tool, so the motor could perhaps have clockwise and anti-clockwise as well as some torque settings (strong, medium, weak). Hi, In case you did not see my post (http://erikos.sweettimez.de/?p=789): [...] One problem I observed with younger kids is the use of the mouse. In that age for example moving the mouse over the whole screen (like for closing an activity) is a hard task. Now, in physics to create an object you have to: click on the screen, hold the button and move the mouse to create the item at your desired size. Sounds hard doesn’t it? Maybe we can present the kid on right mouse click with a palette and let’s say 3 objects at different sizes to select from? [...] Might be an option for some palette information as well. Regards, Simon ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Physics activity (Was: Release v3 tonight?)
On 18 Jul 2009, at 22:30, Asaf Paris Mandoki wrote: Hi, In order to make the UI more friendly y suggest removing hidden features of the joint tool that allow you to add pins because I think it is unexpected behavior. Yes, I almost removed the right click to pin hidden feature when I was fixing up the UI and small object crashing bugs. Happy to see it go no we have an explicit pin tool. Another minor modification can be to change the name of the joint tool to rope tool. What do you think? No. But I agree the joint tool is not ideally named. It's really a rod or strut tool (solid/ridged bar with joints at each end). Perhaps even a link tool. I thought about this in my UI round, but other than tweaking the icon a little I didn't see a clear win. Happy to revise though if there's a consensus – I thought of changing the icon to several of links in a chain, but this would indicate the joint is made of flexible sections, when actually it is a solid rod with a pivot at each end. Regards, --Gary ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [Cs-dev] Sugar on a Stick - and OLPCsound/Csound
Peter, It seems the latest Csound5.10 has not yet made it into updates-testing. I'll try again on at least a daily basis. I've learned a lot about Fedora/Sugar since July 1; I did get your message then, but I don't think I understood its full meaning. At any rate, I did wait for the regular update to appear (which it did shortly). I'll do the same now for the testing version. I appreciate your bearing with this newbee. Art Hunkins - Original Message - From: Peter Robinson pbrobin...@gmail.com To: Art Hunkins abhun...@uncg.edu Cc: sugar-devel@lists.sugarlabs.org Sent: Saturday, July 18, 2009 3:54 AM Subject: Re: [Sugar-devel] [Cs-dev] Sugar on a Stick - and OLPCsound/Csound Art, You need to enable the testing repo. yum --help is your friend here. To enable it on a temporary basis you can do yum --enablerepo=updates-testing update csound or to enable it permanently you edit the /etc/yum.repos.d/fedora-updates-testing.repo changing the first enable= line from 0 to 1. I emailed you the details of how to do that back on Jul 1st. Peter On Sat, Jul 18, 2009 at 2:49 AM, Art Hunkinsabhun...@uncg.edu wrote: Peter, Thanks for this. Can you, or anyone, point me to specific instructions as to how to download and install either of these options? I've tried the obvious methods, such as: yum updates-testing csound and yum update csound but have hit a blank wall. I've never tried anything in testing mode before. Art Hunkins - Original Message - From: Peter Robinson pbrobin...@gmail.com To: Art Hunkins abhun...@uncg.edu Cc: sugar-devel@lists.sugarlabs.org; csound-de...@lists.sourceforge.net Sent: Thursday, July 16, 2009 7:43 AM Subject: Re: [Sugar-devel] [Cs-dev] Sugar on a Stick - and OLPCsound/Csound Hi All, I've tested and applied the patch to F11 and pushed it out as a updates-testing. Please test. https://admin.fedoraproject.org/updates/csound-5.10.1-9.fc11 Or if your too impatient to wait for the updates-testing push you can grab the rpms from koji directly http://koji.fedoraproject.org/koji/buildinfo?buildID=114648 Peter On Mon, Jul 13, 2009 at 4:03 PM, Art Hunkinsabhun...@uncg.edu wrote: Aleksey, Thanks for undertaking this task. Please let me know when the revised build of Csound5.10 is available for update on SoaS. I'm eager to be assured that it solves the compatibility issue with python 2.6. Art Hunkins - Original Message - From: Aleksey Lim alsr...@member.fsf.org To: Art Hunkins abhun...@uncg.edu Cc: Michael Gogins michael.gog...@gmail.com; sugar-devel@lists.sugarlabs.org Sent: Monday, July 13, 2009 12:02 AM Subject: Re: [Sugar-devel] [Cs-dev] Sugar on a Stick - and OLPCsound/Csound On Sun, Jul 12, 2009 at 03:19:31PM -0400, Art Hunkins wrote: Mike Gogins, a Csound developer, has taken care of the Scons issue with Csound5.10, as discussed below. I'd be overjoyed if one of you Sugar developers could take it from there so that we can have SoaS with a Csound that works with python2.6. I can build rpm for soas env. but I'm waiting for fixing my problems with ISP so, I can't do it in nearest few days. Just an option, using Mandriva of Suse ;) -- Aleksey ___ 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] Plain Query Format proposal
Hi all, I'm going to implement [1] for 0.86. Does anyone have any preferences about predefined terms [2]. Jim: I guess your activities (GetInternetArchiveBooks at least) may have some special terms. [1] http://wiki.sugarlabs.org/go/Features/Plain_Query_Format [2] http://wiki.sugarlabs.org/go/Features/Plain_Query_Format#Users_predefined_terms -- Aleksey ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
