Re: [Sugar-devel] Performance: activities start up time
Right, as you can see it only loads gobject introspection stuff. If you do the import after any other gi import it shouldn't even do that, because those modules will have been loaded already. It should basically not touch the disk at all... Which is why it's totally weird that moving the import helps startup time. Did you try to repeat your timings dropping kernel memory cache every time? (unless they was taken that way already). Otherwise they are not going to be very accurate. Did you try to measure the time it takes to do the import? Something simple like this in the unpatched activity code should be enough import logging start = time.time() --- here are the two imports --- logging.error(time.time() - start) On Saturday, 9 November 2013, Gonzalo Odiard wrote: In my system, using strace -e trace=open,close,read,write,connect,accept -p pid in another terminal, when I do: from gi.repository import EvinceDocument I see: open(gi.so, O_RDONLY) = -1 ENOENT (No such file or directory) open(gimodule.so, O_RDONLY) = -1 ENOENT (No such file or directory) open(gi.py, O_RDONLY) = -1 ENOENT (No such file or directory) open(gi.pyc, O_RDONLY)= -1 ENOENT (No such file or directory) open(/usr/bin/gi.so, O_RDONLY)= -1 ENOENT (No such file or directory) open(/usr/bin/gimodule.so, O_RDONLY) = -1 ENOENT (No such file or directory) open(/usr/bin/gi.py, O_RDONLY)= -1 ENOENT (No such file or directory) open(/usr/bin/gi.pyc, O_RDONLY) = -1 ENOENT (No such file or directory) open(/usr/lib64/python2.7/gi.so, O_RDONLY) = -1 ENOENT (No such file or directory) open(/usr/lib64/python2.7/gimodule.so, O_RDONLY) = -1 ENOENT (No such file or directory) open(/usr/lib64/python2.7/gi.py, O_RDONLY) = -1 ENOENT (No such file or directory) open(/usr/lib64/python2.7/gi.pyc, O_RDONLY) = -1 ENOENT (No such file or directory) open(/usr/lib64/python2.7/plat-linux2/gi.so, O_RDONLY) = -1 ENOENT (No such file or directory) open(/usr/lib64/python2.7/plat-linux2/gimodule.so, O_RDONLY) = -1 ENOENT (No such file or directory) open(/usr/lib64/python2.7/plat-linux2/gi.py, O_RDONLY) = -1 ENOENT (No such file or directory) open(/usr/lib64/python2.7/plat-linux2/gi.pyc, O_RDONLY) = -1 ENOENT (No such file or directory) open(/usr/lib64/python2.7/lib-tk/gi.so, O_RDONLY) = -1 ENOENT (No such file or directory) open(/usr/lib64/python2.7/lib-tk/gimodule.so, O_RDONLY) = -1 ENOENT (No such file or directory) open(/usr/lib64/python2.7/lib-tk/gi.py, O_RDONLY) = -1 ENOENT (No such file or directory) open(/usr/lib64/python2.7/lib-tk/gi.pyc, O_RDONLY) = -1 ENOENT (No such file or directory) open(/usr/lib64/python2.7/lib-dynload/gi.so, O_RDONLY) = -1 ENOENT (No such file or directory) open(/usr/lib64/python2.7/lib-dynload/gimodule.so, O_RDONLY) = -1 ENOENT (No such file or directory) open(/usr/lib64/python2.7/lib-dynload/gi.py, O_RDONLY) = -1 ENOENT (No such file or directory) open(/usr/lib64/python2.7/lib-dynload/gi.pyc, O_RDONLY) = -1 ENOENT (No such file or directory) open(/usr/lib64/python2.7/site-packages/gi/__init__.so, O_RDONLY) = -1 ENOENT (No such file or directory) open(/usr/lib64/python2.7/site-packages/gi/__init__module.so, O_RDONLY) = -1 ENOENT (No such file or directory) open(/usr/lib64/python2.7/site-packages/gi/__init__.py, O_RDONLY) = 5 open(/usr/lib64/python2.7/site-packages/gi/__init__.pyc, O_RDONLY) = 6 read(6, \3\363\r\nn;\324Pc\0\0\0\0\0\0\0\0\3\0\0\0@ @\0\0s\311\0\0\0d\0..., 4096) = 2118 read(6, , 4096) = 0 close(6)= 0 open(/usr/lib64/python2.7/site-packages/gi/_gi.so, O_RDONLY) = 7 open(/usr/lib64/python2.7/site-packages/gi/_gi.so, O_RDONLY|O_CLOEXEC) = 8 read(8, \177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0\0\1\0\0\0\220\216\0\0\0\0\0\0..., 832) = 832 close(8)= 0 open(/etc/ld.so.cache, O_RDONLY|O_CLOEXEC) = 8 close(8)= 0 open(/lib64/libgirepository-1.0.so.1, O_RDONLY|O_CLOEXEC) = 8 read(8, \177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0\0\1\0\0\\177\0\2167\0\0\0..., 832) = 832 close(8)= 0 open(/lib64/libgobject-2.0.so.0, O_RDONLY|O_CLOEXEC) = 8 read(8, \177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0\0\1\0\0\0\240\253\340j7\0\0\0..., 832) = 832 close(8)= 0 open(/lib64/libglib-2.0.so.0, O_RDONLY|O_CLOEXEC) = 8 read(8, \177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0\0\1\0\0\0P\240\341i7\0\0\0..., 832) = 832 close(8)= 0 open(/lib64/libpyglib-gi-2.0-python.so.0, O_RDONLY|O_CLOEXEC) = 8 read(8, \177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0\0\1\0\0\0p\32\0\0\0\0\0\0..., 832) = 832 close(8)= 0 open(/lib64/libgmodule-2.0.so.0, O_RDONLY|O_CLOEXEC) = 8 read(8, \177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0\0\1\0\0\\21 k7\0\0\0..., 832) = 832 close(8)= 0
Re: [Sugar-devel] Performance: activities start up time
Here is all that it does if I from gi.repository import Gtk before evince. open(/usr/lib/girepository-1.0/EvinceView-3.0.typelib, O_RDONLY) = 11 close(11) = 0 close(10) = 0 open(/usr/lib/girepository-1.0/EvinceView-3.0.typelib, O_RDONLY) = 11 close(11) = 0 close(10) = 0 open(/usr/lib/girepository-1.0/EvinceDocument-3.0.typelib, O_RDONLY) = 10 On 9 November 2013 06:19, Gonzalo Odiard gonz...@laptop.org wrote: In my system, using strace -e trace=open,close,read,write,connect,accept -p pid in another terminal, when I do: from gi.repository import EvinceDocument I see: open(gi.so, O_RDONLY) = -1 ENOENT (No such file or directory) open(gimodule.so, O_RDONLY) = -1 ENOENT (No such file or directory) open(gi.py, O_RDONLY) = -1 ENOENT (No such file or directory) open(gi.pyc, O_RDONLY)= -1 ENOENT (No such file or directory) open(/usr/bin/gi.so, O_RDONLY)= -1 ENOENT (No such file or directory) open(/usr/bin/gimodule.so, O_RDONLY) = -1 ENOENT (No such file or directory) open(/usr/bin/gi.py, O_RDONLY)= -1 ENOENT (No such file or directory) open(/usr/bin/gi.pyc, O_RDONLY) = -1 ENOENT (No such file or directory) open(/usr/lib64/python2.7/gi.so, O_RDONLY) = -1 ENOENT (No such file or directory) open(/usr/lib64/python2.7/gimodule.so, O_RDONLY) = -1 ENOENT (No such file or directory) open(/usr/lib64/python2.7/gi.py, O_RDONLY) = -1 ENOENT (No such file or directory) open(/usr/lib64/python2.7/gi.pyc, O_RDONLY) = -1 ENOENT (No such file or directory) open(/usr/lib64/python2.7/plat-linux2/gi.so, O_RDONLY) = -1 ENOENT (No such file or directory) open(/usr/lib64/python2.7/plat-linux2/gimodule.so, O_RDONLY) = -1 ENOENT (No such file or directory) open(/usr/lib64/python2.7/plat-linux2/gi.py, O_RDONLY) = -1 ENOENT (No such file or directory) open(/usr/lib64/python2.7/plat-linux2/gi.pyc, O_RDONLY) = -1 ENOENT (No such file or directory) open(/usr/lib64/python2.7/lib-tk/gi.so, O_RDONLY) = -1 ENOENT (No such file or directory) open(/usr/lib64/python2.7/lib-tk/gimodule.so, O_RDONLY) = -1 ENOENT (No such file or directory) open(/usr/lib64/python2.7/lib-tk/gi.py, O_RDONLY) = -1 ENOENT (No such file or directory) open(/usr/lib64/python2.7/lib-tk/gi.pyc, O_RDONLY) = -1 ENOENT (No such file or directory) open(/usr/lib64/python2.7/lib-dynload/gi.so, O_RDONLY) = -1 ENOENT (No such file or directory) open(/usr/lib64/python2.7/lib-dynload/gimodule.so, O_RDONLY) = -1 ENOENT (No such file or directory) open(/usr/lib64/python2.7/lib-dynload/gi.py, O_RDONLY) = -1 ENOENT (No such file or directory) open(/usr/lib64/python2.7/lib-dynload/gi.pyc, O_RDONLY) = -1 ENOENT (No such file or directory) open(/usr/lib64/python2.7/site-packages/gi/__init__.so, O_RDONLY) = -1 ENOENT (No such file or directory) open(/usr/lib64/python2.7/site-packages/gi/__init__module.so, O_RDONLY) = -1 ENOENT (No such file or directory) open(/usr/lib64/python2.7/site-packages/gi/__init__.py, O_RDONLY) = 5 open(/usr/lib64/python2.7/site-packages/gi/__init__.pyc, O_RDONLY) = 6 read(6, \3\363\r\nn;\324Pc\0\0\0\0\0\0\0\0\3\0\0\0@ @\0\0s\311\0\0\0d\0..., 4096) = 2118 read(6, , 4096) = 0 close(6)= 0 open(/usr/lib64/python2.7/site-packages/gi/_gi.so, O_RDONLY) = 7 open(/usr/lib64/python2.7/site-packages/gi/_gi.so, O_RDONLY|O_CLOEXEC) = 8 read(8, \177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0\0\1\0\0\0\220\216\0\0\0\0\0\0..., 832) = 832 close(8)= 0 open(/etc/ld.so.cache, O_RDONLY|O_CLOEXEC) = 8 close(8)= 0 open(/lib64/libgirepository-1.0.so.1, O_RDONLY|O_CLOEXEC) = 8 read(8, \177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0\0\1\0\0\\177\0\2167\0\0\0..., 832) = 832 close(8)= 0 open(/lib64/libgobject-2.0.so.0, O_RDONLY|O_CLOEXEC) = 8 read(8, \177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0\0\1\0\0\0\240\253\340j7\0\0\0..., 832) = 832 close(8)= 0 open(/lib64/libglib-2.0.so.0, O_RDONLY|O_CLOEXEC) = 8 read(8, \177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0\0\1\0\0\0P\240\341i7\0\0\0..., 832) = 832 close(8)= 0 open(/lib64/libpyglib-gi-2.0-python.so.0, O_RDONLY|O_CLOEXEC) = 8 read(8, \177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0\0\1\0\0\0p\32\0\0\0\0\0\0..., 832) = 832 close(8)= 0 open(/lib64/libgmodule-2.0.so.0, O_RDONLY|O_CLOEXEC) = 8 read(8, \177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0\0\1\0\0\\21 k7\0\0\0..., 832) = 832 close(8)= 0 open(/lib64/librt.so.1, O_RDONLY|O_CLOEXEC) = 8 read(8, \177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0\0\1\0\0\0\240\`h7\0\0\0..., 832) = 832 close(8)= 0 open(/lib64/libgio-2.0.so.0, O_RDONLY|O_CLOEXEC) = 8 read(8,
Re: [Sugar-devel] My proposals to improve sugar:
2013/11/6 Daniel Narvaez dwnarv...@gmail.com and has the disadvantage that you can not prove what you do on the xo . I never tested but you should be able to get sugar-build working on the XO itself. If you give it a try and run into issues let me know. I'm pretty sure I'll be able to make it work. I tested some time ago when it didn't use broot... Sugar-build does not support ARM. Cheers, Daniel. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] seeking help to enable nepali keyboard input for XO-4
On Fri, Nov 8, 2013 at 8:48 PM, Basanta Shrestha basanta.shres...@olenepal.org wrote: They are hard/clicky ones. So I think what we should do is a combination of the suggestions made previously: if you set the manufacturing data (KL) [1] to tell the laptops that they have Nepali keyboards, you will be part of the way there. But we need to make a new variant (KV) for the hard/clicky (HS) keyboard. As I mentioned earlier, we need to decide what the key combination for switching languages will be, since there is no physical :Language key. -walter [1] http://wiki.laptop.org/go/Manufacturing_data On Fri, Nov 8, 2013 at 10:24 PM, Daniel Drake d...@laptop.org wrote: On Thu, Nov 7, 2013 at 11:23 PM, Basanta Shrestha basanta.shres...@olenepal.org wrote: But for XO-4 we will just be getting ones with English layout. I was wondering how we can enable nepali keyboard input on it. Are these keyboards hard/clicky/high-school style, or soft/membrane? Daniel -- Basanta Shrestha Network Engineer Open Learning Exchange (OLE) Nepal Tel: +977.1.551, 5520075 Ext. 303 Cell: +977.9818 605110 http://www.olenepal.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- 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] seeking help to enable nepali keyboard input for XO-4
walter wrote: On Fri, Nov 8, 2013 at 8:48 PM, Basanta Shrestha basanta.shres...@olenepal.org wrote: They are hard/clicky ones. So I think what we should do is a combination of the suggestions made previously: if you set the manufacturing data (KL) [1] to tell the laptops that they have Nepali keyboards, you will be part of the way there. But we need to make a new variant (KV) for the hard/clicky (HS) keyboard. As I mentioned earlier, we need to decide what the key combination for switching languages will be, since there is no physical :Language key. at what level is the language key handled, on laptops with the membrane keyboards? (i.e., X? sugar?) that might influence what sort of combination is available or useful for doing the switch. paul -walter [1] http://wiki.laptop.org/go/Manufacturing_data On Fri, Nov 8, 2013 at 10:24 PM, Daniel Drake d...@laptop.org wrote: On Thu, Nov 7, 2013 at 11:23 PM, Basanta Shrestha basanta.shres...@olenepal.org wrote: But for XO-4 we will just be getting ones with English layout. I was wondering how we can enable nepali keyboard input on it. Are these keyboards hard/clicky/high-school style, or soft/membrane? Daniel -- Basanta Shrestha Network Engineer Open Learning Exchange (OLE) Nepal Tel: +977.1.551, 5520075 Ext. 303 Cell: +977.9818 605110 http://www.olenepal.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- Walter Bender Sugar Labs http://www.sugarlabs.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel =- paul fox, p...@laptop.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Sugar Labs Roadmap.
Added both gsettings and activity unit test tasks to the table. On 9 November 2013 01:34, Walter Bender walter.ben...@gmail.com wrote: On Fri, Nov 8, 2013 at 7:19 PM, Daniel Narvaez dwnarv...@gmail.com wrote: On 8 November 2013 13:10, Walter Bender walter.ben...@gmail.com wrote: Classmate and Classmate variants are already quick wide spread in some deployments, e.g., Argentina I wonder if we should try to get some classmates in the hands of Sugar Labs community members. It seems like the most solid hardware option we have for deployments at the moment. I'll look into it. * Chromebook At least one deployment is looking at this option. Looking forward to know how this goes :) Another couple more for community evaluation (evaluation, testing, marketing) * Linux compatible ARM boards * Virtualbox SoaS is our current offering for Virtualbox (As you pointed out in a previous thread, it is a two-step process to install. In my experience, that is 1 too many for our audience. Something we may be able to address by approaching some of the VM suppliers.) We are crossing threads here but... I think it would be great to have a single installer but (without having tried it!) the current installation process doesn't seem terribly bad. I feel that documenting it better and turning it into the first thing you see when you click downloads could go a long way. - RD resources I feel balance with addressing existing deployments needs is not a question Sugar Labs can or should answer. We should encourage and support both, it's up to companies and volunteers involved to see how much of either they could or should be doing. +1 That said, the discipline you have imparted on us regarding unit tests is a step that the community can take. Maybe one of our priorities should be to dust off some basic automatic testing for activities as well. OLPC used to have such a system in place. Of course I'm all for more unit tests :) The buildbot is already trying to start and close activities on every build but it would be great if people wrote more comprehensive unit and UI tests, similarly to what we are doing in the shell. Get them to run into sugar-build/buildbot would be trivial... Maybe we can work on an example for an activity and then propagate (via GCI). We are not a company, we have no resources to allocate. But there are lots of concrete things we can do to encourage people to allocate them. I'm really glad to see that Activity Central figured out how to devote resources to RD. I hope you will be able to keep it up and more people will follow that example. We can leverage initiatives like Google Code. We can try crowd funding. We can apply for grants, as we have been doing sometimes successfully. We can keep lowering the barriers for volunteers, we have been making great progress on that. We can finally solve the un-marketability issue, attracting attention and energies and hence hopefully contributions. Google Code In starts on Nov. 18. But we can keep adding tasks over the course of the contest. Please don't be shy about suggesting tasks. And we could also use a few more mentors. I don't think I'm able to commit to be an official mentor but, as usual, I'll be answering as many questions as possible in irc/mailing lists when I am around. Sort of thinking to puth GConf - GSettings on the list... And Wayland support but that's probably too complex for GCI. GConf to GSettings is definitely GCI caliber introductory task worthy. -- Walter Bender Sugar Labs http://www.sugarlabs.org -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] seeking help to enable nepali keyboard input for XO-4
On Sat, Nov 9, 2013 at 8:38 AM, Paul Fox p...@laptop.org wrote: walter wrote: On Fri, Nov 8, 2013 at 8:48 PM, Basanta Shrestha basanta.shres...@olenepal.org wrote: They are hard/clicky ones. So I think what we should do is a combination of the suggestions made previously: if you set the manufacturing data (KL) [1] to tell the laptops that they have Nepali keyboards, you will be part of the way there. But we need to make a new variant (KV) for the hard/clicky (HS) keyboard. As I mentioned earlier, we need to decide what the key combination for switching languages will be, since there is no physical :Language key. at what level is the language key handled, on laptops with the membrane keyboards? (i.e., X? sugar?) that might influence what sort of combination is available or useful for doing the switch. It is handled in X in the xkb symbol file. -walter paul -walter [1] http://wiki.laptop.org/go/Manufacturing_data On Fri, Nov 8, 2013 at 10:24 PM, Daniel Drake d...@laptop.org wrote: On Thu, Nov 7, 2013 at 11:23 PM, Basanta Shrestha basanta.shres...@olenepal.org wrote: But for XO-4 we will just be getting ones with English layout. I was wondering how we can enable nepali keyboard input on it. Are these keyboards hard/clicky/high-school style, or soft/membrane? Daniel -- Basanta Shrestha Network Engineer Open Learning Exchange (OLE) Nepal Tel: +977.1.551, 5520075 Ext. 303 Cell: +977.9818 605110 http://www.olenepal.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- Walter Bender Sugar Labs http://www.sugarlabs.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel =- paul fox, p...@laptop.org -- 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] [ASLO] Release Abacus-53
Activity Homepage: http://activities.sugarlabs.org/addon/4293 Sugar Platform: 0.96 - 0.100 Download Now: http://activities.sugarlabs.org/downloads/file/28820/abacus-53.xo Release notes: 53 ENHANCEMENT: * Use busy cursor instead of alert when switching between abaci * New translations BUG FIX: * Fixed bug preventing GNOME version from launching 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] Sugar Labs Roadmap.
El 09/11/13 23:00, Sebastian Silva escribió: Argentina has I think about a couple of million of them. I checked and there's 3M in Argentina alone so it's already the winning One Laptop device. Ref: http://es.wikipedia.org/wiki/Classmate_PC#Programa_.22Conectar_Igualdad.22 Interestingly, they run a local derivate of Debian 7, called Huayra, with Mate desktop. I have installed Sweets Desktop 0.94 with Sugar Network on Huayra and and it works fine. Regards, Sebastian ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] seeking help to enable nepali keyboard input for XO-4
Thank you so much Walter and sorry that I am very new to these thing. What I have understood so far is : .mfg-date will list the predefined set to stored data. And we need to set KL to 'np' ( this the name of maping file for Nepali under /usr/share/X11/xkb/symbols/ ) and we need to set some value ( np? ) to KV as well. And we need to decide on a key combination to invoke the keyboard switching between the default(English) and Nepali. Since there is no physical : Language key, I think keyboard combination like alt+space bar should be easy. Please suggest if there is other consideration we need to think of. But I am still wondering how we could alter/change the stored data to our preference or if we can do it ourselves. Please suggest. Regards, Basanta On Sat, Nov 9, 2013 at 6:50 PM, Walter Bender walter.ben...@gmail.comwrote: On Fri, Nov 8, 2013 at 8:48 PM, Basanta Shrestha basanta.shres...@olenepal.org wrote: They are hard/clicky ones. So I think what we should do is a combination of the suggestions made previously: if you set the manufacturing data (KL) [1] to tell the laptops that they have Nepali keyboards, you will be part of the way there. But we need to make a new variant (KV) for the hard/clicky (HS) keyboard. As I mentioned earlier, we need to decide what the key combination for switching languages will be, since there is no physical :Language key. -walter [1] http://wiki.laptop.org/go/Manufacturing_data On Fri, Nov 8, 2013 at 10:24 PM, Daniel Drake d...@laptop.org wrote: On Thu, Nov 7, 2013 at 11:23 PM, Basanta Shrestha basanta.shres...@olenepal.org wrote: But for XO-4 we will just be getting ones with English layout. I was wondering how we can enable nepali keyboard input on it. Are these keyboards hard/clicky/high-school style, or soft/membrane? Daniel -- Basanta Shrestha Network Engineer Open Learning Exchange (OLE) Nepal Tel: +977.1.551, 5520075 Ext. 303 Cell: +977.9818 605110 http://www.olenepal.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- Walter Bender Sugar Labs http://www.sugarlabs.org -- Basanta Shrestha Network Engineer Open Learning Exchange (OLE) Nepal Tel: +977.1.551, 5520075 Ext. 303 Cell: +977.9818 605110 http://www.olenepal.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
