Hi Doru, all, thanks for the hint. I searched around some and hacked up a solution. I leave it below for posterity. After remembering all the flak that Spec got for how hard it is to understand and configure and complexity that seems spurious, I am a bit saddened to find that GT also can be accused of these things. It was much harder for me than I expected to, to get to the bits of code below. In general, I still have no clue how all these presentation things and renderers actually work together, and in specific there is a double dispatch using e.g. renderPharoMethodPresentation: or renderPharoScriptPresentation: that I don't understand its reason for existence. Whatever>>gtInspectorSourceFragmentIn: composite <gtInspectorPresentationOrder: -2> ^(composite custom: RCFixedTextPresentation new) title: 'Fixed width'; display: [asdf] GLMRubricTextPresentation subclass: #RCFixedTextPresentation instanceVariableNames: '' classVariableNames: '' package: 'XXX' RCFixedTextPresentation >>renderGlamorouslyOn: aRenderer self registerAnnouncements. ^ RCFixedTextRenderer render: self from: aRenderer GLMMorphicRubricTextRenderer subclass: #RCFixedTextRenderer instanceVariableNames: '' classVariableNames: '' package: 'XXX' RCFixedTextRenderer>>render: aPresentation | result | result := super render: aPresentation. result textFont: StandardFonts codeFont. ^result -- Johan Fabry, Senior Software Engineer.  johan(a)raincode.com | Email too brief? Here's why! http://emailcharter.org