> You could use SqueakMap:
> -- register your changesets with SqueakMap
> -- register your project with SqueakMap
> -- create a "load script" that loads the changesets, then the project,
> and register the load script on SqueakMap 
> 
> Then just refer people to the load script. ...

Err... honestly that doesn't quite count as "simple" for me.

Jeff, if you have change sets installed which are required by your project
just make sure all the changes are included in the project itself - when you
publish that project you will be asked whether to include the changes (say
yes of course ;-)

If you are going to require the changes by a number of projects you may want
to provide the CS at a separate location and just add something like this to
the project's preamble:

	"make sure we're compatible with 3.6 and possibly later"
	((Smalltalk at: #HTTPClient ifAbsent:[HTTPSocket])
		httpGet: 'http://myHost.com/myChanges/myCS.cs') fileIn.

This will load the changes from some other than the default location (and be
compatible with Squeak prior 3.6 which the SqueakMap version is not). If you
don't care about older versions you can use SqueakMap and add something like

	SMSqueakMap default loadPackageWithID: 'xxxx-yyyy-zzzz-...'

(not sure if the above is correct - someone correct me). The advantage of
this is that the changes only get loaded once (in the http-get example we'd
load the changes every time you open one of the project referring to them)
but it's not compatible with any Squeak prior to 3.6 (which includes the
Squeakland plugin image).

Cheers,
  - Andreas

> -----Original Message-----
> From: squeak-dev-bounces at lists.squeakfoundation.org 
> [mailto:squeak-dev-bounces at lists.squeakfoundation.org] On 
> Behalf Of Brent Vukmer
> Sent: Tuesday, July 15, 2003 10:08 PM
> To: The general-purpose Squeak developers list
> Subject: RE: Distributing Squeak Projects
> 
> 
> 
> > 
> > 
> > Hello,
> > 
> > I'm sure this is a bit of a newbie question, but as I'm 
> > finishing up my first projects I'm beginning to think about 
> > publishing my Squeak projects to the web.  I've already 
> > created a website where I'll post my projects, but I'd like 
> > to make the loading of the projects as easy as possible for 
> > non-squeakers.  Could someone point me in the direction of 
> > resources for publishing Squeak projects?  I'm aware of the 
> > plug-ins available from squeak.org and squeakland, but will 
> > any changesets I've installed be in place when using the 
> > plug-ins?  I've also read that one can strip down the Squeak 
> > image to what's required, and then have the plug-in load that 
> > image? I'm a little confused as to what I need to do to make 
> > my projects easily-accessible to non-squeakers - helpful 
> > resources anyone?
> > 
> > Thanks,
> > Jeff
> > 
> 
> You could use SqueakMap:
> -- register your changesets with SqueakMap
> -- register your project with SqueakMap
> -- create a "load script" that loads the changesets, then the project,
> and register the load script on SqueakMap 
> 
> Then just refer people to the load script. ...
> 
>