In experimenting with creating a custom inspector for my domain object, I came across the following intriguing method:
Float>>#gtInspectorFloatIn: composite
<gtInspectorPresentationOrder: 30>
^ composite table
title: 'Float';
display: [
...
{'binary' -> self binaryLiteralString.
'significand' -> self significand.
'exponent' -> self exponent} ];
column: 'Key' evaluated: #key;
column: 'Value' evaluated: #value;
send: #value
While it was easy enough to adapt this to my needs, I found the #display: and #send: sends quite strange. #display: seems like a strange API - like we're using an object designed to do something other than inspect objects; and I wasn't sure what exactly #send: did, my presentation seemed to function the same way with or without it...
Cheers,
Sean