Thanks for raising this :). I now added a simple implementation in the GTInspector to have Pointers available for all objects. Perhaps it is overdoing it to have it by default on all objects, but it was cheap to implement in a crude way. I still do not eliminate all inspector related objects that point to the current object, but it's a start (see attached the pointers to Smalltalk). Object>>gtInspectorPointersIn: composite <gtInspectorPresentationOrder: 20> composite list title: 'Pointers'; display: [ (self pointersToExcept: { self }) reject: [ :each | each pointsOnlyWeaklyTo: self ] ]; format: [ :each | GTObjectPrinter new asTruncatedTextFrom: each ]; showOnly: 50 [image: Inline image 1] Cheers, Doru On Wed, Dec 25, 2013 at 12:04 PM, Marcus Denker <marcus.denker@inria.fr>wrote:

On 21 Dec 2013, at 15:03, Sven Van Caekenberghe <sven@stfx.eu> wrote:

...

Hi,

It seems that #explorerContents and #hasContentsInExplorer are no longer used.

Implementing a new Eye inspector with #addSpecialFields: seems to affect both the Inspector view as well as the Tree Inspector.

So, should they be removed ?

Yes, but we need to first find a solution for the Pointer Explorer: right now this is a subclass of the old Explorere, therefore this is still in the image.

https://pharo.fogbugz.com/f/cases/11709/remove-old-ObjectExplorer

Marcus

-- www.tudorgirba.com "Every thing has its own flow"

I know. This is why I am arguing that we should make the optional tools not optional. It would be a more profitable approach :). Cheers, Doru On Mon, Dec 30, 2013 at 11:02 AM, Marcus Denker <marcus.denker@inria.fr>wrote:

On 28 Dec 2013, at 13:36, Tudor Girba <tudor@tudorgirba.com> wrote:

...

Thanks for raising this :).

I now added a simple implementation in the GTInspector to have Pointers available for all objects. Perhaps it is overdoing it to have it by default on all objects, but it was cheap to implement in a crude way. I still do not eliminate all inspector related objects that point to the current object, but it's a start (see attached the pointers to Smalltalk).

If the inspector that is in Pharo gets a solution for pointers, then we can directly clean up a lot of old code. With this being done for tools that are just loadable optionally —> we still have to keep the old code of the Explorer around.

Marcus

-- www.tudorgirba.com "Every thing has its own flow"