Hello,
We haven't reporting our progress so much to general OLPC dev community, but of course the Etoys team has been good progress since the B1 release.
A few highlights are:
* Video interface. You can manipulate, rotate, move and etc. the movie stream (taking a still frame is something a kid can program in visual programming interface).
* World Stethoscope. There is a little piece of hardware that converts input from various sensors into sound frequency. You can plug that to B1 machine, and use the input as the program element in Etoys. (Or, any simple microphone works, too, if the input is sound.)
* Various improvements including the visual appearance such as fonts.
There are still some items on the trac, but these are actually solved by yesterday. Early tomorrow, Bert in Germany wiil make up RPM files to be included to the build images. (Then, I'll close these items on trac.)
-- Yoshiki
On Jan 11, 2007, at 0:44 , Yoshiki Ohshima wrote:
Hello,
We haven't reporting our progress so much to general OLPC dev community, but of course the Etoys team has been good progress since the B1 release.
A few highlights are:
Video interface. You can manipulate, rotate, move and etc. the movie stream (taking a still frame is something a kid can program in visual programming interface).
World Stethoscope. There is a little piece of hardware that converts input from various sensors into sound frequency. You can plug that to B1 machine, and use the input as the program element in Etoys. (Or, any simple microphone works, too, if the input is sound.)
Various improvements including the visual appearance such as fonts.
There are still some items on the trac, but these are actually solved by yesterday. Early tomorrow, Bert in Germany wiil make up RPM files to be included to the build images. (Then, I'll close these items on trac.)
Actually, I uploaded the rpm in time so it is already in build 225. Also, there have been constant updates to the rpms in the last weeks which automatically went into the images without much ado (see OS build-log extract below).
- Bert -
build 193 ---> Package etoys.noarch 0:1.0.1118-1 set to be updated build 194 ---> Package etoys.noarch 0:2.0.1134-1 set to be updated build 195 ---> Package etoys.noarch 0:2.0.1134-1 set to be updated build 196 ---> Package etoys.noarch 0:2.0.1134-1 set to be updated build 197 ---> Package etoys.noarch 0:2.0.1134-1 set to be updated build 198 ---> Package etoys.noarch 0:2.0.1142-1 set to be updated build 199 ---> Package etoys.noarch 0:2.0.1142-1 set to be updated build 200 ---> Package etoys.noarch 0:2.0.1142-1 set to be updated build 201 ---> Package etoys.noarch 0:2.0.1145-1 set to be updated build 202 ---> Package etoys.noarch 0:2.0.1145-1 set to be updated build 203 ---> Package etoys.noarch 0:2.0.1145-1 set to be updated build 204 ---> Package etoys.noarch 0:2.0.1145-1 set to be updated build 205 ---> Package etoys.noarch 0:2.0.1156-1 set to be updated build 206 ---> Package etoys.noarch 0:2.0.1156-1 set to be updated build 207 ---> Package etoys.noarch 0:2.0.1156-1 set to be updated build 208 ---> Package etoys.noarch 0:2.0.1156-1 set to be updated build 209 build 210 ---> Package etoys.noarch 0:2.0.1156-1 set to be updated build 211 ---> Package etoys.noarch 0:2.0.1156-1 set to be updated build 212 ---> Package etoys.noarch 0:2.0.1156-1 set to be updated build 213 ---> Package etoys.noarch 0:2.0.1156-1 set to be updated build 214 ---> Package etoys.noarch 0:2.0.1166-1 set to be updated build 215 ---> Package etoys.noarch 0:2.0.1168-1 set to be updated build 216 ---> Package etoys.noarch 0:2.0.1168-1 set to be updated build 217 ---> Package etoys.noarch 0:2.0.1168-1 set to be updated build 218 ---> Package etoys.noarch 0:2.0.1168-1 set to be updated build 219 ---> Package etoys.noarch 0:2.0.1168-1 set to be updated build 220 ---> Package etoys.noarch 0:2.0.1168-1 set to be updated build 221 ---> Package etoys.noarch 0:2.0.1168-1 set to be updated build 222 ---> Package etoys.noarch 0:2.0.1168-1 set to be updated build 223 ---> Package etoys.noarch 0:2.0.1178-1 set to be updated build 224 ---> Package etoys.noarch 0:2.0.1178-1 set to be updated build 225 ---> Package etoys.noarch 0:2.0.1179-1 set to be updated
There are still some items on the trac, but these are actually solved by yesterday. Early tomorrow, Bert in Germany wiil make up RPM files to be included to the build images. (Then, I'll close these items on trac.)
Actually, I uploaded the rpm in time so it is already in build 225. Also, there have been constant updates to the rpms in the last weeks which automatically went into the images without much ado (see OS build-log extract below).
Oh, shoot. I didn't check if there is build 225. Almost everytime I write an email, a new disk image is magically showing up on the server^^;
Of course, I know you have been constantly updating it and I have been installing the disk images!
-- Yoshiki
On Jan 11, 2007, at 1:26 , Yoshiki Ohshima wrote:
There are still some items on the trac, but these are actually solved by yesterday. Early tomorrow, Bert in Germany wiil make up RPM files to be included to the build images. (Then, I'll close these items on trac.)
Actually, I uploaded the rpm in time so it is already in build 225. Also, there have been constant updates to the rpms in the last weeks which automatically went into the images without much ado (see OS build-log extract below).
Oh, shoot. I didn't check if there is build 225. Almost everytime I write an email, a new disk image is magically showing up on the server^^;
Of course, I know you have been constantly updating it and I have been installing the disk images!
I know you know, but the other folks might not know, you know? ;-)
Lately, I see a Changelog added to the daily builds - what's the procedure to get a notice into that? Also, it would be helpful to make that file truly change-log style with newer entries added at the top:
http://olpc.download.redhat.com/olpc/streams/development/build224/ ChangeLog
- Bert -
etoys-dev@lists.squeakfoundation.org