On Fri, 23 May 2003 12:20:49 +1200 (NZST), Richard A. O'Keefe wrote
> I note that it is perfectly possible to embed a Morph into a Workspace.
> (Drag the Morph over to the Workspace, drop it where you want it,
> halo menu "embed into" PluggableTextMorph.)
> 
> Unfortunately, the text doesn't know about such embedded morphs,
> and just flows on underneath them.
> 
> But suppose that
> (1) PluggableTextMorphs treated embedded Morphs as characters, much
>     the way that TeX treats pictures as characters, and
> (2) the compiler treated such a character as an expression, and
> (3) the value of such an expression was the identity of the Morph
>     (so that a Morph would be just another kind of constant).
> 
> Then you could have
>     {frog picture} copy; openInWorld; startHopping
> 
> Sort of like "create textual references to dropped morphs" but
> without the text.
> 
> Of course, this would create problems for ChangeSets...

...certainly, and therefore it is a problem from my viewpoint also. we do not 
work with objects, but text in most cases - but i would like to work with 
objects.