I am trying to wrap my mind around PluggableTextMorph and its internals.

I am using the latest 1.4, where there has been some cleanup done (yay!)

So, PluggableTextMorph, TextMorphForEditView, Text, Paragraph, TextComposer, CharacterScanner, Stylers (in Shout), TextAttributes etc.

I need to understand this for my little game based on text and attributes (there is nothing like a 'real' project to cut my teeth on a myriad of issues).

I wondered if I could make use of Moose for that.

There are things like in setText that use the textMorphClass instance variable and I am not sure I can get structural information from parametrized selectors and classnames done that way.

Would Moose be helpful there? Or am I better doing a Debug It (like I am doing now) and drawing Class and Interaction diagrams ?

Truth be told I am a VAR of Sparx Enterprise Architect (and heavy user). Maybe is it possible to have a bridge between Pharo and Sparx EA to get some documentation done easily. I can import metadata through scripting. So, remixing FAMIX/Moose/Pharo and some investigations may end up providing some nice figures to help with PBE2.

So, tell me what you think and/or where I should go.

There are no reverse engineering tools for pharo but these should be easy to build for a ton of things. Has anybody done an XMI exporter for Pharo classes?

Phil