Re: [Sugar-devel] Physics activity development
Oh, and I don't know if it's still around, but jhbuild was pretty useful if you don't have an xo to work on. Alex On Tue, May 26, 2009 at 9:15 PM, Alex Levenson wrote: > A little background information. In the process of creating x2o, I created > Physics! sort of as a demo. So a lot of things are further along in x2o > because Physics! was sort of my sandbox for creating x2o. So if you want to > polish off Physics!, please take a look at what I did with x2o, which > integrates with the journal. > Alex > > > On Tue, May 26, 2009 at 9:00 PM, Asaf Paris Mandoki wrote: > >> Hi, >> >> I would like to get started adding the play/pause button and the pin >> button. Probably the next step is to integrate the activity with the >> journal. The only problem is that I haven't been able to get my development >> environment working. It seems there are some open issues with ubuntu. My >> plan right now is to wait until the Ubuntu issues are fixed. Any suggestions >> for a better setup? The only thing I have working now is a virtualbox >> environment where i've been testing the activity and found some bugs. I saw >> a commit with the "joystick" feature removed. Is the base code ready to >> start adding the minor button changes? >> >> Thanks, >> Asaf >> >> >> >> On Mon, May 25, 2009 at 2:17 AM, Brian Jordan wrote: >> >>> On Sun, May 24, 2009 at 8:59 PM, Gary C Martin >>> wrote: >>> > Hi Brian, >>> > >>> > On 24 May 2009, at 18:36, Brian Jordan wrote: >>> > >>> >> Hey all, >>> >> >>> >> Gary -- when you get a chance, can you add me as a committer on >>> >> git.sl.o? I'd like to help clean things up! >>> > >>> > You're added! :-) >>> > >>> > Can I request we try and make small clean commits and try to let others >>> know >>> > what we are doing. If you want to hack, Gitorious supports quite a nice >>> > 'Clone repository' and then 'Request merge' process (no commit rights >>> needed >>> > for the main project). The alternative, if you know what you are doing, >>> is >>> > just make your own local git branch to hack on, so you can take care of >>> any >>> > merge/conflict issues yourself when you fold it back into the current >>> > master. >>> > >>> > I'm far from a git expert, but I can recommend some bed time reading >>> at: >>> > >>> > >>> > http://www.eecs.harvard.edu/~cduan/technical/git/<http://www.eecs.harvard.edu/%7Ecduan/technical/git/> >>> > >>> > and/or >>> > >>> >http://gitready.com/ >>> > >>> >>> Thank you, will devote some to that! Need to learn to keep my crazy >>> features in branches. >>> >>> > I'd like to get on with Labyrinth work, if you're willing to have an >>> initial >>> > clean up of the Physics source in the next few days... so what was >>> > 'joysitck' feature all about? ;-) >>> >>> This would probably be best to describe on the wiki page, the idea was >>> to make a UI for assigning keys on the XO-1 to impulses or changes on >>> certain objects, so simple 2 player physics based games could be made >>> from within Physics. >>> >>> Agreed, though, I will rid that from the code so we have a nice base >>> line for crazy-feature branches. >>> >>> > Once the dev.sugarlabs.org component is added we should add the >>> > features/bugs in there to keep them all together. FWIW, from a UI point >>> of >>> > view I had in mind: >>> > >>> > 1) remove/disable 'joysitick' feature as I have no idea what it was >>> meant to >>> > be ;-) >>> > 2) build tool buttons correctly using RadioToolButton so they display >>> state >>> > correctly >>> > 3) use set_accelerator to define visible keyboard shortcuts for the >>> tools >>> > >>> >> Asaf -- do you have a http://git.sugarlabs.org account yet? >>> >> >>> >> This is some feedback from Asaf (these could fit as enhancements in >>> >> http://dev.sugarlabs.org/ ): >>> >> >>> >>> While playing with the activity I found a "pause" button to stop time >>> >>> could be very u
Re: [Sugar-devel] Physics activity development
; >>> >> >>> An other thing I think could be grate is to be able to create >> >>> attractors an repulsors. With stuff like this it gets pretty >> >>> interesting, we could have objects orbiting around the attractors. >> > >> > Yes, all good stuff, there's also a list on >> > http://wiki.laptop.org/go/Physics_%28activity%29 as well, but I'd vote >> for >> > cleaning up what we have first, perhaps adding a play/pause, and keeping >> > Journal state so kids can actually keep their Physics creations (and >> send >> > them to friends when using sugar 0.84). >> >> +1 +1 +1 >> >> Brian >> >> > >> > Regards, >> > --Gary >> > >> >> Thanks >> >> >> >> Brian >> >> >> >> On Sun, May 24, 2009 at 4:17 PM, Gary C Martin >> >> wrote: >> >>> >> >>> Hey Brian, >> >>> >> >>> On 24 May 2009, at 13:57, Brian Jordan wrote: >> >>> >> >>>> Hey Gary, >> >>>> >> >>>> First, I'm attaching Asaf Paris Mandoki, who contacted me last week >> >>>> with an interest in developing on the Physics activity, and has great >> >>>> ideas of things to add. This is a great opportunity! :) >> >>>> >> >>>> I can handle getting Physics on gitorious, the bug tracker and >> a.sl.o. >> >>>> I will try to complete this by the end of today. >> >>> >> >>> Having chatted with Alex Levenson, I've already kicked off the >> migration >> >>> for >> >>> Physics (rep is now in Gitorious, trac request is in, and I've started >> to >> >>> poke at the code, running well at least in sugar-jhbuild and sugar >> 0.84). >> >>> X2o is next on my hit list once Physics is in a reasonable state. >> >>> >> >>>> The things I can use some help with are (1) integrating proper >> >>>> localization to the activity and >> >>> >> >>> Yep, I'm going to do a pass at the code and tidy up some partially >> >>> implemented / broken UI stuff, before requesting it's addition to >> pootle >> >>> (best to start with a reasonably stable set of strings). Would also >> like >> >>> to >> >>> get/text resolution independence (for non XO hardware) and get the >> scene >> >>> state saving to Journal... >> >>> >> >>> Want to get the basics out the way first before we break it again with >> >>> exciting new features ;-) >> >>> >> >>>> (2) figuring out a good way to include the pybox2d source in the git >> >>>> repository, while including an >> >>>> F9-compatible binary on a.sl.o (this was brought up w.r.t. Pippy a >> >>>> couple of times on the fedora devel lists, but I don't remember >> seeing >> >>>> a clear way of how to handle it). >> >>> >> >>> Yea I was worried this might be an issue needing resolved, it's not my >> >>> area >> >>> of speciality, I'll need to take a deeper look at the source. >> >>> >> >>>> Thanks for the ping and your help!! >> >>> >> >>> No, thank you! I was expecting a wall of silence :-) >> >>> >> >>> Regards, >> >>> --Gary >> >>> >> >>>> Brian >> >>>> >> >>>> On Sat, May 23, 2009 at 3:19 PM, Gary C Martin > > >> >>>> wrote: >> >>>>> >> >>>>> Hi Guys, >> >>>>> >> >>>>> I'm making contact to see if any of you are still interested in >> >>>>> developing >> >>>>> your great Physics activity? Most of the active activity development >> >>>>> has >> >>>>> now >> >>>>> moved over to Sugar Labs infrastructure, and we've been getting some >> >>>>> requests for localising Physics. >> >>>>> >> >>>>> We have a Gitorious based source repository (there's no admin >> request >> >>>>> procedure, you can just register an account and migrate/create a >> >>>>> project): >> >>>>> >> >>>>> http://git.sugarlabs.org/ >> >>>>> >> >>>>> Our bug-tracker trac is at: >> >>>>> >> >>>>> http://dev.sugarlabs.org/ >> >>>>> >> >>>>> For activity distribution, Sugar Labs is customising Mozilla addon's >> >>>>> web >> >>>>> front/back end (we're trying to encourage activity developers to >> post >> >>>>> there >> >>>>> activity bundles here), it's still a little ugly but the theme/UI is >> >>>>> still a >> >>>>> work in progress :-) >> >>>>> >> >>>>> http://activities.sugarlabs.org/ >> >>>>> >> >>>>> If no one is available to help, I'd be happy to migrate Physics over >> to >> >>>>> the >> >>>>> Sugar Labs infrastructure, get it added to pootle so we can start >> >>>>> localisation and make sure bundles get released for easy download >> and >> >>>>> inclusion in images/distrobutions. If someone finds they have some >> time >> >>>>> to >> >>>>> come back later just ping me and I can easily add extra commiters; >> >>>>> though >> >>>>> with Gitorious, any one can branch anything, hack a bit, then submit >> a >> >>>>> merge >> >>>>> request (great workflow for dipping in and out of projects). >> >>>>> >> >>>>> Kind Regards, >> >>>>> Gary C Martin >> >>>>> Sugar Labs Activity Team >> >>>>> http://wiki.sugarlabs.org/go/Activity_Team >> >>>>> >> >>> >> >>> >> > >> > >> >> >> >> -- >> Brian Jordan >> OLPC Learning Team Technical Contractor >> Mobile Phone: +250 0783864924 >> Skype: bcjordan >> > > ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [OLPC-GSoC] Fwd: Google Summer of Code 2009 is a go!
Don't forget community mentors! On Fri, Jan 9, 2009 at 11:40 AM, Sharon Lally wrote: > > SJ, it sounds like a good planbut OLPC/1CC had problems retaining > mentors last year, so make sure not to over-commit. The remaining OLPC > staff may not have time to mentor. > Sharon > > > > > On Thu, Jan 8, 2009 at 7:10 PM, Samuel Klein wrote: > >> I'm copying our own gsoc list, and glad to clarify how this should work. >> >> I mentioned to Leslie yesterday that I expected SugarLabs and OLPC >> might have separate GSOC projects this year. Someone representing SL >> should write and formally get on their list of supported >> organizations. [note: this requires tax/ID information for SL] >> >> OLPC is interested in participating in GSOC this year... some of the >> projects I imagine would be activities or software for creation that >> would work particularly with the XO's hardware, or would help needs in >> OLPC deployments. >> >> It would be alright for both SugarLabs and OLPC to have people working >> on code that could be integrated into Sugar (note the different >> activity-development and python coding that was done both as an OLPC >> SoC project and via other orgs who wanted their projects to be useful >> to OLPC as an audience). It is also possible to submit an application >> to more than one organization. >> >> I recommend noting in our organization descriptions (and definition of >> what we are looking for) that people who want to develop tools and >> features for Sugar should apply to SL, and people who want to develop >> things specifically for OLPC deployments, or other software puzzles >> specific to XOs, should apply to OLPC. >> >> I would encourage most activity developers and activity mentors to >> tackle SoC projects under sugarlabs... >> >> SJ >> >> >> On Thu, Jan 8, 2009 at 5:26 PM, Ed McNierney wrote: >> > Yes, but in 2007 "they" were "us", no? >> > >> > Thanks, this is helpful information (I didn't know the status of >> > OLPC's previous GSoC work). I don't see why there is any reason to >> > presume that OLPC would NOT be interested in 2009 GSoC, but I don't >> > know of any active ideas/proposals kicking around here. I would >> > strongly encourage Sugar Labs ideas, however - to Ben's point, there >> > should be no confusion. The only things I could imagine (and it's >> > just imagining) coming from OLPC would be ancillary ideas (school >> > server add-ons?) that would be quite distinct from XO/Sugar software. >> > Go for it! >> > >> >- Ed >> > >> > >> > On Jan 8, 2009, at 3:54 PM, Wade Brainerd wrote: >> > >> >> On Thu, Jan 8, 2009 at 3:50 PM, Tomeu Vizoso >> >> wrote: >> >>> We should take into account that organizations are assigned slots >> >>> based on their well behaviour in past editions. >> >> >> >> To be clear, OLPC was put on GSoC 'probation' last year due to their >> >> poor performance reporting on students' work in 2007. They only >> >> received 4 slots despite hundreds of applications. >> >> >> >> Wade >> >> ___ >> >> 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 >> > >> ___ >> Gsoc mailing list >> g...@lists.laptop.org >> http://lists.laptop.org/listinfo/gsoc >> > > > > -- > Sharon Lally > Director, Human Resources > One Laptop Per Child > 617.452.5680 > sha...@laptop.org > www.laptop.org > > > Give a Laptop. Get a Laptop. Change the world! Visit > http://www.laptop.org/en/ for more information. > > ___ > Gsoc mailing list > g...@lists.laptop.org > http://lists.laptop.org/listinfo/gsoc > > ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
