Re: [Sugar-devel] Multitouch in Fedora
On Wed, Jun 9, 2010 at 22:18, Peter Robinson pbrobin...@gmail.com wrote: Hi, I know people were wondering about multitouch. In the last couple of days there's a couple of posts regarding Multitouch in fedora for those that are interested. http://www.j5live.com/2010/06/09/multitouch-working-in-fedora/ http://blogs.gnome.org/carlosg/2010/06/09/getting-multitouch-to-just-work/ I asked around yesterday and as far as I could see nobody were planning any specific work on (multi-)touch with Gtk+. As the companies doing Linux products with that capability had gone with Qt. But just now have come across this news: http://infoworld.com/d/mobilize/canonical-developing-ubuntu-os-tablets-778 I guess they are talking about something related to Unity, which is Canonical's UX of choice for netbooks. Unity was supposed at the UDS to sit in a similar place to GNOME Shell so it will most probably be using multi touch with Gtk+. If anybody has more details in how this impacts OLPC and Sugar, it would be great if they could share. Regards, Tomeu ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Multitouch in Fedora
On Thu, Jun 10, 2010 at 09:13:49AM +0200, Tomeu Vizoso wrote: I guess they are talking about something related to Unity, which is Canonical's UX of choice for netbooks. Unity was supposed at the UDS to sit in a similar place to GNOME Shell so it will most probably be using multi touch with Gtk+. If anybody has more details in how this impacts OLPC and Sugar, it would be great if they could share. Perhaps trivial, but Ubuntu jobs have been in my RSS feeds for a year or two, and there's been a row of ARM related positions. -- 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] Error in running Physics activity And how read .pdf in Read Activity
Again with problem, Running sugar on Ubuntu 9.10, sugar version is 0.88, I installed physics activity by downloading from sugar/activities page. When i try to run, it gives error as follow: Traceback (most recent call last): File physics.py, line 38, in module import Box2D as box2d File lib/Box2D-2.0.2b1-py2.5-linux-i686.egg/Box2D/__init__.py, line 23, in module File lib/Box2D-2.0.2b1-py2.5-linux-i686.egg/Box2D/Box2D.py, line 6, in module File lib/Box2D-2.0.2b1-py2.5-linux-i686.egg/Box2D/_Box2D.py, line 7, in module File lib/Box2D-2.0.2b1-py2.5-linux-i686.egg/Box2D/_Box2D.py, line 6, in __bootstrap__ ImportError: /home/smita/.python-eggs/Box2D-2.0.2b1-py2.5-linux-i686.egg-tmp/Box2D/_Box2D.so: wrong ELF class: ELFCLASS32 Another query I want to ask is, I am able to view PDF file which is on my USB stick, as a external storage space. But when I copied the same PDF file in my .sugar/default/datastore folder. I am not able to browse for a PDF. Is there any mechanism where I can view .pdf file in read activity, or it can be shown in journal, because in journal there is no extenstion for .pdf, it shows for text,video, image and latest activity I have done. Also, If I want to copy something from my USB stick to journal how to do it, because when I browse USB, and select file wanted to copy, it gives me copy option but there is no paste option in journal. -- Ganesh Gajare (Dragger) Be a FOSSERS, use GNU/Linux ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Error in running Physics activity And how read .pdf in Read Activity
Hi Sorry cant help with error log but: space. But when I copied the same PDF file in my .sugar/default/datastore folder. I am not able to browse for a PDF. simply copying to datastore will probably not work, journal bundles include mime type which control what Activities will open the file Is there any mechanism where I can view .pdf file in read activity, or it can be shown in journal, because in journal there is no extenstion for .pdf, it shows for text,video, image and latest activity I have done. using the journal to copy should set the mime and read will open it Also, If I want to copy something from my USB stick to journal how to do it, because when I browse USB, and select file wanted to copy, it gives me copy option but there is no paste option in journal. after you have mounted your usb there should be icons of the usb and the journal at the bottom of the journal screen, simply drag the file onto the icon to copy it (creating a bundle including mime) Tony ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Hypothetical sugar-0.90 material, draft 1.
On 10 June 2010 04:28, Jameson Quinn jameson.qu...@gmail.com wrote: 2010/6/9 Luke Faraone l...@faraone.cc -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 06/09/2010 08:11 PM, Bernie Innocenti wrote: As far as I know, Browse is still the only hulahop user on this planet, so it's not like we need to keep it around for API compatibility. Actually, hulahop is used by pyjamas[1], as evidenced by these bug reports[2][3] spawned when sugar-hulahop was removed from Ubuntu Lucid. An aside, according to upstream this is not an integral part of their project, but it might be a good idea to involve them in the discussion. These days, I do my work in pyjamas - on the cloud. I have never used pyjamas on the desktop, but for people who do, hulahoop* was the least painful way to get there, and its removal sparked indignation. *OK, it's called hulahop, but this way all the code names mesh more surreally. Sir, you made my day. Seriously, though: the fact that pyjamas-desktop can exist without hulahop doesn't make it attractive to lose it. It may not be integral, but I don't see anybody in the pyjamas world who would be replacing it any time soon, so it is essential as a practical matter. Jameson For pyjamas's purposes, i'm not sure if webwrap (my abstraction layer over hulahop and pywebkitgtk) would be enough. But if I do this right, all Sugar apps will be able to use either hulahop or pywebkitgtk without any further effort. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [SoaS] Heads-up: POSSE folks hacking in Fedora/Sugar thisweek and next
[In light of sense and recent conversations, please can we not cross-post to five mailing lists in the future unless there is clear information that all lists can benefit from] On Wed, Jun 09, 2010 at 03:37:19PM -0400, Walter Bender wrote: On Wed, Jun 9, 2010 at 3:26 PM, Peter Robinson pbrobin...@gmail.com wrote: On Wed, Jun 9, 2010 at 7:50 PM, Art Hunkins abhun...@uncg.edu wrote: I've noticed that neither the SoaS CD Boot Helper nor the SoaS Floppy Disk Boot Helper manage to boot SoaS Mirabelle (Fedora 13). [Please tell me specific devices that don't boot using boot helper CD] [Helper CD is fine, think Windows 2000-era PCs as most benefited] This conversation is about as useful as emailing a car designer's mailing list and saying I bought some diesel but I can't get to the supermarket. We need: 1) Specific machines (BIOS + motherboard model #s) that don't work 2) Precise symptoms - doesn't work, doesn't boot, crashes, hangs, are all useless and frustrating for everyone. Otherwise please don't waste anyone's time. Art Hunkins Peter -walter Martin pgpX53QuZqmKC.pgp Description: PGP signature ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Hypothetical sugar-0.90 material, draft 1.
El Wed, 09-06-2010 a las 23:46 -0300, Gonzalo Odiard escribió: SocialCalc depends of hulahop. My activity Elements too. Ugh. BTW, SocialCalc hardcodes a 3-second delay for localization which opens a race condition. It works intermittently on the XO-1 with Sugar 0.84 and it probably fails to work altogether in other scenarios. Does anyone have any idea how it could be done in an event-driven way? I'm afraid I know nothing about XPCOM embedding. -- // 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] [ASLO] Release Our Music-5
Activity Homepage: http://activities.sugarlabs.org/addon/4226 Sugar Platform: 0.82 - 0.88 Download Now: http://activities.sugarlabs.org/downloads/file/26942/ourmusic-5.xo Release notes: Cosmetic change only 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] [ASLO] Release Our Music MC-5
Activity Homepage: http://activities.sugarlabs.org/addon/4227 Sugar Platform: 0.84 - 0.88 Download Now: http://activities.sugarlabs.org/downloads/file/26940/ourmusicmc-5.xo Release notes: Cosmetic change only Sugar Labs Activities http://activities.sugarlabs.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Error in running Physics activity And how read .pdf in Read Activity
Hi Ganesh, Let me try this email thing again ;) On 10 Jun 2010, at 10:26, ginovation ginovat...@gmail.com wrote: Again with problem, Running sugar on Ubuntu 9.10, sugar version is 0.88, I installed physics activity by downloading from sugar/activities page. When i try to run, it gives error as follow: Traceback (most recent call last): File physics.py, line 38, in module import Box2D as box2d File lib/Box2D-2.0.2b1-py2.5-linux-i686.egg/Box2D/__init__.py, line 23, in module File lib/Box2D-2.0.2b1-py2.5-linux-i686.egg/Box2D/Box2D.py, line 6, in module File lib/Box2D-2.0.2b1-py2.5-linux-i686.egg/Box2D/_Box2D.py, line 7, in module File lib/Box2D-2.0.2b1-py2.5-linux-i686.egg/Box2D/_Box2D.py, line 6, in __bootstrap__ ImportError: /home/smita/.python-eggs/Box2D-2.0.2b1-py2.5-linux-i686.egg-tmp/Box2D/_Box2D.so: wrong ELF class: ELFCLASS32 This is way over my head, but a quick google on that error indicates you are running on a 64bit platform, and that Physics only has a 32bit bundled with it for Box2D. If you file a ticket with the above traceback text on bugs.sugarlabs.org someone may be able to help fix at some point. Another query I want to ask is, I am able to view PDF file which is on my USB stick, as a external storage space. But when I copied the same PDF file in my .sugar/default/datastore folder. I am not able to browse for a PDF. Is there any mechanism where I can view .pdf file in read activity, or it can be shown in journal, because in journal there is no extenstion for .pdf, it shows for text,video, image and latest activity I have done. Also, If I want to copy something from my USB stick to journal how to do it, because when I browse USB, and select file wanted to copy, it gives me copy option but there is no paste option in journal. From the Journal view you should be able to drag and drop the item you want down into the Journal icon in the bottom device strip that appears. Also from a Terminal activity there is a copy-to-journal command that will add files into the Journal. Regards, --Gary -- Ganesh Gajare (Dragger) Be a FOSSERS, use GNU/Linux ___ 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] Journal Implementation
Hello, my name is Bao Vuong. I am trying to implement a feature to the irc that lets a journal entry store the nickname and channels. I read that I need to define read_file and write_file methods. Are there any simple examples I can use? Or a tutorial of how to make one to work? Thank you. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Journal Implementation
Hello, my name is Bao Vuong. I am trying to implement a feature to the irc that lets a journal entry store the nickname and channels. I read that I need to define read_file and write_file methods. Are there any simple examples I can use? Or a tutorial of how to make one to work? Dear Pippy folks, I think your assistance has just been requested! :) Regards, Michael ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Journal Implementation
Hi, A nicely commented example (courtesy Dinko Galetic) demonstrating file operations such as reading and writing can be found here [1]. You may also find this documentation [2] on the python website useful. -- Cheers, Anish [1] http://git.sugarlabs.org/projects/pippy/repos/dgaletic-gsoc2010/blobs/master/data/GSOC%20examples/file%20writing%20and%20reading [2] http://docs.python.org/tutorial/inputoutput.html#reading-and-writing-files On Thu, Jun 10, 2010 at 8:27 PM, Michael Stone mich...@laptop.org wrote: Hello, my name is Bao Vuong. I am trying to implement a feature to the irc that lets a journal entry store the nickname and channels. I read that I need to define read_file and write_file methods. Are there any simple examples I can use? Or a tutorial of how to make one to work? Dear Pippy folks, I think your assistance has just been requested! :) Regards, Michael ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] [ASLO] Release Abacus-13
Activity Homepage: http://activities.sugarlabs.org/addon/4293 Sugar Platform: 0.82 - 0.88 Download Now: http://activities.sugarlabs.org/downloads/file/26944/abacus-13.xo Release notes: * added save/restore of custom abacus parameters Sugar Labs Activities http://activities.sugarlabs.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [IAEP] Supporting Sugar .88 on the XO1
On Thu, May 20, 2010 at 06:48:31PM -0500, David Farning wrote: As Bernie announced, we working on supporting Sugar .88 on the XO-1. This projects is customer driven by the deployment in Paraguay. They, along with bernie, made a decision that it would be more useful, usable, and cost effective to settle on .88 rather than .82. This strictly a decision made by a single deployment, which I support. Great news. Please CC me to bugs/patches involved to this deployment. For now, I'm more working on 0sugar/polyol/libjournal and don't track core related stuff often, but I'll do my best. Besides, I'm planing (next week) start changing ASLO code base (will post to sugar-devel@ about it) to make ASLO more corresponding to particular deployment needs (per deployment QA and activities list at least). As an ecosystem we can make lists of Pros on Cons why this is a good or bad decision and why I am an idiot. At the end of the day this was a decision made by a deployment. The primary reason for this decision is that the deployment does not yet has an established base of .82 machines. Something we need to be aware of as developers is that deployments think on a much longer scale. As developers, if we have a bug we can commit a fix and rebuild within a few days. Deployments can take weeks if not months to push a minor update. Major version upgrades are something developers can do every six months. From my experience a couple couple of weeks of 'hmmm, better file a bug on that' and I have well running machines after an upgrade. For a enterprise, such as a deployment, the decision to update becomes much harder and takes much longer to implement. As Martin pointed out, a significant amount of Quality Assurance goes into a deployment upgrade. Not only do the hardware, OS, and learning platform need to work together, all infrastructure, activities and third party applications must also work after the update. The problem just got significantly harder:) If I hit a bug while while sitting in my office that is one thing. If a teacher hits a bug where the computers no longer connect to the server that is another thing entirely. On the other hand, there have been several significant improvements in both Sugar and Fedora over the last couple of releases. It would be valuable to make those improvement available to end users. My research has indicated that education institutions find that 3 years is the right balance between stability and improved functionality of new software. Because to the newness of the Sugar 2 years is a reasonable first round of updates due to the higher than normal increases in usefulness and usability. Blame and credit are important motivators in this game:( As such, if we fail, it is the fault of Bernie, paraguayeduca, and I for: 1) starting with a bad premise, 2) making bad technical decision, or 3) making bad operational decisions. If we fail it will be due to the cooperative efforts of deployments, Sugar Labs, OLPC, and other interested third parties. david ___ IAEP -- It's An Education Project (not a laptop project!) i...@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep -- Aleksey ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] [ASLO] Release Record-79
Activity Homepage: http://activities.sugarlabs.org/addon/4081 Sugar Platform: 0.82 - 0.88 Download Now: http://activities.sugarlabs.org/downloads/file/26943/record-79.xo Release notes: This version of Record fixes the UI which is broken on sugar-0.86 and beyond. Sugar Labs Activities http://activities.sugarlabs.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Hypothetical sugar-0.90 material, draft 1.
On Tue, Jun 8, 2010 at 12:54 AM, Michael Stone mich...@laptop.org wrote: Under the temporary working hypothesis that we want to make a Sugar release in a couple of months, I'd like to know more about what we might find ourselves integrating. Here's my current list of, er... mostly unvetted rumors. :) Hi Michael, thanks for taking on this effort. Overall, it's a fantastic thing that this is rolling forward. The two first items on your list make me think a bit. - 0install and Vala are controversial, risky and not focussed on pressing end-users' needs. Yes there are some benefits and potential to both (otherwise Aleksey would not be working on them! :-) ) but they also break lots of toys. - Reworking the datastore... while I welcome efforts in a new datastore... _every Sugar release has a new DS implementation_ and they get little testing and I've seen extremely light thinking about what is _actually_ needed. We need _a good, polished DS that covers many aspects sanely_... a new DS is unlikely to do so. IOWs the barrier to merge a new DS should be high. It just triggers my CADT alarms http://www.jwz.org/doc/cadt.html Hopefully your list is not prioritised ;-) and it's just an accident that those two are top-of-the-list... Or maybe there's a goal to have 0.90 be a break lots of toys towards a 'developer release' and then make 1.0 the real deal. m -- martin.langh...@gmail.com mar...@laptop.org -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Journal Implementation
Take a look at this hello world activity, hopefully is what you need http://oficina.paraguayeduca.org/~mabente/codesnacks/sugar/HelloWorldDS.activity.tar.bz2 On Thu, 2010-06-10 at 10:38 -0400, Quoc-Bao Vuong wrote: Hello, my name is Bao Vuong. I am trying to implement a feature to the irc that lets a journal entry store the nickname and channels. I read that I need to define read_file and write_file methods. Are there any simple examples I can use? Or a tutorial of how to make one to work? Thank you. ___ 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] Journal Implementation
Bao, Have I got a manual for you! http://en.flossmanuals.net/ActivitiesGuideSugar/Introduction James Simmons Date: Thu, 10 Jun 2010 10:38:45 -0400 From: Quoc-Bao Vuong vq...@lv5.org Subject: [Sugar-devel] Journal Implementation To: sugar-devel@lists.sugarlabs.org Message-ID: aanlktilocma6ruw6uzammsie5whdzk9swxlstwf0p...@mail.gmail.com Content-Type: text/plain; charset=iso-8859-1 Hello, my name is Bao Vuong. I am trying to implement a feature to the irc that lets a journal entry store the nickname and channels. I read that I need to define read_file and write_file methods. Are there any simple examples I can use? Or a tutorial of how to make one to work? Thank you. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Hypothetical sugar-0.90 material, draft 1.
On Thu, Jun 10, 2010 at 11:48:50AM -0400, Martin Langhoff wrote: On Tue, Jun 8, 2010 at 12:54 AM, Michael Stone mich...@laptop.org wrote: Under the temporary working hypothesis that we want to make a Sugar release in a couple of months, I'd like to know more about what we might find ourselves integrating. Here's my current list of, er... mostly unvetted rumors. :) Hi Michael, thanks for taking on this effort. Overall, it's a fantastic thing that this is rolling forward. The two first items on your list make me think a bit. - 0install and Vala are controversial, risky and not focussed on pressing end-users' needs. Yes there are some benefits and potential to both (otherwise Aleksey would not be working on them! :-) ) but they also break lots of toys. I would say this is targeting to break not toys but players' minds :). The core idea behind these tools, they are just tools, to reach workflow of huge LEGO i.e. low floor - declaring base rules that let use/share/change things more smooth and decentralized in heterogeneous environment (not only for particular deployment like OLPC) when there is only doer-doer interaction scheme. This is not replacing/substitution of existed major sugar core workflow (targeting mainly on deployment e.g. GNU/Linux distributions or OLPC) but about adding another vector. And, I'm tending to think that this 0sugar/polyol/etc stuff is more for Activity Team rather than Development Team. - Reworking the datastore... while I welcome efforts in a new datastore... _every Sugar release has a new DS implementation_ and they get little testing and I've seen extremely light thinking about what is _actually_ needed. We need _a good, polished DS that covers many aspects sanely_... a new DS is unlikely to do so. IOWs the barrier to merge a new DS should be high. It just triggers my CADT alarms http://www.jwz.org/doc/cadt.html Hopefully your list is not prioritised ;-) and it's just an accident that those two are top-of-the-list... Or maybe there's a goal to have 0.90 be a break lots of toys towards a 'developer release' and then make 1.0 the real deal. m -- martin.langh...@gmail.com mar...@laptop.org -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ 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
Re: [Sugar-devel] Hypothetical sugar-0.90 material, draft 1.
On 06/10/2010 11:48 AM, Martin Langhoff wrote: - 0install and Vala are controversial, risky and not focussed on pressing end-users' needs. Yes there are some benefits and potential to both (otherwise Aleksey would not be working on them! :-) ) but they also break lots of toys. In my view, OLPC's ARM announcement creates a pressing problem of avoiding total confusion and fragmentation between different CPU architectures. 0install is, in my view, the most promising candidate solution. (I think the mention of Vala here is a red herring. The Vala sugar-toolkit effort is deliberately independent of Sugar version. It merely provides a new executable that activity developers may opt to include in their activity bundles.) - Reworking the datastore... while I welcome efforts in a new datastore... _every Sugar release has a new DS implementation_ and they get little testing and I've seen extremely light thinking about what is _actually_ needed. That's a very polite way of saying that you disagree with the extensive thinking that's been done about datastore design and implementation for the past three years. Perhaps you should publish your thoughts on DS architecture, or even just a list of use cases that you believe have been overlooked. We need _a good, polished DS that covers many aspects sanely_... a new DS is unlikely to do so. Do you think our current datastore meets your criteria? The consensus among the developers seems to be that our datastore does not live up to our goals for data management. --Ben signature.asc Description: OpenPGP digital signature ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Sugar Digest 2010-06-10
==Sugar Digest== 1. In their humorous treatise on political double-speak, ''Aristotle and an Aardvark go to Washington'', Thomas Cathcart and Daniel Klein define 'contextomy' as a subtle variation on the straw-man argument where you ''yank'' your victim's words out of context. A straw-man argument attributes an opponent to a position that in fact they do not hold. Contextomy adds the twist that you de-contextualize a quote in order to misstate (or overstate) their position. An example of contextomy is Mark Warschauer's post, ''OLPC: How Not to Run a Laptop Program'' [http://edutechdebate.org/one-laptop-per-child-impact/olpc-how-not-to-run-a-laptop-program/]. The premise of Warschauer's article is that the 'OLPC model' is simply passing out XOs and getting out of children’s way. No planning, no training, no teacher engagement... He goes on to say that this is an ill-advised model that does not work. In the article itself Warchauer never cites evidence that this is in fact the 'OLPC model', but in a comment he refers the reader to the OLPC mission statement as justification for his straw-man argument. Contextomy. I am not aware of any OLPC (or Sugar) deployment that in any way resembles Warshauer's straw man, in the United States or elsewhere. (The largest deployment in the United States is the city-wide deployment in Birmingham Alabama, which has involved extensive engagement of teachers, parents, the local university, libraries, churches, and other community assets. As with most deployments, there is extensive [http://www.nsf.gov/discoveries/disc_summ.jsp?cntn_id=116638 observation and longitudinal data] are beginning to become available.) Frankly, it is irresponsible for Warshauer to ignore these data. If he has any actual data to back up his position, he fails to cite it. Meanwhile, in this week's IRC discussion with teachers running Sugar projects, some evidence surfaced that contradicts Warshchauer's argument. (Apologies for my poor translation of the Spanish-language original.) [snip] :C: It is best to hear directly from the actors themselves ... :C: What can different group members tell us about their approaches to the training of teachers ... :F: In Nicaragua selected schools participate in the program, then teachers are invited to general training workshops three or two days. After that process initiated the visits and support in schools. :C: I can share one important element in what I do personally is to make sure that teachers can experience tools in the same way I expect them to do with the children ... :M: In Paraguay at this moment we are training teachers in seventh grade and we are developing a total of 150 hours where we develop educational issues. Principally develop their curricula in various activities. :C: We can not expect teachers to teach in a Constructionist, which taught for instructions ... :J: The workshop of the last two days had a lot of participation active teachers, and they built their own learning projects :S: J. took that approach. :J: [The teachers] said in their evaluation that what they liked most was the process :J: To share and create something with the other :I: It was very fruitful because the projects were assembled collaboratively :J: It is good to see that people value this opportunity, whether they are aware of their base constructionist or not :C: Another important element ... we do not want to sell the idea that after a workshop (2, 3 or up to 5 days) we will teach ALL ... the best way to learn is by doing and using XO Activities ... :M: The constructionist approach to ours is the challenge is that teachers so they understand :C: M, do you mean by that develop curricula of the various activities? :I: There is no construction without collaboration :I: Going from theory to practice and vice versa :M: to touch directly the issues that develop in the classroom :F: In our workshops we work in groups or tables work, we try to have a facilitator at each table. to Teachers are provided guidelines we have developed learning here at the Foundation. :C: According ... construction in collaboration .. I like that! :M: for those who can not be present, there information on a web site or examples of projects? :C: Thanks Mary ... perfect! :C: F. ... and there is a space for teachers develop their own guidelines? :I: They are rich in sharing desks, and guides such as built? :S: It is simple to really understand the idea let children explore, that each child has their skills and why the proposal should be diversified classroom, for example. The Teachers are great instructions. Yesterday there were many corrections at this point. :I: it is interesting that teachers construct their own guides ... :F: Right. At some point the workshop alongside teachers of each level and each plan their own activities :I: Interesting ... :S: In Colombia we have four objectives with the Qualifications [of deployments]: 1. Create local capacity to respond to administrative, technical and
[Sugar-devel] [DESIGN] Alerting users in case of write errors (sl#1842)
I was planning on fixing sl#1842 [1] but I'm not sure what should be the correct method of alerting users incase a write error does occur. Should I popup a dialog box, or use alerts like the one used in chat, sugar-commander? Suggestions welcome. [1] http://bugs.sugarlabs.org/ticket/1842, Cheers, Anish ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Error in running Physics activity And how read .pdf in Read Activity
Thanks Gary and Forster , the Idea given to copy file from USB to the journal works. On Thu, Jun 10, 2010 at 8:07 PM, Gary Martin garycmar...@gmail.com wrote: Hi Ganesh, Let me try this email thing again ;) On 10 Jun 2010, at 10:26, ginovation ginovat...@gmail.com wrote: Again with problem, Running sugar on Ubuntu 9.10, sugar version is 0.88, I installed physics activity by downloading from sugar/activities page. When i try to run, it gives error as follow: Traceback (most recent call last): File physics.py, line 38, in module import Box2D as box2d File lib/Box2D-2.0.2b1-py2.5-linux-i686.egg/Box2D/__init__.py, line 23, in module File lib/Box2D-2.0.2b1-py2.5-linux-i686.egg/Box2D/Box2D.py, line 6, in module File lib/Box2D-2.0.2b1-py2.5-linux-i686.egg/Box2D/_Box2D.py, line 7, in module File lib/Box2D-2.0.2b1-py2.5-linux-i686.egg/Box2D/_Box2D.py, line 6, in __bootstrap__ ImportError: /home/smita/.python-eggs/Box2D-2.0.2b1-py2.5-linux-i686.egg-tmp/Box2D/_Box2D.so: wrong ELF class: ELFCLASS32 This is way over my head, but a quick google on that error indicates you are running on a 64bit platform, and that Physics only has a 32bit bundled with it for Box2D. If you file a ticket with the above traceback text on bugs.sugarlabs.org someone may be able to help fix at some point. Yes, I am running activity on 64 bit machine. Surely I will raise ticket for this, because most of the platforms at my place are 64 bit implementing sugar, if this problem get solved will help us to use activity like physics efficiently. Another query I want to ask is, I am able to view PDF file which is on my USB stick, as a external storage space. But when I copied the same PDF file in my .sugar/default/datastore folder. I am not able to browse for a PDF. Is there any mechanism where I can view .pdf file in read activity, or it can be shown in journal, because in journal there is no extenstion for .pdf, it shows for text,video, image and latest activity I have done. Also, If I want to copy something from my USB stick to journal how to do it, because when I browse USB, and select file wanted to copy, it gives me copy option but there is no paste option in journal. From the Journal view you should be able to drag and drop the item you want down into the Journal icon in the bottom device strip that appears. Also from a Terminal activity there is a copy-to-journal command that will add files into the Journal. Regards, --Gary -- Ganesh Gajare (Dragger) Be a FOSSERS, use GNU/Linux ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- Ganesh Gajare (Dragger) Be a FOSSERS, use GNU/Linux ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Hypothetical sugar-0.90 material, draft 1.
On Thu, Jun 10, 2010 at 1:41 PM, Benjamin M. Schwartz bmsch...@fas.harvard.edu wrote: - Reworking the datastore... while I welcome efforts in a new datastore... _every Sugar release has a new DS implementation_ and they get little testing and I've seen extremely light thinking about what is _actually_ needed. That's a very polite way of saying that you disagree with the extensive thinking that's been done about datastore design and implementation for No. _It says exactly what it says_. People have been thinking lots about the fun part of the problem, thinking superficially about what they'll have fun implementing. Not about the complete problem space. Not about what hits users. Not about what we need for a saner implementation. even just a list of use cases that you believe have been overlooked. Ah... - ENOSPC? - Backwards compatibility? (Horrendously broken ATM on 0.84 -- I have a bad patch for that...) - Integration with GNOME? (for those dual desktop OS builds) - Some reasonable degree of atomicity? - Sensible backup/restore? - Smarter handling of bundle filetypes... = so together with the Journal, it can expose the many images or videos in a 'Record' = so the Record file format gets untangled - Re-thinking of the Journal / Datastore interactions to access the normal filesystem so that Gnome's ~/Documents directory can be browsed - Working gracefully with large files Do you think our current datastore meets your criteria? No. It has heaps of problems. And I love some the cool ideas (git-like smarts for example). But _first_ DS has to shed its current stupidities. Talk of a rewrite that lists cool ideas but none of the big gaps gives me the CADT shakes. Just in case, I am taking http://git.sugarlabs.org/projects/versionsupport-project/repos/mainline/blobs/master/datastore-redesign.html to be Sascha's plan. Hope that's the right one. Hate to sound so cranky, and I honestly like a VCS-styled Journal/DS. But there are many hard problems to solve in the Journal/DS, and many added hard problems that come with the VCS. Ignoring the hard problems and charging with the features won't help a bit. cheers, m -- martin.langh...@gmail.com mar...@laptop.org -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [DESIGN] Alerting users in case of write errors (sl#1842)
On Thu, Jun 10, 2010 at 2:13 PM, Anish Mangal anishmangal2...@gmail.comwrote: I was planning on fixing sl#1842 [1] but I'm not sure what should be the correct method of alerting users incase a write error does occur. Should I popup a dialog box, or use alerts like the one used in chat, sugar-commander? Suggestions welcome. [1] http://bugs.sugarlabs.org/ticket/1842, An alert like a chat or Activity sharing invitation would be nice, but one with a more visible signal is needed. I imagine an alert icon that rises out of the Frame, enlarges and glows for a few moments, then settles back to the Frame, but then shows a glowing edge or corona and bumps up slightly every 15 or 30 seconds in case the learner was focused on another Activity at the time the alert was first displayed (or just decided to postpone attention to the alert and then forgot about the pending need for attention). Of course, the icon should be clickable and reveal a useful palette of actions at any point in its lifetime. New alerts with behavior like the above would be welcome for invitations as well as errors. Thanks! --Fred ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [DESIGN] Alerting users in case of write errors (sl#1842)
We really really really ... need a general notification system. :D On Thu, 2010-06-10 at 14:39 -0400, Frederick Grose wrote: On Thu, Jun 10, 2010 at 2:13 PM, Anish Mangal anishmangal2...@gmail.com wrote: I was planning on fixing sl#1842 [1] but I'm not sure what should be the correct method of alerting users incase a write error does occur. Should I popup a dialog box, or use alerts like the one used in chat, sugar-commander? Suggestions welcome. [1] http://bugs.sugarlabs.org/ticket/1842, An alert like a chat or Activity sharing invitation would be nice, but one with a more visible signal is needed. I imagine an alert icon that rises out of the Frame, enlarges and glows for a few moments, then settles back to the Frame, but then shows a glowing edge or corona and bumps up slightly every 15 or 30 seconds in case the learner was focused on another Activity at the time the alert was first displayed (or just decided to postpone attention to the alert and then forgot about the pending need for attention). Of course, the icon should be clickable and reveal a useful palette of actions at any point in its lifetime. New alerts with behavior like the above would be welcome for invitations as well as errors. Thanks! --Fred ___ 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] [PATCH] Enhancements to Pippy UI
From: anishmangal2002 anishmangal2...@gmail.com
[1] Added a standard 'Edit' toolbar having undo, redo, copy and
paste buttons which also work when the activity is shared.
[2] When the activity is shared, the treeview in the activity host's
window does not disappear so he can load examples by clicking
on them. For other participants, the treeview is kept hidden.
[3] Bump version to v37
Tested alone on sugar-jhbuild-0.88 and as a shared session with
another sugar-jhbuild-0.88 session. (Thanks walterbender)
Signed-off-by: anishmangal2002 anishmangal2...@gmail.com
---
NEWS |7 +++
activity/activity.info |2 +-
pippy_app.py | 34 --
3 files changed, 40 insertions(+), 3 deletions(-)
diff --git a/NEWS b/NEWS
index b19533b..ab6ba9e 100644
--- a/NEWS
+++ b/NEWS
@@ -1,3 +1,10 @@
+37
+* Added a standard 'Edit' toolbar having undo, redo, copy and
+ paste buttons which also work when the activity is shared.
+* When the activity is shared, the treeview in the activity host's
+ window does not disappear so he can load examples by clicking
+ on them. For other participants, the treeview is kept hidden.
+
36
* Add COPYING based on activity.info license field, verify source file
licenses, include LICENSE from Elements upstream SVN, fixes
diff --git a/activity/activity.info b/activity/activity.info
index 26108f7..1664fd6 100644
--- a/activity/activity.info
+++ b/activity/activity.info
@@ -4,7 +4,7 @@ bundle_id = org.laptop.Pippy
service_name = org.laptop.Pippy
class = pippy_app.PippyActivity
icon = activity-icon
-activity_version = 36
+activity_version = 37
mime_types = text/x-python, pickle/groupthink-pippy
show_launcher = yes
diff --git a/pippy_app.py b/pippy_app.py
index 8edad4e..8f3580e 100644
--- a/pippy_app.py
+++ b/pippy_app.py
@@ -33,6 +33,7 @@ from gettext import gettext as _
from activity import ViewSourceActivity, TARGET_TYPE_TEXT
from sugar.activity.activity import ActivityToolbox, \
get_bundle_path, get_bundle_name
+from sugar.activity import activity
from sugar.graphics import style
from sugar.graphics.toolbutton import ToolButton
@@ -80,6 +81,16 @@ class PippyActivity(ViewSourceActivity,
groupthink.sugar_tools.GroupActivity):
palette.menu.append(menu_item)
menu_item.show()
+ EDIT TOOLBAR
+self._edit_toolbar = activity.EditToolbar()
+toolbox.add_toolbar(_('Edit'), self._edit_toolbar)
+self._edit_toolbar.show()
+
+self._edit_toolbar.undo.connect('clicked', self.undobutton_cb)
+self._edit_toolbar.redo.connect('clicked', self.redobutton_cb)
+self._edit_toolbar.copy.connect('clicked', self.copybutton_cb)
+self._edit_toolbar.paste.connect('clicked', self.pastebutton_cb)
+
# The go button
goicon_bw = gtk.Image()
goicon_bw.set_from_file(%s/icons/run_bw.svg % os.getcwd())
@@ -241,7 +252,8 @@ class PippyActivity(ViewSourceActivity,
groupthink.sugar_tools.GroupActivity):
return self.hpane
def when_shared(self):
-self.hpane.remove(self.hpane.get_child1())
+if not self.initiating:
+self.hpane.remove(self.hpane.get_child1())
global text_buffer
self.cloud.sharefield =
groupthink.gtk_tools.TextBufferSharePoint(text_buffer)
@@ -297,6 +309,24 @@ class PippyActivity(ViewSourceActivity,
groupthink.sugar_tools.GroupActivity):
self._vte.grab_focus()
self._vte.feed(\x1B[H\x1B[J\x1B[0;39m)
+def undobutton_cb(self, button):
+global text_buffer
+if text_buffer.can_undo():
+text_buffer.undo()
+
+def redobutton_cb(self, button):
+global text_buffer
+if text_buffer.can_redo():
+text_buffer.redo()
+
+def copybutton_cb(self, button):
+global text_buffer
+text_buffer.copy_clipboard(gtk.Clipboard())
+
+def pastebutton_cb(self, button):
+global text_buffer
+text_buffer.paste_clipboard(gtk.Clipboard(), None, True)
+
def gobutton_cb(self, button):
from shutil import copy2
self.stopbutton_cb(button) # try stopping old code first.
@@ -501,7 +531,7 @@ PIPPY_DEFAULT_ICON = \
def pippy_activity_version():
Returns the version number of the generated activity bundle.
-return 34
+return 37
def pippy_activity_extra_files():
Returns a map of 'extra' files which should be included in the
generated activity bundle.
--
1.7.0.4
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] GCompris packaging
(copying the tecnologia@ and sugar-devel@ lists for their information) Pacita, meet Aleksey, a very active contributor of Sugar, maintainer of the Sugar Labs activity library (ASLO) and packager of GCompris. Aleksey, meet Pacita, the lead of the education team of Paraguay Educa, who has a very strong background on pedagogy and teaching materials. The old monolithic bundle of GCompris was 70MB so big that it was causing problems at all levels with the limited disk space of the XO-1. The new strategy of pulverizing GCompris into a hundred tiny bundles made it unmanageable with the current shell (updater, launcher, switcher, etc). After separate discussions with Pacita and Aleksey, we all seem to agree that GCompris needs to be repackaged differently. From a technical standpoint, breaking GCompris into 4-5 activities would be ideal. However, it's not clear yet how the break should be done to make it more useful in the classroom: by subject? by age group? by curriculum? Educators can offer important input on this. Since I have very little insight on GCompris, I'll stay aside and follow the conversation. -- // 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] [PATCH] Enhancements to Pippy UI
Looks good to me, though I haven't tested it. A comment on if not self.initiating, to explain the intent, might be nice. --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] Hypothetical sugar-0.90 material, draft 1.
It seems that I cannot stop myself killing some kittens: As I see the problem is that the DS wants to solve a lot of problems in a general way. I think that this is simply impossible. A lot of companies tried to create some general storage abstraction other that files, but all of them failed (even M$ tried that for decades...). My prophecy is that you will fail as well. Another way to solve those problems would be to have every activity have its own journal with its own user interface. The activity then could use plain files for storage or an SQLite database or just append a text file. The point is that the storage would be activity specific, with activity dependent optimizations if necessary. The activity would also show a list of existing documents/objects when started and have a New... button to start a fresh one. It would also eliminate the troubled activity start mechanic from the activity ring. Of course SUGAR should have some very good library support to enable creating the default DS user interface in several lines of code. Of course for activities which does not save objects this would be optional. Now because the DS storage would be scattered between activities, they should have to implement a backup/restore API, lets call it BackupAgent: http://developer.android.com/guide/topics/data/backup.html A simple activity could just mention in the MANIFEST that it has a data directory to be backed up and that would be all. Of course the user should be able to use full text search so there should be a either a central index or the activities should implement a search API, lets call it SearchRecentSuggestionsProvider: http://developer.android.com/guide/topics/search/adding-recent-query-suggestions.html Of course SUGAR should have library support to ease creating this search functionality. Now to allow activities to share data they should implement some API to be able to provide content to other activities, lets call it ContentProvider: http://developer.android.com/guide/topics/providers/content-providers.html Of course a flag in the MANIFEST could just allow SUGAR to index the data automatically. It would need some primitive OLE (Object Linking and Embedding) capability which is currently missing from SUGAR, lets call it AppWidgetProvider: http://developer.android.com/guide/topics/appwidgets/index.html The remaining piece would be a dead simple Journal which would just list the recently launched activities. Now why would it be cool? 1. Searching among contacts, mp3 albums and picture bundles can be totally different from the end user perspective. 2. It can be efficient, does not need copying large amounts of data. 3. Activities could be launched from GNOME. 4. It could be backwards compatible (if the APIs are set in stone). 5. The DS code (the library) could be developed when there is a need in an activity, there is no need to redesign the whole thing over and over again. 6. And I am sure that I could find some more... Why it is just a pipe dream? 1. Python does not have anything like the DALVIK virtual machine so every Python process consumes a lot of memory. Because of this, implementing the above infrastructure would consume all available RAM and so would not work. Of course the DS part could be C++ code as well but unfortunately children could not look at the source. 2. It is already implemented so why bother? Now, you should not take this message too seriously but you could seriously consider a per activity DS if you have some free time. Martin Langhoff wrote: On Thu, Jun 10, 2010 at 1:41 PM, Benjamin M. Schwartz bmsch...@fas.harvard.edu wrote: - Reworking the datastore... while I welcome efforts in a new datastore... _every Sugar release has a new DS implementation_ and they get little testing and I've seen extremely light thinking about what is _actually_ needed. That's a very polite way of saying that you disagree with the extensive thinking that's been done about datastore design and implementation for No. _It says exactly what it says_. People have been thinking lots about the fun part of the problem, thinking superficially about what they'll have fun implementing. Not about the complete problem space. Not about what hits users. Not about what we need for a saner implementation. even just a list of use cases that you believe have been overlooked. Ah... - ENOSPC? - Backwards compatibility? (Horrendously broken ATM on 0.84 -- I have a bad patch for that...) - Integration with GNOME? (for those dual desktop OS builds) - Some reasonable degree of atomicity? - Sensible backup/restore? - Smarter handling of bundle filetypes... = so together with the Journal, it can expose the many images or videos in a 'Record' = so the Record file format gets untangled - Re-thinking of the Journal / Datastore interactions to access the normal filesystem so that Gnome's ~/Documents directory can be browsed -
[Sugar-devel] Updating SoaS CD Helper?
Here's what I know about the SoaS CD Helper: On Pentium III machines (Win 2000, ME, 98) SoaS Strawberry and Blueberry boot fine; Mirabelle (Fedora 13) doesn't. Mirabelle fails (gets stuck) after the completion of the SoaS 1 bar at the bottom of the screen, with the message: Unable to ennumerate USB device on port X (1 or 2) FWIW as well, my fairly modern dual-core AMD desktop also fails when booting Mirabelle from CD Helper. This too is right after completion of the SoaS 1 bar, but with blank screen except for a blinking dot in upper left corner. Keyboard is active, and pressing Alt-F4 brings up a login screen: localhost login: above which appears: Fedora release 13 (Goddard) My desktop also fails to boot SoaS *Blueberry* from CD Helper. Here the message, on otherwise blank screen, is: BD: barrier-based sync failed on dm-0:8 disabling barriers Bottom line?: Perhaps if CD Helper could be gotten to work on current systems (especially with Mirabelle), it would also work on the older machines. I'd be happy to be a tester, especially as I've a variety of older units. Art Hunkins - Original Message - From: Walter Bender walter.ben...@gmail.com To: Development of live Sugar distributions s...@lists.sugarlabs.org Cc: Art Hunkins abhun...@uncg.edu; Mel Chua m...@melchua.com; iaep i...@lists.sugarlabs.org; sugar-devel@lists.sugarlabs.org; fedora-education-l...@redhat.com; o...@lists.fedoraproject.org Sent: Wednesday, June 09, 2010 3:37 PM Subject: Re: [SoaS] [Sugar-devel] Heads-up: POSSE folks hacking in Fedora/Sugar thisweek and next On Wed, Jun 9, 2010 at 3:26 PM, Peter Robinson pbrobin...@gmail.com wrote: On Wed, Jun 9, 2010 at 7:50 PM, Art Hunkins abhun...@uncg.edu wrote: I've noticed that neither the SoaS CD Boot Helper nor the SoaS Floppy Disk Boot Helper manage to boot SoaS Mirabelle (Fedora 13). (For that matter, the Floppy Disk Helper doesn't boot anything but Strawberry.) I don't think Floppy Disks are relevant at all. I doubt any of the developers actually have a floppy drive to test. For the boot helper CD. I have no interest in getting it working, I have asked people to provide me specific devices that have problems and need the boot helper CD. The only one i've ever got back is newer Mac's. I know what that problem is. For the rest no one has bothered to send me the specs so I haven't bothered spending the time. I will dig up the old thread where I did offer the specs of the machines we encounter in the Boston Public Schools that will not boot directly off of USB, but are quite happy with a Helper CD. This is also true of the computer we have worked with at the YMCA. I suspect this is true of most of the computers in elementary schools and available to afterschool programs in much of the urban United States. Think Windows-2000-era machines and you will know what is in schools States-side. -walter Is anybody interested in working on this, or are we basically abandoning older computers? See above. Peter Art Hunkins - Original Message - From: Mel Chua m...@melchua.com To: fedora-education-l...@redhat.com; o...@lists.fedoraproject.org; iaep i...@lists.sugarlabs.org; sugar-devel@lists.sugarlabs.org; SoaS s...@lists.sugarlabs.org Sent: Wednesday, June 09, 2010 10:48 AM Subject: [Sugar-devel] Heads-up: POSSE folks hacking in Fedora/Sugar thisweek and next Next week we'll have another - slightly larger - batch from RIT doing the same thing, with myself, Chris Tyler, and Luke Macken focusing more on how to make Fedora a better environment for running/deploying/developing Sugar - if you have any thoughts in this direction, please send comments our way! (Things we've come up with so far: general Python development stuff, liveusb-creator hacks, SVG rendering working strangely in different recent versions of Fedora... we need to turn this into a proper ticket queue.) Just wanted to let y'all know. I'll blog this to Planet in a moment. --Mel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ SoaS mailing list s...@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/soas ___ SoaS mailing list s...@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/soas -- 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] Hypothetical sugar-0.90 material, draft 1.
You are not explaining why this will happen, so this point is moot. The reason is that it seems that it is impossible to do. I just extrapolated historical data. So we're indexing the data automatically, but we still don't have a datastore? Please explain how that would work. The Search activity's data is the generated index. And we want users to have to start other applications to find there stuff *why*? From what I can tell, the trend in the mobile space has been to unify searching across formats, a la the iOS's Spotlight. Exactly. Launch Pictures to handle pictures and launch Write to handle documents. You can have unified search across formats just not unified object handling (display, delete, etc). You'll be breaking backwards compatibility with every previous Sugar version (from what I can tell by your description), and rather than requring us to rewrite the Journal every so often in Sugar, each activity maintainer will have to rewrite it themselves. Now here is the interesting part. You already break compatibility. If there is shared code between these activities (since most cases involve similar models of data storage) we'll have to patch each individually, rather than a shared library. That is the point, to not have shared DS code other than some library what would be included in every activity which would provide some data to search or other activities. Most activities will not have such data. The few activities which would have such DS could be updated individually without breaking compatibility. They could be developed individually *when* *the* *need* *arises*. Now all that said, the Android model is overkill. Something much-much simpler could work IMHO. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] GCompris packaging
Hi Bernie and all, Adding Bruno to the conversation -- he's the main developer of Gcompris (outside Sugar) and I'm not 100% sure he's on this list. He might have ideas about this. Best, Bernie Innocenti ber...@codewiz.org writes: (copying the tecnologia@ and sugar-devel@ lists for their information) Pacita, meet Aleksey, a very active contributor of Sugar, maintainer of the Sugar Labs activity library (ASLO) and packager of GCompris. Aleksey, meet Pacita, the lead of the education team of Paraguay Educa, who has a very strong background on pedagogy and teaching materials. The old monolithic bundle of GCompris was 70MB so big that it was causing problems at all levels with the limited disk space of the XO-1. The new strategy of pulverizing GCompris into a hundred tiny bundles made it unmanageable with the current shell (updater, launcher, switcher, etc). After separate discussions with Pacita and Aleksey, we all seem to agree that GCompris needs to be repackaged differently. From a technical standpoint, breaking GCompris into 4-5 activities would be ideal. However, it's not clear yet how the break should be done to make it more useful in the classroom: by subject? by age group? by curriculum? Educators can offer important input on this. Since I have very little insight on GCompris, I'll stay aside and follow the conversation. -- Bastien ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [PATCH] Enhancements to Pippy UI
Point taken :) Anish Mangal On Fri, Jun 11, 2010 at 2:41 AM, Benjamin M. Schwartz bmsch...@fas.harvard.edu wrote: Looks good to me, though I haven't tested it. A comment on if not self.initiating, to explain the intent, might be nice. --Ben ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Hypothetical sugar-0.90 material, draft 1.
2010/6/10 NoiseEHC noise...@freemail.hu: It seems that I cannot stop myself killing some kittens: Well. Do kill some metaphorical kittens but... maybe... try to avoid being a /perfect example of CADT/. Or maybe it's a good joke and I need to relax ;-) m -- martin.langh...@gmail.com mar...@laptop.org -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] GCompris packaging
On Thu, Jun 10, 2010 at 03:49:28PM -0400, Bernie Innocenti wrote: (copying the tecnologia@ and sugar-devel@ lists for their information) Pacita, meet Aleksey, a very active contributor of Sugar, maintainer of the Sugar Labs activity library (ASLO) and packager of GCompris. Aleksey, meet Pacita, the lead of the education team of Paraguay Educa, who has a very strong background on pedagogy and teaching materials. The old monolithic bundle of GCompris was 70MB so big that it was causing problems at all levels with the limited disk space of the XO-1. The new strategy of pulverizing GCompris into a hundred tiny bundles made it unmanageable with the current shell (updater, launcher, switcher, etc). After separate discussions with Pacita and Aleksey, we all seem to agree that GCompris needs to be repackaged differently. From a technical standpoint, breaking GCompris into 4-5 activities would be ideal. Full v9.3 GC weights 45M (w/o voices), so if it is ok it could be just one activity. However, it's not clear yet how the break should be done to make it more useful in the classroom: by subject? by age group? by curriculum? Educators can offer important input on this. There is some kind of administrative activity[1], but I never touched this. Will see how to sugarize it, I guess with this, we can effectively rich what we need. [1] http://gcompris.net/wiki/index.php?title=Manual#Administering_GCompris Since I have very little insight on GCompris, I'll stay aside and follow the conversation. -- // Bernie Innocenti - http://codewiz.org/ \X/ Sugar Labs - http://sugarlabs.org/ -- Aleksey ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Hypothetical sugar-0.90 material, draft 1.
On Thu, Jun 10, 2010 at 02:28:01PM -0400, Martin Langhoff wrote: On Thu, Jun 10, 2010 at 1:41 PM, Benjamin M. Schwartz bmsch...@fas.harvard.edu wrote: In my view, OLPC's ARM announcement creates a pressing problem of avoiding total confusion and fragmentation between different CPU architectures. 0install is, in my view, the most promising candidate solution. I agree that the problem of multiple arches exists. But you can refer to the lengthy thread about 0install about the nasty tradeoffs involved. No intention to rehash a controversial topic here :-) No intension to fallback to another useless discussion. Just want to synchronize what other people think with what I'm thinking they think. --- So, what the object... The code: 1.1) Sugar Platform dependencies i.e. bunch of required libraries/applications like glibc and xulrunner etc. 1.2) Sucrose 1.3) Sugar Objects (to not separate to activities and documents, since some time it is hard e.g. TA objects or Etoys projects). 1.4) Sugar Objects dependencies that are not part of Sugar Platform could be various libraries or activities (e.g. TA for TA objects) Who might distribute this code: 2.1) GNU/Linux distribution from native packages 2.2) sugar deployments like OLPC that use the same mechanisms like distros but provide additional packages/QA/support efforts 2.3) directly from creator Where this code could be used: 3.1) on XO deployed by particular distributor with sugar installed 3.2) on regular GNU/Linux desktop with some kind of sugar support About subject... I hope I won't be failed if say that ideal sugar user is doer. --- And most popular scheme should be 1.3(4) - 2.3 - 3.*. In most cases for Sugar Objects and in less cases for activities (but still important) and its dependencies (like if some one created convenience math library). Trying to push this flow via 2.1 (less in 2.2) makes the flow much smaller. And tool like 0install lets us follow 2.3. At the same time 0install is not intended to cover all possible variants i.e. not lets switch all sugar deployments to 0install. For example for all sugar deployments regular GNU/Linux distribution way is more preferable. One of core benefits of 0install is that is lets us reuse 2.1 and 2.2 e.g. if someone tying to launch Vnc activity, sugar will popup window with suggestions to install native vnc package. --- Back to original purpose of this post, are people who disagree with 0install (which is just an instrument), are disagree with particular instrument or with 1.3(4) - 2.3 - 3.* scheme itself (or think it is not so important to make not trivial things to rich it). -- Aleksey ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] GCompris packaging
On Fri, Jun 11, 2010 at 01:18:34AM +0200, Bastien wrote: Hi Bernie and all, Adding Bruno to the conversation -- he's the main developer of Gcompris (outside Sugar) and I'm not 100% sure he's on this list. He is... but at this moment he could be trying to figure out how to use gimp to change the walls texture IRL to refresh his apartment :) He might have ideas about this. Best, Bernie Innocenti ber...@codewiz.org writes: (copying the tecnologia@ and sugar-devel@ lists for their information) Pacita, meet Aleksey, a very active contributor of Sugar, maintainer of the Sugar Labs activity library (ASLO) and packager of GCompris. Aleksey, meet Pacita, the lead of the education team of Paraguay Educa, who has a very strong background on pedagogy and teaching materials. The old monolithic bundle of GCompris was 70MB so big that it was causing problems at all levels with the limited disk space of the XO-1. The new strategy of pulverizing GCompris into a hundred tiny bundles made it unmanageable with the current shell (updater, launcher, switcher, etc). After separate discussions with Pacita and Aleksey, we all seem to agree that GCompris needs to be repackaged differently. From a technical standpoint, breaking GCompris into 4-5 activities would be ideal. However, it's not clear yet how the break should be done to make it more useful in the classroom: by subject? by age group? by curriculum? Educators can offer important input on this. Pacita, what about this workflow: * teacher creates new GCompris Administration[1] activity object, to * add change content of Classes, Groups and Profiles; different Administration instances will share this data to not recreate it every time * set activities list for this particular GCompris Administration object * teacher saves and shares GCompris Administration object * students join this object and follow regular GC workflow * teacher in runtime mode, can observe results in Reports tab in GCompris Administration [1] http://gcompris.net/wiki/index.php?title=Manual#Administering_GCompris -- Aleksey ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Paint: trying to fix #1771
I think it works, but i don't know if the right thing to do.
From 97fb2adb1ea97a472e020244ae7a2d22c7a94db3 Mon Sep 17 00:00:00 2001
From: Gonzalo Odiard godi...@gmail.com
Date: Fri, 11 Jun 2010 01:22:36 -0300
Subject: [PATCH] fix #1771 - paint overwrites file type instead of creating
new file
http://bugs.sugarlabs.org/ticket/1771
---
OficinaActivity.py |5 -
1 files changed, 4 insertions(+), 1 deletions(-)
diff --git a/OficinaActivity.py b/OficinaActivity.py
index c72576a..78bc8cf 100644
--- a/OficinaActivity.py
+++ b/OficinaActivity.py
@@ -140,8 +140,8 @@ class OficinaActivity(activity.Activity):
def read_file(self, file_path):
'''Read file from Sugar Journal.'''
+print 'reading file', file_path, mime_type,
self.metadata['mime_type']
-logging.debug('reading file %s', file_path)
pixbuf = gtk.gdk.pixbuf_new_from_file(file_path)
@@ -155,6 +155,9 @@ class OficinaActivity(activity.Activity):
self._setup_handle = self.fixed.connect('size_allocate',
size_allocate_cb)
+if self.metadata['mime_type'] != image/png:
+self._jobject.object_id = None
+
def write_file(self, file_path):
'''Save file on Sugar Journal. '''
--
1.6.6.1
--
Gonzalo Odiard
Responsable de Desarrollo
Sistemas Australes
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
