-----Original Message-----
From:	Richard Smol [SMTP:jazzcat at dds.nl]
Sent:	Tuesday, January 20, 1998 11:07 AM
To:	squeak at cs.uiuc.edu
Subject:	Re: ideas for Squeak projects

Having a not-so-portable Squeak OS doesn't mean that Squeak
programs or images won't be portable anymore.

[Serg Koren]
The point is the more non-portable the Squeak VM is the greater the chance 
that the code it generates/interprets becomes non-portable...for instance 
if you start writing Windows API code directly in Squeak THAT code is no 
longer portable unless the infrastructure it's built on allows for 
portablility. Have common Squeak/Smalltalk hooks into the API so that the 
backend/platform specific code can be unplugged and replaced without 
altering the portability of the Squeak code.


And I still haven't gotten any response as to what the OFFICIAL versions of 
Squeak on the various platforms are and who is charge of them, and what the 
process is on creating/submitting code into it.



Right now, Squeak is the project of a lot of seperately working
individuals, adding more and more classes to the system. This is okay,
but for bigger projects (like Squeak Music) a more cooperative effort
would be desirable >:)

[Serg Koren]
Again my point....who coordinates everything?  Who decides which of  two 
versions of two classes that do the same thing gets rolled into a version? 
 It sounds like you're saying it's a free-for-all and there is no single 
point of contact for managing the different changes that are made and 
released.
Chaos rules!

S