Stand-alone Squeak application on MacOS X

> What I want is that I click on Squeak VM application (on MacOS X) and
> Squeak starts with my image, without asking what image to open.
>
> I found on Squeak Swiki information, saying that "with a Mac VM at
> least as new as 3.2.6b3, you can put .image .sources and .changes in
> the resource path of the VM .app" (
> http://minnow.cc.gatech.edu/squeak/778 ). But when I put my image file
> to Contents/Resources directory of Squeak VM application, it didn't
> change anything - when I click on Squeak VM it still asks about image
> file to open. I also tried to put .sources and empty .changes near my
> image, I tried to put image, .sources and .changes to Contents/MacOS -
> but nothing help.
>
> You are my last hope, please suggest something :-)
>
> --
> Eugene
>
>

> I did (forgot to say it in first email) - no effect.
>
> 2006/6/14, Noury Bouraqadi <[hidden email]>:
>> Hi Eugene,
>>
>> You need to name your image file 'Squeak.image'.
>>
>
> --
> Eugene
>
>

> It works on my PowerBook / MacOS 10.3.9. I just retried it with a
> Squeak Squeak 3.8.12beta4U VM.
>
> Noury
> Le 14 juin 06, à 12:22, Eugene Beschastnov a écrit :
>
>> I did (forgot to say it in first email) - no effect.
>>
>> 2006/6/14, Noury Bouraqadi <[hidden email]>:
>>> Hi Eugene,
>>>
>>> You need to name your image file 'Squeak.image'.
>>>
>>
>> --
>> Eugene
>>
>>
> ------------------------------------------------------------------
> Dr. Noury Bouraqadi - Enseignant/Chercheur
> ARMINES - Ecole des Mines de Douai - Dept. G.I.P
> http://csl.ensm-douai.fr/noury
>
> European Smalltalk Users Group Board
> http://www.esug.org
>
> Squeak: a Free Smalltalk
> http://www.squeak.org
> ------------------------------------------------------------------
>
>
>
>

> Am 14.06.2006 um 11:58 schrieb Eugene Beschastnov:
>
> > Can anybody suggest, how to make stand-alone Squeak application for
> > MacOS X (i.e. Squeak VM with embedded image)?
> >
> > I have standard 3.7-7 VM without modifications.
>
> That is the Unix VM (blue icon) which is different from the regular
> Mac VM (golden icon). Download the latest Mac VM from
>
>         http://squeak.org/Download/
>
> And see
>
>         http://www.smalltalkconsulting.com/html/squeakinfoplist.html
>
> for the VM options, including embedded image support.
>
> - Bert -
>
>
>

> As I remember, I had some troubles with 3.8.12beta4U Mac VM. I may be
> wrong, but I think it was related with MP3 sounds loading.
>
> But I see on http://www.squeakvm.org/unix/ that there is new VM for
> MacOS X - 3.9-7. Is it already stable and recommended for productions
> use?
>
> 2006/6/14, Bert Freudenberg <[hidden email]>:
>> Am 14.06.2006 um 11:58 schrieb Eugene Beschastnov:
>>
>> > Can anybody suggest, how to make stand-alone Squeak application for
>> > MacOS X (i.e. Squeak VM with embedded image)?
>> >
>> > I have standard 3.7-7 VM without modifications.
>>
>> That is the Unix VM (blue icon) which is different from the regular
>> Mac VM (golden icon). Download the latest Mac VM from
>>
>>         http://squeak.org/Download/
>>
>> And see
>>
>>         http://www.smalltalkconsulting.com/html/squeakinfoplist.html
>>
>> for the VM options, including embedded image support.
>>
>> - Bert -

> Hi!
>
> Can anybody suggest, how to make stand-alone Squeak application for
> MacOS X (i.e. Squeak VM with embedded image)?
>
> I have the prepared image, that is used for making stand-alone Windows
> application. This image made with method
> MySoftware class>>deploy
> Smalltalk addToStartUpList: self.
> Smalltalk abandonSources.
> Preferences disableProgrammerFacilities.
> so it doesn't need .sources and .changes files. Also I have standard
> 3.7-7 VM without modifications.
>
> What I want is that I click on Squeak VM application (on MacOS X) and
> Squeak starts with my image, without asking what image to open.
>
> I found on Squeak Swiki information, saying that "with a Mac VM at
> least as new as 3.2.6b3, you can put .image .sources and .changes in
> the resource path of the VM .app" (
> http://minnow.cc.gatech.edu/squeak/778 ). But when I put my image file
> to Contents/Resources directory of Squeak VM application, it didn't
> change anything - when I click on Squeak VM it still asks about image
> file to open. I also tried to put .sources and empty .changes near my
> image, I tried to put image, .sources and .changes to Contents/MacOS -
> but nothing help.
>
> You are my last hope, please suggest something :-)
>
> --
> Eugene
>

