how can I make a thing that can be run?

goran at krampe.se goran at krampe.se
Thu Feb 16 23:03:27 UTC 2006


Kendall Shaw <queshaw at pacbell.net> wrote:
> Corneanu Dan wrote:
> > Hmmm, I'm not sure I get your question right but I think you're doing a
> > confusion.
> 
> The part about the Project class looks like it is an answer to the 
> question I was trying to ask. An application would be a serialized 
> Project. So, for example, Hello world would be a project displaying 
> hello world, opened in a world.
> 
> Kendall

There are numerous ways to deliver squeak "apps" or code. Project files
are used primarily for eToys or "demos" of code.
Most projects in the Squeak community are delivered in source form
instead, using a variety of file formats:

	.st (or .st.gz compressed) - the good old fileout of code. Not used
much anymore.
	.cs (or .cs.gz compressed) - changesets. They are like patches from the
regular world, quite nifty but can be confusing.
	.mcz - Monticello package. This is the "standard" today and is what
most people use. The file is a zip file with source in it, in a special
format to be loaded by Monticello.
	.sar - This is also a zip file with a code snippet inside for
performing the install of the rest of the contents. .mcz files only
contain code so a .sar file can be used as a wrapper in order to include
other kinds of files too.

Well, there you go. There are some other forms too, but here is my
recommendation:

	- For a simple standalone class or a couple of classes, use .st if you
really don't have time to learn something else. Just use the "fileout"
menu choices in the standard browser (on a class or a class category).
	- Use project files for eToys or "demos".
	- Use .cs files (changesets) for small bug fixes etc. It has been
customary for quite some time.
	- Use .mcz files for delivering your package. In short - learn how to
use Monticello.
	- Use a .sar file if you somehow need to complement your .mcz files
with other kinds of files like .gif files etc.

And to put something on SM - just get an account, produce a file of any
of the above formats, upload it using the web UI and create a package
and a release of it. Done.

regards, Göran



More information about the Squeak-dev mailing list