Bryan:<br>It takes a long time to train teachers to use Etoys who have never used<br>a computer before. Etoys _requires_ mastery of the touchpad and that was<br>more than we could teach in 2 weeks of training. Dragging and dropping<br>
is a non-trivial skill.<br><br>I think we can train teachers familiar w/ computers how to use Etoys.<br>Unfortunately, 95% of the teachers we deal and will deal w/ are not very<br>familiar w/ computers.<br><br>This is one of the major differences b/w Nepal's deployments and those<br>
of more developed countries like Uruguay<br><br>Walter:<br>I presume the same thing applies to Javascript and Flash that uses<br>drag and drop?<br><br>Bryan:<br>It is does if you require a lot of dragging-and-dropping together w/<br>
right-clicking. For example, our teachers got the hang of Draw during<br>training but they struggled w/ Etoys. They could do<br>point-click-activities like GCompris, E-Paath, Maze, etc. w/out a<br>problem<br><br><br>Bill:<br>
If you did a usability study comparing the etoys interface with the scratch interface you'll find that scratch provides for a much easier startup<br><br>This includes the touchpad issue (eg. in etoys you have to draw and keep a sprite before you can begin to program) but also there are many other factors which makes scratch easier to use for a beginner<br>
eg.<br><br> * colour coding of different function<br> * all the function areas are visible to start with<br> * clear physical separation of blocks palette from scripting area from stage<br> * easier, more intuitive to see how blocks fit together<br>
<br>I recently had a collaborative session with some xos and was introduced to the excellent etoys collaborative features (etoys chat and ability to pass scripted objects b/w users). These are great. I'm just arguing here about the getting started features which have impacted on the Nepal teacher training.<br>