Decouple the code for explore(obj) and explore() ?

[nthiery]

The layout of the widgets for explore() and explore(obj) may become relatively different. Maybe we would want to split the code accordingly into two classes? Or is there a lot shared between the two?

[zerline]

I agree, they may become rather different. There is still a lot to be shared: the display structure (unless we want it more different than now). And a few methods. A possibility could be to write a base class (XYZExplorer), then make 2 classes ObjectExplorer and ExplorerIndex (or any names) inherit from the base class.

[nthiery]

I agree, they may become rather different. There is still a lot to be shared: the display structure (unless we want it more different than now). And a few methods.

And the history management.

A possibility could be to write a base class (XYZExplorer), then make 2 classes ObjectExplorer and ExplorerIndex (or any names) inherit from the base class.

+1 It could be: - Explorer - ObjectExplorer - SageExplorer No rush though, unless this is of immediate help to maintain / extend the code.

[zerline]

It will be ..

[zerline]

With a4c38c5, we decided to use the same display for now.
In the future, we would like to display, for a catalog, all its values as a table with name, icon, description and args box in case args are required.