[Etoys] How to distribute amd install MO for Apps

Bert Freudenberg bert at freudenbergs.de
Fri Nov 16 14:38:48 EST 2007

You would need to hack the startup script and include the image in  
your .xo. I did that for the OLE Nepal image:


However, it would be extremely inefficient space-wise to do that as  
99% of the image would be identical to the etoys image and you're  
simply wasting 15 MB of space.

- Bert -

On Nov 16, 2007, at 20:31 , Hilaire Fernandes wrote:

> Now I remember Yoshiki wrote several weak ago about another  
> possibility.
> To just ship alternative Squeak/Smalltalk application like DrGeo in
> their own .image.
> What will be required to do that ? Starting from the standard etoys  
> image?
> This solution will solve the problem about loading project file with
> existing geometric diagram.
> Hilaire
> 2007/11/14, Bert Freudenberg <bert at freudenbergs.de>:
>> On Nov 14, 2007, at 20:44 , karl wrote:
>>> Hilaire Fernandes wrote:
>>>> 2007/11/11, korakurider at yahoo.co.jp <korakurider at yahoo.co.jp>:
>>>>> I hit fundamental question: how to distribute and install addon
>>>>> application with translation.
>>>> Yes, you got a point.
>>>> Which features do we need ?
>>>> - a Squeak application should be installable at runtime, without
>>>> modifying the image
>>>> - a project using a loaded application should re-load the  
>>>> application
>>>> - application translation should be reloadable at runtime aswel.
>>>> I have tested loading DrGeo SAR into the OLPC. In my opinion it is
>>>> too
>>>> slow and I am afraid teachers and kids will run away. Imagine a
>>>> situation where a kid need to review sever interactive geometric
>>>> sketch. We will have an acceptability problem there.
>>>> I have heard about ImageSegment, I only got an overall  
>>>> understanding
>>>> about it but I have the felling it may be the fastest solution.
>>> Projects are saved in image segments, but code changes are not
>>> captured in the segment so those are filed in from a changeset.
>>> This is quite slow.
>> Loading an ImageSegment is indeed extremely fast. Even classes and
>> compiled methods can be included in a segment. The problem is that
>> after loading the segment, references ("outpointers") have to be
>> fixed up - for example, all symbols must be made to point to the
>> symbol instance in the image, otherwise you would have duplicate
>> symbols. And we accumulated a lot of cruft over the years that is
>> performed on project load time - fixing up fonts, migrating instances
>> to new class layout etc. Working this out would be very valuable.
>> - Bert -
>> _______________________________________________
>> Etoys mailing list
>> Etoys at lists.laptop.org
>> http://lists.laptop.org/listinfo/etoys
> -- 
> http://blog.ofset.org/hilaire
> Smalltalkers do: [:it | All with: Class, (And love: it)]

More information about the Etoys mailing list