I have mentioned this before, but EyeCollectionInspector is actually written against SequenceableCollection since it expects ordered external integer indexing. That is why currently every Collection subclass without this protocol and/or without a custom inspector fails. The alternative would be to move Collection class>>#inspectorClass to SequenceableCollection>>#inspectorClass. Then Collection subclasses that are not SequenceableCollection and that do not have a custom inspector will fail. Note that fail means a fall back to EyeBasicInspector. On 25 Jul 2014, at 12:32, Stephan Eggermont <stephan@stack.nl> wrote:
I took a look at what would be needed to port the Cuis Trie to Pharo. Trie is a subclass of Collection, and expects at: aKey, not at: anIndex. That breaks the EyeInspector view. What interface expects the explorer a Collection subclass to have?
Stephan