On Tue, 30 Oct 2001, Torge Husfeldt wrote:

> Hi  All,
> Two thoughts how you might to be able to tell the plugin to use more memory:
>
> 1. In the vm source code I read that the Environment varible called
> SQUEAK_MEMORY should be read in on startup (sqXWindow.c::parseEnvironment).

Exactly, that's the way it works right now. Just set this before invoking
your browser.

> 2. can't you just write a shell-script or alias that adds this parameter to
> the others?

Just tried - works, too:

	cd  ~/.netscape/squeak
	mv squeakvm squeakvm.bin
	emacs squeakvm
		-------------
		#! /bin/sh
		exec $0.bin -memory 64m "$@"
		-------------
	chmod +x squeakvm

(Don't forget the quotes around "$@": I did and it won't work.)

This is a rather nice idea, actually. This way, we can put all kind of
cool flags there, like our beloved -xshm ...

> Alternative ideas:
> The plugin executable has to give parameters to the vm anyway, why can't it
> add some memory by that way, or can it? -- Maybe read from the environment or
> the html-tag too?

That's what John M. (below) was talking about. I just haven't implemented
that, yet. When someone has an idea how to fit the browser-plugin sources
into the VM-Maker tree at SF, we could start working on this together ...

> Hope this helps,
> Torge
>
> P.S.: What is the problem with using the standard vm and image with the
> plugin? I recall that the instructions for installing the plugin told me to do
> exactly that.

The Plugin has to be able to communicate with the VM.  This code went into
the Standard VM, after a while, so you could indeed use the plugin with
Ian's VM.

Then, I completely rewrote the Plugin/VM interface, but that code did not
make it into the Standard VM, yet:

	http://swiki.gsug.org/sqfixes/1341.html

And that's where we are right now ...

-- Bert

>
>
> > >On Monday 29 October 2001 08:04 pm, John Hinsley wrote:
> > >>  Trying to save project as file with one of the Squeakland projects I
> > get
> > >>  "space is low...."
> > >>
> > >>  kdf shows I've got 1.6Gb free! OK, so 90% is flying by the seat of the
> > >>  pants on Linux, but 82.3% full?
> > >>
> > >>  So where, exactly, is the space low? And how can I grow it?
> > >
> > >Unfortunately, the default memory maximum for Squeak is 20 megabytes.
> > This
> > >isn't enough for many uses. It's better to specify a larger value with
> > the
> > >-memory flag. However, I'm not sure how to do this with the plugin.
> > >
> > >--
> > >Ned Konz
> > >currently: Stanwood, WA
> > >email:     ned at bike-nomad.com
> > >homepage:  http://bike-nomad.com
> >
> > Well the macintosh plugin takes these values
> >
> > At 1:22 PM -0700 9/27/00, John M McIntosh wrote:
> > >memory="+5"   //Allocate 5MB more than image size
> > >memory="*1.5" //Allocate 1.5 times image size
> > >memory="15"  //Allocate 15MB
> > >
> > >also
> > >memory="15000000" give 15 million bytes
> > >
> > >Other more exotic things like
> > memory="*2.0+15"  should also work (2x image size + 15MB)
> >
> > But if you specified just memory=20 that's only 20mb, maybe you need
> > memory="+10" or something (ie 10mb free head room).
> >
> > Of course this all depends on if the Linux plugin which I'm assuming
> > you are talking about actually does anything meaningful with the
> > memory tag.
> >
> > Andreas gave me the original code to parse the tag, so I'm assuming
> > the windows version handles it correctly.
> >
> > --
> > --
> >
> ===========================================================================
> > John M. McIntosh <johnmci at smalltalkconsulting.com> 1-800-477-2659
> > Corporate Smalltalk Consulting Ltd.  http://www.smalltalkconsulting.com
> >
> ===========================================================================
> >
> >
>
>
>