2015-04-09 13:16 GMT+03:00 Nicolai Hess <nicolaihess@web.de>:

There are methods named #exampleXXX that
- "open" something (the UI-Widget examples for example open a widget/window/dialog ...)
- create an instance for the object class this method is defined (see all methods tagged with pragma <gtExample>

��
And what concrete tool you try to implement?
The little "play-icon" in Nautilus currently depends on the method name, if it is named #exapleXXX, treat
it as example method that *opens something*
GTInspector provides a "instance example" (E.g.)-tab. You can see a list of example methods that *create instances* (and inspect them)

I'm not see problem here. Tab should be named "examples". And when user select example which open some morph it is normal expected behaviour. And when selected example return instance of selected class it can be handled as specific case. And when selected example open morph and returned it user will see it and explore it at same time which is good feature to me.

��

��

If it is special "examples" tab when inpecting/browsing classes why it should be restricted to working only with instances of given class?

If it *opens* a window/ a Morph or anything else, this is a side-effect the glamour team don't want, because they intend to use this example-instance-creation for other
things as well (for example: automatic testing).

Agree, if you want to process group of examples you should distinguish examples which only provide instances without side effects