Re: [Sugar-devel] Please tag tarball releases in git repository, e.g. Sugar 0.87.2
On 01/12/2010 05:51 PM, Tomeu Vizoso wrote: Ping! Thanks for pinging me again, and thanks for the patch. Has been pushed. Regards, Simon ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [DESIGN] 'Resume' vs 'Start a new' Activity
On 11 Jan 2010, at 20:44, Walter Bender wrote: On Mon, Jan 11, 2010 at 3:32 PM, Simon Schampijer si...@schampijer.de wrote: On 01/11/2010 06:12 PM, Wade Brainerd wrote: My feeling regarding all this is that the problem is deeper than finding a way to Resume Latest or Start New from the home screen. IMO, the whole idea of Resume Latest is broken and needs to be ditched. The Journal is the place to resume activities. We need to make the Journal more discoverable and usable instead of trying to mash its features into the home screen. My findings are as well that the Journal is the natural place to resume an activity. The home view is the natural way to create a new activity, since it contains a graphical representation with the available activities. I think resuming is a secondary option we can provide, but should not be the default option when you click on the icon. To overcome the issue of constantly creating new activities I liked the 'open the full palette on left click' option. The learner is then provided with options to choose from. I like this too. It is worth mentioning that on non-OLPC-XO hardware, there is no easily discovered (or typed) dedicated key or mouse movement to get you to the Journal--one of the reasons we have also discussed having the Journal icon always available in the Home View (I am in favor of always at the bottom of the circle). All of these changes collectively may help. I've been trying to stay out of this discussion so far, watching for what might stick. So summing up so far: - Always show Journal in the home ring, though I'd favour having it as the first item, so that would make it always at the top of the circle ;-) - Home view reverted back to the 'start new' activity focus, all icons are un-coloured. - Single left click always reveals the palette with the 'start new' item at the top and 'resume' items below. Some minus design points here as 'start new' and 'resume' will both become 2 clicks away, and take extra palette cursoring dexterity to reach. You could argue both 'start new' and 'resume' will drop to second level features with 'activity palette information' becoming the top level home feature. Being able to read (some of) this palette text would also now be required, so our 'low floor' just got a little higher :-( I do agree though that this provides a compromise between reducing Journal spam and preventing the unintentional overwrite of existing Journal work by making the choice explicit. Regards, --Gary ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [IAEP] Why #sugar should be logged - a plug for transparency and ease of use.
I'm really not interested in beating a dead horse, Sacha, so after making my case I'm more than happy to drop this (though I will continue not to use #sugar for any discussions I would want to save if it is not logged). The reason that I find auto logging saves me work is the same reason I'm now completely in love with Google docs. Call it attention deficit disorder or whatever, but I have 4 different computers on which I normally work, plus I work on other people's computers when I travel. Having stuff in the cloud is simply easier for me. I don't have to think about it. It is just there when I need it. I won't have the logs around like you do. I will forget to store them, forget what I called them when I do store them, or have deleted them in an attempt to reduce the amount of data I'm storing locally, etc. Auto logging in no way prevents you from keeping your own, but it doesn't require me to. jeff On Wed, Jan 13, 2010 at 4:44 AM, Sascha Silbe sascha-ml-ui-sugar-i...@silbe.org wrote: On Tue, Jan 12, 2010 at 09:25:22PM -0500, Jeff Elkner wrote: I'm glad logging locally works for you, Dave, but it doesn't work for me. I really need less things to do, not more ;-) How is logging locally causing more work for you? Do you use an IRC client that cannot be told to always log specific/all channels? Or is searching in your usual computing environment more inconvenient than on some web page? For me local logs are much easier to use/search, so I'm trying to figure out why it's the other way round for you. CU Sascha ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] [RELEASE] sugar-base-0.87.2
== Source == http://download.sugarlabs.org/sources/sucrose/glucose/sugar-base/sugar-base-0.87.2.tar.bz2 ==News== sugar.logger.trace(): lots of debug output (silbe) ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] SoaS with Sugar 0.87.2 coming to a system near you
On 01/11/2010 05:26 PM, Jim Simmons wrote: Simon, Get IA Books does allow you to change the format of the book from the default of DjVu. That drop down is disabled until you actually have a book selected for downloading. Once you have selected a book from the list it should enable itself and you can change the download format before clicking the download button. I may change this in the future but for now you should be able to download some PDFs and continue testing. James Simmons Ahhh, ok - thanks for the explanation. I thought it was a filter for the search. Thanks, Simon ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [DESIGN] 'Resume' vs 'Start a new' Activity
Hi Gary,
thanks very much for your feedback.
On 01/13/2010 02:15 PM, Gary C Martin wrote:
On 11 Jan 2010, at 20:44, Walter Bender wrote:
On Mon, Jan 11, 2010 at 3:32 PM, Simon Schampijersi...@schampijer.de wrote:
On 01/11/2010 06:12 PM, Wade Brainerd wrote:
My feeling regarding all this is that the problem is deeper than
finding a way to Resume Latest or Start New from the home screen.
IMO, the whole idea of Resume Latest is broken and needs to be
ditched. The Journal is the place to resume activities. We need to
make the Journal more discoverable and usable instead of trying to
mash its features into the home screen.
My findings are as well that the Journal is the natural place to resume
an activity. The home view is the natural way to create a new activity,
since it contains a graphical representation with the available activities.
I think resuming is a secondary option we can provide, but should not be
the default option when you click on the icon. To overcome the issue of
constantly creating new activities I liked the 'open the full palette on
left click' option. The learner is then provided with options to choose
from.
I like this too. It is worth mentioning that on non-OLPC-XO hardware,
there is no easily discovered (or typed) dedicated key or mouse
movement to get you to the Journal--one of the reasons we have also
discussed having the Journal icon always available in the Home View (I
am in favor of always at the bottom of the circle). All of these
changes collectively may help.
I've been trying to stay out of this discussion so far, watching for what might
stick. So summing up so far:
- Always show Journal in the home ring, though I'd favour having it as the
first item, so that would make it always at the top of the circle ;-)
That sounds like a good compromise to me.
Side-Note: While thinking about it, Walter mentioned that the Journal is
not as accessible, especially on non XO-hardware. Another thing which is
hard to discover is the frame. I see a lot of kids having issues here.
This is one reason why the Journal is hard to find but as well to see
which activities are open at the moment.
- Home view reverted back to the 'start new' activity focus, all icons are
un-coloured.
Yes.
- Single left click always reveals the palette with the 'start new' item at the
top and 'resume' items below. Some minus design points here as 'start new' and
'resume' will both become 2 clicks away, and take extra palette cursoring
dexterity to reach. You could argue both 'start new' and 'resume' will drop to
second level features with 'activity palette information' becoming the top
level home feature. Being able to read (some of) this palette text would also
now be required, so our 'low floor' just got a little higher :-( I do agree
though that this provides a compromise between reducing Journal spam and
preventing the unintentional overwrite of existing Journal work by making the
choice explicit.
I tested today, to have the left click reveal the palette directly
(patch attached for those who want to try it out). You are right, that
you need two clicks, now. For me it would be ok, to just revert the
behavior to 'start new' by default and leave it to the merchandise
(including teacher) to set the message: resume is in the Journal.
Side-Note 2: I figured today that our use of left click is inconsistent.
In the home view clicking on the activity icon does choose one default
option on left click. Clicking on the XO icon does not have a meaning,
you need the palette. Same is true for clicking on a buddy icon in the
neighborhood or group view. The 'add friend' is not the default.
However, clicking on an activity icon in the neighborhood view does join
it, clicking on an AP does try to connect by default.
Thanks,
Simon
diff --git a/src/jarabe/desktop/favoritesview.py b/src/jarabe/desktop/favoritesview.py
index eccd517..bb55ec1 100644
--- a/src/jarabe/desktop/favoritesview.py
+++ b/src/jarabe/desktop/favoritesview.py
@@ -525,23 +525,10 @@ class ActivityIcon(CanvasIcon):
misc.resume(journal_entry, self._activity_info.get_bundle_id())
def _activate(self):
-if self.palette is not None:
-self.palette.popdown(immediate=True)
-
-if self._resume_mode and self._journal_entries:
-self._resume(self._journal_entries[0])
-else:
-client = gconf.client_get_default()
-xo_color = XoColor(client.get_string('/desktop/sugar/user/color'))
-
-activity_id = activityfactory.create_activity_id()
-launcher.add_launcher(activity_id,
- self._activity_info.get_icon(),
- xo_color)
-
-handle = ActivityHandle(activity_id)
-activityfactory.create(self._activity_info, handle)
-
+if self.palette is None:
+self.palette = self.create_palette()
+
[Sugar-devel] [Opportunity] Control Panel Font configuration --- Developer needed
Hi, the Font configuration [1] does need a control panel configuration panel to rock even more! This is a great task for someone to get into sugar shell programming. I would say, this is a medium to low level of difficulty coders task. With the extension structure this is a fun thing to do, and all the other control panel extensions are excellent examples for you to get started. Interested? Just reply here or send me mail. The work has to be done before the Feature Freeze and please mind that you have to hand it in for review, so handing it in the 1 Feb is a bit tight ;D Thanks, Simon PS: of course senior shell coders are welcome, too ;D [1] http://wiki.sugarlabs.org/go/Features/Font_configuration [2] http://wiki.sugarlabs.org/go/0.88/Roadmap#Schedule ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] [Opportunity] Please do not ignore, this is not a Test!
Hi, you are still looking for a fun task in the new year? You like to help Sugar to become a better quality product? Sugar is more than an ingredient of your Sunday cake to you? --- Then you need to become involved with the Sugar Quality assurance aka testing! Sugar has a 6 months release cycle. To get new Features bug free for the release they have to be tested already during the development cycle. There are so called development releases during the cycle. Those are available as Soas-images [2] and do need testing. If you are interested to help in the cycle you can do that in many different ways depending on your available time: - testing of the development releases - creating of test cases - doing usability tests with the target audience(s) - coordinating a testing team - Sugar Labs testing team coordinator ... Low floor, no ceiling. There are many ways you can help. If this sounds interesting to you, please reply here or send me mail. Thanks, Simon [1] http://wiki.sugarlabs.org/go/0.88/Roadmap#Schedule [2] http://wiki.sugarlabs.org/go/Sugar_on_a_Stick ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [DESIGN] 'Resume' vs 'Start a new' Activity
Hi Simon, On 13 Jan 2010, at 16:38, Simon Schampijer wrote: Hi Gary, thanks very much for your feedback. On 01/13/2010 02:15 PM, Gary C Martin wrote: On 11 Jan 2010, at 20:44, Walter Bender wrote: On Mon, Jan 11, 2010 at 3:32 PM, Simon Schampijersi...@schampijer.de wrote: On 01/11/2010 06:12 PM, Wade Brainerd wrote: My feeling regarding all this is that the problem is deeper than finding a way to Resume Latest or Start New from the home screen. IMO, the whole idea of Resume Latest is broken and needs to be ditched. The Journal is the place to resume activities. We need to make the Journal more discoverable and usable instead of trying to mash its features into the home screen. My findings are as well that the Journal is the natural place to resume an activity. The home view is the natural way to create a new activity, since it contains a graphical representation with the available activities. I think resuming is a secondary option we can provide, but should not be the default option when you click on the icon. To overcome the issue of constantly creating new activities I liked the 'open the full palette on left click' option. The learner is then provided with options to choose from. I like this too. It is worth mentioning that on non-OLPC-XO hardware, there is no easily discovered (or typed) dedicated key or mouse movement to get you to the Journal--one of the reasons we have also discussed having the Journal icon always available in the Home View (I am in favor of always at the bottom of the circle). All of these changes collectively may help. I've been trying to stay out of this discussion so far, watching for what might stick. So summing up so far: - Always show Journal in the home ring, though I'd favour having it as the first item, so that would make it always at the top of the circle ;-) That sounds like a good compromise to me. Side-Note: While thinking about it, Walter mentioned that the Journal is not as accessible, especially on non XO-hardware. Another thing which is hard to discover is the frame. I see a lot of kids having issues here. This is one reason why the Journal is hard to find but as well to see which activities are open at the moment. Oh no, don't bring up discoverability of the frame! One problem at a time ;-) - Home view reverted back to the 'start new' activity focus, all icons are un-coloured. Yes. - Single left click always reveals the palette with the 'start new' item at the top and 'resume' items below. Some minus design points here as 'start new' and 'resume' will both become 2 clicks away, and take extra palette cursoring dexterity to reach. You could argue both 'start new' and 'resume' will drop to second level features with 'activity palette information' becoming the top level home feature. Being able to read (some of) this palette text would also now be required, so our 'low floor' just got a little higher :-( I do agree though that this provides a compromise between reducing Journal spam and preventing the unintentional overwrite of existing Journal work by making the choice explicit. I tested today, to have the left click reveal the palette directly (patch attached for those who want to try it out). You are right, that you need two clicks, now. For me it would be ok, to just revert the behavior to 'start new' by default and leave it to the merchandise (including teacher) to set the message: resume is in the Journal. So resume from home view becomes the secondary palette action, I'd be OK with that, though it leaves outstanding the issue of Journal spam for those who just start new activities every time. FWIW I'm not equating 'Journal spam' and the (more serious) 'out of storage space' state. The largest consumers of storage I'm aware of are a few monster sized activities kids may try and install**. ** random thought, is it feasible to have Browse not start a download unless there is enough storage space? Side-Note 2: I figured today that our use of left click is inconsistent. In the home view clicking on the activity icon does choose one default option on left click. Clicking on the XO icon does not have a meaning, you need the palette. Same is true for clicking on a buddy icon in the neighborhood or group view. The 'add friend' is not the default. However, clicking on an activity icon in the neighborhood view does join it, clicking on an AP does try to connect by default. Yep. I believe we've had this discussion before :-) I seem to remember Eben agreed that what was always intended was for any button that did not have a primary click event should have the click event reveal the full palette. So clicking on the big XO icon should instantly show the palette; clicking a buddy in the neighbourhood should just show the full 'add friend' palette, etc. That way something would at least always happen when a user clicks on a button. I did
[Sugar-devel] Try out version support NOW ;)
Hi everyone!
Good news: I've finally managed to find fixes and workarounds for all
bugs I discovered so far in the version support fork of Sugar,
including the major ones that made trying it out a bumpy ride.
So if you are running sugar-jhbuild (*) and you'd like to try out how
version support might change your life, here's your chance [1]:
1. Backup (DON'T skip this!)
If you've used Sugar before, it is _highly_ recommended to create a
backup of your data store as it will be updated on first startup and
cannot be read by older versions of Sugar afterwards:
cp -a ~/.sugar/default/datastore ~/.sugar/default/datastore.v2
2. Switch to version support:
Replace moduleset = 'sugar' with moduleset = 'sugar-versionsupport' in
sugar-jhbuild/sugar.jhbuildrc.
Move away the old sources for the sugar, sugar-datastore and
sugar-toolkit packages (JHBuild cannot switch between different git
modules):
cd sugar-jhbuild
for pkg in sugar{,-datastore,-toolkit} ; do
mv ${pkg} ${pkg}-upstream
done
Get and build the new sources:
cd sugar-jhbuild
./sugar-jhbuild updateone sugar{,-datastore,-toolkit}
./sugar-jhbuild buildone sugar{,-datastore,-toolkit}
3. Usage
Run as usual:
cd sugar-jhbuild
./sugar-jhbuild run sugar-emulator --fullscreen
Please note that it's based on my VNC support branch, so instead of
Xephyr you'll get a VNC viewer. You shouldn't notice much of a
difference, with the exception of non-US keyboards working properly. To
bring up the VNC menu press F8.
The only visible difference is that the date field in the Journal
details view is now a ComboBox instead of a read-only text field -
meaning that you can select (and resume!) older versions of an entry. As
the current data store doesn't support versions all previously existing
entries will have only a single version, obviously. So in order to try
it out you'll need to resume some entry, modify and save (switch away
from / close) it.
I intended to play with an idea Caspar and I had about about how to
present versions to the user (namely undo/redo buttons inside
activities) but got delayed by technical difficulties so they won't make
it into the thesis (meaning I will work on that only after a significant
delay). Speaking of which: I'm concentrating on the text part (i.e. the
actual thesis) now, so while I highly appreciate (and kindly request)
feedback of any form please don't be offended if it takes a long time
for me to reply.
(*) Sebastian has kindly offered to help me build a custom SoaS but for
scheduling reasons I need to postpone that for some time, sorry.
[1] http://wiki.sugarlabs.org/go/Version_support_for_datastore/Howto
CU Sascha
--
http://sascha.silbe.org/
http://www.infra-silbe.de/
signature.asc
Description: Digital signature
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] [DESIGN] 'Resume' vs 'Start a new' Activity
On Wed, Jan 13, 2010 at 8:15 AM, Gary C Martin gary at garycmartin.com wrote: On 11 Jan 2010, at 20:44, Walter Bender wrote: On Mon, Jan 11, 2010 at 3:32 PM, Simon Schampijer simon at schampijer.de wrote: On 01/11/2010 06:12 PM, Wade Brainerd wrote: My feeling regarding all this is that the problem is deeper than finding a way to Resume Latest or Start New from the home screen. IMO, the whole idea of Resume Latest is broken and needs to be ditched. The Journal is the place to resume activities. We need to make the Journal more discoverable and usable instead of trying to mash its features into the home screen. My findings are as well that the Journal is the natural place to resume an activity. The home view is the natural way to create a new activity, since it contains a graphical representation with the available activities. I think resuming is a secondary option we can provide, but should not be the default option when you click on the icon. To overcome the issue of constantly creating new activities I liked the 'open the full palette on left click' option. The learner is then provided with options to choose from. I like this too. It is worth mentioning that on non-OLPC-XO hardware, there is no easily discovered (or typed) dedicated key or mouse movement to get you to the Journal--one of the reasons we have also discussed having the Journal icon always available in the Home View (I am in favor of always at the bottom of the circle). All of these changes collectively may help. I've been trying to stay out of this discussion so far, watching for what might stick. So summing up so far: - Always show Journal in the home ring, though I'd favour having it as the first item, so that would make it always at the top of the circle ;-) - Home view reverted back to the 'start new' activity focus, all icons are un-coloured. - Single left click always reveals the palette with the 'start new' item at the top and 'resume' items below. Some minus design points here as 'start new' and 'resume' will both become 2 clicks away, and take extra palette cursoring dexterity to reach. You could argue both 'start new' and 'resume' will drop to second level features with 'activity palette information' becoming the top level home feature. Being able to read (some of) this palette text would also now be required, so our 'low floor' just got a little higher :-( I do agree though that this provides a compromise between reducing Journal spam and preventing the unintentional overwrite of existing Journal work by making the choice explicit. I am with you until here. I think we need to be very careful with the introduction of such additional complexity in the UI. Even for older kids, those using the OLPC-XO-1 laptops that have the old jumpy touchpad will have a hard time with this. I would urge the design team to explore a few more ways to solve this problem spatially rather than temporally. I think the two use cases (Resume vs Start a new) are either valuable for the home view thats supposed to be the main workplace of sugar interactions, so I suggest to try hard to design an option to have the two use cases directly graphically available on the screen real estate, one point could be that on average not so many different activity could be displayed in the favorites circle, allowing few options to show them in a StartNew or Resume graphic option: Uncolored icons outside circle, the resuming colored icons inside in an incomplete circle, and Journal icon in centre (down to XO) as to represent even better the idea of reflection and research. note: the inner circle resuming icons should be reasonably smaller that the outer ones becouse they do not need support the usecase to be easily identifiable. ciao carlo regards. -walter Regards, --Gary ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [IAEP] Why #sugar should be logged - a plug for transparency and ease of use.
On Wed, Jan 13, 2010 at 08:29:58AM -0500, Jeff Elkner wrote: I'm really not interested in beating a dead horse, [...] I deliberately focussed on your workflow issue exactly to avoid that. :) [...], but I have 4 different computers on which I normally work, plus I work on other people's computers when I travel. Having stuff in the cloud is simply easier for me. OK, this was the missing part of the puzzle. You're running IRC clients on several different computers that don't share the logs in any way, so naturally you prefer it to be kept in a central, public place (i.e. a web site since IRC doesn't support server-side storage). Since I keep the IRC logs (and a whole lot of other stuff) in sync using unison [1] and often work offline I naturally prefer the logs to be kept locally. Thanks, I do understand your needs better now! :-| [1] http://www.cis.upenn.edu/~bcpierce/unison/ CU Sascha -- http://sascha.silbe.org/ http://www.infra-silbe.de/ signature.asc Description: Digital signature ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [IAEP] Why #sugar should be logged - a plug for transparency and ease of use.
On Wed, Jan 13, 2010 at 08:02:20PM +0100, Sascha Silbe wrote: OK, this was the missing part of the puzzle. You're running IRC clients on several different computers that don't share the logs in any way, so naturally you prefer it to be kept in a central, public place (i.e. a web site since IRC doesn't support server-side storage). For interest, on an OLPC channel several of us have started using quassel. This provides logs, backlog while you are absent, and connections from different computers. Though I've not yet needed to verify simultaneous connections. You do need to place a quassel server in the cloud somewhere. -- 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] [ANNOUNCE] Sucrose 0.87.3 Development Release
Hi On Wed, Jan 13, 2010 at 11:59 AM, Simon Schampijer si...@schampijer.de wrote: Dear Sugar Community, this is the third development release in the 0.88 release cycle - see the schedule [1] for more details. Please note that the schedule has been adjusted lately. See [2] for more info. The detailed changes and where to download the sources can be found in the release notes [3]. Sebastian is going to create a new Soas-Fedora12 image for testing and announce it in this thread. Can't wait to test the .iso, i'm also trying to get teachers and people on deployments more aware, for testing new features and giving feedback, these development snapshots can be the way to improve it. In behalf of the sugar community, Your Release Team [1] Schedule: http://wiki.sugarlabs.org/go/0.88/Roadmap [2] http://lists.sugarlabs.org/archive/sugar-devel/2010-January/021900.html [3] Release Notes: http://wiki.sugarlabs.org/go/0.88/0.87.3_Notes ___ 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] gitorious and uploading public key
Hi George. (adding sugar-devel to cc) It happen to me also, the solution (IIRC) then was wait, wait, wait. cheers. Rafael Ortiz On Wed, Jan 13, 2010 at 4:15 PM, George Hunt georgejh...@gmail.com wrote: Hi everyone, Earlier I successfully uploaded a public ssh key to git.sugarlabs.org. But then I decided to change key pairs, created a new set, and then tried to upload a the new one. I'm getting the following message: This sshkey is being created, it will be ready pretty soon I came back a day later. Still no joy. Tried again, same response. Any suggestions? George ___ Devel mailing list de...@lists.laptop.org http://lists.laptop.org/listinfo/devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Automated coverage testing?
G'day, Is there an automated test for Sugar or for activities? Something that will act like a user and generate keyboard and mouse actions to exercise each feature at least once. -- 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] Automated coverage testing?
Hi Quozl On Wed, Jan 13, 2010 at 7:48 PM, James Cameron qu...@laptop.org wrote: G'day, Is there an automated test for Sugar or for activities? Something that will act like a user and generate keyboard and mouse actions to exercise each feature at least once. There was this effort http://code.google.com/p/sugarbot/wiki/Index although i don't know it's actual state. it would be nice to explore mago and adapt it to sugar. http://mago.ubuntu.com/ -- 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
Re: [Sugar-devel] [DESIGN] 'Resume' vs 'Start a new' Activity
On Sun, Jan 10, 2010 at 12:18, Gerald Ardito gma...@gmail.com wrote: Edward, I am interested in what you have about the various key click behavior on the basic XO. I will be able to resume work on these issues soon. We are beginning to settle into our new home. And, I can validate your estimate about the year to learn from our pilot program last year. I'm not clear what you mean. I wrote about Alan Kay's estimate that it takes a year to go from an idea for a lesson to something tested, verified, and polished. Do you mean a year for teachers to get an idea of what they are doing with XOs? In fact, we can expect to go on improving these processes for decades, perhaps centuries, considering the model of the printing press and the profusion of kinds of publishing over the last five and a half centuries. I can also say that it depends less upon prior experience with computers as it does with a willingness to explore and meet obstacles, at least the 5th graders with whom I've been working. Many times, students at this level with a certain amount of experience with computers don't/can't really generalize to a new system. Adults are almost universally convinced that they are unable to generalize from Word to Open Office or from Windows to Linux. Linux Users are more able to generalize, at least in part because they tend to be familiar with multiple distributions. Part of the problem is the insistence in schools on Right Answers. In order to learn something new, you have to be willing to make mistakes that you could avoid by staying with what you know. Anything that is worth doing at all is worth doing wrong. http://wiki.sugarlabs.org/go/User:Mokurai/Quotes#Pablo_Picasso Pablo Picasso * I am always doing that which I can not do, in order that I may learn how to do it. Thanks again. Gerald On Sat, Jan 9, 2010 at 12:21 AM, Edward Cherlin echer...@gmail.com wrote: On Fri, Jan 8, 2010 at 19:14, Gerald Ardito gma...@gmail.com wrote: Edward, This is very helpful. Thanks. My pleasure. I have lots more of this sort of thing in draft. Let me know of any other such issues you have run into, and I can give you what I have, or think about it further. There are numerous uses for left-click, double-click, triple-click, click-and-drag, right click, hover, and in some systems mouse gestures. I use a four-button trackball, and my son uses a special game control mouse, but we don't have to get into all of that with Sugar. ^_^ It will also be helpful, if you try my suggested process, to document how long it takes for children in a given class to catch on to an idea, and how long it takes for it to become automatic. I don't know how we can instrument such a study, but I expect that someone here will have an idea. I expect to see variations by age, by prior computer experience (positive or negative), and by cultural and social factors. BTW, nobody should suppose that this succession of ideas is finished and perfect. No amount of sympathetic imagination can substitute for classroom experience, any more than a battle plan can survive contact with the enemy. I want to hear suggestions for improvement, and I want to hear about other issues that arise. Alan Kay has said that it takes about a year to polish a math or physics lesson, and I will be surprised if it is very much shorter for each of the key issues in Sugar. Gerald -- Edward Mokurai (默雷/धर्ममेघशब्दगर्ज/دھرممیگھشبدگر ج) Cherlin Silent Thunder is my name, and Children are my nation. The Cosmos is my dwelling place, the Truth my destination. http://www.earthtreasury.org/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
