Removing Morphic

Michael Latta lattam at
Sat Oct 21 06:39:29 UTC 2006

You can drag a morph assembly into a palette and then when you drag it back
out you create a clone of the assembly.  I think the reason most people use
code to create assemblies is that the tools make reuse of a class easier
than reuse of instances.  If you take a look at the Self system where
instances have a more first-class role in the tooling it works a bit better
(which is where Morphic was invented).






From: squeak-dev-bounces at
[mailto:squeak-dev-bounces at] On Behalf Of Todd
Sent: Friday, October 20, 2006 11:09 PM
To: The general-purpose Squeak developers list
Subject: Re: Removing Morphic


There's something fundamental missing from Morphic WRT direct manipulation.
You can put together assemblies of morphs, but using them as a template for
created duplicate assemblies is lacking (or I never discovered the nifty
technique that lets me freeze-dry a morph and reanimate it on demand ala
NextStep's InterfaceBuilder). 


Nobody builds morphic UI using direct manipulation because it doesn't fully
support it.


On Oct 20, 2006, at 12:46 PM, karl wrote:

Morphic is a direct manipulation framework. I Self you program the morphs as
you go, instance based, kind of like building your program in the Inspector.
This is not implemented the same way in Squeak. Morphic in Squeak is mostly
programmed through classes, but you can still manipulate the Morphs directly
in very cool way. Pull things apart etc.


-------------- next part --------------
An HTML attachment was scrubbed...

More information about the Squeak-dev mailing list