Where do you want the Example tab?
There exist a raw support for examples for each class, but it is not announced yet because it is still a work in progress.
About the view presentation: Keep in mind that we are talking about the inspector which is the most basic of all tools (I know it's hard to believe it is a basic tool :)). That is why defaults have to be handled carefully because the tool is supposed to handle a large amount of use cases.
However, now you have two mechanisms that can help with your problem:
1.
a. You execute your script once.
b. Switch to the View presentation
c. Modify and execute again
d. You will get the View presentation
So, in the end, we get only one extra click (step b.). I think this is a good compromise for now.
2.
Actually, the View presentation is an extension that you can define yourself.
gtInspectorViewIn: composite
<gtInspectorPresentationOrder: 30>
composite roassal2
title: 'View';
initializeView: [ self ]
The order of the tabs is defined by the number from the pragma. You can try adding it first, but then it would not be as in the default case for all other objects. We need to experiment with this for a while to figure out the best approach.
For example, when debugging a faulty view, you precisely do not want to view, but might want a presentation that shows the structure of elements without rendering the view. That is why at the moment, the default is the State of the object and the idea is to make mechanism 1 a bit more powerful so that you can mold the environment to the actual context.
Doru
Cheers,
Doru