Re: [Sugar-devel] depending on introspection
On Fri, Jun 18, 2010 at 19:20, Sascha Silbe sascha-ml-ui-sugar-de...@silbe.org wrote: Excerpts from Daniel Drake's message of Fri Jun 18 16:08:34 + 2010: Fair points, but these are all Debian's problems, in my opinion. It falls into the We're innovating, can you keep up? camp. No, they're my problem because I develop Sugar on Debian systems. Can you afford to leave me behind? Is it worth the advantage of being able to use introspection (or whatever other bleeding edge technology that requires modifying major system libraries instead of just installing additional ones) right now? Sascha, what would take to have a modern GNOME stack on the Debian systems you use? Thanks, Tomeu Sascha -- http://sascha.silbe.org/ http://www.infra-silbe.de/ ___ 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] depending on introspection
On Wed, Aug 18, 2010 at 11:05, Tomeu Vizoso to...@sugarlabs.org wrote: On Fri, Jun 18, 2010 at 19:20, Sascha Silbe sascha-ml-ui-sugar-de...@silbe.org wrote: Excerpts from Daniel Drake's message of Fri Jun 18 16:08:34 + 2010: Fair points, but these are all Debian's problems, in my opinion. It falls into the We're innovating, can you keep up? camp. No, they're my problem because I develop Sugar on Debian systems. Can you afford to leave me behind? Is it worth the advantage of being able to use introspection (or whatever other bleeding edge technology that requires modifying major system libraries instead of just installing additional ones) right now? Sascha, what would take to have a modern GNOME stack on the Debian systems you use? Also, note that sticking to the current dependencies won't allow us to keep jhbuild lean because we'd have to build old stuff for distros such as Fedora. Regards, Tomeu Thanks, Tomeu Sascha -- http://sascha.silbe.org/ http://www.infra-silbe.de/ ___ 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] [olpc-nz] Samoa deployments
On Tue, 2010-08-17 at 11:42 -0400, David Farning wrote: Awesome please submit the bug reports to the sl bug tracker with the keyword 'dextrose' or to this ML. We are monitoring the list as it is the best source of feed back in the sugar/olpc ecosystem. We installed os300py on all the laptops and found quite a few bugs. I've raised some tickets: http://bugs.sugarlabs.org/ticket/2186 http://bugs.sugarlabs.org/ticket/2185 http://bugs.sugarlabs.org/ticket/2184 http://bugs.sugarlabs.org/ticket/2183 http://bugs.sugarlabs.org/ticket/2182 I've got some more to raise, but they will have to wait until tomorrow. I also noticed some things that I can't reproduce and probably won't raise tickets for. Every now and again, especially when the laptop was busy, opening a new activity would briefly show in a window frame like you see on an http basic authentication dialog. Usually this would disappear within a couple of seconds and the contents of the window would move up to a normal full screen view but very occasionally it would persist and you would have an activity in a window that you could move around. I'll raise a ticket for this, as it happened quite often (but nearly always the activity went full screen within a couple of seconds). Once, Browse froze due to a modal dialog in another window. I'm not really sure how I managed it, but while starting Browse, two Browse windows started and the background one had a modal dialog. This blocked both windows and gave the impression that browse had frozen. I eventually alt-tabbed (heading for the terminal to investigate there) and noticed the other window. Dismissing the dialog in the background window unlocked browse. Unfortunately I didn't take proper notes at the time as I only had a few minutes to use the internet and I really needed to do something rather than diagnose problems, sorry. I think the popup might have been an http-basic challenge, but extensive testing here couldn't reproduce the lock up with such a challenge. This problem might have been related to the window manager decorations visible problem above but I can't remember. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Browse-115 stops when pop-up tab closes
On 18 August 2010 03:06, Christoph Derndorfer christoph.derndor...@gmail.com wrote: On Sat, Aug 14, 2010 at 8:54 AM, Lucian Branescu lucian.brane...@gmail.com wrote: Afaict, this isn't a bug in Browse, but in sugar.activity.Activity. I also can't find any evidence in the logs that it segfaults. I'm afraid unless I can reproduce it I can't do anything. Could you save the HTML page that opens a new window (tab), with javascript and everything? That may help me reproduce it. Sorry, I missed that message of yours... Would a Firefox - Save complete page copy be good enough for this purpose? That should be enough to reproduce it, yes. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Help testing new sugar packages in F14
Hi, to get the new Sugar release 0.90 [1] into shape and make it a stable release we want people to test the nightly Soas snapshots [2]. In order to get the new packaged tarballs into those builds they have to meet certain criteria first [3], hence we need people testing them. You can simply do this by getting the rpms from koji and install them into your latest soas snapshot and restart Sugar. What I do in short is: - open the Browse activity and go to http://koji.fedoraproject.org - search for the package (sugar, sugar-toolkit...) - click on the latest F14 version and then right-click on the download option of the 'noarch' rpm and choose 'copy link' from the palette (if you download directly it is stored in the Journal) - then open the terminal activity log in as root and you can copy in the address here using ctrl+shift+v or the edit tab in the toolbar - the command for updating the rpm is: 'rpm -U [name of rpm]' Once you tested the package you can comment on bodhi [4] about your findings and give karma points. If you have not done so yet, you should create a Fedora account [5], so your comments have a higher value. Why not start today? Here are some packages that would need your testing [6] [7]. Btw, there will be a Fedora testing day [8] this Thursday and we want to give a go on Sugar, too. More info to come. If you have questions please feel free to ask. I am as well on irc #sugar most of the day. Regards, Simon [1] http://wiki.sugarlabs.org/go/0.90/Roadmap#Schedule [2] http://alt.fedoraproject.org/pub/alt/nightly-composes/soas/ [3] https://fedoraproject.org/wiki/Package_update_acceptance_criteria [4] https://admin.fedoraproject.org/updates [5] https://admin.fedoraproject.org/accounts/user/new?_csrf_token=88fb044408f6ad820284d0a7f38dc7731efb1808 [6] https://admin.fedoraproject.org/updates/sugar-artwork-0.89.3-1.fc14,sugar-toolkit-0.89.3-1.fc14?_csrf_token=88fb044408f6ad820284d0a7f38dc7731efb1808 [7] https://admin.fedoraproject.org/updates/sugar-toolkit-0.89.2-1.fc14,sugar-presence-service-0.90.0-1.fc14,sugar-0.89.3-1.fc14,sugar-base-0.90.0-1.fc14?_csrf_token=88fb044408f6ad820284d0a7f38dc7731efb1808 [8] https://fedorahosted.org/fedora-qa/ticket/108 ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] UI testing, GitHub (was Re: List of widgets used in Sugar?)
Excerpts from Tim McNamara's message of Mon Aug 16 04:41:39 +0200 2010: More generally, Experior is coming along relatively nicely. Great news! The canonical branch is being hosted on GitHub [3]. Partially because I wanted to see what all the fuss was about. Mainly because of its lightweight issue tracker. Once I feel that the code is at a fairly stable state, I'll move the tracker to bugs.sugarlabs.org. Please report back how well GitHub worked out for you and what the relative advantages / disadvantages are. FWIW, we seem to have finally found someone with time and willingness to upgrade our gitorious instance. Yay to Raul! *Emerging Issues:* - Experior is designed to test actvities, I can't seem to test sugar-core UI feature atm That's fine IMO. The core system (Shell etc.) and sugar-toolkit are likely to have different needs than activities when it comes to testing. Don't try to bend a tool to achieve two different jobs, rather focus on doing one of them well. Sascha -- http://sascha.silbe.org/ http://www.infra-silbe.de/ signature.asc Description: PGP signature ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Why automated testing and dogfooding is crucial (was: Re: code submitted for review should have been tested)
Excerpts from Tomeu Vizoso's message of Wed Aug 11 12:22:00 +0200 2010: any code contributor is expecting that their patches will be tested by the reviewer? A contributor should test their code to the best of their ability. A reviewer can, but doesn't have to test the code. A tester can, but doesn't have to review the code. With the mailing list based review model, this is expressed as the separate Reviewed-By and Tested-By tags. Because of this specific commit, file transfers have been broken since early this year and it's obvious that this code wasn't tested at all: http://git.sugarlabs.org/projects/sugar/repos/mainline/commits/11828796 Me being the original author of the patch, it's obvious that the code was tested rather well before submitting it for review. But a) I'm not perfect, so some code paths were not exercised before the initial submission for review b) it took many months before the patch was accepted, so it bitrotted. Simon probably had to solve a number of conflicts; also some changes in the surroundings of the patch might have been ignored by the VCS. All this is an error-prone process that requires any test to be re-run / re-done. This is a very nice example of a) how the long time patches wait in the review queue and the cumbersome process of submitting them to Trac is negatively affecting the project (I remember fixing an issue in this very patch related to file sharing, but probably never submitted an updated patch to Trac because it was rejected anyway back then). b) why automated testing is crucial. (I don't think I need to elaborate that point, it should be obvious from the above if it wasn't obvious before already.) Given the current poor state of our testing efforts, The best way to get Sugar tested well (besides automatic tests which only catch specific cases) is by eating our own dog food. Of course, this requires us to accept some high ceiling patches (that no deployment will call for) instead of just low floor ones. This might increase the risk of breaking something (or raising the floor), but IMO is more than offset by the better testing and increased number of motivated contributors we get. Please consider this mail food for thought, not a direct retort to your complaint about the breakage. That I was the one who authored this original patch is merely a detail showing that even careful and experienced contributors (as I consider myself to be) can't be relied upon to not make mistakes. We need to accept the fact that humans are imperfect and cater for it by tuning our processes and goals. Sascha -- http://sascha.silbe.org/ http://www.infra-silbe.de/ signature.asc Description: PGP signature ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Why automated testing and dogfooding is crucial (was: Re: code submitted for review should have been tested)
On Wed, Aug 18, 2010 at 11:54, Sascha Silbe sascha-ml-ui-sugar-de...@silbe.org wrote: Excerpts from Tomeu Vizoso's message of Wed Aug 11 12:22:00 +0200 2010: any code contributor is expecting that their patches will be tested by the reviewer? A contributor should test their code to the best of their ability. A reviewer can, but doesn't have to test the code. A tester can, but doesn't have to review the code. With the mailing list based review model, this is expressed as the separate Reviewed-By and Tested-By tags. Because of this specific commit, file transfers have been broken since early this year and it's obvious that this code wasn't tested at all: http://git.sugarlabs.org/projects/sugar/repos/mainline/commits/11828796 Me being the original author of the patch, it's obvious that the code was tested rather well before submitting it for review. But a) I'm not perfect, so some code paths were not exercised before the initial submission for review b) it took many months before the patch was accepted, so it bitrotted. Simon probably had to solve a number of conflicts; also some changes in the surroundings of the patch might have been ignored by the VCS. All this is an error-prone process that requires any test to be re-run / re-done. This is a very nice example of a) how the long time patches wait in the review queue and the cumbersome process of submitting them to Trac is negatively affecting the project (I remember fixing an issue in this very patch related to file sharing, but probably never submitted an updated patch to Trac because it was rejected anyway back then). b) why automated testing is crucial. (I don't think I need to elaborate that point, it should be obvious from the above if it wasn't obvious before already.) Given the current poor state of our testing efforts, The best way to get Sugar tested well (besides automatic tests which only catch specific cases) is by eating our own dog food. Of course, this requires us to accept some high ceiling patches (that no deployment will call for) instead of just low floor ones. This might increase the risk of breaking something (or raising the floor), but IMO is more than offset by the better testing and increased number of motivated contributors we get. You make good points, but the bit about dogfooding doesn't hold as well because I, for example, don't ever use file transfer in GNOME. In any case, I don't think you are saying that if I propose a patch that changes code in the file transfer path I shouldn't have tested file transfers? Btw, I've been looking at AT-SPI with eyes on accessibility and testing today. Regards, Tomeu Please consider this mail food for thought, not a direct retort to your complaint about the breakage. That I was the one who authored this original patch is merely a detail showing that even careful and experienced contributors (as I consider myself to be) can't be relied upon to not make mistakes. We need to accept the fact that humans are imperfect and cater for it by tuning our processes and goals. Sascha -- http://sascha.silbe.org/ http://www.infra-silbe.de/ ___ 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] touchpad mode selection
On 08/07/2010 08:22 PM, Walter Bender wrote: On Fri, Aug 6, 2010 at 9:10 AM, Paul Foxp...@laptop.org wrote: walter -- currently we try at boot time and set the touchpad to whichever mode the user last requested. moving this initialization to sugar was one of the last changes you made to the sugar code, i think. but when you were in the office you mentioned that it might be preferable to always revert to capacitive (normal) mode at boot time, so that the user doesn't get stuck or confused by pen mode (which is certainly less discoverable' than normal mode). the more i think about it, the more i think that's a good idea. what do other people (who, hopefully have tried both modes) think? paul =- paul fox, p...@laptop.org http://bugs.sugarlabs.org/attachment/ticket/2006/0001-touchpad-with-finger-mode-default.patch defaults to capacitive on boot. It no longer uses the FLAG_FILE and thus that file is no longer needed by your patch either. Its presence will not impact the functionality, as far as I know. I've tested this on 258py. I'd appreciate your doing a quick review just to make sure I didn't miss anything. -walter Hi Walter, first of all thanks for your work! I have been testing the device option on 850 XO-1.0 (it is just a matter of copying the files over from the 0.90 patch that just landed in master). I find it quite hard to use the stylus mode as one really needs to scratch over the touchpad. Especially when one wants to revert the setting after using the stylus mode it is hard to reveal the frame, move to the icon and click it. There have been discussions about which mode it should have after booting. Another case where it might hard to discover which mode one is using at that time is after suspend. You have to scratch as well in order to wake up the machine. Regards, Simon PS: style nitpick: I would capitalize the strings 'style' and 'finger' and align them left in the palette. PSS: if others want to test on the XO-1.0 I can make some rpms quickly. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] touchpad mode selection
simon wrote: On 08/07/2010 08:22 PM, Walter Bender wrote: On Fri, Aug 6, 2010 at 9:10 AM, Paul Foxp...@laptop.org wrote: walter -- currently we try at boot time and set the touchpad to whichever mode the user last requested. moving this initialization to sugar was one of the last changes you made to the sugar code, i think. but when you were in the office you mentioned that it might be preferable to always revert to capacitive (normal) mode at boot time, so that the user doesn't get stuck or confused by pen mode (which is certainly less discoverable' than normal mode). the more i think about it, the more i think that's a good idea. what do other people (who, hopefully have tried both modes) think? paul =- paul fox, p...@laptop.org http://bugs.sugarlabs.org/attachment/ticket/2006/0001-touchpad-with-finger-mode- default.patch defaults to capacitive on boot. It no longer uses the FLAG_FILE and thus that file is no longer needed by your patch either. Its presence will not impact the functionality, as far as I know. I've tested this on 258py. I'd appreciate your doing a quick review just to make sure I didn't miss anything. -walter Hi Walter, first of all thanks for your work! I have been testing the device option on 850 XO-1.0 (it is just a matter of copying the files over from the 0.90 patch that just landed in master). I find it quite hard to use the stylus mode as one really needs to scratch over the touchpad. Especially when one wants to revert the setting after using the stylus mode it is hard to reveal the frame, move to the icon and click it. yes, the stylus mode requires a lot of pressure. There have been discussions about which mode it should have after booting. the system support for enabling stylus mode at boot was removed recently -- i can't remember if it's gone in 850 or 851. this leaves the decision up to sugar -- and i'm now firmly in the camp that the pad should revert to capacitive mode at boot time. Another case where it might hard to discover which mode one is using at that time is after suspend. You have to scratch as well in order to wake up the machine. but what would you propose? switching to finger mode just before suspending, and back to stylus mode right after resume? paul Regards, Simon PS: style nitpick: I would capitalize the strings 'style' and 'finger' and align them left in the palette. PSS: if others want to test on the XO-1.0 I can make some rpms quickly. =- paul fox, p...@laptop.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] touchpad mode selection
On 08/18/2010 02:30 PM, Paul Fox wrote: simon wrote: On 08/07/2010 08:22 PM, Walter Bender wrote: On Fri, Aug 6, 2010 at 9:10 AM, Paul Foxp...@laptop.org wrote: walter -- currently we try at boot time and set the touchpad to whichever mode the user last requested. moving this initialization to sugar was one of the last changes you made to the sugar code, i think. but when you were in the office you mentioned that it might be preferable to always revert to capacitive (normal) mode at boot time, so that the user doesn't get stuck or confused by pen mode (which is certainly less discoverable' than normal mode). the more i think about it, the more i think that's a good idea. what do other people (who, hopefully have tried both modes) think? paul =- paul fox, p...@laptop.org http://bugs.sugarlabs.org/attachment/ticket/2006/0001-touchpad-with-finger-mode- default.patch defaults to capacitive on boot. It no longer uses the FLAG_FILE and thus that file is no longer needed by your patch either. Its presence will not impact the functionality, as far as I know. I've tested this on 258py. I'd appreciate your doing a quick review just to make sure I didn't miss anything. -walter Hi Walter, first of all thanks for your work! I have been testing the device option on 850 XO-1.0 (it is just a matter of copying the files over from the 0.90 patch that just landed in master). I find it quite hard to use the stylus mode as one really needs to scratch over the touchpad. Especially when one wants to revert the setting after using the stylus mode it is hard to reveal the frame, move to the icon and click it. yes, the stylus mode requires a lot of pressure. There have been discussions about which mode it should have after booting. the system support for enabling stylus mode at boot was removed recently -- i can't remember if it's gone in 850 or 851. this leaves the decision up to sugar -- and i'm now firmly in the camp that the pad should revert to capacitive mode at boot time. Yeah, right this is working fine. Another case where it might hard to discover which mode one is using at that time is after suspend. You have to scratch as well in order to wake up the machine. but what would you propose? switching to finger mode just before suspending, and back to stylus mode right after resume? paul Hmm, good question - so far I wanted to raise the issue ;) Maybe one should see how users react here. I personally find the stylus mode hard to use (especially getting out of it), though users that want to use it or have tough conditions where this is of advantage might find it working well for them. Regards, Simon ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] touchpad mode selection
Hi I was playing with OS373pyg and managed to disable the touchpad. Fortunately I was able to recover by pressing the power button. I was expecting to get a dialogue or something. My thinking is that its too easy to switch modes and that there should be some warning. There is no key press combination that reverts the change. Maybe something like the Windows change display settings, where you have to confirm your selection within a time period, would be a good addition? Tony On 08/07/2010 08:22 PM, Walter Bender wrote: On Fri, Aug 6, 2010 at 9:10 AM, Paul Foxp...@laptop.org wrote: walter -- currently we try at boot time and set the touchpad to whichever mode the user last requested. moving this initialization to sugar was one of the last changes you made to the sugar code, i think. but when you were in the office you mentioned that it might be preferable to always revert to capacitive (normal) mode at boot time, so that the user doesn't get stuck or confused by pen mode (which is certainly less discoverable' than normal mode). the more i think about it, the more i think that's a good idea. what do other people (who, hopefully have tried both modes) think? paul =- paul fox, p...@laptop.org http://bugs.sugarlabs.org/attachment/ticket/2006/0001-touchpad-with-finger-mode-default.patch defaults to capacitive on boot. It no longer uses the FLAG_FILE and thus that file is no longer needed by your patch either. Its presence will not impact the functionality, as far as I know. I've tested this on 258py. I'd appreciate your doing a quick review just to make sure I didn't miss anything. -walter Hi Walter, first of all thanks for your work! I have been testing the device option on 850 XO-1.0 (it is just a matter of copying the files over from the 0.90 patch that just landed in master). I find it quite hard to use the stylus mode as one really needs to scratch over the touchpad. Especially when one wants to revert the setting after using the stylus mode it is hard to reveal the frame, move to the icon and click it. There have been discussions about which mode it should have after booting. Another case where it might hard to discover which mode one is using at that time is after suspend. You have to scratch as well in order to wake up the machine. Regards, Simon PS: style nitpick: I would capitalize the strings 'style' and 'finger' and align them left in the palette. PSS: if others want to test on the XO-1.0 I can make some rpms quickly. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel _ This mail has been virus scanned by Australia On Line see http://www.australiaonline.net.au/mailscanning ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Feature Freeze exception request: spiral extension to Home View feature
I am requesting an exception to Feature Freeze. I just completed what I hope to be the final clean up of the spiral extension to the Home View. The ticket is here: http://bugs.sugarlabs.org/ticket/2143 The patch is here: http://bugs.sugarlabs.org/attachment/ticket/2143/0001-adding-spiral-extension-to-Ring-View.patch The feature request is here: http://wiki.sugarlabs.org/go/Features/Spiral_Home_View The discussion thread with the design team is here: http://lists.sugarlabs.org/archive/sugar-devel/2010-August/025953.html Thank you for your consideration. regards. -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
Re: [Sugar-devel] touchpad mode selection
On Wed, Aug 18, 2010 at 8:47 AM, fors...@ozonline.com.au wrote: Hi I was playing with OS373pyg and managed to disable the touchpad. Fortunately I was able to recover by pressing the power button. I was expecting to get a dialogue or something. My thinking is that its too easy to switch modes and that there should be some warning. There is no key press combination that reverts the change. I think this is a good idea. Anyone have suggestions as to what key we should assign? Maybe something like the Windows change display settings, where you have to confirm your selection within a time period, would be a good addition? While you cursor is over the button, you can just click to revert. But maybe a more verbose string indicating what the button does would be helpful? Tony On 08/07/2010 08:22 PM, Walter Bender wrote: On Fri, Aug 6, 2010 at 9:10 AM, Paul Foxp...@laptop.org wrote: walter -- currently we try at boot time and set the touchpad to whichever mode the user last requested. moving this initialization to sugar was one of the last changes you made to the sugar code, i think. but when you were in the office you mentioned that it might be preferable to always revert to capacitive (normal) mode at boot time, so that the user doesn't get stuck or confused by pen mode (which is certainly less discoverable' than normal mode). The current implementation reverts to capacitive mode by default. the more i think about it, the more i think that's a good idea. what do other people (who, hopefully have tried both modes) think? paul =- paul fox, p...@laptop.org http://bugs.sugarlabs.org/attachment/ticket/2006/0001-touchpad-with-finger-mode-default.patch defaults to capacitive on boot. It no longer uses the FLAG_FILE and thus that file is no longer needed by your patch either. Its presence will not impact the functionality, as far as I know. I've tested this on 258py. I'd appreciate your doing a quick review just to make sure I didn't miss anything. -walter Hi Walter, first of all thanks for your work! I have been testing the device option on 850 XO-1.0 (it is just a matter of copying the files over from the 0.90 patch that just landed in master). I find it quite hard to use the stylus mode as one really needs to scratch over the touchpad. Especially when one wants to revert the setting after using the stylus mode it is hard to reveal the frame, move to the icon and click it. There have been discussions about which mode it should have after booting. Another case where it might hard to discover which mode one is using at that time is after suspend. You have to scratch as well in order to wake up the machine. Regards, Simon PS: style nitpick: I would capitalize the strings 'style' and 'finger' and align them left in the palette. PSS: if others want to test on the XO-1.0 I can make some rpms quickly. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel _ This mail has been virus scanned by Australia On Line see http://www.australiaonline.net.au/mailscanning ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -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
Re: [Sugar-devel] Help testing new sugar packages in F14
On 08/18/2010 11:52 AM, Simon Schampijer wrote: Hi, to get the new Sugar release 0.90 [1] into shape and make it a stable release we want people to test the nightly Soas snapshots [2]. In order to get the new packaged tarballs into those builds they have to meet certain criteria first [3], hence we need people testing them. You can simply do this by getting the rpms from koji and install them into your latest soas snapshot and restart Sugar. What I do in short is: - open the Browse activity and go to http://koji.fedoraproject.org - search for the package (sugar, sugar-toolkit...) - click on the latest F14 version and then right-click on the download option of the 'noarch' rpm and choose 'copy link' from the palette (if you download directly it is stored in the Journal) - then open the terminal activity log in as root and you can copy in the address here using ctrl+shift+v or the edit tab in the toolbar - the command for updating the rpm is: 'rpm -U [name of rpm]' Once you tested the package you can comment on bodhi [4] about your findings and give karma points. If you have not done so yet, you should create a Fedora account [5], so your comments have a higher value. Why not start today? Here are some packages that would need your testing [6] [7]. Btw, there will be a Fedora testing day [8] this Thursday and we want to give a go on Sugar, too. More info to come. If you have questions please feel free to ask. I am as well on irc #sugar most of the day. Regards, Simon [1] http://wiki.sugarlabs.org/go/0.90/Roadmap#Schedule [2] http://alt.fedoraproject.org/pub/alt/nightly-composes/soas/ [3] https://fedoraproject.org/wiki/Package_update_acceptance_criteria [4] https://admin.fedoraproject.org/updates [5] https://admin.fedoraproject.org/accounts/user/new?_csrf_token=88fb044408f6ad820284d0a7f38dc7731efb1808 [6] https://admin.fedoraproject.org/updates/sugar-artwork-0.89.3-1.fc14,sugar-toolkit-0.89.3-1.fc14?_csrf_token=88fb044408f6ad820284d0a7f38dc7731efb1808 [7] https://admin.fedoraproject.org/updates/sugar-toolkit-0.89.2-1.fc14,sugar-presence-service-0.90.0-1.fc14,sugar-0.89.3-1.fc14,sugar-base-0.90.0-1.fc14?_csrf_token=88fb044408f6ad820284d0a7f38dc7731efb1808 [8] https://fedorahosted.org/fedora-qa/ticket/108 Actually, you can use as well the updates testing repository to test new rpms. Completely forgot about that. yum --enablerepo=updates-testing update sugar sugar-toolkit... And Bernie pointed out that fedora-easy-karma [1] can be used for people who do not like to use web interfaces. Gary pointed out that he has issues running the latest snapshot under virtualization (Virtual Box) does not work for him (black screen). If anybody has an idea... Regards, Simon [1] http://fedoraproject.org/wiki/Fedora_Easy_Karma ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [SoaS] Help testing new sugar packages in F14
On 18 Aug 2010, at 16:55, Simon Schampijer wrote: On 08/18/2010 11:52 AM, Simon Schampijer wrote: Hi, to get the new Sugar release 0.90 [1] into shape and make it a stable release we want people to test the nightly Soas snapshots [2]. In order to get the new packaged tarballs into those builds they have to meet certain criteria first [3], hence we need people testing them. You can simply do this by getting the rpms from koji and install them into your latest soas snapshot and restart Sugar. What I do in short is: - open the Browse activity and go to http://koji.fedoraproject.org - search for the package (sugar, sugar-toolkit...) - click on the latest F14 version and then right-click on the download option of the 'noarch' rpm and choose 'copy link' from the palette (if you download directly it is stored in the Journal) - then open the terminal activity log in as root and you can copy in the address here using ctrl+shift+v or the edit tab in the toolbar - the command for updating the rpm is: 'rpm -U [name of rpm]' Once you tested the package you can comment on bodhi [4] about your findings and give karma points. If you have not done so yet, you should create a Fedora account [5], so your comments have a higher value. Why not start today? Here are some packages that would need your testing [6] [7]. Btw, there will be a Fedora testing day [8] this Thursday and we want to give a go on Sugar, too. More info to come. If you have questions please feel free to ask. I am as well on irc #sugar most of the day. Regards, Simon [1] http://wiki.sugarlabs.org/go/0.90/Roadmap#Schedule [2] http://alt.fedoraproject.org/pub/alt/nightly-composes/soas/ [3] https://fedoraproject.org/wiki/Package_update_acceptance_criteria [4] https://admin.fedoraproject.org/updates [5] https://admin.fedoraproject.org/accounts/user/new?_csrf_token=88fb044408f6ad820284d0a7f38dc7731efb1808 [6] https://admin.fedoraproject.org/updates/sugar-artwork-0.89.3-1.fc14,sugar-toolkit-0.89.3-1.fc14?_csrf_token=88fb044408f6ad820284d0a7f38dc7731efb1808 [7] https://admin.fedoraproject.org/updates/sugar-toolkit-0.89.2-1.fc14,sugar-presence-service-0.90.0-1.fc14,sugar-0.89.3-1.fc14,sugar-base-0.90.0-1.fc14?_csrf_token=88fb044408f6ad820284d0a7f38dc7731efb1808 [8] https://fedorahosted.org/fedora-qa/ticket/108 Actually, you can use as well the updates testing repository to test new rpms. Completely forgot about that. yum --enablerepo=updates-testing update sugar sugar-toolkit... And Bernie pointed out that fedora-easy-karma [1] can be used for people who do not like to use web interfaces. Gary pointed out that he has issues running the latest snapshot under virtualization (Virtual Box) does not work for him (black screen). If anybody has an idea... Just to confirm, I just tested again with the latest soas-x86_64-20100817.16.iso image and it is still showing a black screen at the point it should be showing X. It's not a lockup or a failed boot process, looks just to be that something display related in F14 and VirtualBox are not happy with each other yet (been happily using F13 VB VMs for some time). You can send the F14 VM the shutdown signal and it will gracefully shut its self down again. I also tested with various vga boot parameters incase it was resolution related, but all end up at black (800x600, 1024x768, 1600x1200). Regards, --Gary Regards, Simon [1] http://fedoraproject.org/wiki/Fedora_Easy_Karma ___ 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] [Design] Deleting Activity directory when deleting Activity bundle
On Fri, 30 Jul 2010 15:41:29 -0400, Frederick Grose fgr...@gmail.com wrote: This ticket has some important discussion that was proposed for airing on the mailing list. http://bugs.sugarlabs.org/ticket/2074 There are patches under review that would delete learner data, perhaps unwittingly. An Activity bundle is deleted from the Home list view bundle pallet by invoking the 'Erase' menu action. I have submitted a solution for that scenario already, because it was a corner case for 2074. A 'Confirm erase' alert dialog appears that asks if you want to permanently erase the Activity (bundle). It provides a negative 'Keep' and positive 'Erase' button. This is not necessary anymore. Because now it does not delete the installed activity anymore. For the proposed patch, to prevent the unwitting loss of Activity profile data or other content that may be stored in the Activity directory, an option checkbox should be added, such as, (check) erase all associated data, which could default to yes (checked). My last patches include your comments :) Without this, Learners may unexpectedly delete content that they downloaded at some expense, or be forced to reset profile preferences. If there isn't time to implement this data protection feature for the upcoming Dextrose release, we should not forget to provide this feature for all future learners (who may not have the same storage and usability constraints that prompted this patch). --Fred I would appreciate if someone could review my patches. Saludos, tincho ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Enabling logging by default
Hi, I was looking at Sugar on Ubuntu, and we were considering enabling logging (in ~/.sugar/debug) by default. Is there any reason not to do this, when targeting machines that aren't resource constrained like the XO? Would it be sensible to have it enabled as a default upstream in Sugar? Thanks, ╒═╕ │Luke Faraone ╭Debian / Ubuntu Developer╮│ │http://luke.faraone.cc╰Sugar Labs, Systems Admin╯│ │PGP: 5189 2A7D 16D0 49BB 046B DC77 9732 5DD8 F9FD D506 │ ╘═╛ 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] Enabling logging by default
On Wed, Aug 18, 2010 at 21:19, Luke Faraone l...@faraone.cc wrote: Hi, I was looking at Sugar on Ubuntu, and we were considering enabling logging (in ~/.sugar/debug) by default. Is there any reason not to do this, when targeting machines that aren't resource constrained like the XO? Would it be sensible to have it enabled as a default upstream in Sugar? It would be certainly useful for me as a developer. Regards, Tomeu Thanks, ╒═╕ │Luke Faraone ╭Debian / Ubuntu Developer╮│ │http://luke.faraone.cc ╰Sugar Labs, Systems Admin╯│ │PGP: 5189 2A7D 16D0 49BB 046B DC77 9732 5DD8 F9FD D506 │ ╘═╛ ___ 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] Enabling logging by default
El Wed, 18-08-2010 a las 15:19 -0400, Luke Faraone escribió: Hi, I was looking at Sugar on Ubuntu, and we were considering enabling logging (in ~/.sugar/debug) by default. Is there any reason not to do this, when targeting machines that aren't resource constrained like the XO? Would it be sensible to have it enabled as a default upstream in Sugar? Logging *is* enabled by default, not just at the most noisy level. Personally, I rarely change the values in ~/.sugar/debug because I find the extra messages a useless distraction. All errors are being logged anyway. -- // 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] [Design] Deleting Activity directory when deleting Activity bundle
On 30 July 2010 13:41, Frederick Grose fgr...@gmail.com wrote: A 'Confirm erase' alert dialog appears that asks if you want to permanently erase the Activity (bundle). It provides a negative 'Keep' and positive 'Erase' button. For the proposed patch, to prevent the unwitting loss of Activity profile data or other content that may be stored in the Activity directory, an option checkbox should be added, such as, (check) erase all associated data, which could default to yes (checked). I disagree with the addition of a checkbox - in my experience, this kind of complexity will result in a random response from the user. I agree with the idea of deleting profile data when an activity is uninstalled. (if they want the profile data, why uninstall the activity?) Daniel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] touchpad mode selection
While you cursor is over the button, you can just click to revert. Thanks I missed that, did the cursor jump or was I being stupid? Either way it shows that the unsuspecting user can get confused Tony ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] touchpad mode selection
On Wed, Aug 18, 2010 at 5:06 PM, fors...@ozonline.com.au wrote: While you cursor is over the button, you can just click to revert. Thanks I missed that, did the cursor jump or was I being stupid? Either way it shows that the unsuspecting user can get confused The cursor should move. But I agree, it is confusing to the unsuspecting user. -walter Tony -- 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] [Design] Deleting Activity directory when deleting Activity bundle
On Wed, Aug 18, 2010 at 4:52 PM, Daniel Drake d...@laptop.org wrote: On 30 July 2010 13:41, Frederick Grose fgr...@gmail.com wrote: A 'Confirm erase' alert dialog appears that asks if you want to permanently erase the Activity (bundle). It provides a negative 'Keep' and positive 'Erase' button. For the proposed patch, to prevent the unwitting loss of Activity profile data or other content that may be stored in the Activity directory, an option checkbox should be added, such as, (check) erase all associated data, which could default to yes (checked). I disagree with the addition of a checkbox - in my experience, this kind of complexity will result in a random response from the user. +1 I agree with the idea of deleting profile data when an activity is uninstalled. (if they want the profile data, why uninstall the activity?) +1 (I presume the concern was over whether or not an update would remove the profile data.) Daniel ___ 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] [Design] Deleting Activity directory when deleting Activity bundle
Walter Bender wrote: On Wed, Aug 18, 2010 at 4:52 PM, Daniel Drake d...@laptop.org wrote: On 30 July 2010 13:41, Frederick Grose fgr...@gmail.com wrote: A 'Confirm erase' alert dialog appears that asks if you want to permanently erase the Activity (bundle). It provides a negative 'Keep' and positive 'Erase' button. For the proposed patch, to prevent the unwitting loss of Activity profile data or other content that may be stored in the Activity directory, an option checkbox should be added, such as, (check) erase all associated data, which could default to yes (checked). I disagree with the addition of a checkbox - in my experience, this kind of complexity will result in a random response from the user. +1 I agree with the idea of deleting profile data when an activity is uninstalled. (if they want the profile data, why uninstall the activity?) +1 (I presume the concern was over whether or not an update would remove the profile data.) A related problem for Soas is that an .xo stores it's activities in a different location (/home/liveuser/Activities) than those installed with the .iso (/user/share/sugar/activities My experience is that one had to use rmdir -R /user/share/sugar/activities/().Activity to make a similar version of an .xo activity start. Would the Confirm erase checkbox check and delete both locations? Tom Gilliard satellit Daniel ___ 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
[Sugar-devel] journal sort options
with os373pyg if i sort the journal by creation date, all entries (except tamyblock.py) show a creation date 41 years 8 months ago. Is this right? If so its not very useful. tony ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] journal sort options
On Thu, Aug 19, 2010 at 09:53:11AM +1000, fors...@ozonline.com.au wrote: with os373pyg if i sort the journal by creation date, all entries (except tamyblock.py) show a creation date 41 years 8 months ago. Is this right? If so its not very useful. Forty one years? Two years would be fine. Check the time on your computer to see if it is set to the current year? -- 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] journal sort options
Forty one years? Two years would be fine. Check the time on your computer to see if it is set to the current year? How do I set the time please? I have been meaning to ask that for ages! It would be good if this was in my settings / control panel so the user can check their time and date. I have only found the timezone. Thanks Tabitha ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] journal sort options
On Wednesday, August 18, 2010 09:38:28 pm James Cameron wrote: On Thu, Aug 19, 2010 at 09:53:11AM +1000, fors...@ozonline.com.au wrote: with os373pyg if i sort the journal by creation date, all entries (except tamyblock.py) show a creation date 41 years 8 months ago. Is this right? If so its not very useful. Forty one years? Two years would be fine. Check the time on your computer to see if it is set to the current year? That's a zero in a ctime property (it counts since the Unix epoch). Do new entries display correct ctimes? It may be that a reindex didn't trigger on upgrade. -- James Cameron http://quozl.linux.org.au/ -- -Andrés signature.asc Description: This is a digitally signed message part. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Enabling logging by default
On 18 Aug 2010, at 20:36, Bernie Innocenti wrote: El Wed, 18-08-2010 a las 15:19 -0400, Luke Faraone escribió: Hi, I was looking at Sugar on Ubuntu, and we were considering enabling logging (in ~/.sugar/debug) by default. Is there any reason not to do this, when targeting machines that aren't resource constrained like the XO? Would it be sensible to have it enabled as a default upstream in Sugar? Logging *is* enabled by default, not just at the most noisy level. Personally, I rarely change the values in ~/.sugar/debug because I find the extra messages a useless distraction. All errors are being logged anyway. FWIW +1, I now very rarely change the values. In the few occasions I have enabled them to hunt something specific down I've been swamped, and given up, though I admit in these cases it's often been collaboration bugs I've been trying to look for, unfortunately with little success. As far as resolving bugs, it's 95% about reproducibility, if you can't reliably trigger an issue a few times in a row of testing, it is very unlikely you can report it in a way that will lead to a fix (though a smattering of clustered reports can at least lead to some attention on a general area). --Gary -- // 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 ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] setting date and time (was: re: journal sort options)
On Thu, Aug 19, 2010 at 12:42:47PM +1200, Tabitha Roder wrote: How do I set the time please? I have been meaning to ask that for ages! It would be good if this was in my settings / control panel so the user can check their time and date. The short answer; switch to GNOME and set it there. Sugar does not provide a way to set the date and time, as far as I can see. Other desktop systems provide that. GNOME provides a right-click option on the clock (top right of screen) called Adjust Date Time and this seems to work fine. Laptops in deployments with a school server set the date and time periodically, I've heard. I've not tested this. You can use the Terminal activity to gain access the underlying operating system and set the time there. There are several tools available. How easily this is done depends on what other packages may be installed on the operating system. As I don't know which operating system build you are asking about, I'll assume the OLPC builds. 1. one tool is rdate, which is on the OLPC builds, but that requires a server nearby that runs the time service on port 37. The command is rdate -s SERVER, where SERVER is the IP address or host name of the server. 2. another tool is ntpdate, but it is not on the OLPC builds that I test. I install it on units that I want to remain better synchronised. The command is ntpdate pool.ntp.org, although there are people who would like you to consider carefully whether you deploy this over thousands or millions of laptops. There would be a more appropriate name than pool.ntp.org, so that the distributed load can be identified. 3. yet another tool is the Linux date command, but the format of the input is archaic. I do not recommend it. Once you set the time on the operating system kernel, the next controlled shutdown should store it into the Real Time Clock (RTC) of an XO or normal computer. You can encourage this to happen earlier using a command hwclock --systohc. On XO hardware, with security disabled, you can set the time using OpenFirmware: http://wiki.laptop.org/go/Fix_Clock#If_the_screen_turns_on_but_you_cannot_enter_Linux -- 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] Enabling logging by default
El Wed, 18-08-2010 a las 15:38 -0400, Luke Faraone escribió: On 08/18/2010 03:36 PM, Bernie Innocenti wrote: El Wed, 18-08-2010 a las 15:19 -0400, Luke Faraone escribió: Hi, I was looking at Sugar on Ubuntu, and we were considering enabling logging (in ~/.sugar/debug) by default. Is there any reason not to do this, when targeting machines that aren't resource constrained like the XO? Would it be sensible to have it enabled as a default upstream in Sugar? Logging *is* enabled by default, not just at the most noisy level. Personally, I rarely change the values in ~/.sugar/debug because I find the extra messages a useless distraction. All errors are being logged anyway. Can't the more verbose logging be filtered out if necessary? It's easier than another round trip to try and get more verbose logs. Most existing software defaults not to log anything below warnings because the extra noise in the logs is very annoying and can cause a lot of overhead. In Sugar, you get dozens of log lines just by hovering the cursor over icons. This stuff almost never helps finding an actual bug and would have to be filtered 99% of the time by pre-pending a regular expression to the usual tail -f. -- // 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] journal sort options
That's a zero in a ctime property (it counts since the Unix epoch). Do new entries display correct ctimes? It may be that a reindex didn't trigger on upgrade. depends on what you call a new entry, saved activities are all 41 years, but saved photos, clipboard items and tamyblock.py(saved by turtleblocks at install time) display correctly ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] journal sort options
On Wednesday, August 18, 2010 10:27:47 pm fors...@ozonline.com.au wrote: That's a zero in a ctime property (it counts since the Unix epoch). Do new entries display correct ctimes? It may be that a reindex didn't trigger on upgrade. depends on what you call a new entry, saved activities are all 41 years, but saved photos, clipboard items and tamyblock.py(saved by turtleblocks at install time) display correctly By new entries I mean journal entries that were created after you upgraded to a build with the journal sorting feature. -- -Andrés signature.asc Description: This is a digitally signed message part. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [Design] Deleting Activity directory when deleting Activity bundle
On 19 Aug 2010, at 00:38, Thomas Gilliard wrote: Walter Bender wrote: On Wed, Aug 18, 2010 at 4:52 PM, Daniel Drake d...@laptop.org wrote: On 30 July 2010 13:41, Frederick Grose fgr...@gmail.com wrote: A 'Confirm erase' alert dialog appears that asks if you want to permanently erase the Activity (bundle). It provides a negative 'Keep' and positive 'Erase' button. For the proposed patch, to prevent the unwitting loss of Activity profile data or other content that may be stored in the Activity directory, an option checkbox should be added, such as, (check) erase all associated data, which could default to yes (checked). I disagree with the addition of a checkbox - in my experience, this kind of complexity will result in a random response from the user. +1 +1 I agree with the idea of deleting profile data when an activity is uninstalled. (if they want the profile data, why uninstall the activity?) +1 +1 Deleting such data may actually be what is required in the case of something that has saved broken 'profile' data. Erase and re-install is a common user meme (often sabotaged by broken/unexpected preference files living in unknown places). If an activity is storing user activity information in it's data directory (e.g. more than just preference information or data for caching purposes that can be regenerated), I'd assume it to be a design flaw and worthy of a bug ticket in trac. That user state belongs in the Journal. (I presume the concern was over whether or not an update would remove the profile data.) A related problem for Soas is that an .xo stores it's activities in a different location (/home/liveuser/Activities) than those installed with the .iso (/user/share/sugar/activities My experience is that one had to use rmdir -R /user/share/sugar/activities/().Activity to make a similar version of an .xo activity start. Would the Confirm erase checkbox check and delete both locations? If an activity is unbundled in /user/share/sugar/activities/ the list view does not give the user an Erase option. If an activity is in ~/Activities but has permissions that prevent the user from deleting, the Erase option is shown but disabled/dimmed out. --Gary Tom Gilliard satellit Daniel ___ 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 ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] setting date and time (was: re: journal sort options)
El Thu, 19-08-2010 a las 11:23 +1000, James Cameron escribió: Laptops in deployments with a school server set the date and time periodically, I've heard. I've not tested this. The method used to set the clock from the oats server is (deliberately) very imprecise. See the thread Clocks on the XOs for more details. -- // 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] journal sort options
By new entries I mean journal entries that were created after you upgraded to a build with the journal sorting feature. if i save a write document etc its 41 years old the exceptions are clipboard items, photos and tamyblock.py ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] journal sort options
Known for six months? http://bugs.sugarlabs.org/ticket/1729 -- 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] journal sort options
Hi Tony, On 19 Aug 2010, at 02:52, fors...@ozonline.com.au wrote: By new entries I mean journal entries that were created after you upgraded to a build with the journal sorting feature. if i save a write document etc its 41 years old the exceptions are clipboard items, photos and tamyblock.py Sorry to be slow getting to this thread, but it's a known issue (now I hope). I mailed the dextrose mail list about it back on 30th July (they picked up the same patch as the py builds). Seems like there are some missing (or needed) data store patches from the builds to correctly support the creation time UI. Chatting on irc #sugar about it today regarding 0.90 inclusion of the same patch, so hopefully folks involved are all now clear on this issue. Here's the original ticket (started as a feature request/patch for sorting by size): http://bugs.sugarlabs.org/ticket/1915 Allegedly, there is also a 'ctime' related ticket with the extra DS patches, but I couldn't find it. Regards, --Gary ___ 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] journal sort options
Hi James, On 19 Aug 2010, at 03:14, James Cameron wrote: Known for six months? http://bugs.sugarlabs.org/ticket/1729 No this is/was a different issue. I'm pretty sure this was related to Journal entry corruption after hard crashes, leaving partial DS entries. I believe some work may have already landed to make sure activity session data is flushed to storage sooner, reducing the chance of partial/corrupt/missing entries after hard crashes. Regards, --Gary -- 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 mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
