andreas.raab at gmx.de
Fri Feb 7 01:34:37 UTC 2003
> I am a bloody SmallTalk / Squeak beginner, so please excuse my stupid
Not stupid (just partly answered in FAQs - see
> #1: How can I create an EXE with Squeak so that other people
> can start my application like any other app (on Windows). I
> read something that this is possible with SmallTalk/X but I
> could not find any docs for this topic concerning Squeak.
Check out http://minnow.cc.gatech.edu/squeak/778 The easiest way of doing
this is to provide a "multi-file distribution" which must at least include:
* The VM (Squeak.exe - which you may rename into "myApp.exe")
* An image file (myApp.image)
On Windows, if you put the two into the same directory you can start your
app by simply double-clicking the VM (the VM looks for a single file with
the extension ".image" in its directory so it will find it) but since this
search can sometimes take more time than you'd like, it is often helpful to
provide a shortcut or .bat file which has the name of your app instead and
is set up so that it starts vm+image (e.g., "Squeak.exe myApp.image"). If
you make a proper installer you can create the shortcut directly on the
desktop or in the program menu.
> #2: In which form SmallTalk programmers deliver their
> applications to the end user (who have no SmallTalk installed)?
For Squeak, the above is your best option.
> #3: There are threads in SmallTalk. Are these threads mapped
> to threads of the operation system or are SmallTalk threads
> something completely different?
They are not "something completely" but merely "slightly" different but no,
they are not mapped on threads of the OS. Essentially they are preemptive
(and very!) lightweight threads which preempt only other threads at lower
priority (so scheduling within a priority is cooperative).
More information about the Squeak-dev