Opportunity for speedup
I just measured the time taken by the boot animation by the simple technique of renaming /usr/bin/rhgb-client so the initscripts can't find it. With boot animation, OS build 7 (an older 8.2.1 candidate) takes 60 seconds from first dot (indicating OFW transfer to Linux) to Sugar "prompt for your name". Without it, 53 seconds. I repeated the test several times with consistent results. Clearly, it should be possible to display that amount of information in much less than 7 seconds. The boot animation code is in the OLPC domain, not the upstream domain, so replacing it should be relatively free of upstream politics. So if anybody is interested in implementing a relatively simple boot-time speedup, I offer this as low-hanging fruit. I suggest 1 second (differential time between animation and no-animation cases) as a reasonable target goal, assuming images of the complexity of the current ones. Arbitrary full-screen graphics might require more time, but speeding up the baseline case is a good starting point. Go wild. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: XFT emacs rocks on the XO...
On Wed, Feb 11, 2009 at 12:59 AM, Martin Langhoff wrote: > Also, the XO ships with a very limited vim. yum install vim-enhanced > has improved my part-time vim usage. can we fix this in the next refresh? how much extra space did it take? vim is useful. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
XFT emacs rocks on the XO...
Stock F9 emacs isn't very usable on the XO screen, unfortunately. Lack of fonts and high dpi make it rather painful. After struggling a bit to get a comfy hacking/editing environment on my XOs, I ended up installing the precooked Xft-enabled emacs rpms, as per: http://wiki.laptop.org/go/Emacs and after setting a nice readable font... I'm very happy with the setup. Also, the XO ships with a very limited vim. yum install vim-enhanced has improved my part-time vim usage. 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 ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Little bits of atomicity...
Hacking on bits of Browse is taking me down the path of reading various random bits of Sugar. And I wanted to drop a quick note... Modern POSIX systems give us a cheap safe atomic way of dealing with updates to small files: write to a tempfile and move it into place. Opening a critical file in place for update is fraught with problems, specially on a device where power is not guaranteed... ... like a schoolserver or a laptop... (That's the mantra I've taken with the XS. All the code must be failsafe.) Anyway, I tried to craft a patch for profile.py, only to find it's now gone gconf. So no patch today :-/ Having switched to gconf, I wonder, is there a plan for what to do when people need to fiddle with their Sugar config stuff? gconftool is significantly harder to use than nano or vi. 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 ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: updating activities
2009/2/10 victor : > Trying to update activities here, from the sugar control panel. It says it > cannot > access the network to check for updates, even if I have a an ethernet > connection > to the XO that is working (and I can ping the outside world). It prolly can't find the updater-page to check. When in the process of updating, you should see which uri it tries to check. See what it is, and see if you can open/reach the page in a browser/utility from the XO. /Ties > > Suggestions? > > Thanks > > Victor > ___ > Devel mailing list > Devel@lists.laptop.org > http://lists.laptop.org/listinfo/devel > > ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Deployment Training 101 course, now in moodle
http://moodle.olenepal.org/course/view.php?id=28 you can try it out by logging in as guest This is the course I am giving to Nepal's deployment vlounteers -- Bryan W. Berry Technology Director OLE Nepal, http://www.olenepal.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Deployment Training 101 course, now in moodle
http://moodle.olenepal.org/course/view.php?id=28 you can try it out by logging in as guest This is the course I am giving to Nepal's deployment vlounteers -- Bryan W. Berry Technology Director OLE Nepal, http://www.olenepal.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Minutes from olpc-friends' Feb. 03 and 10 Deployment Meetings
Folks, Last Tuesday, we held an awesome deployment meeting (at 2000 UTC on #olpc-deployment on irc.freenode.net) which featured sustained engagement with the Hernan's deployment troika: logistico, técnico y pedagógico, as well as extensive brainstorming of solutions for issues relevant to Peru, Sierra Leone, and Birmingham. Minutes: http://wiki.laptop.org/go/Deployment_meetings/20090203 Today, we had a quiet sharing of knowledge with Wade Brainerd, head of the Sugar Labs ActivityTeam, a nice Nepal update, some fine exploratory thoughts on the Rwanda deployment, and a pitch by Richard Smith for help with his long-awaited Multi-Battery Charger. Minutes: http://wiki.laptop.org/go/Deployment_meetings/20090210 Enjoy, and please join us in a few hours 0500 UTC or again next Tuesday at 2000 UTC. As always, please add items to the next meetings' agenda at the bottom of http://wiki.laptop.org/go/Deployment_meetings so that interested folks can prepare questions and remarks or update the http://wiki.laptop.org/go/Deployment_wishlist (For extra motivation, be sure to check out dsd's four most recent wishes -- contributed live, directly from Paraguay!) Voluntarily yours, Michael P.S. - Sorry that it took me so long to get last week's minutes posted -- they were hard to disentangle! ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Announcing the first 8.2.1 release candidate.
Hi! This e-mail is to announce the first in a series of signed candidate builds leading up to the release of 8.2.1. We'd love your help testing them before release. You can upgrade to this new build (candidate-800) using the instructions here: http://wiki.laptop.org/go/Friends_in_testing#Preparation Some particular areas we'd like to see testing of: * Connecting to encrypted wireless access points. We believe there are regressions here that we're trying to understand. The test procedure is: - connect to a WEP/WPA AP - suspend/resume using the power button, see what happens - reboot, see what happens Some hypotheses we're trying to investigate are: - WEP always works - WPA works with some percentage chance of success You can read more about the wireless testing that's been done already: http://lists.laptop.org/pipermail/devel/2009-February/023096.html http://lists.laptop.org/pipermail/devel/2009-February/022993.html * We have a version of Browse that reads PDFs in the browser rather than Read, and that needs testing: http://dev.laptop.org/raw-attachment/ticket/9112/Browse-101.xo * To install other activities, you can use the "Software Update" section in the control panel, activated by hovering over the home view XO-man. * It would be great to have help writing the release notes at: http://wiki.laptop.org/go/Release_notes/8.2.1 The input to the release notes is the state described by Michael Stone's excellent Trac report here: http://dev.laptop.org/report/38 You can find out how to send in feedback on this page: http://wiki.laptop.org/go/Reporting_bugs Thanks! - Chris, on behalf of the 8.2.1 team. -- Chris Ball ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: OLPC upgrades
On Wed, Feb 11, 2009 at 1:41 PM, wrote: > as I said, it's a ever shrinking list, but last I heard the security > changes cascaded to other issues, and there were journal related issues. It shrinks because people pick one, and help us working on it :-) Action > speculation. Hop on board! :-D 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 ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: OLPC upgrades
On Wed, 11 Feb 2009, Peter Robinson wrote: >>> The sugar "distro" is basically Fedora, with a few modifications for >>> things like the security that OLPC uses. Sugar is actually the GUI >>> that sits on top of the distro. >> >> yes, but those modifications are significant. I know that Sugar is the name >> of the GUI, but there are still things that don't work in any other >> environment (not as many as there used to be, and they are being addressed), >> and I don't know of a better name to use for the whole set. > > The major changes AFAIA are rainbow for security. Most of the rest of > the changes to fedora are to reduce dependencies now and a few other > minor bits that are actively being upstreamed. So what sort of things > don't work in any other environment? as I said, it's a ever shrinking list, but last I heard the security changes cascaded to other issues, and there were journal related issues. in broad strokes things worked, but not completely. it may be that when I wasn't looking the last of the issues got resolved. If this is the case then it should be possible (on a high enough power laptop) to get an experiance exactly the same as on the XO with Sugar on top of Fedora Is this the case? ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: OLPC upgrades
>> The sugar "distro" is basically Fedora, with a few modifications for >> things like the security that OLPC uses. Sugar is actually the GUI >> that sits on top of the distro. > > yes, but those modifications are significant. I know that Sugar is the name > of the GUI, but there are still things that don't work in any other > environment (not as many as there used to be, and they are being addressed), > and I don't know of a better name to use for the whole set. The major changes AFAIA are rainbow for security. Most of the rest of the changes to fedora are to reduce dependencies now and a few other minor bits that are actively being upstreamed. So what sort of things don't work in any other environment? Peter ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: OLPC upgrades
On Tue, 10 Feb 2009, Peter Robinson wrote: >> or just run other distros (like many of us are doing) >> >> however, even those of us who run other distros (and see the differences) >> would like to see the Sugar 'distro' improve. > > The sugar "distro" is basically Fedora, with a few modifications for > things like the security that OLPC uses. Sugar is actually the GUI > that sits on top of the distro. yes, but those modifications are significant. I know that Sugar is the name of the GUI, but there are still things that don't work in any other environment (not as many as there used to be, and they are being addressed), and I don't know of a better name to use for the whole set. David Lang ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: OLPC upgrades
> > or just run other distros (like many of us are doing) > > however, even those of us who run other distros (and see the differences) > would like to see the Sugar 'distro' improve. The sugar "distro" is basically Fedora, with a few modifications for things like the security that OLPC uses. Sugar is actually the GUI that sits on top of the distro. Peter ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [IAEP] Keep tabs on Sugar development
Awesome!! Really appreciate the efforts. Way to Go!! -- Prakhar Agarwal Linux User# 474643 http://fedoraproject.org/wiki/User:Prakhar "Life is the greatest teacher" ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: OLPC upgrades
On Tue, 10 Feb 2009, Wade Brainerd wrote: > On Tue, Feb 10, 2009 at 5:44 PM, wrote: > >> On Wed, 11 Feb 2009, Martin Langhoff wrote: >> >>> We can skip the "build a replacement" step, and head for the goal faster. >>> >> >> the entire sugar infrastructure is a 'build a replacement' step. people are >> questioning if it was the right thing to do as opposed to using existing >> tools and infrstructure. (with the other part of the question being is it >> faster to go ahead and try to optimise Sugar or switch to more mature >> solutions) >> > > I don't think you can correlate 'mature' with 'fast'. Gnome is quite mature > but also quite bloated. > > The XO is a weak machine by today's performance standards, so trying to run > today's Linux is going to require heavy optimization no matter what you > start with. > > People just have to stop arguing about it and start doing that optimization > work, like Benjamin did today :) or just run other distros (like many of us are doing) however, even those of us who run other distros (and see the differences) would like to see the Sugar 'distro' improve. David Lang ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: OLPC upgrades
On Tue, Feb 10, 2009 at 5:44 PM, wrote: > On Wed, 11 Feb 2009, Martin Langhoff wrote: > >> We can skip the "build a replacement" step, and head for the goal faster. >> > > the entire sugar infrastructure is a 'build a replacement' step. people are > questioning if it was the right thing to do as opposed to using existing > tools and infrstructure. (with the other part of the question being is it > faster to go ahead and try to optimise Sugar or switch to more mature > solutions) > I don't think you can correlate 'mature' with 'fast'. Gnome is quite mature but also quite bloated. The XO is a weak machine by today's performance standards, so trying to run today's Linux is going to require heavy optimization no matter what you start with. People just have to stop arguing about it and start doing that optimization work, like Benjamin did today :) Cheers, Wade ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: OLPC upgrades
On Wed, 11 Feb 2009, Martin Langhoff wrote: > 2009/2/11 Wade Brainerd : >> I have spent the last 10 years optimizing software for a living, and can >> tell you without a doubt that any system can be optimized without starting >> from scratch. >> It's just much harder to understand the performance characteristics of a >> large, complex, existing system than it is to imagine an ideal performance >> world in your head. > > +1 on both. Experience teaches that performance comes from > understading and optimising a complex system. If you build a > replacement system, it's initial performance _will suck_ until you > study it, understand it and optimise it. > > We can skip the "build a replacement" step, and head for the goal faster. the entire sugar infrastructure is a 'build a replacement' step. people are questioning if it was the right thing to do as opposed to using existing tools and infrstructure. (with the other part of the question being is it faster to go ahead and try to optimise Sugar or switch to more mature solutions) David Lang > (I've only seen one exception to the rule above -- and was the > building of git. But it's a rare case where you get a band of > battle-hardened kernel devs building a small and focused cli tool.) > > cheers, > > > > m > ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] Minimal steps to start hacking on Browse.xo?
On Wed, Feb 11, 2009 at 6:25 AM, Wade Brainerd wrote: > Agreed that navigation is currently hard. I would love to see a new > Gitorious splash page that just lists *all* the projects like GitWeb does, Yes! that'd be a big improvement. Or a search of some kind. As it stands, I had to paginate "blind" as it's not even sorted. Obviously, not a top priority, but it'd be a good thing :-) >> > 4 - run it from the checkout... how? >> >> Just link to it from ~/Activities and it should work. > > Actually, cd to the activity directory and run > python setup.py dev > This will create the aforementioned symlink. Then restart X > (Ctrl-Alt-Erase). *Thanks* Tomeu and Wade for the hints. /me hack hack hack! 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 ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: OLPC upgrades
2009/2/11 Wade Brainerd : > I have spent the last 10 years optimizing software for a living, and can > tell you without a doubt that any system can be optimized without starting > from scratch. > It's just much harder to understand the performance characteristics of a > large, complex, existing system than it is to imagine an ideal performance > world in your head. +1 on both. Experience teaches that performance comes from understading and optimising a complex system. If you build a replacement system, it's initial performance _will suck_ until you study it, understand it and optimise it. We can skip the "build a replacement" step, and head for the goal faster. (I've only seen one exception to the rule above -- and was the building of git. But it's a rare case where you get a band of battle-hardened kernel devs building a small and focused cli tool.) 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 ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: OLPC upgrades
2009/2/7 Tiago Marques > That seems a good idea. > The use of SVGs seems unnecessary. Although an awsome functionality, which > probably saves a lot of work, would allow to scale the use of Sugar to > systems with bigger screens - were it probably will never be in use. I've > never seen SVGs being used extensively in a desktop system, let alone an > "embedded" one. > Caching the SVGs as pixmaps can help this out a lot. I remember IRIX from the mid 90s using vector-based icons, and it didn't seem to have performance issues. > As I talked with some people that know more Python than me, they argued > that programmer productivity would be a major factor for it's use in some > situations. I haven't heard that argument here. I haven't read a good > argument that justifies the burden of using an interpreted language in a > desktop environment, so it really does seem stubbornness more than anything > else, even more and it's all already written in Python. > It is wonderful to be able to modify a part of the Sugar shell or an Activity directly on the XO, without the need for a compiler and a wide variety of installed headers and libraries eating up space on your disk, not to mention obscure build systems and megabytes of build artifacts. It's also great that most activities are <100k downloads and are totally cross platform and architecture independent. > No matter what interpreted language you're using, it will always stink. > Either it's java, python, javascript, whatever. Sugar isn't a webapp, it > doesn't even need to be so portable that it can't be written in a language > that can be compiled. > Here's the difference: In Sugar, Python fills the role of the *glue* code. It doesn't do any real work itself. > Even in powerful machines, most programs I have used written in Java have a > huge amount of computing and memory overhead - and Java isn't the worst of > it, I read. > Do you need high performance for every program? I use GMail all day and have never had a performance issue with it. > I can't stress this enough: unless the whole OLPC project is starting to > take aim at building a laptop that doesn't cost less than $170, I don't see > any reason at all not to properly optimize the software. You will always be > running some kind of over powered, embedded type system, with little RAM and > CPU power. > I completely agree, I just want to make sure the optimization happens to the right parts - the parts that do the heavy lifting. And the algorithms that control the parts that do the heavy lifting. For example, I was recently involved in a discussion about the pulsing icon that is shown when activities launch. It turns out, the *entire screen* was being redrawn at 10fps, not just the activity icon. Not to mention that the icon caching was not working, so the .svg file was being reparsed each frame and going through a text filter like s/&stroke_color;/#aabbcc/ to achieve the pulsed color. Fortunately Benjamin Berg corrected this today. Another one, I have had to rewrite large chunks of THREE of my activities to overcome performance issues in Cairo (which is an optimized library written in C). I have written several games and other realtime activities for the XO and not yet seen Python become a bottleneck. > The whole project is taking the show source thing way too far, hurting you > too much, especially as that is still far from "the vision". You already > have Pippy, which should be enough for most kids. The really good kids won't > have a problem doing the work to go to the next step(building activities and > such) and you can always leave the door open for python activities, while > having the basis of Sugar in C, C++ or something. Isn't that what bindings > between languages are for? > I'm telling you, I'm still looking for some solid performance numbers. Memory issues I am more inclined to believe but again, actually optimizing the problem (controlling Python's garbage collector) is a much better solution than throwing everything away and starting over! I have spent the last 10 years optimizing software for a living, and can tell you without a doubt that any system can be optimized without starting from scratch. It's just much harder to understand the performance characteristics of a large, complex, existing system than it is to imagine an ideal performance world in your head. Best regards, Wade > Best regards, > > Tiago Marques > ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
In Sugar land even bugs are sweet...
So sweet that our tracker [1] got sticky and needs a bit of triage help to get going again. That is why the Sugar Labs BugSquad [2] meets this week for their first Triage session. When: Thursday 12 February, 2009 - 16.00 (UTC Where: irc.freenode.net, #sugar-meeting Who: You do not need any programming knowledge to be in the BugSquad; in fact it is a great way to return something to the Sugar community if you cannot program. What: Read at [3] about the work a triager is doing. Looking forward to see you on Thursday, Simon [1] http://dev.sugarlabs.org [2] http://sugarlabs.org/go/BugSquad [3] http://sugarlabs.org/go/BugSquad/TriageGuide ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] Keep tabs on Sugar development
> 2009/2/10 Wade Brainerd : >> Want to know who has been working on what? How active a particular >> developer or project is? Want to know right away when a particular bug gets >> fixed? When a new project gets started? How about a graph of commit >> activity over time? >> Add the following feed to your RSS reader: >> http://git.sugarlabs.org/events.atom >> Bernie helped me out with this a few weeks ago, and I like it so much I want >> to share it with everyone. It's like a 'commits' list but even better. >> It's really encouraging to see all the work people are doing on Sugar. >> Cheers, >> Wade >> PS- If you don't have an RSS reader already, try out Google Reader. Its >> List view works pretty well for this feed. Awesome, one missing piece for me! Thanks Bernie and Wade, Simon ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] Minimal steps to start hacking on Browse.xo?
On Tue, Feb 10, 2009 at 4:42 AM, Tomeu Vizoso wrote: > On Tue, Feb 10, 2009 at 02:28, Martin Langhoff > wrote: > > Hi! > > > > I found the git repo for Browse xo! Hurray! (finding things in github > > is hard work, or perhaps I managed to find the hardest path to it). > > Gitorious, not github, but do you have any suggestion? Agreed that navigation is currently hard. I would love to see a new Gitorious splash page that just lists *all* the projects like GitWeb does, but I know that could be hard to do and we have more pressing infrastructure needs. > > 2 - yum install git > > > > 3 - git clone git://git.sugarlabs.org/browse/mainline.git > >mv mainline.git browse.git > > (btw, shoud this be called browse.git, or browse-mainline.git?) > > I would call it 'browse'. The best way to do this is: git clone git://git.sugarlabs.org/browse/maineline.git browse The second argument controls the name of the directory it's synced to. > > 4 - run it from the checkout... how? > > Just link to it from ~/Activities and it should work. Actually, cd to the activity directory and run python setup.py dev This will create the aforementioned symlink. Then restart X (Ctrl-Alt-Erase). Wade ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Keep tabs on Sugar development
Just what I needed! Thanks, Tomeu 2009/2/10 Wade Brainerd : > Want to know who has been working on what? How active a particular developer > or project is? Want to know right away when a particular bug gets fixed? > When a new project gets started? How about a graph of commit activity over > time? > Add the following feed to your RSS reader: > http://git.sugarlabs.org/events.atom > Bernie helped me out with this a few weeks ago, and I like it so much I want > to share it with everyone. It's like a 'commits' list but even better. It's > really encouraging to see all the work people are doing on Sugar. > Cheers, > Wade > PS- If you don't have an RSS reader already, try out Google Reader. Its List > view works pretty well for this feed. > ___ > Devel mailing list > Devel@lists.laptop.org > http://lists.laptop.org/listinfo/devel > > ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Keep tabs on Sugar development
Want to know who has been working on what? How active a particular developer or project is? Want to know right away when a particular bug gets fixed? When a new project gets started? How about a graph of commit activity over time? Add the following feed to your RSS reader: http://git.sugarlabs.org/events.atom Bernie helped me out with this a few weeks ago, and I like it so much I want to share it with everyone. It's like a 'commits' list but even better. It's really encouraging to see all the work people are doing on Sugar. Cheers, Wade PS- If you don't have an RSS reader already, try out Google Reader. Its List view works pretty well for this feed. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
updating activities
Trying to update activities here, from the sugar control panel. It says it cannot access the network to check for updates, even if I have a an ethernet connection to the XO that is working (and I can ping the outside world). Suggestions? Thanks Victor ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
devel OS upgrades, joyrides, sucrose
Hi everyone, pardon my confusion, but could you explain how things should be done? I want to get the latest development OS for the XO. Last year, I was using olpc-update $ olpc-update joyride-N Now my question is: how does the latest software produced by sugarlabs gets into the equation? Do I get the latest sucrose etc by upgrading to the latest joyride? Who is managing Joyrides and how does the latest sugar software gets included? Thanks Victor ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
VIG Meeting Notice for Today, Agenda Request
Folks - We're on for our regular meeting at 4 PM, #olpc-admin on freenode, today. I've been a bit out of touch with what our current/urgent issues are, so please email any agenda items you'd like covered. I'll look over last week's minutes, but I'd rather not just re-hash the same issues just for lack of planning the things we DO need to discuss. Thanks! - Ed ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: maintaining activity web information
On Tue, Feb 10, 2009 at 01:05, S Page wrote: > (Please forward to whatever the sugar activity mailing list is.) > > There's a lot of activity information on wiki pages to maintain, I > couldn't find any documentation on how to maintain it all. > So I wrote > http://wiki.laptop.org/go/Maintaining_activity_web_information based on > how activities like Etoys are set up. > > I added a section about the fields to update when you migrate your > activity to SugarLabs. > > I think it's accurate, edit away if not. > > It's clearly *way too much work* because of overlapping redundant info. > Perhaps this is why many activity web pages and > Activities/Another_list have out-of-date info. > > Maintenance should be much simpler. I have specific ideas how to get > there, but I'm not even clear where the info should live. I think there > has to be one web site where you can browse all activities, but is that > site wiki.laptop.org or sugarlabs.org (or git.sugarlabs.org)? Sugar Labs' plan is to adapt addons.mozilla.org for that purpose. Regards, Tomeu ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] Minimal steps to start hacking on Browse.xo?
On Tue, Feb 10, 2009 at 02:28, Martin Langhoff wrote: > Hi! > > I found the git repo for Browse xo! Hurray! (finding things in github > is hard work, or perhaps I managed to find the hardest path to it). Gitorious, not github, but do you have any suggestion? > Not being a Sugar dev, I want to do some light hacking on Browse.xo > but I don't have a Sugar environment prepared to hack on it. How can I > get going with minimum steps...? If you want that activity to run on 8.2 and are comfortable hacking on the XO, then you have started well. > So far, what I've tried to do... > > 1 - grab an XO with 8.2 Keep in mind that Browse depends on hulahop, that is the component used to embed mozilla. If since the 8.2 times an API change happened, you may want to hack on HEAD (having installed 0.83.x) and afterwards backport to the sucrose-0.82 branch. Then build bundles from each of those branches. > 2 - yum install git > > 3 - git clone git://git.sugarlabs.org/browse/mainline.git >mv mainline.git browse.git > (btw, shoud this be called browse.git, or browse-mainline.git?) I would call it 'browse'. > 4 - run it from the checkout... how? Just link to it from ~/Activities and it should work. HTH, Tomeu > is there a better way? > > 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-de...@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel > ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
