forums.jakob at resfarm.de
Sun Jun 3 22:15:51 UTC 2018
PluggableTextMorph is the MorphicToolBuilder variant of MVC's
PluggableTextView, whereas I assume TextMorph is the original Morphic thing
ported from Self. The purpose of the latter is to display text in Morphic
and the purpose of the former is to display (and edit) text in tools. The
pluggable morph contains a "non-pluggable" one. So, to me it looks like
these two should not be confused, regarding #isTextMorph and #isTextView.
Regarding PluggableTextMorphPlus and the fact that PluggableTextMorph does
not have a class comment, Tim might have a point. The Plus class does have
a comment: "A pluggable text morph with support for color." But since any
(Pluggable)TextMorph also supports colored text somehow, this explanation
is a little too brief. It adds support for accessing the color from the
model and adds the optional text styler for syntax highlighting. ...and an
acceptAction, but this is definitely not captured in the class comment.
Anyway, PluggableTextMorph*Plus* is what MorphicToolBuilder builds when you
ask for a pluggable text, be it for code or plain text.
It is unfortunate that MVC (or anything else) does not benefit from text
styling (or any further customization, such as spell checker marks) this
way, although Text and its color support are not specific to Morphic.
tim Rowledge <tim at rowledge.org> schrieb am So., 3. Juni 2018, 22:31:
> A bigger and more interesting question is why on earth we have three
> distinct classes. I suspect unfinished experiments that got glommed into
> the system without adequate thought and left there because nobody knows
> what the hell was really intended.
> tim Rowledge; tim at rowledge.org; http://www.rowledge.org/tim
> Earth is 98% full...please delete anyone you can.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Squeak-dev