Re: [Sugar-devel] [Announcing] unstable 0.103.2 release and API, UI and String freeze.
Ah, I see now Quozl! I thought your solution was totally different. Please check out this patch: https://github.com/sugarlabs/sugar/pull/476 On Tue Jan 20 2015 at 9:10:59 am James Cameron qu...@laptop.org wrote: On Mon, Jan 19, 2015 at 09:19:23AM +, Sam P. wrote: Hi James, On Sat Jan 17 2015 at 2:51:29 pm James Cameron [1]qu...@laptop.org wrote: [...] Tested on Fedora 20 on XO-4. The autocomplete of activity name in search entry (2ac6c3c) does work, though it can be disconcerting. Perhaps it should mark the completion as selected text, so that further typing will erase it. Be a slow typer and type C l o c k and you get Clockock. Hum, how slow is a slow typer? I need to be typing at about 2 chars per second, but what is it like on the XO4? Children with developmental disabilities or in the early stage of keyboard learning will type slowly enough to trigger this problem. It can be easily reproduced on an XO-4 by typing one key every two seconds. I'm happy for this to be the test case descriptor. I don't think that selecting the text is the right approach. If I am a slow typer, I would appreciate the computer autocompleting me :) I disagree. I think selecting the completion is the right approach. It is how Firefox handles the issue. That way, when the user does not observe the completion, any further typing will immediately erase the completion. Perhaps you haven't understood what I mean. Imagine this: - empty field, - press 'c', the 'c' appears, - after one second delay, autocomplete is ambiguous (clock, chat, record, physics, stopwatch, calculate), so nothing further happens, - press 'l', the 'l' appears, - after one second delay, autocomplete is unambiguous, so 'ock' is added to the text, and 'ock' is to be highlighted as selected text, - press 'o', the selected 'ock' is erased, and the 'o' appears, - after one second delay, autocomplete is unambiguous, so 'ck' is added to the text, and 'ck' is highlighted as selected text, At the moment, without a fix, 'Clocko' is in the field. -- 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] [Announcing] unstable 0.103.2 release and API, UI and String freeze.
Hi It depends on whether you are a touch typist. The touch typist will be looking at the screen and will see the autocomplete. The non touch typist willl be looking at the keyboard and will not notice it. Tony I don't think that selecting the text is the right approach. If I am a slow typer, I would appreciate the computer autocompleting me :) ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [Announcing] unstable 0.103.2 release and API, UI and String freeze.
On Tue, Jan 20, 2015 at 10:14:02AM +, Sam P. wrote: Ah, I see now Quozl! I thought your solution was totally different. Please check out this patch: https://github.com/sugarlabs/sugar/pull/476 Thanks, fixes my test case. Another one; want to activate Implode, but make a mistake and type 'imple' instead of 'implo', completion is 'Simple English Wikipedia', with 'e English Wikipedia' selected, and the 'S' off-screen. But imagine not looking at display, type backspace and 'o', result in field is 'Simplo', no such activity. (I really noticed this one, because this is the name of the battery manufacturer of XO-4 samples I'm testing.) Can the selection be non-contiguous and cover the 'S' as well? -- 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] [Announcing] unstable 0.103.2 release and API, UI and String freeze.
On Mon, Jan 19, 2015 at 09:19:23AM +, Sam P. wrote: Hi James, On Sat Jan 17 2015 at 2:51:29 pm James Cameron [1]qu...@laptop.org wrote: [...] Tested on Fedora 20 on XO-4. The autocomplete of activity name in search entry (2ac6c3c) does work, though it can be disconcerting. Perhaps it should mark the completion as selected text, so that further typing will erase it. Be a slow typer and type C l o c k and you get Clockock. Hum, how slow is a slow typer? I need to be typing at about 2 chars per second, but what is it like on the XO4? Children with developmental disabilities or in the early stage of keyboard learning will type slowly enough to trigger this problem. It can be easily reproduced on an XO-4 by typing one key every two seconds. I'm happy for this to be the test case descriptor. I don't think that selecting the text is the right approach. If I am a slow typer, I would appreciate the computer autocompleting me :) I disagree. I think selecting the completion is the right approach. It is how Firefox handles the issue. That way, when the user does not observe the completion, any further typing will immediately erase the completion. Perhaps you haven't understood what I mean. Imagine this: - empty field, - press 'c', the 'c' appears, - after one second delay, autocomplete is ambiguous (clock, chat, record, physics, stopwatch, calculate), so nothing further happens, - press 'l', the 'l' appears, - after one second delay, autocomplete is unambiguous, so 'ock' is added to the text, and 'ock' is to be highlighted as selected text, - press 'o', the selected 'ock' is erased, and the 'o' appears, - after one second delay, autocomplete is unambiguous, so 'ck' is added to the text, and 'ck' is highlighted as selected text, At the moment, without a fix, 'Clocko' is in the field. -- 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] [Announcing] unstable 0.103.2 release and API, UI and String freeze.
Hi James, On Sat Jan 17 2015 at 2:51:29 pm James Cameron qu...@laptop.org wrote: [...] Tested on Fedora 20 on XO-4. The autocomplete of activity name in search entry (2ac6c3c) does work, though it can be disconcerting. Perhaps it should mark the completion as selected text, so that further typing will erase it. Be a slow typer and type C l o c k and you get Clockock. Hum, how slow is a slow typer? I need to be typing at about 2 chars per second, but what is it like on the XO4? I don't think that selecting the text is the right approach. If I am a slow typer, I would appreciate the computer autocompleting me :) Busy cursor during activity launch doesn't appear to work. There was no attempt to flush the display. No idea if there was a ticket for this, it isn't mentioned in the commit: https://github.com/sugarlabs/sugar/commit/6c8141ba9994d8ec1f5e29d5ec7e39 34091636ee Can be fixed by using the technique in the following commit: https://github.com/sugarlabs/sugar/commit/726aaeeff70848b7f31c7ae6e4392a 4d49f2d7d1 I'm not touching it for a few days in case GCI team want to take it on. Good catch! I have made a patch https://github.com/sugarlabs/sugar/pull/475 Thanks, Sam ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [Announcing] unstable 0.103.2 release and API, UI and String freeze.
On January 16, 2015 at 9:51 PM Peter Robinson pbrobin...@gmail.com wrote: To help with testing it would be nice if RPMS based on these versions could be made available via Fedora's updates-testing repo (or maybe koji) for F20-F21. We've never pushed new major releases of any sort to a stable Fedora release as there's too much QA and testing required and no one ever commits to doing it. Sorry, but I don't believe updates-testing can be considered stable, that is for, you know... testing. I'm not suggesting pushing to updates where the packages could be updated without user intervention. One must specifically enable the updates-testing repo to receive the new rpms. Guess the ball is in sugarlabs' court then. Sorry, but that just shows you don't understand how updates-testing works. Packages that go there are designed to end up in stable and it's a short term area to stage the updates to be tested by default max 7 days. Sorry I was under the impression that 'the karma feedback' would need to have a high enough rating before the update would pass to the updates repo. On the plus side I've pushed this to rawhide and people can download a nightly live image from tomorrow and spin it up on either a USB stick or their favourite virtual platform and have a self contained test environment and get it all with little effort. I'd rather not download a half gig iso file for testing 5MBs worth of sugar code. Pity sugar 0.104 will miss rawhide's branching cutoff for F22 by 3 days[1][2]. From what I read above there is no hope for 0.104 to be part of F22 then. Errr. no, you're again wrong. According to the F-22 schedule [1] the final free is 5th May, the features have to be feature complete by Alpha and given the above release is the feature complete release we're already there. Sugar 0.104 is due to be stable by Feb 13th which means we'll have it there before the beta freeze. Good to know, thanks Jerry ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] [Announcing] unstable 0.103.2 release and API, UI and String freeze.
Hello everyone, These are the tarballs for the _last_ 0.103.x UNSTABLE release, and with this release we reach the API, UI and String freeze [1]. - http://download.sugarlabs.org/sources/sucrose/glucose/sugar/sugar-0.103.2.tar.xz - http://download.sugarlabs.org/sources/sucrose/glucose/sugar-toolkit-gtk3/sugar-toolkit-gtk3-0.103.2.tar.xz - http://download.sugarlabs.org/sources/sucrose/glucose/sugar-artwork/sugar-artwork-0.103.2.tar.xz - http://download.sugarlabs.org/sources/sucrose/glucose/sugar-datastore/sugar-datastore-0.103.2.tar.xz - http://download.sugarlabs.org/sources/sucrose/glucose/sugar-runner/sugar-runner-0.103.2.tar.xz It's time to switch focus on updating translations, everyone can contribute through or new Pootle instance [2]! We have time until February 13, before the 0.104.0 STABLE release. We welcome all the help you can provide! Regards, Martin. Refs: 1. http://wiki.sugarlabs.org/go/0.104/Roadmap 2. http://translate.sugarlabs.org/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [Announcing] unstable 0.103.2 release and API, UI and String freeze.
Hi All: On January 16, 2015 at 6:17 AM Martin Abente martin.abente.lah...@gmail.com wrote: Hello everyone, These are the tarballs for the _last_ 0.103.x UNSTABLE release, and with this release we reach the API, UI and String freeze [1]. - http://download.sugarlabs.org/sources/sucrose/glucose/sugar/sugar-0.103.2.tar.xz - http://download.sugarlabs.org/sources/sucrose/glucose/sugar-toolkit-gtk3/sugar-toolkit-gtk3-0.103.2.tar.xz - http://download.sugarlabs.org/sources/sucrose/glucose/sugar-artwork/sugar-artwork-0.103.2.tar.xz - http://download.sugarlabs.org/sources/sucrose/glucose/sugar-datastore/sugar-datastore-0.103.2.tar.xz - http://download.sugarlabs.org/sources/sucrose/glucose/sugar-runner/sugar-runner-0.103.2.tar.xz To help with testing it would be nice if RPMS based on these versions could be made available via Fedora's updates-testing repo (or maybe koji) for F20-F21. Jerry It's time to switch focus on updating translations, everyone can contribute through or new Pootle instance [2]! We have time until February 13, before the 0.104.0 STABLE release. We welcome all the help you can provide! Regards, Martin. Refs: 1. http://wiki.sugarlabs.org/go/0.104/Roadmap 2. http://translate.sugarlabs.org/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [Announcing] unstable 0.103.2 release and API, UI and String freeze.
On Fri, Jan 16, 2015 at 12:09:50PM -0600, Jerry Vonau wrote: To help with testing it would be nice if RPMS based on these versions could be made available via Fedora's updates-testing repo (or maybe koji) for F20-F21. Or if not Fedora, perhaps on people.sugarlabs.org ... and if someone does this, please explain the steps. -- 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] [Announcing] unstable 0.103.2 release and API, UI and String freeze.
On January 16, 2015 at 6:17 AM Martin Abente martin.abente.lah...@gmail.com wrote: Hello everyone, These are the tarballs for the _last_ 0.103.x UNSTABLE release, and with this release we reach the API, UI and String freeze [1]. - http://download.sugarlabs.org/sources/sucrose/glucose/sugar/sugar-0.103.2.tar.xz - http://download.sugarlabs.org/sources/sucrose/glucose/sugar-toolkit-gtk3/sugar-toolkit-gtk3-0.103.2.tar.xz - http://download.sugarlabs.org/sources/sucrose/glucose/sugar-artwork/sugar-artwork-0.103.2.tar.xz - http://download.sugarlabs.org/sources/sucrose/glucose/sugar-datastore/sugar-datastore-0.103.2.tar.xz - http://download.sugarlabs.org/sources/sucrose/glucose/sugar-runner/sugar-runner-0.103.2.tar.xz To help with testing it would be nice if RPMS based on these versions could be made available via Fedora's updates-testing repo (or maybe koji) for F20-F21. We've never pushed new major releases of any sort to a stable Fedora release as there's too much QA and testing required and no one ever commits to doing it. On the plus side I've pushed this to rawhide and people can download a nightly live image from tomorrow and spin it up on either a USB stick or their favourite virtual platform and have a self contained test environment and get it all with little effort. Peter ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [Announcing] unstable 0.103.2 release and API, UI and String freeze.
On 01/16/2015 04:25 PM, Peter Robinson wrote: On January 16, 2015 at 6:17 AM Martin Abente martin.abente.lah...@gmail.com wrote: Hello everyone, These are the tarballs for the _last_ 0.103.x UNSTABLE release, and with this release we reach the API, UI and String freeze [1]. - http://download.sugarlabs.org/sources/sucrose/glucose/sugar/sugar-0.103.2.tar.xz - http://download.sugarlabs.org/sources/sucrose/glucose/sugar-toolkit-gtk3/sugar-toolkit-gtk3-0.103.2.tar.xz - http://download.sugarlabs.org/sources/sucrose/glucose/sugar-artwork/sugar-artwork-0.103.2.tar.xz - http://download.sugarlabs.org/sources/sucrose/glucose/sugar-datastore/sugar-datastore-0.103.2.tar.xz - http://download.sugarlabs.org/sources/sucrose/glucose/sugar-runner/sugar-runner-0.103.2.tar.xz To help with testing it would be nice if RPMS based on these versions could be made available via Fedora's updates-testing repo (or maybe koji) for F20-F21. We've never pushed new major releases of any sort to a stable Fedora release as there's too much QA and testing required and no one ever commits to doing it. On the plus side I've pushed this to rawhide and people can download a nightly live image from tomorrow and spin it up on either a USB stick or their favourite virtual platform and have a self contained test environment and get it all with little effort. Peter ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel I hope koji builds a working SoaS .iso It has been failing lately for all rawhide live builds Tom Gilliard ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [Announcing] unstable 0.103.2 release and API, UI and String freeze.
On January 16, 2015 at 6:25 PM Peter Robinson pbrobin...@gmail.com wrote: On January 16, 2015 at 6:17 AM Martin Abente martin.abente.lah...@gmail.com wrote: Hello everyone, These are the tarballs for the _last_ 0.103.x UNSTABLE release, and with this release we reach the API, UI and String freeze [1]. - http://download.sugarlabs.org/sources/sucrose/glucose/sugar/sugar-0.103.2.tar.xz - http://download.sugarlabs.org/sources/sucrose/glucose/sugar-toolkit-gtk3/sugar-toolkit-gtk3-0.103.2.tar.xz - http://download.sugarlabs.org/sources/sucrose/glucose/sugar-artwork/sugar-artwork-0.103.2.tar.xz - http://download.sugarlabs.org/sources/sucrose/glucose/sugar-datastore/sugar-datastore-0.103.2.tar.xz - http://download.sugarlabs.org/sources/sucrose/glucose/sugar-runner/sugar-runner-0.103.2.tar.xz To help with testing it would be nice if RPMS based on these versions could be made available via Fedora's updates-testing repo (or maybe koji) for F20-F21. We've never pushed new major releases of any sort to a stable Fedora release as there's too much QA and testing required and no one ever commits to doing it. Sorry, but I don't believe updates-testing can be considered stable, that is for, you know... testing. I'm not suggesting pushing to updates where the packages could be updated without user intervention. One must specifically enable the updates-testing repo to receive the new rpms. Guess the ball is in sugarlabs' court then. On the plus side I've pushed this to rawhide and people can download a nightly live image from tomorrow and spin it up on either a USB stick or their favourite virtual platform and have a self contained test environment and get it all with little effort. I'd rather not download a half gig iso file for testing 5MBs worth of sugar code. Pity sugar 0.104 will miss rawhide's branching cutoff for F22 by 3 days[1][2]. From what I read above there is no hope for 0.104 to be part of F22 then. Jerry 1. http://wiki.sugarlabs.org/go/0.104/Roadmap 2. http://fedoraproject.org/wiki/Releases/22/Schedule ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [Announcing] unstable 0.103.2 release and API, UI and String freeze.
To help with testing it would be nice if RPMS based on these versions could be made available via Fedora's updates-testing repo (or maybe koji) for F20-F21. We've never pushed new major releases of any sort to a stable Fedora release as there's too much QA and testing required and no one ever commits to doing it. Sorry, but I don't believe updates-testing can be considered stable, that is for, you know... testing. I'm not suggesting pushing to updates where the packages could be updated without user intervention. One must specifically enable the updates-testing repo to receive the new rpms. Guess the ball is in sugarlabs' court then. Sorry, but that just shows you don't understand how updates-testing works. Packages that go there are designed to end up in stable and it's a short term area to stage the updates to be tested by default max 7 days. On the plus side I've pushed this to rawhide and people can download a nightly live image from tomorrow and spin it up on either a USB stick or their favourite virtual platform and have a self contained test environment and get it all with little effort. I'd rather not download a half gig iso file for testing 5MBs worth of sugar code. Pity sugar 0.104 will miss rawhide's branching cutoff for F22 by 3 days[1][2]. From what I read above there is no hope for 0.104 to be part of F22 then. Errr. no, you're again wrong. According to the F-22 schedule [1] the final free is 5th May, the features have to be feature complete by Alpha and given the above release is the feature complete release we're already there. Sugar 0.104 is due to be stable by Feb 13th which means we'll have it there before the beta freeze. Please actually get your facts right about the process before spreading FUD. Peter [1] https://fedoraproject.org/wiki/Releases/22/Schedule ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [Announcing] unstable 0.103.2 release and API, UI and String freeze.
On Fri, Jan 16, 2015 at 09:17:30AM -0300, Martin Abente wrote: These are the tarballs for the _last_ 0.103.x UNSTABLE release, and with this release we reach the API, UI and String freeze [1]. [...] Please add a brief change log to your release announcements. The git commit logs are split across multiple repositories, are too detailed, and have merge commits. We welcome all the help you can provide! I've built RPMs for Fedora 20, using Peter's src.rpm for Fedora 22. http://rpmdropbox.laptop.org/f20/?C=M;O=D I've no idea how he did what he did, but the src.rpm works for me on Fedora 20. ;-) The ARM RPMs were built in a Fedora 20 mock (mock --rebuild), the i686 RPMs were built outside a mock (rpmbuild --rebuild). Tested on Fedora 20 on XO-4. The autocomplete of activity name in search entry (2ac6c3c) does work, though it can be disconcerting. Perhaps it should mark the completion as selected text, so that further typing will erase it. Be a slow typer and type C l o c k and you get Clockock. Busy cursor during activity launch doesn't appear to work. There was no attempt to flush the display. No idea if there was a ticket for this, it isn't mentioned in the commit: https://github.com/sugarlabs/sugar/commit/6c8141ba9994d8ec1f5e29d5ec7e3934091636ee Can be fixed by using the technique in the following commit: https://github.com/sugarlabs/sugar/commit/726aaeeff70848b7f31c7ae6e4392a4d49f2d7d1 I'm not touching it for a few days in case GCI team want to take it on. -- James Cameron http://quozl.linux.org.au/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
