Epaath image customization

How to pimp a fresh and clean Etoys image to a luxurious Epaath image

For this procedure it's helpful to have the etoys-migration-files directory handy. A public one is available on dev.laptop

What follows is a step by step instruction:

Get the latest Etoys image

That would be: EtoysV3.sources and etoys-dev-3.0.zip

Place EtoysV3.sources in the directory where you've got SqueakV3.sources, and unzip the etoys-dev-3.0.zip to a directory of your preference.

Or just use the stock Etoys image for now. It doesn't really matter.

Import latest changes in Image

Left-click on world to pop up menu -> update code from server And wait a bit till all has been downloaded and loaded into the image.

Install Monticello

This is not a straight line procedure, since the standard Etoys image has diverged a bit from the main squeak line. For now see the 'Installing Monticello on your Etoys image' section in Etoys Tips and Tricks.

Install the latest OLE Monticello package

Open a Monticello browser and click +Package. Enter 'OLE' and accept. Then with the (empty) OLE package being highlighted, click +Repository and select 'http'. Change the location into 'http://squeaksource.com/OLE' and leave user and password be. Both should say 'squeak'. Accept. Highlight the repository and click Open. Wait for a bit and a new window should open. Select the latest OLE version from the pane on the right and click 'load'.

And now you should have a new and fresh OLE lib installed.

Local patches

Go to the changesets directory in the etoys-migration-files directory, and file them in.

Devanagari fonts

Go to the devanagari-fonts directory in the etoys-migration-files directory. Drag the Devnew.ttf file into your etoys image. Drag a textmorph from your supply-bin, conjure up it's halo, select DevanagariNew and select a point size.

Then again conjure up the halo, select the DevanagariNew font and select 'new size'. Fill in 60, 72, 100, 200, 300 or 400, and repeat the process to add the rest. If you are thrown into the debugger, that's to be expected. We should file a bug report for that if it's not already done.

Then execute:

TTCFont registerAll

As from [1]. We should still submit a proper patch for this.

And we're done.

Note that rendering Devenagari has been fixed. This does require updating your image to incorporate the latest changesets. The stuff we did in the preceding section is only meant for rendering of Devanagari letters. We still need to follow the preceding procedure though, cause we need to be backward compatible.

sounds

Just drag all the files from the common-sounds folder under etoys-migration-files into the etoys image. Answer 'save' at the dialog, and accept with the suggested name.

We play all sounds as wavs at the moment. Preferably they would probably be something like ogg files to save mem.

custom classes

We should also load a couple of .st files that haven't been integrated into the OLE Monticello package yet. Just file in all files in dir 'class-files' under etoys-migration-files.

preferences

Some preferences should also be adjusted. Some are automatically activated with setting the image into production mode which is described below.

The only ones we for now do manually are the preference variables warnIfChangesFileReadOnly and startupInUntrustedDirectory, which we set to false and true respectively (by searching for the concerning variable in world menu > help > preferences).

XO Game Collection

We load the 'XO Game collection.*.pr' (whichever is the latest version, if there are more) project file into the image.

Setting Image to deploy|author mode|user mode

If you're going to use the image for developing, click the world to get the world menu, select OLE and select author mode. If you want to see how a user would experience, select 'user mode'. User mode toggles a few values so users don't get bothered by all the options that developers get. If you think that's a good idea? That's another question.

If you're actually going to use the image for deployment in Nepali schools, select deploy, and also select toggle flaps, to hide the flaps that the OLE developers often use to store objects off-screen.

Save image

Save that image!!

and we're done.