Hi, I see where the issue comes from.
The <gtExample> are like test methods that return an object. That object serves as example, but it is not necessarily a user facing object. Look at the picture below showing BlDragExamples>>#draggableInParent. BlDragExamples>>#draggableInParent calls several other methods that are marked as <gtExample>. In the second pane in the inspector you can see these inner methods being unfolded. These examples show how to setup the inner part, and how the pieces fit together. In this case, the outmost example is indeed an element that can be played with (you see it here on the third pane), but the inner objects can be as interesting through the various custom views. This way of working replaces testing and bridges the gap with documentation. You can learn about it here: https://medium.com/@Chis_Andrei/exemplifying-software-fd39a420472a Or if you load the full GToolkit, you can follow tutorials live in the environment by inspecting: GtInspector openOn: (GtDocumenter editorForPillar: (IceRepository repositoriesLocation / 'feenkcom'/ 'gtoolkit-examples' / 'doc' / 'tutorial' / 'examples-tutorial.pillar’)) Cheers, Doru > On Sep 16, 2018, at 11:08 AM, Hilaire <hila...@drgeo.eu> wrote: > > Le 16/09/2018 à 08:00, Tudor Girba a écrit : >> The examples are found in methods annotated with <gtExample>. What do you >> mean that "Several examples are not actionable”? Could you provide examples >> of that to find out what the problem is? > > For examples, in those classes I don't know what to do: > * > *BlDragExamples or in categories, Bloc-Example>Events > > These are code you can read, but no clue what to do with it. > No actionable examples to experiment with to visualize, to edit the code > in live to learn how this work, etc. > It looks like the same for most examples. > > Hilaire > > -- > Dr. Geo > http://drgeo.eu > > > -- www.feenk.com "We can create beautiful models in a vacuum. But, to get them effective we have to deal with the inconvenience of reality."
