Hi, I am happy to see the concept of an example method catching attention again.
As explained before, the GTExample was already present in the Pharo image, but it was introduced more as a helper for testing GT extensions. Now, I just created an issue for removing GTExamples from the GT-Inspector package and from the main Pharo image: https://pharo.fogbugz.com/f/cases/18965/Remove-GTExample-from-the-GT-Inspector-package Cheers, Doru > On Aug 18, 2016, at 10:45 PM, Denis Kudriashov <dionisi...@gmail.com> wrote: > > > 2016-08-18 19:50 GMT+02:00 stepharo <steph...@free.fr>: >> Hi >> >> Why not use <example> pragma in the way you propose for <examplar>? Why we >> need two? > > Apparently from the old discussion, people like <example> to prompt and open > the example > when this is something visual. This is ok for me. > > Ok, let's distinguish them. Scripts are scripts (maybe <script> is better > name than <example>?) > > I thought that we don't need two options because in practice <example> only > opens morph or inspector. And for morphs we already have morph tab in > inspector. So morph examples could be easily converted to <examplar> without > any loss. > > In my proposal we can get the best of both worlds. > - instance to use in tests > - instance to learn and tweak with GTInspector > - examples that we can see opening. > > -- www.tudorgirba.com www.feenk.com "Every thing should have the right to be different."
