"Andreas Raab" <andreas.raab at gmx.de> wrote:
> Starting a remote image isn't that hard - anything that'll listen on the
> right port and know how to identify the location of the image for the
> particular client would work. For example, the client could make a request
> to some "Nebraska launcher" which would handle the request by launching the
> appropriate image and hand back the port to use for this particular nebraska
> session. This could even be done by adding this functionality to a
> SuperSwiki so that you can browse through the projects, click on one, and
> once clicked it will run on the (remote) server with a (local) Nebraska
> client.


You're right, it's easy, though you do have to wire it together yourself
a bit.

I personally use a Unix shell as the "Nebraska launcher".  For example,
I have a file with this content:

	Utilities authorName: 'lex'.
	NebraskaServerMorph serveWorld: World

Then I start squeak like this:

	squeak -headless server.image  server.st

And on my local machine I type:

	NetworkTerminalMorph openAndConnectTo: 'server.name'


You have to set the author name, because otherwise the nebraska server
will sometimes ask for it with a pop up dialog.  Overall, it's not the
smoothest setup, but it does work.

Oh, and as Andreas said, it currently only works for basic 2D
interactions; it doesn't handle sound, video, or 3D graphics.  Each of
these would take some doing.

-Lex