Stefan Matthias Aust wrote:
 
> Actually, separating controller and view isn't that useful, but separating
> the model is.  

	Just now I noticed that this is what MorphicWrappers started for: to
supply a [generic then specific] view-controller for every/any object-model in
Squeak... And I think they'r good at it.
	Historical note (not so historical): When we started the MathMorphs
course, we created some mathematical objects, and then we wanted them to show
up in a morphic World, our first approach was to make Polynomial to be a
subclass of Morph, but, after some (not much) time, it started to sound
ridiculous, so we moved Polynomial to some better place, and created a wrapper 
for it, realizing that such a wrapper could be used to place any object in a
morphic World. After this, we ended up with a lot of objects living in our
World, and then, we wanted to interact with them. It was straight forward to
add support for menus showing every message that could be sent to this
objects, after this we needed the ability to supply arguments for this
messages, so we gave it the ability to receive dropped morphs.
	But it was not easy to place new morphs/objects in the world, so
we tried several different aproaches: first, we used a little workspace where
everything you wrote in it got added to the World, we didn't liked it too
much, because there were to different context, the Workspaces context and the
morphic context... finally we found this type-in-the-air stuff, that is really
direct. And it's a closer aproach to real-world object handling.

	That's it.

	thanks

	Modeled Bye!
	Richie++

--- For a personal reply use gera at core-sdi.com