Re: [Sugar-devel] OS/X11 support for XO-1 hardware?
da...@lang.hm wrote: >> It would allow for much improved >> video performance since you could play back a 320x240 >> video on the full screen at considerable CPU savings. > > except that you would spend those CPU savings doing the scaling up from > 320x240 to the higher resolution. Argh and double argh! You're both wrong. 1. Video playback in any sane player is already routed through XV, which uses the GPU's video overlay scaler (and YUV->RGB converter). The result is that playing a 320x240 video at 1200x900 full-screen already costs zero extra CPU cycles. No need to mess with screen resolution. 2. The Geode LX GPU can do both output scaling and video-overlay scaling, independently, at the same time. On the latest drivers, we should be able to set the screen resolution to 600x450, scaled up to 1200x900, and then play a 320x240 video, scaled up to 480x360 (which means 960x720 physical LCD pixels), all without using any CPU power for scaling. There are lots of good reasons to play with screen resolution. My favorite reason is that reducing the resolution to 800x600 would make all graphical operations runs twice as fast, and use half as much memory, while introducing a negligible drop in display quality (the display, remember, is not _really_ 1200x900 in color mode; the total number of color elements is equivalent to 800x450). --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] Journal empty in Soas-200902231225 and what is Soas-200902241809.iso in snapshots/2/ ?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, Feb 25, 2009 at 07:41:43PM -0800, Edward Cherlin wrote: >On Wed, Feb 25, 2009 at 6:50 PM, Ton van Overbeek wrote: >> When trying out Soas-200902231225 the journal stays empty. >> Anybody else seen this ? Please look at the logfiles below ~.sugar/default/logs (or wherever they are stored on your installation), and post info on any indications on crashes found there. >This is true in several versions of Sugar, including Ubuntu packages. >Jonas Smedegård has made a patch for it, available from > >http://debian.jones.dk/ sid sugar Above is not usable for Soas - and my website contains more than 2000 Debian packages, so above is little use even for Sugarlabs developers. The actual patch is patch 0001 that I have now posted here: http://debian.jones.dk/pkg/sugar/sugar-datastore/sid/auryn/patches/ The patch was grabbed from Sugarlabs development tree, so should be already applied in recent releases of sugar-datastore, which I believe is in the Soas release mentioned above. In other words: Even if the symptom is the same, this most likely is *not* the same problem that used to be in Debian and Ubuntu. Kind regards, - Jonas - -- * Jonas Smedegaard - idealist og Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkmmG2gACgkQn7DbMsAkQLiCBQCgnkNN4rsJVqdiCL4iK8akj8KJ Ez4An3zQtxYQ9nrx0VWaZobLb9Jm2AKj =hs2Y -END PGP SIGNATURE- ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Journal empty in Soas-200902231225 and what is Soas-200902241809.iso in snapshots/2/ ?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, Feb 25, 2009 at 07:41:43PM -0800, Edward Cherlin wrote: >Jonas Smedegård has made a patch for it, available from ^ Nice try, and you (or some dictionary in your MUA?) are right in general that danish "aa" is better written "å", but for names specifically it often has a significance of being family names with a long proud trail. My middle name is "Smedegaard" and not "Smedegård". :-) - Jonas - -- * Jonas Smedegaard - idealist og Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkmmFq0ACgkQn7DbMsAkQLirTwCfTXkKr+S5ICJ/hg0JA5VX3id0 7coAnRdmoMtBqaCR9GZ+ok3ykvL0idk7 =8eoH -END PGP SIGNATURE- ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Journal empty in Soas-200902231225 and what is Soas-200902241809.iso in snapshots/2/ ?
On Wed, Feb 25, 2009 at 6:50 PM, Ton van Overbeek wrote: > When trying out Soas-200902231225 the journal stays empty. > Anybody else seen this ? This is true in several versions of Sugar, including Ubuntu packages. Jonas Smedegård has made a patch for it, available from http://debian.jones.dk/ sid sugar > Ton van Overbeek > ___ > Devel mailing list > de...@lists.laptop.org > http://lists.laptop.org/listinfo/devel > -- Silent Thunder (默雷/धर्ममेघशब्दगर्ज/دھرممیگھشبدگر ج) is my name And Children are my nation. The Cosmos is my dwelling place, The Truth my destination. http://wiki.sugarlabs.org/go/User:Mokurai (Ed Cherlin) ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] OS/X11 support for XO-1 hardware?
With the spin-off of Sugar development to sugarlabs, it is nice to see the development continued. However, it seems that the OLPC layoffs and refocus has scuttled the work to complete some OS and system software support for the XO-1 hardware features. For example, I have been waiting for the video scaler support to allow for adjustable display resolutions on the XO. Among other things, it would allow programs that don't understand a 1200x900 but only 6x4" display to work at a more usable resolution where the graphic elements and text/fonts are consistent and visible to the naked eye... It would allow for much improved video performance since you could play back a 320x240 video on the full screen at considerable CPU savings. I had thought this capability would be coming with the Fedora 10 move in 9.1.0. With that release now scuttled, I'm wondering more generally, are these pieces being picked up anywhere? Would it make sense to have an 8.2.2 release involving the move to Fedora 10 but pretty much the same as 8.2.1 otherwise? --Chris ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] setup.py release?
Hey all, OLPC's 8.2.0 builds have a 'release' bundlebuilder command. That's what I have always used to release new versions of my activities, since it works in such a consistent manner. The command increments activity.info, updates NEWS, makes a new Git tag vXX, builds xo and tar.bz2 bundles, and finally pushes everything to Git. I noticed this argument doesn't exist on SoaS builds. Any reason for that, any any chance of getting it back? Cheers, Wade ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [RELEASE] Moon-9
On 25 Feb 2009, at 10:18, Simon Schampijer wrote: > Gary C Martin wrote: >> == .XO Bundle == >> http://addons.sugarlabs.org/en-US/sugar/addon/4034 > > Worked fine for me. > >> http://wiki.laptop.org/images/5/51/Moon-9.xo >> ...or use the software update panel. >> == Source == >> http://download.sugarlabs.org/sources/honey/Moon/Moon-9.tar.bz2 >> == Git == >> http://git.sugarlabs.org/projects/moon >> == Features == >> - Code cleanup (make pylint happier) >> - Merged alsroot's excellent independence resolution code addition >> (resizes moon image to fit available display, much better for misc >> SoaS hardware screen resolutions) > > Worked awesomely for me - testing with 800x600 - good work! Fab, thank alsroot! :-) >> - Updated localizations (latest from Pootle, thanks all!) >> == Documentation == >> http://wiki.laptop.org/go/Moon > > We might want to move the documentation to the Sugarlabs wiki - I > have seen Walter did it already http://sugarlabs.org/go/Activities/TurtleArt > - I need to do it for Browse as well. Yes, I was waiting to see where addons/activities.sl.org was going to get us in terms of a useful place for activity documentation, it certainly covers the trivial case. I'd hate to see the SL wiki churn into a mess of out of date activity pages. There's also the potential for these activity help documents (verging on lesson plan, example use walkthrus) becoming something you get with the activity, I'm not a huge fan of internal help, but I could at least see a .xo bundle at install (or erase) time add (or remove) some html content (a little like a library collection). Browse could then default to an index page (KISS, no nested side bar attempt at ontology, just a tiled 'book' view for all library collections and a way to search them). Regards, --Gary > Cheers, > Simon ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Auto-authentication for Browse -
Hello Everyone, My name is Hamilton Chua and I am new to these lists and even newer to sugar development and the olpc in general so please do forgive me if the questions I am about to ask have been asked and answered before. I am using a development snapshot of Sugar on a Stick (SoaS) and XS (0.5.1) on Virtualbox 2.1.4. So here are my questions : 1) It seems registration does not work on SoaS because it lacks the info that you normally have on an OLPC laptop in order to successfully register with an XS server. I would like to ask what the significance, if any, of registration. In the snapshot I have, it seems that I can set the jabber server on the control panel and it seemed that I was all set. 2) For the XS Cookie (Plan C here) to work, do I need to register sugar with an XS server ? 3) Are there plans to make registration work for Sugar installed on hardware other than an OLPC ? Thanks very much in advance. Best, Hamilton -- View this message in context: http://n2.nabble.com/Auto-authentication-for-Browse---tp2204988p2383357.html Sent from the Sugar Development mailing list archive at Nabble.com. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Sugar Digest 2009-02-24
Also, the black highlighted phrases, couldn`t they be colored with another color? I think the idea interesing, its just that it looks strange to have them around with a black background, perhaps a different highlighted mode would be best. But once again, I don`t know the philosophy of the graphical design of the website, so rock on your vision. Eduardo 2009/2/25 Eduardo H. Silva : > 2009/2/24 Walter Bender : > `snip` >> >> 5. Christian Marc Schmidt has been making great progress on the new >> static website (See >> http://www.christianmarcschmidt.com/projects/sugarlabs/betasite). We >> are still seeking more screenshots of the work of children using >> Sugar, i.e., "authentic" Sugar images. > > I find the menu which pops-up a bit confusing, took me a while to > figure it out. Cant it be made as spread out menu along the top of the > webpage, like its usually done in other websites? A first class > `toolbar` of options, and beneath them the sub-options of the clicked > option. > > Other than that, loved the cartoons (although a bit scary with all > those sharks around), but definitelly inspiring. > > Eduardo > >> >> === Tech Talk === >> >> 6. Lionel Laské has been looking into the use of Mono as a Sugar >> resource, opening up to us the .NET community. Please see his post, >> “Mono on Sugar for dummies”, on the French .NET community site >> (http://www.techheadbrothers.com/Articles.aspx/developper-mono-xo). >> >> 7. S. Page, in reminding us, "Don't bet against the browser", posted a >> link to a Pippy-like tool for Javascript (See >> http://billmill.org/static/canvastutorial/). >> >> 8. Sascha Silbe "finally managed to get Linux working" on his phone, >> so he couldn't resist installing Sugar (See >> http://sascha.silbe.org/photos/dsc04708.jpg, >> http://sascha.silbe.org/photos/dsc04709.jpg, >> http://sascha.silbe.org/photos/dsc04710.jpg, and >> http://sascha.silbe.org/photos/dsc04711.jpg). Sascha says, "No, it >> isn't really usable - only 64MB of physical RAM means swapping ~30MB >> to SD just to start Sugar (no activities running). Sugar isn't >> touchscreen-"compatible" as well (there are no "plain" movements, just >> clicks and drags)." But it looks great. >> >> === Sugar Labs === >> >> 9. Gary Martin has generated another SOM from the past week of >> discussion on the IAEP mailing list (Please see >> http://wiki.sugarlabs.org/go/Image:2009-February-14-20-som.jpg). >> >> -walter >> -- >> Walter Bender >> Sugar Labs >> http://www.sugarlabs.org >> ___ >> Sugar-devel mailing list >> Sugar-devel@lists.sugarlabs.org >> http://lists.sugarlabs.org/listinfo/sugar-devel >> > ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Sugar Digest 2009-02-24
2009/2/24 Walter Bender : `snip` > > 5. Christian Marc Schmidt has been making great progress on the new > static website (See > http://www.christianmarcschmidt.com/projects/sugarlabs/betasite). We > are still seeking more screenshots of the work of children using > Sugar, i.e., "authentic" Sugar images. I find the menu which pops-up a bit confusing, took me a while to figure it out. Cant it be made as spread out menu along the top of the webpage, like its usually done in other websites? A first class `toolbar` of options, and beneath them the sub-options of the clicked option. Other than that, loved the cartoons (although a bit scary with all those sharks around), but definitelly inspiring. Eduardo > > === Tech Talk === > > 6. Lionel Laské has been looking into the use of Mono as a Sugar > resource, opening up to us the .NET community. Please see his post, > “Mono on Sugar for dummies”, on the French .NET community site > (http://www.techheadbrothers.com/Articles.aspx/developper-mono-xo). > > 7. S. Page, in reminding us, "Don't bet against the browser", posted a > link to a Pippy-like tool for Javascript (See > http://billmill.org/static/canvastutorial/). > > 8. Sascha Silbe "finally managed to get Linux working" on his phone, > so he couldn't resist installing Sugar (See > http://sascha.silbe.org/photos/dsc04708.jpg, > http://sascha.silbe.org/photos/dsc04709.jpg, > http://sascha.silbe.org/photos/dsc04710.jpg, and > http://sascha.silbe.org/photos/dsc04711.jpg). Sascha says, "No, it > isn't really usable - only 64MB of physical RAM means swapping ~30MB > to SD just to start Sugar (no activities running). Sugar isn't > touchscreen-"compatible" as well (there are no "plain" movements, just > clicks and drags)." But it looks great. > > === Sugar Labs === > > 9. Gary Martin has generated another SOM from the past week of > discussion on the IAEP mailing list (Please see > http://wiki.sugarlabs.org/go/Image:2009-February-14-20-som.jpg). > > -walter > -- > Walter Bender > Sugar Labs > http://www.sugarlabs.org > ___ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel > ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [RELEASE] Moon-9
Gary C Martin wrote: > == .XO Bundle == > > http://addons.sugarlabs.org/en-US/sugar/addon/4034 Worked fine for me. > http://wiki.laptop.org/images/5/51/Moon-9.xo > ...or use the software update panel. > > == Source == > > http://download.sugarlabs.org/sources/honey/Moon/Moon-9.tar.bz2 > > == Git == > > http://git.sugarlabs.org/projects/moon > > == Features == > > - Code cleanup (make pylint happier) > - Merged alsroot's excellent independence resolution code addition > (resizes moon image to fit available display, much better for misc > SoaS hardware screen resolutions) Worked awesomely for me - testing with 800x600 - good work! > - Updated localizations (latest from Pootle, thanks all!) > > == Documentation == > > http://wiki.laptop.org/go/Moon We might want to move the documentation to the Sugarlabs wiki - I have seen Walter did it already http://sugarlabs.org/go/Activities/TurtleArt - I need to do it for Browse as well. Cheers, Simon ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Future of Rainbow + Sugar?
On Tue, Feb 24, 2009 at 18:29, Wade Brainerd wrote: > To me, Bitfrost was just one more lofty windmill OLPC tried to tilt because > it seemed like an interesting challenge. I'm not clear why Sugar needs more > protection from rogue activities than a normal desktop environment has from > rogue applications. > Reinventing the desktop as a constructivist learning environment is a big > enough task for one development team / community to swallow. Reinventing > security is an altogether separate cause. > That said, Rainbow exists, so we don't need to do anything to remove it. So > long as people step up to maintain it and help activity developers fix the > issues they run into. Yeah, that's a very important point. I think we already know the kind of issues we can expect to find and maybe should think twice before throwing out all that knowledge. I don't see Rainbow in Sugar as too controversial, because: - the modifications needed to the Sugar platform are minimal, - most activities don't need to be modified and the ones that do, shouldn't be hard to modify (though there's the issue of unmodified X apps), - we have already agreed that we need a system-wide switch for disabling Rainbow and a way to white list activities that for some reason cannot run yet inside Rainbow. That system-wide switch means that distributors of Sugar will be the ones to decide if they want Rainbow or not. The Sugar community just listens to their deployers and tries to find a way to accommodate that need. No one is forced to use Rainbow, though it's true that activity authors need to take into account a set of limitations if they want their activities to run everywhere. Regards, Tomeu > But Michael, what you seem to be asking for - someone to pick up your solo > project and finish it - almost never happens in software development. Code > is a personal expression of the programmer who wrote it. If it ever does > get finished by someone else, it likely gets rewritten in the process. > Best regards, > Wade ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] future of the grab key?
Hi Paul, this looks as awesome work! If I understood correctly what you did, nor applications nor the shell need to be modified in order to benefit from this, right? If so, then I guess this is something as independent from Sugar as the Geode X driver may be and you don't need to worry about Sugar schedules. Just about the schedules of the people that you want to ship this ;) I recommend you the same I recommended Michael on #sugar: once Sugar on a Stick gets a bit more stable on the XO, build your own images with your software in and ask people to try it. Or if you don't need so much wide testing, just package it and tell people to install the rpm on top of SoaS on the XO. Regards, Tomeu On Tue, Feb 24, 2009 at 21:31, wrote: > since we're examining unloved features today, i have something > to show and tell, too. > > i'd like to get input on some work i've done to get the grab > key(s) on the XO working. i don't think what i've done is quite > how they were originally planned to work, but maybe it's close > enough. i also know erik did a bunch of work on this last fall > (see extensive patches on #447), and i've never been sure why > that hasn't gotten picked up, so i'd like to know more about > that, too. > > background: i've been working on a (non-XO) project recently > that led me to implement a userspace virtual keyboard. as the last > step of that project, i implemented modifier-based scrolling -- i > can hold a key, use the joystick (on the keyboard device in > question), and instead of getting motion events, scroll-button-press > events are generated and injected into the uinput device. it > works very nicely. > > when i asked a question related to my project a few weeks ago on > IRC, tomeu asked if i was thinking about the grab key. i wasn't > back then, but the thought stuck with me. > > so: i've now implemented a fairly small daemon that sits between > the XO keyboard/touchpad pair and the evdev kernel driver. it > opens the keyboard and touchpad /dev/input/eventN nodes (in such > a way that X will skip them when it starts), creates a third > eventN node via uinput, and shuttles events in between. the only > thing it does with the data is watch for the grab keys -- when it > sees one, it does as described above: ensuing touchpad events > are translated into a smaller number of scroll-button events, and > as a result the window moves instead of the mouse pointer. > > but as i was finishing it up and testing it, i realized that it > doesn't really do what i pictured the grab key as doing. > > i had pictured the grab key as causing the mouse cursor to, well, > "grab" the window contents, to allow dragging it around. (just > like clicking and dragging on google maps.) > > but what i'd done was different: when one's finger moved on the > touchpad, the _scrollbars_ moved. the mouse pointer stayed > stationary with respect to the window edges, and the window > contents moved in the _opposite_ direction from the finger on > the touchpad. > > since i wasn't sure what to make of this frame-of-reference > reversal, i did the obvious thing: i reversed the behavior, but > added a commandline option to put it back, just in case. (the > original "backward" behavior still feels more correct on the > joystick pointer of my original project, for instance.) > > since the mouse cursor remains stationary on the screen, it still > doesn't feel like you're "grabbing" the contents, but it's may be > more intuitive than the way it was. any thoughts on this? > > you can try it if you'd like: > http://dev.laptop.org/git?p=users/pgf/grabkeyd > it needs to be started before X, and uinput needs to be loaded. > (happily, uinput is already in the XO releases.) initially the > easiest way to test it is: > # modprobe uinput > # init 3 > # ./grabkeyd -l > [ check that grabkeyd is running, check /var/log/messages > for failure ] > # init 5 > > as i recall, one of the objections to erik's implementation last > year was that it required the XTEST extension, which is considered > a security risk. as far as i know, there's no risk to my current > implementation. (other than, if it dies, you lose your mouse and > keyboard. uh oh -- better run it from init. :-) > > because it's in a fairly critical path, grabkeyd has facility for > running at an elevated scheduling priority. currently this is a > SCHED_FIFO priority, which is probably safe, but perhaps > overkill. it's not the default. > > comments solicited... > > > paul > =- > paul fox, p...@laptop.org > ___ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel > ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
