I just realized the update Andreas described yesterday hits one of these 
points directly, and others indirectly.
He wrote:
> New Text Editors
> ----------------
> A complete new set of text editors (Editor, TextEditor and 
> SmalltalkEditor) are available. They replace TextMorphEditor and break 
> one of the last hard links between Morphic and MVC. With the new 
> editors it will finally become possible to have Morphic be 
> self-contained without the need to rely on portions of MVC. 
Ross Boylan wrote:
> .....
> * TextMorphEditor is a subclass of ParagraphEditor, an ST80 remnant.
> ....
> TextMorph's have many of the same features: there is a separate editor 
> object, and they end up using ST80 code.
>
> This was in a 3.10 image.
3.10.1, more precisely, since the changes are in 3.10.2
>
> So, are there reasons for this division of labor, or did they simply 
> evolve trying to build new functionality on top of old functionality?  
> My understanding of the morphic spirit led me to expect that the basic 
> objects, StringMorph and TextMorph, would be handling the user 
> interaction much more directly.  
As I understand it, the new code handles everything in morphic, but 
still uses helper objects.  That is, it does not handle the editing 
within the original morph.
> What I see has more of an MVC flavor, though it's more complicated 
> than that.
MVC there was a reference to the approach, so eliminating the ST80 
remnant doesn't necessarily change anything.

Ross