[Sugar-devel] [DESIGN] Default ad-hoc networks
Hi, olpc has decided to present ad-hoc networks like they did with mesh networks: three icons in the neighborhood view representing ad-hoc networks with the channels 1, 6, 11. This should preserve the workflow previously introduced and ease the use of ad-hoc networks. More details for the reasoning can be found in [1]. I think this is a great idea and should maybe be adopted by the upstream development, too. So here is what we found out so far: - 3 icons in the neighborhood view representing the 3 channels - we would need three different icons allowing to differentiate the different channels (an interesting idea is here [3]) - those icons should show the status like the Access Point icons does (connected/unconnected) - if someone clicks on one of the icons he joins a possible existing networks or creates a new network - a badge could indicate if a network is already 'active' created by someone else - naming: so far we decided to not name the networks mesh networks to avoid confusion, some voted for 'local network' some for 'our network', others, votes? - the option to create adhoc networks should be removed from the frame device to avoid confusion What do people think about that? Can the design team help to make this happen? Regards, Simon [1] http://lists.laptop.org/pipermail/devel/2009-December/026831.html [2] http://dev.laptop.org/ticket/9845 [3] http://lists.laptop.org/pipermail/devel/attachments/20100422/d9d33027/attachment-0001.png http://lists.laptop.org/pipermail/devel/2010-April/028315.html ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Did someone say Webkit?
On Mon, Apr 26, 2010 at 8:38 PM, Bobby Powers bobbypow...@gmail.com wrote: I wrote surf a while ago, and it was quite an easy port. In fact, the demo browser for pywebkitgtk was (at least at one point) based on browse. I did most of the work in a day and a half, but ran into problems with both webkit's packaging and the feature-completeness of pywebkitgtk (the ability to download files, for example), both of which seem to be solved now. There are also gir bindings for webkit (in webkit's trunk), so it might be worth investigating their completeness, especially since pywebkitgtk seems to be unmaintained, as Sayamindu pointed out. I believe we use the GIR bindings for webkit at litl. So you can probably consider them well supported. --scott -- ( http://cscott.net/ ) ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Did someone say Webkit?
I plan to use current hulahop/pywebkitgtk to start out since there's less to figure out. Since it's an abstraction layer, the backends can be switched later. I need a lot of feedback on what the abstraction layer itself needs to do. Afaik, only Browse and Read use browser engines so far. And then again, there may not be enough time write a leakless enough abstraction to be used by anything other than Browse. On 27 April 2010 08:56, C. Scott Ananian csc...@laptop.org wrote: On Mon, Apr 26, 2010 at 8:38 PM, Bobby Powers bobbypow...@gmail.com wrote: I wrote surf a while ago, and it was quite an easy port. In fact, the demo browser for pywebkitgtk was (at least at one point) based on browse. I did most of the work in a day and a half, but ran into problems with both webkit's packaging and the feature-completeness of pywebkitgtk (the ability to download files, for example), both of which seem to be solved now. There are also gir bindings for webkit (in webkit's trunk), so it might be worth investigating their completeness, especially since pywebkitgtk seems to be unmaintained, as Sayamindu pointed out. I believe we use the GIR bindings for webkit at litl. So you can probably consider them well supported. --scott -- ( http://cscott.net/ ) ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [SoaS] SOAS-3: Final Activity List - Attention needed!
==Preliminary soas-i386-20100426 testing== 2GB USB: ./livecd-iso-to-disk --format --reset-mbr --overlay-size-mb 1200 /home//Desktop/soas-i386-20100426.16.iso /dev/sdg Boot in ACER Aspire One no Plymouth startup screen: barf12 hangs at end of progress bar ===- f13 Reboot edit boot screen: remove quiet and add selenux=0 to boot line Ethernet connection works f1 Wireless connects to Airport Extreme CP/Update Read 7886 TA 8386 DL Record with Browse from ASLO Activities: Browse 115 Etoys 45 Log 23 (-)No Presence service.log entries NO JABBER (-)Write69 Writes to header IRC 6 Physics 4 Terminal 31 TA(7886) Read (8386) *Record67 DL with Browse (-) ERRORS ON INSTALL TO HD: liveinst (Anaconda) in terminal: [liveu...@localhost ~]$ liveinst umount: /media/*: not found No volume groups found Traceback (most recent call last): File /usr/sbin/anaconda, line 817, in module import kickstart File /usr/lib/anaconda/kickstart.py, line 21, in module from storage.deviceaction import * File /usr/lib/anaconda/storage/__init__.py, line 31, in module import parted File /usr/lib/python2.6/site-packages/parted/__init__.py, line 52, in module from partition import Partition File /usr/lib/python2.6/site-packages/parted/partition.py, line 249, in module partitionFlag[__flag] = _ped.partition_flag_get_name(__flag) ValueError: Invalid flag provided. [liveu...@localhost ~]$ Shutdown works reboot w/o quiet: udevd[578]: Bus= will be removed in a future udev version, please use SUBSYSTEM= to match the event device *** Warning -- SELinux targeted policy relabel is required *** Relabeling could take a very long time, depending on file *** system size and speed of hard drives *** (proceeds slowly) + 5 minutes as relabels finally restarts This looks like the long wait at end of bars Tom Gilliard satellit Peter Robinson wrote: Hi All, So as it stands the final Activity list that we're pushing for SOAS-3 will be as below unless someone gives me reasonable doubt as to the release team's (Sebastian and myself) decision. So the final list is: - browse - physics - turtleart - irc - log - terminal - Record - Read - Write - Chat. - etoys In literally the last 10 minutes Sebastian and I have fixed the Write issue and over the last 2 weeks with the latest Record release and a number of fixes and testing I've got Record to what seems to be a stable and working release. The last of the changes should be in the daily build from tomorrow (including a fix from sdz for the lack of a boot screen). One thing to note is that other than sdz and I there has only been one other person test and report back on the builds (Thanks Thomas!) so if you haven't done so until now we are now on the home straight so please test. I don't want to here the day after release Blah is broken because someone hasn't taken 10 minutes to test the release, I will be less than impressed! For those who forget where they can get the daily build you can from this link. http://alt.fedoraproject.org/pub/alt/nightly-composes/soas/ Regards, The SoaS release team! ___ SoaS mailing list s...@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/soas ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Did someone say Webkit?
On Mon, 2010-04-26 at 17:38 -0700, Bobby Powers wrote: I wrote surf a while ago, and it was quite an easy port. In fact, the demo browser for pywebkitgtk was (at least at one point) based on browse. I did most of the work in a day and a half, but ran into problems with both webkit's packaging and the feature-completeness of pywebkitgtk (the ability to download files, for example), both of which seem to be solved now. Surf still works fine in Sugar 0.88 + Fedora 13. How about uploading it to ASLO and putting the source code in git? -- // 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] [SoaS] SOAS-3: Final Activity List - Attention needed!
On Tue, Apr 27, 2010 at 12:45 PM, Thomas C Gilliard satel...@bendbroadband.com wrote: ==Preliminary soas-i386-20100426 testing== 2GB USB: ./livecd-iso-to-disk --format --reset-mbr --overlay-size-mb 1200 /home//Desktop/soas-i386-20100426.16.iso /dev/sdg Boot in ACER Aspire One no Plymouth startup screen: barf12 hangs at end of progress bar ===- f13 Reboot edit boot screen: remove quiet and add selenux=0 to boot line It will be in the build from today, it was too late to hit yesterdays build. Ethernet connection works f1 Wireless connects to Airport Extreme CP/Update Read 7886 TA 8386 DL Record with Browse from ASLO Please just test the Activities included. Record that we ship is essentially 67 anyway. The ASLO isn't part of SoaS. Activities: Browse 115 Etoys 45 Log 23 (-)No Presence service.log entries NO JABBER (-)Write 69 Writes to header Should be fixed in the next daily build. IRC 6 Physics 4 Terminal 31 TA (7886) Read (8386) *Record 67 DL with Browse Again, please just report on issues with the installed Activities. (-) ERRORS ON INSTALL TO HD: liveinst (Anaconda) in terminal: [liveu...@localhost ~]$ liveinst umount: /media/*: not found No volume groups found Traceback (most recent call last): File /usr/sbin/anaconda, line 817, in module import kickstart File /usr/lib/anaconda/kickstart.py, line 21, in module from storage.deviceaction import * File /usr/lib/anaconda/storage/__init__.py, line 31, in module import parted File /usr/lib/python2.6/site-packages/parted/__init__.py, line 52, in module from partition import Partition File /usr/lib/python2.6/site-packages/parted/partition.py, line 249, in module partitionFlag[__flag] = _ped.partition_flag_get_name(__flag) ValueError: Invalid flag provided. [liveu...@localhost ~]$ I'll check the liveinst bug reports. Shutdown works reboot w/o quiet: udevd[578]: Bus= will be removed in a future udev version, please use SUBSYSTEM= to match the event device *** Warning -- SELinux targeted policy relabel is required *** Relabeling could take a very long time, depending on file *** system size and speed of hard drives *** (proceeds slowly) + 5 minutes as relabels finally restarts This looks like the long wait at end of bars That tends to take a while. Was that on the instance that you installed to disk? Peter ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [SoaS] SOAS-3: Final Activity List - Attention needed!
Peter Robinson wrote: On Tue, Apr 27, 2010 at 12:45 PM, Thomas C Gilliard satel...@bendbroadband.com wrote: ==Preliminary soas-i386-20100426 testing== 2GB USB: ./livecd-iso-to-disk --format --reset-mbr --overlay-size-mb 1200 /home//Desktop/soas-i386-20100426.16.iso /dev/sdg Boot in ACER Aspire One no Plymouth startup screen: barf12 hangs at end of progress bar ===- f13 Reboot edit boot screen: remove quiet and add selenux=0 to boot line It will be in the build from today, it was too late to hit yesterdays build. Ethernet connection works f1 Wireless connects to Airport Extreme CP/Update Read 7886 TA 8386 DL Record with Browse from ASLO Please just test the Activities included. Record that we ship is essentially 67 anyway. The ASLO isn't part of SoaS. Activities: Browse 115 Etoys 45 Log 23 (-)No Presence service.log entries NO JABBER (-)Write69 Writes to header Should be fixed in the next daily build. IRC 6 Physics 4 Terminal 31 TA(7886) Read (8386) *Record67 DL with Browse Again, please just report on issues with the installed Activities. ok An interesting thing occured: when I called the record 67 for first time after DL,sugar rebooted record started and worked the 2nd time I started it.(selinux re-label?) (-) ERRORS ON INSTALL TO HD: liveinst (Anaconda) in terminal: [liveu...@localhost ~]$ liveinst umount: /media/*: not found No volume groups found Traceback (most recent call last): File /usr/sbin/anaconda, line 817, in module import kickstart File /usr/lib/anaconda/kickstart.py, line 21, in module from storage.deviceaction import * File /usr/lib/anaconda/storage/__init__.py, line 31, in module import parted File /usr/lib/python2.6/site-packages/parted/__init__.py, line 52, in module from partition import Partition File /usr/lib/python2.6/site-packages/parted/partition.py, line 249, in module partitionFlag[__flag] = _ped.partition_flag_get_name(__flag) ValueError: Invalid flag provided. [liveu...@localhost ~]$ I'll check the liveinst bug reports. Shutdown works reboot w/o quiet: udevd[578]: Bus= will be removed in a future udev version, please use SUBSYSTEM= to match the event device *** Warning -- SELinux targeted policy relabel is required *** Relabeling could take a very long time, depending on file *** system size and speed of hard drives *** (proceeds slowly) + 5 minutes as relabels finally restarts This looks like the long wait at end of bars That tends to take a while. Was that on the instance that you installed to disk? I was trying to use liveinst to install to a USB. This is one of the tried and true ways to get a real install USB (ext3 file structure) they are much more stable and can repair themselves with journaling if damaged. (Take 2x size of live USB) I think that this is a VERY IMPORTANT FEATURE Tom Gilliard satellit Peter ___ 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] [SoaS] SOAS-3: Final Activity List - Attention needed!
On Tue, Apr 27, 2010 at 1:34 PM, Thomas C Gilliard satel...@bendbroadband.com wrote: Peter Robinson wrote: On Tue, Apr 27, 2010 at 12:45 PM, Thomas C Gilliard satel...@bendbroadband.com wrote: ==Preliminary soas-i386-20100426 testing== 2GB USB: ./livecd-iso-to-disk --format --reset-mbr --overlay-size-mb 1200 /home//Desktop/soas-i386-20100426.16.iso /dev/sdg Boot in ACER Aspire One no Plymouth startup screen: barf12 hangs at end of progress bar ===- f13 Reboot edit boot screen: remove quiet and add selenux=0 to boot line It will be in the build from today, it was too late to hit yesterdays build. Ethernet connection works f1 Wireless connects to Airport Extreme CP/Update Read 7886 TA 8386 DL Record with Browse from ASLO Please just test the Activities included. Record that we ship is essentially 67 anyway. The ASLO isn't part of SoaS. Activities: Browse 115 Etoys 45 Log 23 (-)No Presence service.log entries NO JABBER (-)Write 69 Writes to header Should be fixed in the next daily build. IRC 6 Physics 4 Terminal 31 TA (7886) Read (8386) *Record 67 DL with Browse Again, please just report on issues with the installed Activities. ok An interesting thing occured: when I called the record 67 for first time after DL,sugar rebooted record started and worked the 2nd time I started it.(selinux re-label?) (-) ERRORS ON INSTALL TO HD: liveinst (Anaconda) in terminal: [liveu...@localhost ~]$ liveinst umount: /media/*: not found No volume groups found Traceback (most recent call last): File /usr/sbin/anaconda, line 817, in module import kickstart File /usr/lib/anaconda/kickstart.py, line 21, in module from storage.deviceaction import * File /usr/lib/anaconda/storage/__init__.py, line 31, in module import parted File /usr/lib/python2.6/site-packages/parted/__init__.py, line 52, in module from partition import Partition File /usr/lib/python2.6/site-packages/parted/partition.py, line 249, in module partitionFlag[__flag] = _ped.partition_flag_get_name(__flag) ValueError: Invalid flag provided. [liveu...@localhost ~]$ I'll check the liveinst bug reports. Shutdown works reboot w/o quiet: udevd[578]: Bus= will be removed in a future udev version, please use SUBSYSTEM= to match the event device *** Warning -- SELinux targeted policy relabel is required *** Relabeling could take a very long time, depending on file *** system size and speed of hard drives *** (proceeds slowly) + 5 minutes as relabels finally restarts This looks like the long wait at end of bars That tends to take a while. Was that on the instance that you installed to disk? I was trying to use liveinst to install to a USB. This is one of the tried and true ways to get a real install USB (ext3 file structure) they are much more stable and can repair themselves with journaling if damaged. (Take 2x size of live USB) I think that this is a VERY IMPORTANT FEATURE So the relabel happened on the 'real install' and not the live image, correct? If so the selinux relabel is expected the first time round on a 'real install'. Peter ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [SoaS] SOAS-3: Final Activity List - Attention needed!
Peter Robinson wrote: On Tue, Apr 27, 2010 at 1:34 PM, Thomas C Gilliard satel...@bendbroadband.com wrote: Peter Robinson wrote: On Tue, Apr 27, 2010 at 12:45 PM, Thomas C Gilliard satel...@bendbroadband.com wrote: ==Preliminary soas-i386-20100426 testing== 2GB USB: ./livecd-iso-to-disk --format --reset-mbr --overlay-size-mb 1200 /home//Desktop/soas-i386-20100426.16.iso /dev/sdg Boot in ACER Aspire One no Plymouth startup screen: barf12 hangs at end of progress bar ===- f13 Reboot edit boot screen: remove quiet and add selenux=0 to boot line It will be in the build from today, it was too late to hit yesterdays build. Ethernet connection works f1 Wireless connects to Airport Extreme CP/Update Read 7886 TA 8386 DL Record with Browse from ASLO Please just test the Activities included. Record that we ship is essentially 67 anyway. The ASLO isn't part of SoaS. Activities: Browse 115 Etoys 45 Log 23 (-)No Presence service.log entries NO JABBER (-)Write69 Writes to header Should be fixed in the next daily build. IRC 6 Physics 4 Terminal 31 TA(7886) Read (8386) *Record67 DL with Browse Again, please just report on issues with the installed Activities. ok An interesting thing occured: when I called the record 67 for first time after DL,sugar rebooted record started and worked the 2nd time I started it.(selinux re-label?) (-) ERRORS ON INSTALL TO HD: liveinst (Anaconda) in terminal: [liveu...@localhost ~]$ liveinst umount: /media/*: not found No volume groups found Traceback (most recent call last): File /usr/sbin/anaconda, line 817, in module import kickstart File /usr/lib/anaconda/kickstart.py, line 21, in module from storage.deviceaction import * File /usr/lib/anaconda/storage/__init__.py, line 31, in module import parted File /usr/lib/python2.6/site-packages/parted/__init__.py, line 52, in module from partition import Partition File /usr/lib/python2.6/site-packages/parted/partition.py, line 249, in module partitionFlag[__flag] = _ped.partition_flag_get_name(__flag) ValueError: Invalid flag provided. [liveu...@localhost ~]$ I'll check the liveinst bug reports. Shutdown works reboot w/o quiet: udevd[578]: Bus= will be removed in a future udev version, please use SUBSYSTEM= to match the event device *** Warning -- SELinux targeted policy relabel is required *** Relabeling could take a very long time, depending on file *** system size and speed of hard drives *** (proceeds slowly) + 5 minutes as relabels finally restarts This looks like the long wait at end of bars That tends to take a while. Was that on the instance that you installed to disk? I was trying to use liveinst to install to a USB. This is one of the tried and true ways to get a real install USB (ext3 file structure) they are much more stable and can repair themselves with journaling if damaged. (Take 2x size of live USB) I think that this is a VERY IMPORTANT FEATURE So the relabel happened on the 'real install' and not the live image, correct? NO it happened on the live USB when first Booted 2GB USB: ./livecd-iso-to-disk --format --reset-mbr --overlay-size-mb 1200 /home//Desktop/soas-i386-20100426.16.iso /dev/sdg I think that it is causing the 5+ minute hang on the end of the - f13 Progress bars This will cause most users to think that it is failed. Maybe you want to delete quiet from the boot line so users can see the progress... I did the liveinst test later Tom Gilliard satellit If so the selinux relabel is expected the first time round on a 'real install'. Peter ___ 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] [PATCH] _update_signal_match wasn't initialized
James, On Tue, 2010-04-27 at 11:25 +1000, James Cameron wrote: On Mon, Apr 26, 2010 at 03:50:17PM -0400, Raul Gutierrez Segales wrote: Because of missing initialization and a weak test for the existence of the object (self._update_signal_match is not None) Turtle Art was crashing when resuming from the Journal. Reviewed, but I didn't understand. This might be my fault. Your patch appears to be to sugar-toolkit. Correct. self._update_signal_match is only used in DSObject, it is already initialised in sugar-toolkit 0.84.9, and you're adding the initialisation to DSMetadata, where it is not used. Sorry, this was done on the run.. Because we were spinning new builds. Looking at it with more detail, the problem is that self._update_signal_match is initialized in the wrong order (after a call to set_object_id that depends on it). diff --git a/src/sugar/datastore/datastore.py b/src/sugar/datastore/datastore.py index 6ff10de..7aa4d15 100644 --- a/src/sugar/datastore/datastore.py +++ b/src/sugar/datastore/datastore.py @@ -109,12 +109,12 @@ class DSMetadata(gobject.GObject): class DSObject(object): def __init__(self, object_id, metadata=None, file_path=None): +self._update_signal_match = None self.set_object_id(object_id) self._metadata = metadata self._file_path = file_path self._destroyed = False self._owns_file = False -self._update_signal_match = None def get_object_id(self): return self._object_id ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] VncLauncher doesn't run on F11
Hi, Using VncLauncher-4 on F11: it fails to start the VNC server because the binary links against the wrong version of libssl. This activity is used very often in deployments for presentations, training sessions, etc, so it would be nice to have a new version. Daniel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [SoaS] SOAS-3: Final Activity List - Attention needed!
I'd much rather we work together. Making Sugar and its Activities robust is a challenge and doing so on Sugar on a Stick even more. We have a resources problem that needs to be solved; part of the solution is to make Sugar better known, to developers, to teachers, and to the industry (OEMs...). It's a chicken-and-egg situation; Sugar could catch on quickly if robust, but that requires resources we don't have. But teachers, education buyers, journalists need to be able to see and touch Sugar, and for that they need a solution (the historical scarcity of XOs for reviewers has been part of OLPC's PR problem since the start). Sugar on a Stick has had that role. However, the new version (as well as it will fulfill a production role) won't fulfill the demo role. This creates a problem. The version numbers were marketing numbers (SoaS-1 was beta-1, SoaS-2 was v1, etc.) and appropriating the number for a version unsuitable for demoing Sugar means marketing can't work with it. Sean On Mon, Apr 26, 2010 at 9:48 PM, Peter Robinson pbrobin...@gmail.com wrote: Hi Sean, I'm so pleased that you think that all the hard work that Sebastian, myself and all the other Sugar developers that have put into the Sugar 0.88 release and associated SoaS release is so 0.5. and a whole lot less than previous releases. I think your choice is demeaning to the hard work that everyone does and without active testing of other Activities by other people it only hurts SoaS when things don't work because the release team are the only people that test stuff and aren't paid full time to do this. Peter On Mon, Apr 26, 2010 at 8:22 PM, Sean DALY sdaly...@gmail.com wrote: As stated previously, it's a mistake for this release to be numbered v3. I won't be able to do anything with it. Sean On Mon, Apr 26, 2010 at 9:16 PM, Peter Robinson pbrobin...@gmail.com wrote: Hi All, So as it stands the final Activity list that we're pushing for SOAS-3 will be as below unless someone gives me reasonable doubt as to the release team's (Sebastian and myself) decision. So the final list is: - browse - physics - turtleart - irc - log - terminal - Record - Read - Write - Chat. - etoys In literally the last 10 minutes Sebastian and I have fixed the Write issue and over the last 2 weeks with the latest Record release and a number of fixes and testing I've got Record to what seems to be a stable and working release. The last of the changes should be in the daily build from tomorrow (including a fix from sdz for the lack of a boot screen). One thing to note is that other than sdz and I there has only been one other person test and report back on the builds (Thanks Thomas!) so if you haven't done so until now we are now on the home straight so please test. I don't want to here the day after release Blah is broken because someone hasn't taken 10 minutes to test the release, I will be less than impressed! For those who forget where they can get the daily build you can from this link. http://alt.fedoraproject.org/pub/alt/nightly-composes/soas/ Regards, The SoaS release team! ___ SoaS mailing list s...@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/soas ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Keyboard navigability of the Sugar UI
Today I filed a bug to keep track of an issue that has been bothering me for a long time: http://bugs.sugarlabs.org/ticket/1969 Being an important UI issue, we'd need a good discussion with the design team. Unfortunately, we cannot always follow existing Gnome conventions for keyboard shortcuts. For example, rename cannot be done with F2 because it's already used for the buddy view. -8--8--8--8--8- The Sugar UI should be 100% navigable without using a mouse. Besides being an accessibility issue, it's important for quick navigation, especially for users stuck with a broken XO touchpads. Some proposed changes: * Favorites view * Search should be enabled in the shell view * A caret should appear when the user starts to type * Non-matching activities should be grayed out * TAB should cycle through possible completions * Cursor keys should cycle through the icons * Journal * Cursor up/down should scroll a caret on the list * ENTER should open the selected item (Linux/Windows style) * Rename item: TBD (just type something?) * Go to proprieties: TBD (cursor right?) * Change volume: TBD * Unmount all hot pluggable devices: TBD * Activities list view * Should behave like the journal * Network Neighborhood * Similar to favorites view * Toolbars * There should be a key to move the focus to the toolbars (alt-space?) -- // 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] VncLauncher doesn't run on F11
On Tue, Apr 27, 2010 at 3:06 PM, Daniel Drake d...@laptop.org wrote: Hi, Using VncLauncher-4 on F11: it fails to start the VNC server because the binary links against the wrong version of libssl. This activity is used very often in deployments for presentations, training sessions, etc, so it would be nice to have a new version. Some time around F-11 Fedora moved from the standard vnc to tigervnc for various different reasons (don't remember the exact time or reasons). Do any of the tigervnc* packages provide the same functionality? Peter ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [SoaS] SOAS-3: Final Activity List - Attention needed!
Sean, I would much rather we work together as well! Firstly your point (SoaS-1 was beta-1, SoaS-2 was v1, etc.) is a completely different point of view than your previous official press releases from SugarLabs [1] and [2]. I believe one of the major points of marketing is about consistency. To quote the first release LinuxTag, Berlin, June 24, 2009: Sugar Labs™, nonprofit provider of the Sugar Learning Platform to over one-million children worldwide, announces the immediate availability of Sugar on a Stick v1 Strawberry. and the second PARIS, December 8, 2009 — Netbook World Summit — Sugar Labs(R), volunteer-driven nonprofit provider of the Sugar Learning Platform for over one-million children around the world, announces the release of Sugar on a Stick v2 Blueberry. You are correct we all want to make Sugar better known. The whole reason we have slimmed down the Activities is to make the included Activities stable so Sugar could catch on quickly if robust but I completely disagree with your the new version won't fulfil the demo role. The whole point of the Activities chosen was to cover all the major features of Sugar in a group of Activities that is stable and works. As stated previously I and others think we are better off shipping a smaller selection of Activities that cover all main features of Sugar such as Collaboration and Media rather than 100s of Activities that don't work as expected, crash randomly or fail of different hardware. So what major features of Sugar have we missed in the list of included Activities? Given that there is not enough people doing QA and that I believe we are better off shipping a smaller stable base that demos the core features of Sugar. If we stop releasing official releases until we had the resources to make every Activity stable and tested we would never have released Sugar on a Stick v1 Strawberry or Sugar on a Stick v2 Blueberry and by the time that happened for v3 people would have long since forgotten that SoaS even existed. not what the ides of Marketing is about and we wouldn't be making Sugar better known, to developers, to teachers, and to the industry (OEMs...). Peter [1] http://www.sugarlabs.org/index.php?template=pressarticle=20090624language=english#20090624 [2] http://www.sugarlabs.org/index.php?template=pressarticle=20091208language=english#20091208 On Tue, Apr 27, 2010 at 3:16 PM, Sean DALY sdaly...@gmail.com wrote: I'd much rather we work together. Making Sugar and its Activities robust is a challenge and doing so on Sugar on a Stick even more. We have a resources problem that needs to be solved; part of the solution is to make Sugar better known, to developers, to teachers, and to the industry (OEMs...). It's a chicken-and-egg situation; Sugar could catch on quickly if robust, but that requires resources we don't have. But teachers, education buyers, journalists need to be able to see and touch Sugar, and for that they need a solution (the historical scarcity of XOs for reviewers has been part of OLPC's PR problem since the start). Sugar on a Stick has had that role. However, the new version (as well as it will fulfill a production role) won't fulfill the demo role. This creates a problem. The version numbers were marketing numbers (SoaS-1 was beta-1, SoaS-2 was v1, etc.) and appropriating the number for a version unsuitable for demoing Sugar means marketing can't work with it. Sean On Mon, Apr 26, 2010 at 9:48 PM, Peter Robinson pbrobin...@gmail.com wrote: Hi Sean, I'm so pleased that you think that all the hard work that Sebastian, myself and all the other Sugar developers that have put into the Sugar 0.88 release and associated SoaS release is so 0.5. and a whole lot less than previous releases. I think your choice is demeaning to the hard work that everyone does and without active testing of other Activities by other people it only hurts SoaS when things don't work because the release team are the only people that test stuff and aren't paid full time to do this. Peter On Mon, Apr 26, 2010 at 8:22 PM, Sean DALY sdaly...@gmail.com wrote: As stated previously, it's a mistake for this release to be numbered v3. I won't be able to do anything with it. Sean On Mon, Apr 26, 2010 at 9:16 PM, Peter Robinson pbrobin...@gmail.com wrote: Hi All, So as it stands the final Activity list that we're pushing for SOAS-3 will be as below unless someone gives me reasonable doubt as to the release team's (Sebastian and myself) decision. So the final list is: - browse - physics - turtleart - irc - log - terminal - Record - Read - Write - Chat. - etoys In literally the last 10 minutes Sebastian and I have fixed the Write issue and over the last 2 weeks with the latest Record release and a number of fixes and testing I've got Record to what seems to be a stable and working release. The last of the changes should be in the daily build from tomorrow (including a fix from sdz for the lack
[Sugar-devel] Experimental work... updated.
This is just a quick note to let interested parties know that I've updated my experimental repo at http://dev.laptop.org/git/users/mstone/sugar git://dev.laptop.org/users/mstone/sugar to sugar*-0.88. For those who are curious, this repo: * combines all six of the sugar, sugar-toolkit, sugar-base, sugar-artwork, sugar-datastore, and sugar-presence-service repos into a single repo [1], [1]: To see how, google for git subtree merge. The progit.org and kernel.org hits are both helpful. * replaces the complete autotools infrastructure of all six repos mentioned above with a single top-level Makefile of some 250 lines, and * removes most uses of logging from the sugar python source code in favor of error-reporting via cgitb's verbose tracebacks [1] and info reporting via print. [2]: cgitb is a little-known module in the Python standard library which provides verbose tracebacks in either plaintext or HTML. Regards, and apologies in advance for the remaining rough edges, Michael ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] What application in f13 liveinst (Anaconda) takes the live, compressed, file system and converts it to a normal file system during a HD install?
I am curious: What application in the f13 liveinst Anaconda (Install to HD link on the live desktop of gnome) takes the live file system and converts it to a normal file system on HD install after the files are transferred to the HD during installation Can we use this to take the soas live file system and do a conversion to a real HD install? Tom Gilliard satellit ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Introduction to this year's GSoC teams
Thank you to all of the students and mentors that have invested their time in assisting Sugar Labs through the GSoC application process. Contratulations to the successful students! As you will have inferred from my previous emails, this year's applications were of a very high calibre. If you were unsuccessful, we would still love your contributions! There were several applications that we regretfully needed to turn down that would be excellent additions to Sugar. Here are the successful projects: *Enhancing Sugar on a Stick* Sebastian Dziallas (sdziallas), mentored by Walter Bender http://wiki.sugarlabs.org/go/Summer_of_Code/2010/Improved_Sugar_on_a_Stick Selected comments: - The author of this proposal has outlined a realistic timeline for a valuable project and has demonstrated that he has the knowledge, motivation, and contacts necessary to succeed and to grow. - SoaS is a critial part of the Sugar strategy for reaching out to teachers. ** *Pippy Improvements* Dinko Galetić (dgaletic), mentored by Michael Stone http://wiki.sugarlabs.org/go/Summer_of_Code/2010/Pippy_improvements Selected comments: - This is a fine proposal, well aligned with Sugar's goals, made by a talented candidate. *Abstract Browser* Lucian Branescu Mihaila (lucian), mentored by Luis Gustavo Lira http://wiki.sugarlabs.org/go/Summer_of_Code/2010/AbstractBrowser Selected comments: - This is a clear and focused proposal about a clear need - Lucian demonstrated that he is up to the task last summer--he could revitalize this important corner of Sugar I wish the teams the best of luck. Congratulations to the sucessful students! I'll be updating the wiki today my time. Please feel to come to me with any questions. Regards, Tim McNamara Sugar Labs GSoC 2010 Coordinator ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Experimental work... updated.
On Tue, Apr 27, 2010 at 11:44:39AM -0400, Michael Stone wrote: This is just a quick note to let interested parties know that I've updated my experimental repo at http://dev.laptop.org/git/users/mstone/sugar git://dev.laptop.org/users/mstone/sugar Looks good. Even has my #897 fix in it. Thanks! I like the idea of one repository, it makes working with it much easier. Have you noticed a significant performance improvement from removing logging? I did before I found the O_SYNC on a slow system. -- James Cameron http://quozl.linux.org.au/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [PATCH] _update_signal_match wasn't initialized
On Tue, Apr 27, 2010 at 09:43:21AM -0400, Raul Gutierrez Segales wrote: Looking at it with more detail, the problem is that self._update_signal_match is initialized in the wrong order (after a call to set_object_id that depends on it). No worries, now I understand, and approve. Reviewed-by: James Cameron qu...@laptop.org -- 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] Get Books in ASLO?
Sayamindu, As I had mentioned before, I am making a FLOSS Manual on e-book reading and Sugar. I wanted to include a mention of your Get Books Activity in there, and I was surprised to find that Get Books is not in ASLO. I really think it ought to be at this point. James Simmons ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] stopwatch activity
I noticed something interesting with he stopwatch activity on the XO 1.5 C2 with build 120. When the XO goes into suspend, the clock stops display, but upon resume, will show actual time elapsed (clock keep counting). Mark also works correctly, displaying the time when the Mark button is clicked, irrespective of the display. I'm not sure what the behavior should be, though. Should the activity prevent suspend? cheers, Sameer -- Dr. Sameer Verma, Ph.D. Associate Professor, Information Systems Director, Campus Business Solutions San Francisco State University http://verma.sfsu.edu/ http://opensource.sfsu.edu/ http://cbs.sfsu.edu/ http://is.sfsu.edu/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Experimental work... updated.
On Tue, Apr 27, 2010 at 11:44:39AM -0400, Michael Stone wrote: This is just a quick note to let interested parties know that I've updated my experimental repo at http://dev.laptop.org/git/users/mstone/sugar git://dev.laptop.org/users/mstone/sugar Looks good. Even has my #897 fix in it. Thanks! My pleasure; thanks for the patch. I like the idea of one repository, it makes working with it much easier. I particularly like that I can test sugar*-0.88 directly on my XO by running something comparable to yum install git-core gcc glibc-devel make vim git clone git://dev.laptop.org/users/mstone/sugar; cd sugar make xo-builddeps env PREFIX=/usr ./configure make; make install I also like how easy it is to consider patches that touch multiple subsystems in their entirety. Have you noticed a significant performance improvement from removing logging? I did before I found the O_SYNC on a slow system. Neat! (I haven't timed it yet myself -- I made the change soley because, for me, it improves the signal-to-noise ratio in the codebase.) Michael ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] stopwatch activity
On Tue, 27 Apr 2010, Sameer Verma wrote: I noticed something interesting with he stopwatch activity on the XO 1.5 C2 with build 120. When the XO goes into suspend, the clock stops display, but upon resume, will show actual time elapsed (clock keep counting). Mark also works correctly, displaying the time when the Mark button is clicked, irrespective of the display. I'm not sure what the behavior should be, though. I think that's fine behavior. Most stopwatches don't stop running by themselves, so I don't see why ours should. Should the activity prevent suspend? My philosophy is that suspend should be _absolutely transparent_ to the user; i.e. its effects should not be detectable, in the same way that processor voltage scaling is undetectable. This suggests that Stopwatch should inhibit suspend while it is visible onscreen. I'm reluctant to do this, though, because it feels like an ugly hack. The right solution would be for the suspend system to recognize that Stopwatch has a timer set to expire in 100 ms, and postpone suspend. --Ben ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] stopwatch activity
On Tue, Apr 27, 2010 at 8:00 PM, Benjamin M. Schwartz bmsch...@fas.harvard.edu wrote: On Tue, 27 Apr 2010, Sameer Verma wrote: I noticed something interesting with he stopwatch activity on the XO 1.5 C2 with build 120. When the XO goes into suspend, the clock stops display, but upon resume, will show actual time elapsed (clock keep counting). Mark also works correctly, displaying the time when the Mark button is clicked, irrespective of the display. I'm not sure what the behavior should be, though. I think that's fine behavior. Most stopwatches don't stop running by themselves, so I don't see why ours should. Indeed, so when the numbers stop at a certain point, it looks strange. Should the activity prevent suspend? My philosophy is that suspend should be _absolutely transparent_ to the user; i.e. its effects should not be detectable, in the same way that processor voltage scaling is undetectable. This suggests that Stopwatch should inhibit suspend while it is visible onscreen. I'm reluctant to do this, though, because it feels like an ugly hack. The right solution would be for the suspend system to recognize that Stopwatch has a timer set to expire in 100 ms, and postpone suspend. --Ben Sameer -- Dr. Sameer Verma, Ph.D. Associate Professor, Information Systems Director, Campus Business Solutions San Francisco State University http://verma.sfsu.edu/ http://opensource.sfsu.edu/ http://cbs.sfsu.edu/ http://is.sfsu.edu/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Did someone say Webkit?
On Tue, Apr 27, 2010 at 8:56 AM, C. Scott Ananian csc...@laptop.org wrote: There are also gir bindings for webkit (in webkit's trunk), so it might be worth investigating their completeness, especially since pywebkitgtk seems to be unmaintained, as Sayamindu pointed out. I believe we use the GIR bindings for webkit at litl. So you can probably consider them well supported. Marco says I'm wrong: we're driving webkit over dbus. I know our *dbus* gir bindings are well supported! (I'm writing all my code for the 8051 these days.) --scott -- ( http://cscott.net/ ) ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Experimental work... updated.
On Tue, Apr 27, 2010 at 11:44:39AM -0400, Michael Stone wrote: This is just a quick note to let interested parties know that I've updated my experimental repo at http://dev.laptop.org/git/users/mstone/sugar git://dev.laptop.org/users/mstone/sugar to sugar*-0.88. For those who are curious, this repo: * combines all six of the sugar, sugar-toolkit, sugar-base, sugar-artwork, sugar-datastore, and sugar-presence-service repos into a single repo [1], I followed different way, see http://wiki.sugarlabs.org/go/Documentation_Team/Services/Scalable_development_model http://wiki.sugarlabs.org/go/Activity_Team/Polyol [1]: To see how, google for git subtree merge. The progit.org and kernel.org hits are both helpful. * replaces the complete autotools infrastructure of all six repos mentioned above with a single top-level Makefile of some 250 lines, and * removes most uses of logging from the sugar python source code in favor of error-reporting via cgitb's verbose tracebacks [1] and info reporting via print. [2]: cgitb is a little-known module in the Python standard library which provides verbose tracebacks in either plaintext or HTML. Regards, and apologies in advance for the remaining rough edges, Michael ___ 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