> If you use the VM form Ian (which can be launched from the command  
> line), you can create a file named myapplication.command containing:
> -=-=-=-=-=-=-=-=-=-=-=-=
> #!/bin/bash
> squeak -nodisplay myimage.image
> -=-=-=-=-=-=-=-=-=-=-=-=
>
> The fact that the name ends with .command makes this file  
> executable by double-clicking on it.
>
> Cheers,
> Alexandre
>
>
> Am Jun 14, 2006 um 10:58 AM schrieb Eugene Beschastnov:
>
>> Hi!
>>
>> Can anybody suggest, how to make stand-alone Squeak application for
>> MacOS X (i.e. Squeak VM with embedded image)?
>>
>> I have the prepared image, that is used for making stand-alone  
>> Windows
>> application. This image made with method
>> MySoftware class>>deploy
>> Smalltalk addToStartUpList: self.
>> Smalltalk abandonSources.
>> Preferences disableProgrammerFacilities.
>> so it doesn't need .sources and .changes files. Also I have standard
>> 3.7-7 VM without modifications.
>>
>> What I want is that I click on Squeak VM application (on MacOS X) and
>> Squeak starts with my image, without asking what image to open.
>>
>> I found on Squeak Swiki information, saying that "with a Mac VM at
>> least as new as 3.2.6b3, you can put .image .sources and .changes in
>> the resource path of the VM .app" (
>> http://minnow.cc.gatech.edu/squeak/778 ). But when I put my image  
>> file
>> to Contents/Resources directory of Squeak VM application, it didn't
>> change anything - when I click on Squeak VM it still asks about image
>> file to open. I also tried to put .sources and empty .changes near my
>> image, I tried to put image, .sources and .changes to Contents/
>> MacOS -
>> but nothing help.
>>
>> You are my last hope, please suggest something :-)
>>
>> --
>> Eugene
>>
>
> --
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel  http://www.cs.tcd.ie/Alexandre.Bergel
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>
>
>

> Err, I wouldn't call that a "stand-alone Squeak application".
>
> 1) it would require that the Squeak Unix VM is already installed,  
> and registered in the search path
> 2) the image file has to be installed in your home directory, so  
> you couldn't put your "app" elsewhere
> 3) It starts Terminal.app and leaves behind a totally unnecessay  
> terminal window
>
> 1 and 2 could be dealt with by a more sophisticated shell script,  
> but that Terminal window is really a show stopper. Also, it  
> wouldn't work if someone deleted Terminal.app for security reasons.
>
> Similar issues apply to an AppleScript, but at least you could get  
> around using Terminal.app. Croquet uses that approach.
>

> Sveinbjorn Thordarso's Platypus is what I used to create the script
> that launches Croquet on the Mac. I like Platypus better than
> applescript, since I could use normal Unix /bin/sh scripts to find
> a relative path to the VM and image file to launch them. So
> you can do things like this:
>
> #!/bin/sh
> cd "$1/.."
> cd bin/macintosh
> open -a Squeak3.8.12beta3U.app "../../Croquet1.0.10.image"
>
>
>
>
> On Jun 15, 2006, at 6:17 AM, Bert Freudenberg wrote:
>> Err, I wouldn't call that a "stand-alone Squeak application".
>>
>> 1) it would require that the Squeak Unix VM is already installed,  
>> and registered in the search path
>> 2) the image file has to be installed in your home directory, so  
>> you couldn't put your "app" elsewhere
>> 3) It starts Terminal.app and leaves behind a totally unnecessay  
>> terminal window
>>
>> 1 and 2 could be dealt with by a more sophisticated shell script,  
>> but that Terminal window is really a show stopper. Also, it  
>> wouldn't work if someone deleted Terminal.app for security reasons.
>>
>> Similar issues apply to an AppleScript, but at least you could get  
>> around using Terminal.app. Croquet uses that approach.
>>