and contexts, then why not provide for Squeak VM's to optionally open new projects in their own windows?  

For non-windowing systems, this would simply default to the status quo effect of rewriting the existing Display, but for modern windowing systems, this could have the effect that many have been agitating for -- a meaningfully machine-independent approach to building real multiwindowing systems, leaving Morphic to do each window's context in turn.  

Context shifting could be a consequence of Window selection/deselection (or whatever the native GUI taxonomy calls it), and two worlds can meet, but in a decidedly Smalltalk and uniquely Squeaky fashion.

An interesting sidebar to this is that independent project contexts neglects the possibility that these contexts may well want to communicate one with another.  Of course, this can be accomplished through existing shared resources, such as files and databases, but perhaps some more robust notion of piping or communicating information between projects (and perhaps betwen images) should be designed in at the front end?  Perhaps two worlds may really want to share some information in the sense they are shared in the status quo?  Is there a more powerful abstraction that captures all these notions?

Just another view.

Best,
A

------------------------------------------------------------------------
Andrew C. Greenberg  	(813) 223-7000 x 209
Carlton Fields		(813) 229-4133 (fax)
777 S. Harbour Island Blvd.
Tampa, Florida		agree at carltonfields.com

Nothing herein is intended to be a signature or other authentication.