[etoys-dev] Preparing for Monticello-based updates

Andreas Raab andreas.raab at gmx.de
Mon Apr 26 23:57:56 EDT 2010

Hi Bert -

Thanks for the instructions, I followed them and they work well. For 
looking at the Flash issues this has been the first time that I've been 
using an Etoys image in a while and I noticed some highly annoying 
things that I thought I'd point out:

* Keyboard shortcuts. Some keyboard shortcuts seem completely broken on 
Windows. At first I thought this is a VM issue but they don't work with 
the the VM in the Etoys app either. Is there a way to fix that? Having 
shortcuts like "implementors" not work makes working somewhere between 
hard and impossible. Any ideas how to fix that?

* Scaling. As much as I understand the desire, is there a way to turn 
off display scaling and the uber-large cursors? The fonts are simply too 
hard on my eyes for continuous work.

* Image saving. At first I tried a "save as" but this complained about 
not finding the sources/changes file afterwards. How come? Second, 
saving the image produces a visible flashing which is for some reason 
completely discomforting - it looks as if there was an error that the 
system tried to inform me about by the flash.

   - Andreas

On 4/25/2010 7:56 PM, Bert Freudenberg wrote:
> On 19.04.2010, at 13:52, Bert Freudenberg wrote:
>> Hi folks,
>> as we discussed lately we want to enable easier contributions, following a model similar to Squeak's "trunk". I spent the weekend making the latest tools from Squeak work in the Etoys image. I did not push it to the update stream yet, but it is attached. Let's discuss in the developer meeting on IRC later today.
>> Here is how to test it:
>> * Download Etoys-To-Go4-Final.zip from squeakland.org and unzip and run
>> * get halo for world, choose "preferences..." from halo menu
>> * disable "eToyFriendly" in the "scripting category"
>> * click the gray World background, choose "previous project" from the World menu
>> * you'll be taken to the hidden top-level project, light-blue background
>> * now is a good time to save the image
>> This will result in an image ready for development work. I'm suggesting to use Etoys-To-Go because it is self-contained and allows to save the image easily. The regular install is read-only.
>> Now for my stuff ...
> ... which I just pushed to the new 4.1 update stream at etoys.squeak.org
> * Evaluate this in a workspace to set the new update server (you need at least a 4.0.2336 image):
> 	HTTPSocket httpFileInNewChangeSet: 'etoys.squeak.org/updates/newUpdateStream-bf.cs'
> * Then load updates. This will ask if you want to advance to 4.1, say yes. Load updates again
> * This will take quite a while ...
> * ... but eventually you should have an image with Monticello loaded :)
> Heres a log of the changes:
> http://squeakland.org/updates/
> This includes the recategorization from trunk (huge 1 MB changeset) and an edited version of Karl's recategorization, ending up in a quite reasonable number of packages IMHO. Also, thanks to Eliot for porting the compiler changes!
> The next step should be to create proper packages and commit them to the etoys repo. The will differ a bit from your initial ones, Karl. Do we want to try to merge yours or would it be simpler to start clean and just fix the underscores again?
> - Bert -
> _______________________________________________
> etoys-dev mailing list
> etoys-dev at squeakland.org
> http://lists.squeakland.org/mailman/listinfo/etoys-dev

More information about the etoys-dev mailing list