I just test this and it looks pretty bad. About 50% slower than original Drgeo xo bundle.
I installed the VM and Etoys image your recommended. Then I installed into this image the drgeo.cs from a PC. Usability in the XO is close to zero. All Etoys updated that way seems slow by the way (without any drgeo upgrade). Damn, this ruined the activity I planed with students tomorrow.
Hilaire
2009/10/27 Bert Freudenberg bert@freudenbergs.de:
On 27.10.2009, at 15:57, Hilaire Fernandes wrote:
2009/10/27 Bert Freudenberg bert@freudenbergs.de:
No. These OS updates are under development. The latest stable release by OLPC is still 8.2.1.
Regarding your original subject line, there is *nothing* I know that would prevent the latest Etoys to work with the latest Sugar. The latest Etoys also works with the old Sugar as already installed on the XOs.
Yes, that's what I need to know. Just to be sure, can I just replace the .image .changes file in the XO with newer ones based from Etoys4?
This should work I think but I'd recommend to install the latest RPM. That way you get all the additional files too, like translations, fixed example projects, help guides etc:
Do I need to update the VM as well, or does the one in the XO still fine with newer Etoys?
Should work fine, but again I'd recommend updating to the latest RPM. There is a reason we release updated VMs too ;)
But you would have to upgrade Etoys yourself, same procedure as ever:
Yes, in all case I have to do that, as I need to ship DrGeo code as well.
To share projects among XO laptop, I think I will have to use a wifi access point and a third party laptop providing FTP or Superswiki2 access. It is really ridiculous mesh network is of no help to share files.
Thanks for the info. and tips.
Hilaire
No problem :)
- Bert -
etoys-dev mailing list etoys-dev@squeakland.org http://lists.squeakland.org/mailman/listinfo/etoys-dev